Fix Boot Error 0xc0000001 on Windows 10/11 (Exact Commands)

The fast answer. Error code 0xc0000001 means Windows couldn't read critical boot data — usually a corrupt system file, a damaged registry hive (especially the SAM), or a corrupted BCD store. The screen typically says "Your PC couldn't start properly" or "A required device isn't connected or can't be accessed." Boot into Windows Recovery (WinRE), open Advanced options → Command Prompt, and repair system files and the boot configuration:

bootrec /scanos
bootrec /rebuildbcd
sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows
chkdsk C: /f /r

Confirm the Windows drive letter inside WinRE before running these — it may not be C:. If it started right after a Windows Update, try Uninstall Updates from WinRE first.

Why this happens

Corrupted system files — an unclean shutdown, power loss, or interrupted update damaged Windows system files needed during boot. This is the most common cause.
Damaged SAM or registry hive — the Security Account Manager (SAM) file or another registry hive under C:\Windows\System32\config is corrupt or unreadable. Windows can't authenticate or load settings, so it halts at 0xc0000001.
Corrupted BCD store — the Boot Configuration Data is missing entries or pointing to a volume Windows can't reach, often after a failed update or unclean shutdown.
Disk errors or failing drive — bad sectors on the boot volume prevent Windows from reading system files or the registry.
Faulty RAM — bad memory can silently corrupt data written to disk, including boot-critical files and registry hives.

Step-by-step fix

Step 1 — Get into Windows Recovery (WinRE)

Force three failed boots (power on, then hold the power button to kill it as the Windows logo appears, three times) and Windows opens Automatic Repair. Or boot from a Windows 10/11 install USB and choose Repair your computer. Then go to Troubleshoot → Advanced options.

Step 2 — Run Startup Repair

In Advanced options, choose Startup Repair. It's Microsoft's first-line automated fix for this error and resolves many cases without manual commands. If it reports it couldn't repair the PC, continue below.

Step 3 — If it started after an update, uninstall the update

In Advanced options, choose Uninstall Updates → Uninstall latest quality update (or Uninstall latest feature update if a feature update was the last thing installed). This reverses most update-triggered cases without touching your data. Reboot and test before doing anything else.

Step 4 — Rebuild the boot configuration

In Advanced options → Command Prompt, run these in order:

bootrec /scanos
bootrec /rebuildbcd
bootrec /fixmbr
bootrec /fixboot

When bootrec /rebuildbcd finds a Windows installation, type Y to add it. Reboot and test.

UEFI/GPT note: on modern UEFI systems bootrec /fixboot can return "Access is denied" — that's expected. Use the bcdboot procedure instead to rebuild the EFI boot files.

Step 5 — Repair system files with SFC and DISM (offline)

Still in the WinRE Command Prompt, confirm which drive letter WinRE assigned to the Windows partition (it may not be C:). Run DISM to repair the component store, then SFC to fix individual system files:

dism /image:C:\ /cleanup-image /restorehealth

Wait for DISM to finish (it can take 15–30 minutes), then run SFC:

sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

Replace C: with the actual Windows drive letter if it differs in WinRE. Reboot and test.

Step 6 — Check disk health

If the error persists, the drive itself may have bad sectors corrupting system files or registry hives. From the WinRE Command Prompt:

chkdsk C: /f /r

Replace C: with the Windows drive letter. /f fixes file-system errors; /r locates bad sectors and recovers readable data. Reboot and test.

Step 7 — Try System Restore

If commands haven't resolved it and you have restore points, go to Advanced options → System Restore and pick a restore point from before the error started. This rolls back system files, drivers, and registry entries (including the SAM) without deleting personal files.

Step 8 — Test RAM

Faulty memory can silently corrupt the registry and system files, causing 0xc0000001 to keep coming back after every repair. From a WinRE Command Prompt, launch the Windows Memory Diagnostic:

mdsched.exe

Choose Restart now and check for problems. The test runs before Windows loads. If it reports errors, reseat or replace the faulty RAM module before re-running any of the above repairs.

Data safety: If the files on this machine matter and you don't have a backup, image the drive before you run repairs. chkdsk /r, SFC, DISM, and BCD rebuilds are normally safe, but a drive that's already failing can lose data when stressed by a full-surface scan. Take a full sector image to a known-good external disk first, and never run repairs on the only copy of irreplaceable data.

GRAM tip: The repair steps above run in Windows Recovery, which is already on the broken PC. Once the machine boots again, plug in GRAM — a free portable repair toolkit that runs from a USB inside Windows — to check disk SMART health, read the event logs and crash history, and let its AI agent confirm whether the root cause was a bad update, a failing drive, or bad RAM so the error doesn't come back.

Download GRAM free See AI pricing →

FAQ

Can I fix this without a second working computer?

Yes. Windows Recovery (WinRE) lives on the broken PC itself — force three failed boots to trigger Automatic Repair, or boot from any Windows install USB. All the Startup Repair, bootrec, SFC, DISM, and System Restore steps run inside WinRE. No second computer is required. (GRAM runs inside Windows rather than from boot media — use it once the machine boots to verify disk health and confirm the root cause.)

What does “A required device isn't connected or can't be accessed” mean?

Despite the wording, it almost never means a cable is loose. Windows uses this message when it can't read a file it needs during boot — typically a corrupt registry hive, damaged BCD, or bad sectors on the boot volume. The “device” is the logical volume or file, not a physical cable. Start with the software repairs above before suspecting hardware.

Will SFC, DISM, or chkdsk erase my files?

No. sfc replaces only corrupted protected system files. dism /cleanup-image /restorehealth repairs the Windows component store. chkdsk /f /r repairs the file system and can occasionally move damaged file fragments to FOUND.000 folders, but it does not wipe the drive. If the data is irreplaceable, image the drive first anyway.

Could this be a RAM problem?

Yes. Bad memory can corrupt data as Windows writes it to disk, damaging registry hives and system files in a way that survives every repair attempt. If you fix the error and it keeps coming back, run the Windows Memory Diagnostic (mdsched.exe) or a more thorough tool like MemTest86. Replace any faulty module before re-running repairs.