Windows 10 displays a duplicate boot menu after removing an SSD because the Windows Boot Manager retains stale configuration entries in the EFI System Partition. These orphaned records persist even when the physical drive is gone, causing the system to pause at startup and ask you to choose between valid and invalid operating system installations.
Understanding the Boot Configuration Data
The issue stems from how Windows manages its boot environment. When you install Windows on multiple drives, the installer creates separate entries in the Boot Configuration Data (BCD) store. This store resides on the EFI System Partition (ESP), which is a small FAT32 partition present on UEFI-based systems. Removing one of the physical SSDs does not automatically delete these registry-like entries. The computer still sees the configuration file pointing to a path that no longer exists, resulting in the confusing "Windows run" or similar selection screen during POST (Power-On Self-Test).
To resolve this, you must manually clean up the BCD store. This process involves identifying the specific identifiers associated with the removed drive and deleting them from the active boot configuration. It is important to note that this operation affects only the software configuration for booting; it does not alter any data on your remaining SSD or affect the integrity of your installed Windows files.
Accessing the Command Prompt
Before modifying boot settings, you need administrative access to the command line. The most reliable method is using the Windows Recovery Environment (WinRE). If you can currently boot into Windows normally, open the Start menu, type
cmd, right-click on Command Prompt, and select Run as administrator. However, if your system fails to boot properly due to the conflicting entries, you may need to force entry into WinRE by holding Shift while clicking Restart, or by using a Windows installation USB drive.
Once in the recovery environment, navigate to Troubleshoot > Advanced options > Command Prompt. This ensures you have full control over the boot sector without interference from running services. If you are already in a standard Windows session with admin rights, you can skip to the next section directly.
Identifying Boot Entries
The primary tool for managing these entries is
bcdedit. Open your elevated command prompt and type the following command to list all current boot entries:
bcdedit /enum /v
This command outputs a verbose list of all devices and boot managers. You will see several sections, including
Windows Boot Manager,
Current OS Loader, and potentially other entries labeled
{default} or with unique GUIDs. Look for entries that reference the missing SSD. Often, these entries will have a description like "Windows 10" but point to a device path that no longer exists, such as a different volume UUID than your current main drive.
Be careful not to delete the entry marked as
Current under the OS Loader section, as this is the working boot configuration for your active system. Identifying the correct target requires comparing the
device and
osdevice values against your known hardware setup. If you are unsure which entry corresponds to the removed drive, it is safer to check the
description field or use
bcdedit /enum firmware to see hardware-specific details.
Removing Stale Entries
Once you have identified the GUID of the obsolete boot entry, you can remove it using the
/deletevalue or
/delete switch. For example, if the obsolete entry's identifier is
{12345678-1234-1234-1234-123456789abc}, you would run:
bcdedit /delete {12345678-1234-1234-1234-123456789abc}
If the command succeeds, you will receive a message stating that the operation completed successfully. If you encounter an error saying the element is required or cannot be deleted, it might mean that entry is currently set as the default or critical loader. In such cases, you may need to reset the default boot entry first using
bcdedit /set {default} device partition=C: (assuming C: is your current drive) before attempting deletion again.
After cleaning the BCD store, restart your computer. The boot menu should no longer appear, and Windows should load directly into your desktop. This fix is consistent across various hardware configurations and is often necessary after major storage changes. For users experiencing broader storage recognition issues, you might also want to review related troubleshooting guides, such as those found in
Windows 11 Pro i7 running, won't accept new hard drive already running Pro or
Windows 10 HPE EliteBook 650G9: External 5.25'' Enclosure Not Showing in Windows Explorer.
Preventing Future Issues
To avoid this situation in the future, consider disabling the boot menu timeout if you only ever use one operating system. You can do this by running
bcdedit /timeout 0 in an administrator command prompt. This sets the boot selection timer to zero seconds, effectively hiding the menu unless you hold down the Shift key during startup. Additionally, always ensure you are shutting down Windows properly before physically removing internal drives, as improper shutdowns can sometimes leave residual locks on boot configurations.
Frequently Asked Questions
What if I delete the wrong boot entry?
If you accidentally delete the active boot entry, Windows will fail to start and display a "Boot Device Not Found" error. To fix this, you will need to boot from a Windows installation media or recovery drive and use the Startup Repair feature to rebuild the BCD store automatically.
Can I use Disk Management to fix this?
No, Disk Management handles partition volumes and drive letters, not the low-level boot configuration data stored in the EFI partition. You must use command-line tools like
bcdedit to modify these specific boot manager entries.
Why does the boot menu still show after deleting an entry?
Sometimes, multiple entries reference the same physical drive or partition. Deleting one entry might leave another orphaned record that points to the same non-existent location. Run
bcdedit /enum again to verify if any other stale entries remain and delete them individually.
Is it safe to edit the BCD store?
Yes, editing the BCD store is safe provided you do not delete the entry currently marked as
Current or
Default for your active operating system. Always double-check the GUIDs and descriptions before executing delete commands to prevent boot failures.
How do I disable the boot menu permanently?
You can disable the automatic display of the boot menu by setting the timeout value to zero using the command
bcdedit /timeout 0. This forces Windows to bypass the selection screen and load the default operating system immediately upon power-on.