F5F Stay Refreshed Hardware Desktop Problem with PC failing to boot Windows after switching to a secondary drive.

Problem with PC failing to boot Windows after switching to a secondary drive.

Problem with PC failing to boot Windows after switching to a secondary drive.

S
SmileyFishMC
Member
60
02-04-2016, 06:20 PM
#1
So i just swapped a hard drive from my PC—not the Windows OS drive—but before I bought an SSD, my Windows was on that SSD. After the switch, Windows won’t boot and I can only access BIOS. The SSD is recognized, but Windows isn’t detected because when I set it to UEFI - Legacy and chose it as the boot drive, it shows a message like “no bootable drive detected connect” or “restart/try again.” However, when I plug in my old original drive, Windows boots normally. It also shows a blue screen with three options: “Windows I have 3 drives in my PC,” and two of them display Windows while the other restarts the PC. Windows 1 is the SSD, and Windows 10 is the original drive. I recently reinstalled Windows on the SSD too. I’m confused about this situation and wondering if it’s related to dual boot setup or something else. Can I fix it without reinstalling Windows again?
S
SmileyFishMC
02-04-2016, 06:20 PM #1

So i just swapped a hard drive from my PC—not the Windows OS drive—but before I bought an SSD, my Windows was on that SSD. After the switch, Windows won’t boot and I can only access BIOS. The SSD is recognized, but Windows isn’t detected because when I set it to UEFI - Legacy and chose it as the boot drive, it shows a message like “no bootable drive detected connect” or “restart/try again.” However, when I plug in my old original drive, Windows boots normally. It also shows a blue screen with three options: “Windows I have 3 drives in my PC,” and two of them display Windows while the other restarts the PC. Windows 1 is the SSD, and Windows 10 is the original drive. I recently reinstalled Windows on the SSD too. I’m confused about this situation and wondering if it’s related to dual boot setup or something else. Can I fix it without reinstalling Windows again?

D
DeathbatAttack
Junior Member
6
02-05-2016, 03:07 AM
#2
It seems the EFI boot partition on your other drive was probably detected by the Windows installer during installation on your new drive, preventing a separate one from being created. After removal, Windows doesn’t know how to start. This explains why it’s advised to clear all other drives during installation—likely you’ll need a fresh setup again, using only the drive you’re installing Windows onto and the USB flash drive for installation, which is common now.

Once the issue is fixed, using a partition manager such as Paragon Partition Manager Community Edition can help remove any hidden Windows partitions left on the old drive. This ensures Windows doesn’t present conflicting boot options when both drives are connected, avoiding potential problems or slow startup after the fix.
D
DeathbatAttack
02-05-2016, 03:07 AM #2

It seems the EFI boot partition on your other drive was probably detected by the Windows installer during installation on your new drive, preventing a separate one from being created. After removal, Windows doesn’t know how to start. This explains why it’s advised to clear all other drives during installation—likely you’ll need a fresh setup again, using only the drive you’re installing Windows onto and the USB flash drive for installation, which is common now.

Once the issue is fixed, using a partition manager such as Paragon Partition Manager Community Edition can help remove any hidden Windows partitions left on the old drive. This ensures Windows doesn’t present conflicting boot options when both drives are connected, avoiding potential problems or slow startup after the fix.

E
57
02-05-2016, 11:56 PM
#3
I thought that too, thanks for the clarification. I'll likely just transfer the files to another drive in the meantime, since I'm planning to buy a new 2TB M.2 NVMe SSD soon and will do a clean reinstall then.
E
endergirlsarah
02-05-2016, 11:56 PM #3

I thought that too, thanks for the clarification. I'll likely just transfer the files to another drive in the meantime, since I'm planning to buy a new 2TB M.2 NVMe SSD soon and will do a clean reinstall then.

J
joaonazar8
Junior Member
5
02-07-2016, 02:33 AM
#4
Good luck to you.
J
joaonazar8
02-07-2016, 02:33 AM #4

Good luck to you.

B
BOTPanax
Member
52
02-08-2016, 05:30 PM
#5
I duplicated the system 118mb partitions and everything functions flawlessly.
B
BOTPanax
02-08-2016, 05:30 PM #5

I duplicated the system 118mb partitions and everything functions flawlessly.

I
iNaomiPlays
Senior Member
609
02-09-2016, 06:17 PM
#6
Well, I'm glad it worked out, but that's really not the way it should be done. The EFI boot partition is created specifically in support of a particular hardware configuration and since you've changed hardware by adding a new SSD it's actually not specifically for your current configuration, but so long as it works and since you're going to be getting a different SSD soon as you said, then you can simply do a clean install then but when you do be sure to disconnect all the other drives until after the installation.
I
iNaomiPlays
02-09-2016, 06:17 PM #6

Well, I'm glad it worked out, but that's really not the way it should be done. The EFI boot partition is created specifically in support of a particular hardware configuration and since you've changed hardware by adding a new SSD it's actually not specifically for your current configuration, but so long as it works and since you're going to be getting a different SSD soon as you said, then you can simply do a clean install then but when you do be sure to disconnect all the other drives until after the installation.