SSD Won't Boot to Win 10 if Manually Selected in BIOS (ACHI driver error?)

Apr 8, 2018
4
0
20
I bought a new SSD and recently installed Windows 10 on it via a USB flash drive. I realized my old SSD (running Windows 7) and motherboard were running in IDE mode, so I switched to ACHI (after editing the registry to load ACHI drivers). The new SSD wouldn't boot (it would get stuck at "Loading Operating system", Insert CD/DVD; DISK BOOT FAILURE)

So I reformatted the new SSD and reinstalled Windows 10. Now it boots if I configure my BIOS to make it my first boot device. But if I press F12 during BIOS loadup and manually select the new SSD I get the same boot error I had when I first installed it via IDE.

It's not a *huge* issue, but I would really like to be able to solve this problem. It seems like manually selecting the drive results in ACHI drivers not being loaded. What can I do to fix this?
 
Solution
Ok... well in case anyone reading this in the future cares... I figured it out. I just had to disconnect my other SSD while reinstalling Windows 10 on the new one. During install I deleted the partition and reinstalled it clean, and now W10 boots up whether I manually select the new SSD or not. I guess for some reason Win 10 was installing ACHI drivers onto the old SSD...? I don't know... sounds ridiculous but whatever. As long as it's working.
Apr 8, 2018
4
0
20


I already wrote "so I switched to ACHI (after editing the registry to load ACHI drivers)". I know there's a different process for Windows 7 vs 10. I did it for both SSDs.

I can even boot from the new drive when it's ordered as "first boot device" in my BIOS and I just let the BIOS post normally. My issue is that when I choose "boot menu" in the BIOS and manually select the drive, it won't boot. As if manually selecting the drive results in ACHI drivers not being loaded. What is the cause of this? And how do I fix it?
 
dual boot windows 7 on one drive and windows 10 on another drive?
you might want to look at http://neosmart.net/EasyBCD/
keep track of the boot loaders.

I no longer dual boot. I use either a sata III hot swap caddy and swap in a physical drive or I run a virtual machine to load the older os. something like this: https://www.newegg.com/Product/Product.aspx?Item=9SIA1GK6ME4033&cm_re=3.5_hot_swap_caddy-_-9SIA1GK6ME4033-_-Product

just to avoid boot loaders from being installed on the wrong drive, and drive letters from getting reassigned on me.
I use a dual caddy so I can use a separate data drive.



 
Apr 8, 2018
4
0
20

"just to avoid boot loaders from being installed on the wrong drive"
Can this actually happen? Why would my new SSD boot fine on normal startup but have an error when I select it manually?
 
Apr 8, 2018
4
0
20
Ok... well in case anyone reading this in the future cares... I figured it out. I just had to disconnect my other SSD while reinstalling Windows 10 on the new one. During install I deleted the partition and reinstalled it clean, and now W10 boots up whether I manually select the new SSD or not. I guess for some reason Win 10 was installing ACHI drivers onto the old SSD...? I don't know... sounds ridiculous but whatever. As long as it's working.
 
Solution
boot loaders are installed on a reserve partition on only one of the drives. generally these are small partitions that are not normally assigned a driver letter.