Fix: No Boot Device Found After Installing a New SSD

“No boot device found” after adding a new SSD almost always means the firmware looked at every drive it could see and found nothing it knows how to start. A brand-new drive is blank, so the usual fix is to confirm the PC detects the drive, then install Windows onto it from a USB stick in UEFI mode. If you cloned an old drive instead, rebuilding the boot files is the likely cure. This guide applies to Windows 10 and Windows 11 desktops and laptops, and most people finish in 30 to 60 minutes.

Quick Answer

• Open the BIOS/UEFI setup and confirm the new SSD appears in the storage or boot list; reseat it if it does not.
• Set the boot mode to UEFI (not Legacy/CSM) and make the correct drive or the USB stick first in the boot order.
• Blank SSD: boot a Windows installation USB, pick the drive’s unallocated space, and let Setup create the partitions.
• Cloned SSD: boot the same USB, open Repair your computer, and run Startup Repair or rebuild the boot files with bcdboot.
• Still stuck: update the BIOS, check the M.2 slot, and read the troubleshooting list below.

Before You Start

Power the PC off and unplug it before touching any hardware. On a laptop, shut down fully (not sleep) and disconnect the charger. Touch bare metal on the case to discharge static before handling the SSD.

Back up anything you care about on your old drive before you change partitions. Several steps below, especially the diskpart clean command, erase a disk completely, and the command does not ask twice. Always confirm the disk number by its size before you run it.

You will need a second working computer and an 8 GB or larger USB flash drive to create Windows installation media with Microsoft’s Media Creation Tool. The USB drive gets erased during that process. If your copy of Windows 11 or Windows 10 was activated with a digital license on this PC, Windows usually reactivates itself after a clean install on the same hardware once you are online; you can check under Settings > System > Activation afterward. If activation fails, use Microsoft’s activation troubleshooter or support.

BIOS screens vary between brands. Change only the settings named here and write down each original value first.

Method 1: Make Sure the BIOS Sees the SSD and Boots in UEFI Mode

Everything else fails if the firmware cannot see the drive, so start here.

1. Restart the PC and tap the setup key as it powers on. Common keys are Del, F2, F10 or Esc; the splash screen or your motherboard manual lists the right one.
2. Look for a storage, NVMe or SATA information page, or the Boot tab. Your SSD should be listed by model name (for example a brand and capacity). If it is listed, go to step 5.
3. If it is missing, power off, unplug the PC, and reseat the drive. For an M.2 SSD, remove the screw, slide the drive fully into the slot at a slight angle, press it flat, and fasten the screw so it sits in the correct standoff notch for its length.
4. Check your motherboard manual for lane sharing. On many boards, populating one M.2 slot disables certain SATA ports, and some slots only work with specific drive types. Move the SSD to another M.2 slot if the manual says the first one conflicts.
5. On the Boot page, set the boot mode to UEFI. If you see CSM (Compatibility Support Module) or Legacy enabled, disable it. A UEFI installation needs a GPT-partitioned drive, while Legacy mode expects an older MBR layout, and a mismatch is a common reason a freshly installed drive refuses to start.
6. Leave Secure Boot alone unless a later step requires otherwise. Secure Boot blocks unsigned boot code, so turning it off lowers protection against boot-level malware; Windows 11 also expects it to be available.
7. Save and exit (usually F10).

Why it works: firmware can only boot what it can see, and UEFI-installed Windows needs UEFI mode. After this step, a blank drive will still say “no boot device” until Windows is installed, but you will now be able to boot the USB stick.

Method 2: Install Windows on the Blank SSD

A new SSD has no partitions and no boot loader, so there is nothing to find. Setup builds both.

1. On another PC, download the Media Creation Tool from Microsoft’s Windows download page, run it, choose USB flash drive, and let it finish writing the installer.
2. Unplug other storage drives from the target PC if you can, particularly the old Windows drive. This keeps Setup from placing the boot files on the wrong disk, which is a classic reason a new install “works” only while the old drive is connected.
3. Plug the USB stick into the target PC and open the one-time boot menu (often F12, F8, F11 or Esc). Choose the entry that starts with UEFI: followed by the USB name.
4. In Windows Setup, pick your language, click Install now, then choose I don’t have a product key if your PC already holds a digital license, and select the edition that matches it.
5. Choose Custom: Install Windows only (advanced).
6. On the “Where do you want to install Windows?” screen, you should see the new SSD as Drive 0 Unallocated Space with its full capacity. Select it and click Next. Setup creates the EFI, recovery and main partitions on its own.
7. The PC restarts several times. When the first restart prompt appears, remove the USB stick so the PC boots from the SSD.

If the drive does not show in the list, click Load driver. Some laptops and desktops with Intel RST/VMD storage controllers or RAID mode set in the BIOS hide NVMe drives until the vendor’s storage driver is loaded; switching the controller to AHCI in the BIOS is a possible alternative, but changing it on a PC that already has Windows installed can prevent that Windows from booting.

Method 3: Repair the Boot Files on a Cloned or Moved SSD

If you cloned your old drive or moved Windows to the new SSD and now see “no boot device,” the data is probably intact but the boot entry or EFI partition was not carried over correctly.

1. Boot from the Windows USB stick as in Method 2, but on the first screen click Next, then Repair your computer.
2. Go to Troubleshoot > Advanced options > Startup Repair and choose your Windows installation. Let it run; it fixes many simple cases.
3. If that fails, return to Advanced options and open Command Prompt. Type diskpart, press Enter, then list volume. Find the Windows volume (the large NTFS one; its letter is often D: inside the recovery environment) and the small FAT32 volume of roughly 100 to 300 MB, which is the EFI System Partition.
4. Assign a letter to the EFI volume: select volume X (use its number) then assign letter=S, then exit.
5. Rebuild the entries: bcdboot D:\Windows /s S: /f UEFI, substituting your actual Windows drive letter. You should see “Boot files successfully created.”
6. Close the window, click Continue, and remove the USB stick.

If there is no FAT32 EFI volume at all, the clone skipped it; the safest route is a clean install per Method 2 or re-cloning the whole disk, including every partition, with your cloning software’s “system” or “entire disk” option. Legacy-style bootrec /fixmbr commands target MBR systems and do not repair a UEFI/GPT setup.

If It Did Not Work

• SSD still missing in the BIOS: try another M.2 slot or SATA port and cable, and install the latest BIOS from your motherboard or laptop maker’s support page, since newer firmware often adds drive compatibility. Follow the vendor’s update instructions exactly and never power off during a flash.
• “Windows cannot be installed to this disk. The selected disk is of the GPT partition style”: you booted the USB in Legacy mode. Restart, pick the UEFI: entry in the boot menu, and confirm CSM is off.
• “The selected disk has an MBR partition table”: you are in UEFI mode but the disk is MBR. In Setup press Shift+F10, run diskpart, list disk, select disk 0 (match the size!), clean, convert gpt, exit, then click Refresh. This erases that disk.
• Error code 0xc000000f or 0xc000000e on screen: Windows found a boot entry but could not read it, which points to a damaged or missing BCD. Repeat Method 3.
• Boots only with the old drive attached: the boot files landed on the old disk. Disconnect it, boot the USB, and run the bcdboot step against the new SSD’s EFI partition.
• Installer fails midway: check the Setup logs in the Panther folder (in the recovery Command Prompt, X:\Windows\Panther) for the stop code, and look it up in Microsoft’s documentation.

Common Questions

Do I need to initialize the SSD in Disk Management first?

Not for a fresh install, because Windows Setup initializes and partitions the disk for you. Initialization in Disk Management matters when you add the SSD as a second data drive to a PC that already boots, and there you should choose GPT.

Should I turn off Secure Boot to fix this?

Usually no. A blank drive has nothing for Secure Boot to block, and Windows 11 installation media is signed. Disabling it reduces protection against tampered boot code, so only do so if a vendor guide for a specific operating system tells you to, and turn it back on afterward.

Why does the BIOS show the SSD but the PC still says no boot device?

Detection and bootability are different. The drive is present but contains no valid EFI System Partition with Windows boot files, which is exactly what Method 2 or Method 3 supplies.

Can I keep my old drive connected during installation?

You can, but disconnecting it is safer. Setup may otherwise write the boot loader to the older drive, and the new SSD then fails to start on its own.

Is the SSD faulty if none of this works?

Less likely than a seating, slot or boot-mode problem. If it is not detected in two slots or on another computer, ask the seller about a replacement.

Update History

• October 14, 2026 – Initial publication; steps checked against Windows 11 24H2/25H2 and current driver releases.
• Menus can differ slightly by Windows build, BIOS vendor and driver version; check your own screens against the steps.

Sources

• Microsoft documentation on creating Windows installation media and Windows Setup disk requirements
• Microsoft documentation for BCDBoot command-line options and DiskPart commands
• Microsoft Windows 11 UEFI, GPT and Secure Boot guidance
• Dell support guidance on “No Bootable Device Found” and UEFI versus Legacy boot mode
• Motherboard vendor manuals for M.2 slot and SATA lane sharing