You turn the PC on and instead of your desktop you get a plain black screen with short white text, and Windows has stopped with error code 0xc0000001:
Your PC/Device needs to be repaired A required device isn't connected or can't be accessed. Error code: 0xc0000001 You'll need to use recovery tools. If you don't have any installation media (like a disc or USB device), contact your PC administrator or PC/Device manufacturer.
The wording is designed to make you reach for the reinstall button. Don’t — not yet. 0xc0000001 is one of the most recoverable startup errors there is, and in most cases your files, applications and settings are completely intact. The machine simply cannot assemble the pieces it needs to begin loading Windows.
This guide covers every fix that works, in the order a technician would try them, with the exact commands. It also covers the branch most guides skip — what to do when Startup Repair fails and the boot files are not the problem.
Quick answer — what usually fixes 0xc0000001
- Unplug every external device — external drives, USB sticks, SD cards, docks, printers. Then check the boot order in BIOS.
- Run Startup Repair once from the Recovery Environment.
- Rebuild the boot files with
bcdboot, or withbootrec /fixmbr,/fixboot,/scanos,/rebuildbcd. - Repair the disk:
chkdsk C: /f /r. - Repair the Windows image offline:
DISM /RestoreHealththensfc /scannow. - If none of that works, suspect a corrupted registry hive — restore it or roll back with System Restore.
Rather not type commands at a recovery prompt? Let the toolkit run the whole sequence.
What error code 0xc0000001 actually means
0xc0000001 is a Windows boot status code, not a blue-screen stop code. It is raised by the Windows Boot Manager before the kernel loads, and it means: a required component could not be accessed, so startup cannot continue.
That “required component” is one of four things, and knowing which one saves a lot of time:
| Cause | Typical trigger | Fix |
|---|---|---|
| Boot files / boot sector | Interrupted update, disk write error, cloned drive, dual-boot removal | Methods 3 and 4 |
| Corrupt system files | Failed update, malware, forced shutdown during servicing | Method 6 |
| Damaged registry hives | Power loss while writing, failing disk, bad shutdown | Method 7 |
| Disk or hardware fault | Failing drive, loose cable, SATA mode change in BIOS | Methods 1 and 5 |
Is this the same as a BCD error?
Not quite, and the distinction matters. Windows shows the same “Your PC/Device needs to be repaired” screen for a whole family of codes. If yours ends in something other than 0xc0000001 — for example 0xc000000f, 0xc000000e, 0xc0000034, 0xc0000098, 0xc000014c, 0xc00000bb or 0xc0000225 — you are looking at a boot-configuration problem, and you should follow the dedicated BCD errors guide instead.
This page is about 0xc0000001: the cases where the boot configuration is often fine, but the files, hives or disk behind it are not.
Two rules before you start. First, if the drive is making clicking, grinding or buzzing noises, stop immediately — power down and treat it as a data-recovery job rather than running repairs. Second, if your drive uses BitLocker, have your 48-digit recovery key to hand; you cannot repair a locked volume offline without it.
Method 1 — Strip the PC down and check the BIOS
This costs two minutes and fixes more cases than anyone expects. The error text mentions a device that “isn’t connected or can’t be accessed” — and that is literally true when Windows is trying to start from the wrong disk.
- Unplug everything external. External hard drives, USB sticks, SD cards, card readers, docks, printers, webcams. Leave only power, display, keyboard and mouse.
- Enter BIOS/UEFI setup (F2, Del, F10 or Esc) and confirm your Windows drive is first in the boot order. A USB stick plugged in at the wrong moment is a very common cause of this error.
- While you are there, check the SATA / storage mode (AHCI, RAID or IDE). If a BIOS update changed it, set it back to the value Windows was installed with — usually AHCI.
- If you have a desktop, power down and reseat the drive’s SATA and power cables. A loose cable produces intermittent, confusing failures.
Method 2 — Run Startup Repair, but do not repeat it endlessly
Startup Repair fixes a specific and limited set of startup problems. Run it once, and if it fails, move on — running it five times will not change the outcome.
- Get into the Recovery Environment: force three interrupted boots by holding the power button for 10 seconds as the logo appears, three times. On the fourth start, Windows offers recovery. If that does not work, use one of the other ways in.
- Choose Troubleshoot → Advanced options → Startup Repair.
- Reboot when it finishes, whether or not it reports success.
If it reports that it could not repair your PC, the log it wrote is genuinely useful — here is how to read it and what to do next.
Method 3 — Rebuild the boot files
Even when the BCD store itself is intact, damaged boot files or a bad boot sector produce 0xc0000001. Open Command Prompt from the recovery menu.
Step 1: Find your volumes
diskpart list vol exit
Drive letters in recovery often differ from the ones you know. Note the volume containing your Windows folder, and the small FAT32 volume (100–300 MB) that is the EFI System Partition.
Step 2: Rebuild with bcdboot
bcdboot C:\Windows /s S: /f UEFI
Substitute your own letters. On a Legacy BIOS / MBR machine use:
bcdboot C:\Windows /s S: /f BIOS bootsect /nt60 C: /mbr
Step 3: If that fails, use bootrec
bootrec /fixmbr bootrec /fixboot bootrec /scanos bootrec /rebuildbcd
bootrec /fixboot returning Access is denied and /rebuildbcd returning Element not found or The system cannot find the path specified are all known, and each has a specific fix: see Element not found, path not found, and the full BCD rebuild procedure.
Method 4 — Check the file system
chkdsk C: /f /r
/f fixes logical errors and /r also scans for and recovers from bad sectors. On a large drive /r can take several hours, so run it when you can leave the machine alone. If it reports recovering data from bad sectors, treat the drive as suspect and back up as soon as you can.
Method 5 — Repair the Windows image offline
If core system files were damaged, restoring them often clears 0xc0000001 outright. Run DISM before SFC — DISM repairs the component store that SFC restores from.
DISM /Image:C:\ /Cleanup-Image /RestoreHealth sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows
Back on the desktop, finish with the online versions:
DISM /Online /Cleanup-Image /RestoreHealth sfc /scannow
DISM takes 10–30 minutes and may look stuck at 20% or 40%. If it fails with 0x800f081f or 0x80073712, use the DISM and SFC error guide, or the complete system-file repair walkthrough.
Method 6 — Revert a stuck update
An update that never committed leaves pending operations that block startup. From recovery:
dism /Image:C:\ /Cleanup-Image /RevertPendingActions
Or use the menu route: Troubleshoot → Advanced options → Uninstall Updates, starting with the latest quality update and then the latest feature update.
Method 7 — Repair or restore the registry hives
This is the branch most guides skip, and it is exactly why some 0xc0000001 cases survive a perfectly executed BCD rebuild. Windows keeps its core configuration in hive files under C:\Windows\System32\config. If SYSTEM, SOFTWARE or DEFAULT is damaged, the boot process cannot continue — and no amount of boot-file repair will help.
Option A: Check whether a backup copy exists
dir C:\Windows\System32\config\RegBack
If the files there are non-zero in size, you can restore them. Back up the current hives first, then copy:
mkdir C:\RegBackup copy C:\Windows\System32\config\* C:\RegBackup\ copy C:\Windows\System32\config\RegBack\* C:\Windows\System32\config\
Heads-up: since Windows 10 version 1803, automatic hive backups to RegBack are disabled by default, so that folder is usually empty on modern systems. If it is, use Option B.
Option B: Roll back with System Restore
System Restore restores the registry hives along with system files and drivers, and leaves your personal files completely alone.
- Troubleshoot → Advanced options → System Restore.
- Choose a restore point dated before the problem started.
- Use Scan for affected programs to review what changes, then confirm.
If there are no restore points, protection was disabled — worth switching on once you are back up. Then try the toolkit’s boot-file and system-file repairs, or continue to Method 8.
Method 8 — Test the hardware properly
If every software repair fails, stop and verify the hardware. A drive that is intermittently failing will defeat every fix on this page.
- Check the drive’s health. The complete method is in how to check hard disk health in Windows 10 & 11.
- Run a memory test. Boot from recovery media or use Windows Memory Diagnostic; faulty RAM corrupts data on the way to the disk and causes exactly this class of error.
- Reset the BIOS to defaults, then re-apply only the boot order and SATA mode. Undervolting, XMP and aggressive power settings can destabilise storage.
- Disable Fast Startup once you are back on the desktop — Control Panel → Power Options → Choose what the power buttons do → Change settings that are currently unavailable, and untick Turn on fast startup. It caches the kernel session to disk and is implicated in a long list of startup failures.
The one-click option: repair 0xc0000001 without memorising commands
Let VMTechs Boot Repair Toolkit do the whole recovery sequence
Everything above — identifying the right partitions, rebuilding boot files, checking the disk, repairing the component store, restoring system files, reverting stuck updates — is precisely what the toolkit runs, in the correct order, with a live log showing each step and its result.
Why it is faster than doing it by hand:
- It scans before it changes anything — 33 checks across disk layout, boot configuration, recovery environment, registry, system files and diagnostics, in one dashboard.
- It matches your exact error to the right repair. Pick
0xc0000001from the error list and it runs the sequence that applies to it, instead of making you guess. - It works when Windows will not start. Run it from WinRE, or from the rescue USB it can build for you on any working PC.
- It repairs the parts that are hard to reach by hand — system files validated against Microsoft’s own signatures, offline service and driver management, offline crash-dump analysis, and log analysis that reads
SrtTrail.txt, CBS, DISM and ReAgent to name the root cause. - Nothing is deleted. Standard boot repairs never format the Windows partition or reinstall Windows. Your files, apps and settings stay exactly where they are.
- Every high-impact action is reversible — it backs up first, asks for confirmation, and shows you the undo path before it runs.
Get VMTechs Boot Repair Toolkit →
One portable file for 64-bit Windows 10 & 11 · Free features included · See every repair option
Fix 0xc0000001 in three steps
- Create a rescue USB on any working PC — open the toolkit and choose Create Rescue USB. It builds a bootable stick from that PC’s recovery image or a Windows 10/11 ISO. Nothing is downloaded and no Windows ADK is required.
- Boot the broken PC from it (or into WinRE if it still offers that) and run the toolkit. Let the environment scan finish — it finds your Windows installation, disk layout and encryption status automatically.
- Select
0xc0000001from the error list and press Run Selected. The guided repair runs boot-file repair, BCD rebuild, DISM, SFC and disk checks in the correct order. Reboot when it reports success.
Frequently asked questions
Will fixing 0xc0000001 delete my files?
No. Rebuilding boot files, repairing the BCD, running DISM/SFC, chkdsk and System Restore all leave your personal files untouched. The only destructive option is a clean reinstall, which you should not need.
Can I fix this without a Windows installation disc or USB?
Often yes. Interrupting the boot three times brings up the Recovery Environment, which includes Startup Repair, System Restore, Safe Mode and Command Prompt. A rescue USB is better — it gives you driver, service and dump-analysis tools too — but it is not always required.
Startup Repair says it could not repair my PC. Now what?
That is normal for this error, and it means the problem is outside what Startup Repair fixes. Read the log it produced and work through Methods 3 to 7 — here is how.
The error appeared after I cloned my drive or upgraded to an SSD.
Very common. The clone copied the data but the boot files on the new disk were not configured for it, or the SATA mode changed. Rebuild the boot files with bcdboot (Method 3) and confirm the BIOS boot order points at the new drive.
It boots now, but I am worried it will come back.
Two things make that far less likely: check the drive’s SMART health, and turn off Fast Startup. If the drive shows reallocated or pending sectors, replace it by cloning rather than reinstalling — that way your setup survives the move.
Conclusion
Error code 0xc0000001 looks like a dead machine and is usually a few repairable components away from a working one. Work down the list in order: strip the hardware back, run Startup Repair once, rebuild the boot files, check the disk, repair the Windows image, and if all of that fails, look at the registry hives and the drive’s health.
Take note of every change so you can reverse it, and resist the reinstall until you have tried these. If you would rather not spend the evening at a recovery prompt, the VMTechs Boot Repair Toolkit runs the same sequence automatically and tells you exactly what it found.
