Your PC restarts, and instead of the desktop you get a black recovery screen with the stop code 0xc000000f and a line pointing at \Windows\system32\winload.exe or \Boot\BCD. It looks fatal, but in most cases nothing on your drive is actually gone; the boot instructions that tell Windows where to load from are damaged. This guide walks through the fixes in order, starting with the safest automatic repair and only moving to manual command-line work if the easy options fail.
What the 0xc000000f Stop Code Is Actually Telling You
Microsoft documents stop code 0xc000000f alongside messages such as "File: \Windows\system32\winload.exe ... a required file is missing or contains errors" and "File: \Boot\BCD ... The Boot Configuration Data for your PC is missing or contains errors." Reading those lines tells you which part of the startup chain broke.
The documented cause is one of three things: the Boot Configuration Data (BCD) is corrupted, the reference to the device or OS device inside the BCD is missing or unknown, or a critical system binary is missing or corrupted. In plain terms, Windows knows it should start but can no longer find or trust the files that load it.
This matters because it points you toward the right fix. The answer is to repair the boot configuration or the system files, not to wipe the drive and reinstall. Work through the steps below before you consider anything more drastic.
Getting Into the Windows Recovery Environment
Every fix here runs inside the Windows Recovery Environment (WinRE), so the first job is reaching it. If you can still get to the sign-in or Start screen, hold the Shift key while you select Power > Restart.
If Windows still loads to the desktop, you can also go through Settings. On Windows 11, open Settings > System > Recovery and under Advanced startup select Restart now. On Windows 10, open Settings > Update & Security > Recovery and under Advanced startup select Restart now.
If the PC will not boot at all, Windows launches WinRE automatically after it fails to start multiple times. You can force this by powering the machine off during the Windows logo on two start attempts, then starting it a third time.
If WinRE still will not open, boot from Windows installation or recovery media instead. Create that media with the official Media Creation Tool on another working PC, boot from it, and choose Repair your computer to reach the same recovery menu.
Fix 1: Let Startup Repair Do the Work Automatically
This is the easiest and safest place to begin, because it requires no commands and is built to diagnose and fix the kinds of startup problems behind 0xc000000f. In WinRE, select Troubleshoot > Advanced options > Startup Repair > Restart.
Startup Repair is a built-in Windows recovery tool that automatically scans for and repairs problems that stop Windows from starting, including damaged boot files. Letting it run is a low-risk first attempt that often clears the BCD and winload errors you saw on the screen.
Let it run fully and restart. If your device uses BitLocker, you will need your recovery key to proceed. This fix applies to both Windows 10 and Windows 11.
Fix 2: Roll Back a Bad Update From the Recovery Menu
If the boot failure started right after Windows installed an update, removing that update is the next thing to try. In WinRE, select Troubleshoot > Advanced options > Uninstall Updates.
From there, choose either Uninstall latest quality update or Uninstall latest feature update, depending on which type lined up with the failure. This is the documented WinRE path for removing a problem update when Windows will not boot.
Be aware that some updates cannot be uninstalled this way, so the option may not always succeed. This path applies to both Windows 10 and Windows 11.
Fix 3: Use Safe Mode to Undo a Bad Driver
If you suspect a driver triggered the failure rather than an update, Safe Mode gives you a way in. In WinRE, select Troubleshoot > Advanced options > Startup Settings > Restart.
When the menu appears, press 4 (or F4) for Safe Mode, or press 5 (or F5) for Safe Mode with Networking if you need internet access. Safe Mode starts Windows with only essential drivers and services.
If the problem disappears in Safe Mode, you can remove or roll back the driver that was causing it. If the device is encrypted, you will need your BitLocker key to reach Safe Mode. This applies to both Windows 10 and Windows 11.
Fix 4: Rebuild the Boot Records With bootrec
When the automatic options have not cleared the error, it is time to repair the boot records by hand. In WinRE, choose Troubleshoot > Advanced options > Command Prompt, then run the following commands in order.
- 1.
bootrec /FixMbrwrites a Windows-compatible MBR to the system partition without overwriting the partition table. - 2.
bootrec /FixBootwrites a new boot sector to the system partition. - 3.
bootrec /ScanOsscans all disks for Windows installations and shows entries that are not currently in the BCD store. - 4.
bootrec /RebuildBcdscans all disks for installations and lets you add them to the BCD store, rebuilding the BCD.
These commands directly target the \Boot\BCD corruption behind 0xc000000f. The documentation for these bootrec switches is published on a page marked for Windows Vista and Windows 7, but the tool itself is still present and usable in the Windows 10 and Windows 11 Recovery Environment.
Fix 5: Scan the Disk for File-System Errors With chkdsk
If files or the BCD appear corrupted, a disk check can find and fix the underlying problem. A typical example for checking a drive and fixing errors is chkdsk d: /f. The full documented syntax is chkdsk [<volume>[[<path>]<filename>]] [/f] [/v] [/r] [/x] [/i] [/c] [/l[:<size>]] [/b] [/scan] [/forceofflinefix] [/perf] [/spotfix] [/sdcleanup] [/offlinescanandfix] [/freeorphanedchains] [/markclean] [/?].
The /f switch fixes file-system errors and requires the drive to be locked, while /r additionally locates bad sectors, recovers readable information, and includes everything /f does. Run without parameters, chkdsk only reports status and changes nothing.
From the WinRE Command Prompt against the offline system volume, the documented form is CHKDSK /f D:. Replace D: with your actual system-volume letter, which you can identify by running BCDEdit with no parameters and reading the value next to osdevice in the Windows Boot Loader section.
Fix 6: Repair System Files With DISM and SFC
If you managed to get Windows to boot, for example through Safe Mode, you can repair corrupted system files from within Windows. Open an elevated Command Prompt by typing cmd in the Search box, right-clicking Command Prompt, and selecting Run as administrator.
Run the two tools in this order. First run DISM.exe /Online /Cleanup-image /Restorehealth, which repairs the Windows component store, then run sfc /scannow, which scans all protected system files and replaces corrupted ones with a cached copy.
Microsoft documents running DISM before SFC, because DISM repairs the component store that SFC draws its known-good files from. Do not close the window until the scan reaches 100%. The System File Checker tool applies to Windows Vista, 7, 8/8.1, 10, and 11.
Fix 7: Run SFC, DISM, and chkdsk Offline From WinRE
When Windows still will not start at all, you can run the same repairs against the offline installation from the Command Prompt. Boot from installation media, choose Repair your computer, then go to Troubleshoot > Advanced options > Command Prompt to get there.
First, run BCDEdit to find the system volume's drive letter, shown next to osdevice. Then run the offline checks in order, replacing D: with your identified volume letter throughout.
- 1.
CHKDSK /f D:to check and fix file-system errors on the offline system volume. - 2.
SFC /scannow /offbootdir=D:\ /offwindir=D:\windowsto run an offline System File Check against the offline Windows volume. - 3.
DISM /image:D:\ /cleanup-image /restorehealthto restore the offline image health.
This is the documented offline equivalent of the DISM and SFC step for when the operating system cannot start. Note that the offline DISM command is documented as applying to Windows Server 2012 and later.
Frequently Asked Questions
Does fixing 0xc000000f erase my files?
The repairs in this guide target the boot configuration and system files, not your personal data. Startup Repair, bootrec, chkdsk, SFC, and DISM are designed to repair the existing installation rather than wipe it. The documented cause of 0xc000000f is corrupted Boot Configuration Data or a missing system binary, which is why the recommended fix is repair rather than reinstall.
What is the difference between the BCD error and the winload.exe error?
Both appear under the same 0xc000000f stop code, but they name different files. The "\Boot\BCD" message means the Boot Configuration Data for your PC is missing or contains errors, while the "\Windows\system32\winload.exe" message points to a required boot file that is missing or contains errors. The underlying causes overlap, so the same sequence of fixes addresses both.
Do I need my BitLocker recovery key?
If your device uses BitLocker, you will need your recovery key for Startup Repair and to reach Safe Mode. Have that key ready before you start so you are not stuck partway through the process. The key is tied to the account used to set up the device, so locate it before you begin.
Why run DISM before SFC?
DISM repairs the Windows component store that SFC draws its known-good files from. If you run SFC first against a damaged component store, it may not have a clean copy to restore from. Running DISM.exe /Online /Cleanup-image /Restorehealth first, then sfc /scannow, gives the best chance of a complete repair.
What if I cannot even reach the recovery menu?
Windows launches WinRE automatically after it fails to start multiple times, and you can force this by powering off during the Windows logo on two attempts, then starting a third time. If that still does not work, create installation or recovery media with the official Media Creation Tool on another PC, boot from it, and choose Repair your computer to reach the same tools.
