Fix boot error 0xc000000e
0xc000000e is STATUS_NO_SUCH_DEVICE, 'A device that does not exist was specified.' Microsoft says it happens when the boot configuration data names a device that does not exist, so winload.exe cannot be loaded. Make sure the firmware sees the Windows drive, undo any recent disk or storage mode change, then run Startup Repair or rebuild the boot files with bcdboot.
Checked November 10, 2026 against the manufacturer's own pages.
The short version
What to install and where it comes from. Every link goes to the manufacturer or Microsoft, never to a copy.
Official files only, nothing bundled
Step by step
Confirm the firmware can see the Windows drive
Enter the firmware setup at power on and look at the storage or boot list. If the SSD or hard drive is missing there, reseat its cable or M.2 slot on a desktop, or contact the PC maker. No software fix helps until the drive shows up.
Undo a recent storage or boot mode change
If you changed the SATA mode (for example AHCI to RAID or Intel RST), the boot mode (UEFI or legacy), or swapped drives, put the setting back as it was and restart.
Disconnect every other drive
Unplug USB sticks, external disks and any second internal drive you added. With one disk left, the boot entry has fewer wrong places to point.
Run Startup Repair
Boot from a Windows 11 USB made on another PC, choose Next, Repair your computer, Troubleshoot, Advanced options, Startup Repair. Let it finish, then select Shut down and power on again.
Look at what the boot entry points to
In the recovery Command Prompt (Shift+F10 on the setup screen) run bcdedit /enum. Under Windows Boot Loader, check the device and osdevice lines. If they say unknown, the entry points at a partition Windows cannot find.
Write fresh boot files with bcdboot
Run diskpart, list vol, exit to learn the Windows drive letter in recovery, which is often not C. Then run bcdboot with that path, for example bcdboot D:\Windows. Microsoft documents bcdboot as the tool to recreate system partition files from the Windows partition.
What the device in the error really is
The NTSTATUS name, STATUS_NO_SUCH_DEVICE, sounds like a missing gadget. At boot it almost always means a disk or partition. Windows Boot Manager reads the BCD store, finds the entry for Windows, and follows its device and osdevice values to \Windows\system32\winload.exe (or winload.efi on UEFI). Microsoft’s article on this error states the cause directly: the BCD names a device that does not exist.
So the question is what changed between the last good start and now. The usual answers are a cloned or replaced drive, a partition that was deleted or resized, or a firmware setting that changes how the disk is presented to Windows.
Telling it apart from 0xc0000225
Both codes come from Boot Manager and both are fixed with boot repairs, but they point to different gaps. With 0xc000000e, the BCD exists and is readable, yet it points to a location that is not there. With 0xc0000225 and no file named, the BCD itself is often missing or unreadable. That is why bcdedit /enum is worth a look here. If it lists entries with unknown devices, rewriting the store with bcdboot is the direct fix.
A storage driver mode change
Switching the controller from AHCI to RAID or Intel RST in the firmware changes which storage driver Windows needs at boot. If that driver is not set to load, the disk can vanish from Windows’ view during startup. Setting the controller back to its earlier mode is the fastest test. Change the mode only after following the PC maker’s instructions for that switch.
Questions
Why did 0xc000000e appear after I cloned my drive?
The copy has new disk and partition identities, but the boot data may still name the old ones. Remove the old drive, then run bcdboot against the new Windows partition.
What does A required device isn't connected or can't be accessed mean?
It is the plain wording often shown with 0xc000000e on the blue recovery screen. The device is the partition the boot entry names, which Windows cannot reach.
Can a failing SSD cause 0xc000000e?
Yes. If the drive drops out or is not detected at power on, the boot entry points at a device that is gone. Check it in the firmware setup and run the PC maker's storage diagnostics.
Do I need to reinstall Windows?
Usually not. Repairing the boot entry or recreating the boot files fixes most cases. Reinstalling is only needed if the Windows partition itself is damaged.