Windows boots to “No Operating System Found” after changing the boot drive

rickm76

I moved my Windows installation to another SSD, but after changing the boot order, the PC says “No Operating System Found.” The Windows partition and files are still there. Do I need to rebuild the boot files, or did I miss something during the migration?

LeoF_225

rickm76 The first thing I'd check is whether you're actually booting the new SSD in the same mode Windows was installed with.

If this is a UEFI installation, the thing you normally want in the boot menu is Windows Boot Manager, not just the SSD model/name.

Also, Windows can have the OS partition on one drive while the EFI System Partition is sitting on another drive. That would explain why the old drive worked before the migration but the new drive doesn't boot by itself.

I'd check the BIOS/UEFI boot entries and the partition layout before rebuilding anything.

GreyNotebook

LeoF_225 Yep, I've been bitten by the "Windows is on the new SSD, but the boot files aren't" situation.

If you still have the old SSD connected, try shutting down and disconnecting it completely. Then check whether the new SSD has an EFI System Partition (usually a small FAT32 partition) in addition to the Windows NTFS partition.

If the machine only boots when the old SSD is connected, that's a pretty strong clue that the boot files are still on the old disk.

techsince98

GreyNotebook Small correction to the usual advice: don't assume "the Windows partition is on SSD #2" means SSD #2 is bootable.

UEFI doesn't simply look for an NTFS partition containing `Windows\System32` and magically figure it out. It needs an EFI bootloader and a valid boot configuration.

And don't start running random `bootrec` commands just because the error says "No Operating System Found." On a modern UEFI/GPT installation, `bcdboot` is often the more relevant tool for recreating the Windows boot environment.

ProbablyFine

techsince98 Classic Windows migration moment:

"Windows is definitely on the new SSD."

BIOS: "Cool story. Where's the bootloader?"

😂

Seriously though, if the old SSD is still installed, I'd test the new SSD completely by itself. Otherwise the PC can happily keep using the old drive's EFI partition and make the migration look successful until you remove the old drive.

tommyk

ProbablyFine So if I understand this correctly, the OS files and the boot files don't necessarily have to be on the same physical drive?

That's probably what I would have assumed, so this is useful to know.

LeoF_225

tommyk Correct.

On a typical UEFI/GPT Windows setup, you'll have an EFI System Partition (ESP) containing the boot files and a larger NTFS partition containing Windows itself. They can be on the same disk, but Windows setup can also end up putting the EFI partition on a different disk if multiple drives are connected during installation.

That's why "I can see all my Windows files on the new SSD" doesn't prove that the new SSD contains everything needed to boot independently.

GreyNotebook

LeoF_225 If you're comfortable checking from Windows Recovery, I'd do this before changing anything:

1. Boot from a Windows installation/recovery USB.

2. Open Command Prompt.

3. Run `diskpart`, then `list disk` and `list volume`.

4. Identify the new SSD and look for the small FAT32 EFI partition.

5. Make sure you know which drive letter the actual Windows partition has in recovery mode.

Don't assume Windows is `C:` in the recovery environment. It often isn't.

techsince98

GreyNotebook That last point is important.

A lot of "just run bcdboot C:\Windows" guides are dangerous because WinRE may assign the Windows partition a different letter.

I'd first verify it with something like `dir C:\Windows`, `dir D:\Windows`, etc., until you find the actual installation. Same with the EFI partition: identify it by filesystem/type rather than guessing based on partition number.

The commands are easy. Identifying the correct partitions is the part people mess up.

ProbablyFine

techsince98 Windows Recovery drive letters are basically Schrödinger's drive letters.

Your C: drive is C: until you boot recovery, at which point Windows goes, "You know what? Let's call it D: today."

So yeah, verify the letters before firing off `bcdboot`. A wrong target here is a much less entertaining surprise than it sounds.

tommyk

ProbablyFine Taking notes:

* Windows partition being present doesn't mean the disk is bootable

* UEFI wants Windows Boot Manager

* EFI partition may be on a different disk

* WinRE drive letters can change

* Don't blindly use boot repair commands

This actually explains a lot of weird "my cloned SSD works only with the old SSD installed" cases I've seen.

GreyNotebook

tommyk If the new SSD has the Windows partition but no usable boot files, `bcdboot` can usually recreate them.

For example, after identifying the correct Windows partition and EFI partition in WinRE, the general idea is:

`bcdboot <WindowsDrive>:\Windows /s <EFIDrive>: /f UEFI`

Obviously replace those drive letters with the ones you actually identified.

After that, reboot and check the UEFI boot menu for **Windows Boot Manager** on the new SSD.

I would keep the old SSD untouched until the new one has successfully booted on its own.

techsince98

GreyNotebook One more distinction: rebuilding the BCD isn't the same thing as repairing a physically damaged Windows installation.

If the new SSD's Windows files are intact and the problem started immediately after changing the boot device, I'd investigate the boot chain first.

Also, don't convert GPT/MBR or switch UEFI/Legacy mode just because someone says "try the other boot mode." That can turn a simple boot-entry problem into a second problem.

LeoF_225

techsince98 Exactly.

The boot path here is roughly:

UEFI firmware → Windows Boot Manager → BCD → Windows installation.

If the firmware can't find a valid Windows Boot Manager on the new disk, it can fail before Windows itself even gets a chance to start.

So the fact that the Windows partition is readable is actually useful evidence: it suggests the data may be fine, while the boot path is what's broken or still tied to the old drive.

ProbablyFine

LeoF_225 At this point I'd vote for the old SSD being the "secret employee" of this Windows installation.

Everything works while it's plugged in, then you remove it and suddenly Windows discovers it was emotionally dependent on that drive all along.

I'd clone/backup anything important first, then fix the boot setup on the new SSD. Definitely don't wipe the old drive yet.

GreyNotebook

ProbablyFine I'd troubleshoot it in this order:

1. Disconnect the old SSD.

2. Confirm the new SSD is detected in UEFI.

3. Check whether the new SSD has an EFI System Partition.

4. Make sure the firmware is using UEFI mode if the Windows installation is UEFI/GPT.

5. If necessary, use WinRE to identify the Windows and EFI partitions and rebuild the boot files with `bcdboot`.

6. Reboot and select **Windows Boot Manager** associated with the new SSD.

If `bcdboot` reports an error, post the output of `list disk`, `list volume`, and the exact error. That would tell us a lot more than guessing.

And definitely don't delete the old SSD's partitions until the new one has booted successfully by itself.