Error code 0xc000000f on boot indicates a Windows boot problem, typically corrupted Boot Configuration Data (BCD) or a missing/corrupt system file. To both get the PC booting again and recover the document, follow these steps in order of least to most complex.
- Try standard recovery options
- If Windows shows “Automatic Repair” or “Startup Repair” on boot, allow it to run.
- If you have a recent full system backup, restoring from that backup is the simplest way to get back to a working system (and your documents) without manual repair.
- If Windows will not boot: attach the disk to another PC and copy the document
If the document is critical, recover it before attempting deeper repairs:
- Power off the affected PC.
- Physically remove the system drive and attach it to another Windows PC as a secondary/data disk (via SATA/USB adapter or internally).
- On the working PC, open Disk Management and ensure the attached disk is online and has drive letters.
- Browse to the user profile on the attached disk (for example,
\Users\<username>\Documents or the folder where the document was saved) and copy the document to the working PC or external storage.
Once the document is safe, proceed to repair the boot issue.
- Repair boot error 0xc000000f (BCD corruption or missing system file)
A. Identify Windows and Boot partitions
- With the problem disk still attached to the working PC as a data disk, open Disk Management.
- Identify:
- Windows partition: contains a
Windows folder and is usually the largest partition.
- Boot partition: contains a hidden
Boot folder (size typically 300–500 MB). Enable viewing hidden and protected system files in File Explorer to see it.
B. Repair Boot Configuration Data (BCD)
Use these steps when the error mentions \Windows\system32\winload.exe or \Boot\BCD with status 0xc000000f:
- Open an elevated Command Prompt on the working PC.
- Run
bcdedit against the BCD store on the attached disk to list entries. For example (Generation 1 firmware):
bcdedit /store <BootPartitionLetter>:\Boot\BCD /enum /v
For Generation 2 firmware:
bcdedit /store <BootPartitionLetter>:\EFI\Microsoft\Boot\BCD
- Note the identifier for Windows Boot Loader (either
{default} or a GUID).
- Repair the BCD entries so that
device and osdevice point to the correct Windows partition, using the documented bcdedit commands for your VM/PC generation. This step fixes most BCD corruption issues.
- When finished, detach the disk from the working PC and reinstall it in the original PC, then try booting again.
C. If the error mentions a specific driver file (for example, \Windows\System32\drivers\<binary>.sys)
- With the disk attached to the working PC, run a file system check on the affected volume:
chkdsk <DriveLetter>: /F
- On the attached disk, go to the path shown in the error (for example,
\Windows\System32\drivers).
- Rename the problematic file:
ren <binary-name>.sys <binary-name>.sys.old
- Search for a clean copy of that driver in the WinSxS store on the same disk:
dir <binary-name> /s
- From the latest version found in
\Windows\WinSxS\..., copy it back to \Windows\System32\Drivers on the attached disk. For example:
copy <DriveLetter>:\Windows\WinSxS\<folder>\<binary-name>.sys <DriveLetter>:\Windows\System32\Drivers\
- If no suitable version exists in WinSxS, copy the file from another working Windows 10 installation that has the same OS and update level.
- Reinstall the disk in the original PC and boot.
If these steps do not restore boot, and there is no usable backup, a clean reinstall of Windows may be required. Ensure the recovered document is stored safely on external media before reinstalling.
References: