I'm facing a frustrating boot problem with my Windows 11 installation. Here's the situation: Windows is installed on a Kingston SSD, but the crucial UEFI bootloader is located on a separate Samsung NVMe SSD. This means if I disconnect the Samsung SSD, my computer won't start up at all. This mess happened because during the Windows 11 Pro activation after a hardware change, the Microsoft assistant installed Windows on the Kingston but didn't disconnect the Samsung, which led to the EFI partition being created on the Samsung instead of the Kingston. Now, I'm stuck with Windows on one drive and the boot files on another, which isn't safe or ideal. I can't even clean the Samsung drive because Windows sees it as the current boot/system drive. To make things worse, my BIOS only lists the Samsung as a boot option, so I need to fix this configuration to avoid potential future issues if I remove or clean the Samsung SSD. My goal is to have Windows and the boot loader on the same drive, ideally the Samsung, before I can have a proper boot order setup. Has anyone experienced this, and what steps should I take to straighten it out?
3 Answers
I had a similar issue before! You might need to manually move your EFI bootloader to the Kingston drive. To do this, use a tool like BCDBoot from the command prompt in recovery mode to fix the boot entries. After you've moved the boot loader, make sure to set the Kingston SSD as your first boot option in BIOS. This should solve the issue with the disjointed setup!
Just a heads up, since you mentioned the cloning part too—if you plan on cloning the Samsung SSD to another drive, make sure everything's organized first. It might be wise to only clone when your boot and OS partitions are correctly aligned. Otherwise, you could end up duplicating this whole mess onto another SSD!
It sounds like you need to do a bit of reconfiguration. First, make sure to back up your data, as messing with these settings can lead to data loss. Then, you might want to boot from a Windows installation USB and repair the startup. During the repair, make sure to set the correct on-disk boot parameters so that the Windows boot loader gets associated with the Kingston SSD where Windows is actually installed. After that, try to get into BIOS and see if you can set the Kingston as the main boot drive once the repair is complete.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures