Windows Error 0xc000000e: How to Fix It and Boot Again

Error 0xc000000e usually means Windows can’t find the boot files or the drive it needs to start. In plain English, that points to a Boot Configuration Data problem, a loose or missing drive connection, or a drive that may be failing. Start with the safest checks first, then use Windows recovery tools to repair the boot files.

What error 0xc000000e is telling you

0xc000000e

This error appears during startup when Windows reaches the point where it expects to find its boot files, but can’t access them. That often happens because the Boot Configuration Data, or BCD, is damaged, the boot order changed, the system drive was moved, or the drive itself is having trouble being read.

A loose SATA cable, a disconnected power lead, or an external drive confusing the boot order can trigger it too. If the PC was working before and then started showing this message after a power loss, update, drive swap, or BIOS change, a boot-file or connection problem is more likely than a full Windows failure.

When this fix path applies

These steps are for a Windows PC that stops at the 0xc000000e startup error and won’t reach the desktop. They’re not meant for slow boot times, random app crashes, or blue screens that happen after Windows has already started.

This applies to recent Windows versions that use BIOS or UEFI boot. You’ll need Administrator access for some recovery commands, and in a few cases you’ll need Windows installation media or a recovery USB. A restart is part of the process, and a backup is ideal if the PC still lets you copy files.

Start with two safe checks first:

• Unplug all USB drives, external hard drives, memory cards, and any dock or adapter that could look like a boot device.
• Enter BIOS or UEFI setup and confirm the system drive is listed in storage or boot information.

If the machine is a desktop, you may need to shut it down and open the case to check cables; if it’s a laptop, stick to the external checks and BIOS or UEFI settings unless you’re comfortable opening it.

Start with the safest checks

Begin with the easy checks that don’t touch your files. A surprising number of 0xc000000e cases come from the PC trying to boot from the wrong device or from a drive connection that’s come loose.

1. Shut the PC down completely.
2. Unplug all USB drives, external hard drives, memory cards, and any dock or adapter that could look like a boot device.
3. Power the PC back on and see whether the error changes.
4. If it still fails, enter BIOS or UEFI setup and confirm the system drive is listed in storage or boot information.
5. Check that the Windows drive is first in the boot order.

If the drive does not appear at all, that points away from a simple Windows boot-file problem and toward a hardware or connection issue. On a desktop, reseat the SATA data cable and power cable, then try again. On a laptop, if the drive is accessible and you’re comfortable doing it, reseating the SSD can help, but if not, move on to recovery tools.

Use Windows Startup Repair first

If the drive is detected, the next safest move is Windows Startup Repair. It can fix common boot problems automatically and is less risky than manual command-line repairs.

You’ll need Windows recovery media or an installed recovery environment. On a separate working PC, create a Windows installation USB if you don’t already have one, then boot the problem PC from that USB. Once you see the Windows Setup screen:

1. Select your language and keyboard layout.
2. Choose Repair your computer instead of Install now.
3. Go to Troubleshoot > Advanced options > Startup Repair.
4. Pick the Windows installation you want to repair if prompted.

Troubleshoot > Advanced options > Startup Repair

If Startup Repair succeeds, the PC should restart into Windows. If it reports that it couldn’t repair your PC, that usually means the boot files need manual repair or the drive has a deeper problem.

Rebuild the boot files if Startup Repair fails

If Startup Repair doesn’t fix it, the next move is to rebuild the boot files from recovery tools. This is where bootrec and bcdboot come in. You should do this from the Windows recovery environment or installation media, not from the broken Windows install itself.

1. Boot from the Windows installation USB and open Repair your computer.
2. Go to Troubleshoot > Advanced options > Command Prompt.
3. First, try to repair the boot record and boot sector.

bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd

4. If the system still won’t boot, rebuild the boot files with bcdboot. You may need to identify the Windows and EFI partitions first.

bcdboot C:\Windows /f UEFI

If your Windows folder is on a different drive letter in recovery mode, replace C: with the correct one. Recovery environments don’t always assign the same letters you see inside Windows.

If bootrec /fixboot says access is denied, or bcdboot fails because it can’t find the Windows folder, that usually means either the partitions are not what you expect or the disk has a file-system problem. In that case, check the drive in recovery with diskpart and dir before trying again, or move on to hardware checks if the drive looks unstable.

Check whether the drive is actually failing

If the drive is missing from BIOS or UEFI, the problem may not be Windows at all. A bad SSD or hard drive, a failed controller, or a loose connection can all stop the boot process before Windows gets a chance to load.

Common warning signs include:

• The drive doesn’t appear in BIOS or UEFI at all.
• The PC sometimes sees the drive and sometimes doesn’t.
• You hear clicking, grinding, or repeated spinning-up sounds from a hard drive.
• Startup Repair and boot-file repairs fail repeatedly with different errors.
• The system worked after a restart once, then failed again soon after.

If the drive shows up inconsistently, don’t keep power-cycling it over and over. That can make a failing disk worse. If you can still access recovery tools, copy off anything important first. If the drive is completely absent in BIOS or UEFI after checking cables, the safest assumption is a hardware fault until proven otherwise.

If Windows still won’t start

If the boot files are repaired and the drive still won’t start Windows, shift focus to your data first. If the drive is readable in recovery, copy your important files to an external drive before trying bigger fixes.

From there, the next steps depend on what you found:

• If the drive is healthy and the boot files were the main problem, try the recovery repairs again and check the boot order one more time.
• If Windows files are badly damaged but the drive is fine, a repair install or a clean reinstall may be the practical way forward.
• If the drive is failing, replace it before reinstalling Windows. Reinstalling onto a bad drive just puts you back here.

Avoid a reinstall until you’ve tried to save your files and you’re reasonably sure the drive itself is stable. A reinstall can overwrite recovery chances if the disk is already failing.

If the data matters and the drive is unstable, stop repeated repair attempts and use file-copy tools from recovery or another operating system to retrieve what you can. If the drive isn’t detected at all, professional data recovery may be the only realistic option.

How to avoid seeing this error again

Once the PC boots again, keep the boot path simple. Don’t leave USB drives plugged in during startup unless you need them, and don’t change the boot order unless you know why you’re doing it.

A few habits help reduce the chance of another boot failure:

• Shut down Windows normally instead of holding the power button.
• Keep backups of important files on another drive or cloud storage.
• If you update BIOS or UEFI settings, note the original boot order first.
• Avoid moving an SSD or hard drive between systems without checking how that system boots.
• Watch for early drive trouble, like delays, missing boots, or file errors, and back up sooner rather than later.

If your PC uses an older hard drive, replacing it before it fails completely can save a lot of recovery work. Even with an SSD, keeping a backup matters because boot problems can still happen after a power cut or firmware issue.

Questions people usually ask next

Does 0xc000000e mean my files are gone? Not usually. The error is about startup, not automatic data loss. If the drive is still readable, your files may be intact even though Windows won’t boot.

Can this be fixed without reinstalling Windows? Yes, often it can. Startup Repair, fixing the boot order, and rebuilding the boot files with bootrec or bcdboot are the usual first tries.

How long should the repair take? It depends on what’s wrong. A simple startup repair may take only a few minutes, while checking the drive, rebuilding boot files, or copying data out can take longer.

What if the drive isn’t detected in BIOS or UEFI? Treat that as a hardware or connection problem first. Check the cables on a desktop, and if the drive still isn’t seen, replace it or have it tested before trying more Windows repairs.

Conclusion

Start with the simple checks, then use Startup Repair, and only move on to manual boot-file repair if the first pass fails. If the drive isn’t consistently detected, focus on saving your data and checking the hardware instead of repeating repairs that won’t stick.

Frequently Asked Questions

Does error 0xc000000e mean Windows is deleted?

No. It usually means Windows can’t find the boot files or the boot device, not that the operating system was deleted.

Can I fix 0xc000000e without reinstalling Windows?

Often yes. Startup Repair and rebuilding the boot files are the usual first fixes, and they don’t require a reinstall.

What if I can see the drive in BIOS but Windows still won’t boot?

That usually points to a boot configuration problem rather than a dead drive. Startup Repair or `bcdboot` is the next step.

Should I keep trying repairs if the drive disappears sometimes?

No. Intermittent detection is a warning sign. Save what you can first, then decide whether the drive needs replacement or professional recovery.