Rightek Rescue · Guides · "Your PC needs to be repaired"
Blue "Your PC needs to be repaired" screen? Here's how to fix 0xc000000f
That blue Recovery screen usually means Windows can't find the files that tell it how to boot — the boot configuration is missing or damaged. Your Windows and your files are still on the drive; the PC just can't reach them yet.
What you're seeing
- A blue Recovery screen: “Your PC/Device needs to be repaired”
- Error code
0xc000000f,0xc0000034, or0xc0000098 - “The Boot Configuration Data for your PC is missing or contains errors”
- A missing file such as
\Boot\BCDorwinload.efi
Why it happens
- The Boot Configuration Data (BCD) store is missing or corrupt
- The EFI System Partition got damaged (often after a failed update or a clone to a new drive)
- A critical boot file (
winload.efi,bootmgfw.efi) is gone - The drive's boot order or partition markers were changed
Fix it yourself — the manual steps
- Boot from a Windows installation USB — choose Repair your computer → Troubleshoot → Advanced options.
- Try Startup Repair first.
- If that fails, open Command Prompt and rebuild the boot store:
bootrec /scanos,bootrec /rebuildbcd,bootrec /fixmbr,bootrec /fixboot. - For UEFI PCs you may need
bcdboot C:\Windows /s <ESP>: /f UEFI— getting the ESP letter right here matters. - Reboot and remove the USB.
What the code is telling you
The three codes on this screen are not interchangeable, and each points somewhere slightly different:
- 0xc000000f — the boot manager could not read the Boot Configuration Data. The BCD store is missing, corrupt, or on a partition it can no longer reach.
- 0xc0000034 — the BCD is readable but contains no valid entry for Windows. Common after a failed feature update or a partition change.
- 0xc0000098 — the entry exists but points at something that is not there.
All three are boot configuration rather than Windows itself, which is why they are among the more recoverable failures. Your installation and your files are usually completely intact behind them.
Getting the EFI partition letter right
This is the step where manual attempts stall. On a UEFI machine the boot files live on the EFI
System Partition, which deliberately has no drive letter — so bootrec /fixboot
returns Access is denied, and most guides stop there without saying why.
The partition needs a temporary letter first. From the Command Prompt:
diskpartlist disk, thenselect disk 0(whichever holds Windows)list partition— the EFI one is the small FAT32 partition, typically 100–500 MB, labelled Systemselect partition 1(whichever that is), thenassign letter=Sexit
Then rebuild the boot files onto it, with your Windows volume identified — remember it is usually not C: in here:
bcdboot D:\Windows /s S: /f UEFI
Getting either letter wrong writes boot files to the wrong place. It is recoverable, but it turns a ten-minute job into an afternoon, and it is the reason this particular repair has a reputation.
The order that actually works
Running the bootrec commands in the wrong sequence wastes time. What works:
- Startup Repair first. It is automatic, safe, and handles the common case. Run it twice — it occasionally fixes a second fault on the second pass.
- Then
bootrec /scanosto confirm Windows is still found. If it reports zero installations, the problem is bigger than the BCD and rebuilding it will not help. - Then
bootrec /rebuildbcd, which offers to add what it found. /fixmbronly on Legacy/MBR systems. On a UEFI machine it does nothing useful, and it is in every guide regardless.
If it started after a clone or a disk change
Cloning is a common route here, and the cause is usually mundane: the boot entry points at a disk identifier that no longer exists, or the original drive is still connected and the firmware is booting that. Disconnect the source drive and check the boot order before running any repair — on more occasions than you would expect, that is the entire fix.
⚡ The one-click way: let Rightek Rescue do it
Rescue rebuilds the boot store and repairs the boot files automatically — in the right order, no commands. On any working PC: download Rescue, put it on a USB (one click makes it bootable), boot the affected PC from it, and choose Fix My PC. It finds the cause and repairs Windows in place — your files, accounts and programs stay where they are. Not sure what's wrong? It tells you free before it fixes anything.
FAQ
What does 0xc000000f mean?
It means Windows couldn't read the Boot Configuration Data - the small database that tells the PC how to start Windows. It's a boot problem, not lost data.
Will I lose my files?
Very unlikely. This is a boot/system problem, not a data problem - your files are almost always intact. Rescue repairs the system side and leaves your personal files where they are. Any repair on a damaged drive carries some risk, so copy irreplaceable files off first if you can.
Do I need a second computer?
Yes - any working PC to download Rescue and make the USB. Any USB stick 8GB+ works.
Which Windows versions are supported?
Windows 10 and 11. Rescue runs from the USB, outside your broken Windows, so it works even when Windows won't start.
Why does bootrec /fixboot say access is denied?
Because on UEFI systems the EFI System Partition has no drive letter, so the command cannot reach it. It is not a sign of a worse problem. Assign a temporary letter with diskpart, then use bcdboot to write the boot files to it.
Do these repairs put my files at risk?
No. Rebuilding the boot configuration writes to small structures on the system partition, not to the volume holding your documents. Nothing in this process formats, repartitions or overwrites your data.
bootrec /scanos found zero Windows installations. What does that mean?
That the boot configuration is not your only problem — either the Windows partition is not being seen at all, which points at the storage driver or the disk itself, or the installation is genuinely damaged. Rebuilding the BCD will not help until that is resolved.
Is 0xc000000f different from 0xc0000034?
Yes, slightly. 0xc000000f means the boot manager could not read the BCD store at all. 0xc0000034 means it read it but found no valid Windows entry in it. Both are boot configuration faults and both usually repair, but the second more often follows a failed feature update or a partition change.