Fix STATUS_UNSUCCESSFUL (0xC0000001) Boot Error in Windows 10/11
The 0xC0000001 error halts boot with 'Operation Failed.' Start with a quick reboot, then check disk integrity, and finally repair boot files. I'll walk you through each step.
What the 0xC0000001 Error Means
You're staring at a black screen with 'STATUS_UNSUCCESSFUL' and error code 0xC0000001. This usually shows up right when Windows tries to load — after the BIOS logo, before the spinning dots appear. I've seen this happen most often after a sudden power loss, a failed Windows update, or a corrupted driver install. It's not a hardware failure, so don't panic.
The error means the Windows bootloader or a critical system file got corrupted. The fix is straightforward if you follow the steps in order. Start with the simplest one — it works more often than you'd think.
Quick Fix: Hard Reboot (30 seconds)
I know it sounds too simple, but a hard reboot clears transient memory states that sometimes trip this error. Hold the power button down for 10 seconds until the machine shuts off completely. Wait 10 seconds, then press the power button again. If you see the Windows logo and it boots normally, you're done. If the error comes back, move to the next step.
Moderate Fix: Run chkdsk from Recovery Environment (5 minutes)
The most common cause behind 0xC0000001 is file system corruption on your boot drive. chkdsk scans and fixes it. You'll need to boot from a recovery drive or use Windows Recovery Environment (WinRE). Here's how to get there:
- Insert a Windows installation USB or recovery drive. If you don't have one, boot the PC, and as soon as you see the Windows logo, hold the power button to force shut down. Do this three times — Windows will automatically launch WinRE on the fourth boot.
- From WinRE, go to Troubleshoot > Advanced Options > Command Prompt.
- Type the following and press Enter:
chkdsk C: /f /r
If your system drive uses a different letter (sometimes D: or E: in WinRE), rundiskpart, thenlist volumeto find it. - Let chkdsk run — it can take 10-20 minutes on a large drive. It will repair bad sectors and fix file system errors.
- After it finishes, type
exitand restart the PC.
If chkdsk finds and fixes errors, the boot should work. If not, the bootloader itself is damaged. Keep going.
Advanced Fix: Rebuild Boot Configuration Data (15+ minutes)
The BCD (Boot Configuration Data) store tells Windows which partition to boot from. When it's corrupt, Windows throws 0xC0000001 before it even gets a chance to load. We'll rebuild it using bootrec commands.
Boot back into WinRE and open Command Prompt again. Run these commands in order:
bootrec /fixmbr— repairs the Master Boot Record. This isn't usually the full problem, but it doesn't hurt.bootrec /fixboot— writes a new boot sector. If it fails with 'Access is denied,' runbootsect /nt60 SYS /mbrinstead (this works on Windows 10/11).bootrec /scanos— scans for Windows installations on all drives. It should find your Windows partition and list it.bootrec /rebuildbcd— this is the key. It scans for Windows installations again and asks if you want to add each one to the BCD. Press Y (or A for all) and Enter.
After these run, restart. If the error persists, there's one more thing: a corrupted system file that survived chkdsk. From the same Command Prompt, run:
sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows
Replace C: with your actual system drive letter. This checks all protected system files and replaces bad ones. It can take 15-20 minutes. After it finishes, restart again.
When Nothing Works
If you're still stuck after all that, the problem might be a driver conflict from a recent update. Boot into Safe Mode by pressing F8 (or Shift + F8 during boot) and uninstall the last installed driver or roll back the latest Windows update. If Safe Mode doesn't load either, you're looking at a clean install — but I'd try a startup repair from WinRE first. Sometimes it catches things the manual commands miss.
Note: The 0xC0000001 error is almost never a hardware failure. Don't replace your hard drive or RAM before trying these steps. I've fixed dozens of these with just chkdsk and bootrec.
I hope this gets you back up and running. Drop a comment if you hit a snag — I read every one.
Was this solution helpful?