Windows 10 cannot get recovery disk to install fresh windows version, get set back through BIOS endlessly

  • Thread starter Thread starter JadeWingDragon
  • Start date Start date
J

JadeWingDragon

I'm trying to migrate Windows from an SSD (120GB) to a new larger SSD (1TB). The internet is of course full of ways to do this, and I originally tried cloning the drive (via easeUS and similar tools), but all gave me one error or another. I decided that I was okay with a clean install if it got rid of the gremlins, since any vaguely important files were either on a separate HDD and/or on the cloud. I learned from posts like this that Windows should be smart enough to recognize the hardware if I'm just switching the boot drive, so I created a recovery disk (I don't have a handy spare USB) and disconnected everything but the BD/DVD drive and the new SSD. After booting successfully from the Recovery Disk, I get to the expected screen like this:





However, when I hit "Next", it goes back through the BIOS splash screen and tries to boot the computer like normal, which of course doesn't work since the bootable drive isn't there. This happens with two separate recovery disks, both created by and for this computer, one made today and another made maybe 1.5 years ago that was previously used successfully to do a clean install.


Furthermore, if I'm not fast enough to get into the boot options, and it tries to boot from the (new) drive, I get this:




I'm not really sure what this screen means, and hitting either F1 and F8 are exercises in frustration neither do anything.


Other things I've tried:

- Using the SATA port (and cable, separately and simultaneously) used by the old SSD to see if something didn't like the SATA port the new drive is installed on for some reason, but the same thing happens

-Disabling CSM in BIOS (I honestly don't know what this does, but another thread had a somewhat similar issue and this was one thing they said to try) The computer won't see any drives with CSM disabled, just has old boot options from when I experimented with Linux Ubuntu and Mint (side question: how do I get rid of these?)


When the computer is properly connected it has no issue recognizing the drive, so I don't think the drive itself is bad.


Please help. I fully admit to having just enough technical knowledge and google-fu to get me in trouble, and something I tried could've made the situation worse than it would have otherwise been, but I'd really like to have more room on my C: drive.


System info, if needed:

Gigabyte GA-Z77X-D3H

Intel i5-3570K

NVIDIA GTX960 (other note: this is a relatively new (<1 month) hardware change/upgrade from an older graphics card. I don't know if this has any effect)

32GB RAM

Blu-ray read/write drive

Storage:
Kingston HyperX 120GB SSD --current C: drive

Crucial MX300 1050GB SSD --new drive

Seagate Barracuda 500GB and 3TB HDDs --for user files

Continue reading...
 
Back
Top