Windows fails to boot after installing Ubuntu on a separate drive because the system firmware’s boot order has shifted to prioritize the new Linux installation over the existing Windows bootloader. This occurs when the Ubuntu installer modifies the NVRAM variables or creates a new EFI System Partition entry that takes precedence, causing the motherboard to look for a GRUB loader instead of the Windows Boot Manager. Resetting the UEFI boot priority in the BIOS/UEFI settings restores the correct startup sequence without requiring complex command-line repairs.
Understanding the Boot Priority Shift
When you install a second operating system like Ubuntu Server, the installer often detects existing EFI System Partitions (ESP) and may add its own bootloader entries to the Unified Extensible Firmware Interface (UEFI) NVRAM. Unlike legacy BIOS systems that rely on Master Boot Records (MBR), modern UEFI systems store boot configuration directly in firmware variables. The Windows Boot Manager is typically stored in the ESP on your M.2 SSD, while Ubuntu installs GRUB into the same partition or a dedicated one on the secondary SSD. If the firmware is configured to check the secondary drive first, it will attempt to load GRUB. If GRUB cannot find the Ubuntu kernel or if the user accidentally selects the wrong entry, the system appears to hang or reboot immediately. This is not a corruption of the Windows files on the M.2 SSD but rather a misdirection of the boot path. It is crucial to understand that tools likebootrec /fixmbr are obsolete for UEFI systems and can damage the partition table if used incorrectly. The solution lies in adjusting the firmware's decision logic, not repairing disk sectors.
Accessing and Navigating UEFI Settings
To resolve this, you must access the motherboard’s setup utility. Restart your computer and repeatedly press the designated key during the initial POST (Power-On Self-Test) screen. Common keys include F2, Delete, F12, or Esc, depending on your manufacturer. For Dell systems, which are common in dual-drive setups, F2 enters Setup and F12 opens the One-Time Boot Menu. Once inside the UEFI interface, navigate to the section labeled "Boot Order," "Boot Configuration," or "Startup." The exact naming varies by vendor, but the function remains consistent: it lists the devices and bootable partitions the firmware will attempt to load from, in priority order. You will likely see multiple entries here, including "Ubuntu," "GRUB," "WD_BLACK SN770," and "Windows Boot Manager."Reordering the Boot Entries
The primary goal is to ensure "Windows Boot Manager" is the first option in the list. Use the keyboard arrows or mouse, as permitted by your interface, to move the Windows entry to the top position. If you see a generic entry named "Windows Boot Manager" associated with your M.2 SSD, select it. In some cases, you might see an entry simply named after the drive model; however, "Windows Boot Manager" is the specific UEFI variable that points to the\EFI\Microsoft\Boot\bootmgfw.efi file.
After reordering, save the changes and exit. Most UEFI interfaces require you to select "Save Changes and Exit" or press F10. The system will restart and should now load Windows directly. If you wish to keep Ubuntu accessible, you do not need to delete its entries. Instead, you can use the One-Time Boot Menu (often F12) during startup to manually select the Ubuntu drive whenever you want to switch to Linux. This method keeps both installations intact and allows for easy switching without altering the permanent boot order.
Verifying the EFI Partition Integrity
If changing the boot order does not resolve the issue, verify that the Windows EFI partition is still intact. Boot from a Windows Installation Media USB and open the Command Prompt. Rundiskpart, then list disk to identify your drives. Select the disk containing Windows (sel disk 0 usually) and then list vol. Look for a small FAT32 partition (typically 100-500 MB) labeled as System or Hidden. If this partition is missing or corrupted, the Windows Boot Manager cannot be found regardless of boot order. In such rare cases, you may need to rebuild the BCD store using bootrec /rebuildbcd, but this is only necessary if the partition itself is damaged, not merely if the boot order is wrong.
For more detailed guidance on managing dual-boot configurations on similar hardware, refer to our guide on Dual Booting Windows and Ubuntu 22.04 LTS on DelVostro 5581 with Separated Drives Not Working. Additionally, if you encounter display issues once you successfully boot back into Linux, check out our troubleshooting steps for Jerky Scrolling in Ubuntu.
Preventing Future Boot Conflicts
To avoid this issue during future OS installations, consider disabling the secondary drive in the UEFI settings before running the Ubuntu installer. This forces the installer to create a self-contained environment on the new SSD without interfering with the Windows NVRAM variables. After installation, re-enable the drive and adjust the boot order again. Alternatively, always use the One-Time Boot Menu to select the target drive during installation, ensuring the installer writes its bootloader to the correct location without overriding the default Windows entry.Frequently Asked Questions
Will resetting the boot order delete my Ubuntu data?
No, changing the UEFI boot priority only affects which operating system loads first at startup. Your Ubuntu files, partitions, and configurations remain completely untouched on the secondary SSD. You can still access Ubuntu by selecting it from the One-Time Boot Menu or by moving its entry to the top of the boot order list later.Can I fix this using the Windows Recovery Command Prompt?
Generally, no. Since the issue is a firmware-level boot priority conflict rather than a corrupted Windows file system, command-line tools likesfc /scannow or chkdsk will not resolve the problem. While bootrec /rebuildbcd can repair a missing BCD store, it is unnecessary if the Windows Boot Manager entry exists in the UEFI variables but is simply listed below Ubuntu.