Error Code 0xC00185 | Fix Steps That Actually Work

When this shows up, Windows is failing before the sign-in screen. You might see a “Recovery” screen, a restart loop, or a file path like \Windows\System32\ntoskrnl.exe. The common thread is simple: Windows can’t complete the handoff from firmware (UEFI/BIOS) to the operating system.

This guide walks you through a safe order of fixes that starts gentle and gets deeper only when needed. You’ll know what each step changes, what to expect on screen, and when it’s smarter to switch to data rescue instead of repeated repair attempts.

What Error Code 0xC00185 Usually Means

Windows startup relies on a small set of files and settings that tell the PC where Windows lives and how to launch it. When those files are missing, damaged, or on a disk that can’t be accessed, Windows stops early and throws a recovery status code.

On many systems, the message is tied to the Boot Configuration Data (BCD). That data acts like a map for boot. If the map is unreadable, Windows can’t locate the right loader, the right partition, or the right set of startup instructions.

Typical triggers include a hard power cut, a sudden crash during updates, a disk with bad sectors, or a BIOS setting change that alters how the drive is presented. The fixes below aim to restore that boot map, confirm the drive is reachable, then repair Windows files once the PC can see its own installation again.

Error Code 0xC00185 Fix Steps When Windows Won’t Start

Work through these in order. After each step, reboot once and see if Windows reaches the sign-in screen. If you get back into Windows, skip to the prevention section near the end.

Get Into Windows Recovery (WinRE)

If you already land on a Recovery screen, you’re in the right place. If you don’t, use one of these paths to reach WinRE.

• Interrupt boot three times — Power on, wait for the spinning dots or logo, then hold the power button to shut down; repeat until Recovery loads.
• Use a Windows USB installer — Boot from the USB, pick Repair your computer, then open Troubleshoot.
• Use built-in OEM Recovery — Tap the vendor key (often F11, F12, or Novo) at power-on to open Recovery options.

Run Startup Repair First

Startup Repair is the cleanest first move because it attempts fixes without you typing commands.

1. Open Startup Repair — WinRE → Troubleshoot → Advanced options → Startup Repair.
2. Select your account — Pick the admin account when asked, then enter the password if prompted.
3. Reboot after it completes — If it reports it couldn’t repair, move on to the next section.

Rebuild Boot Files From Command Prompt

If Startup Repair fails, rebuild the boot records and the BCD. This is the step that most directly targets the reason the code appears.

1. Open Command Prompt — WinRE → Troubleshoot → Advanced options → Command Prompt.
2. Find the Windows drive letter — Type dir c:, then dir d: until you see the Windows folder.
3. Run boot repair commands — Type these lines one at a time, pressing Enter after each:

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

If /fixboot returns “Access is denied,” you can often still rebuild BCD using bcdboot once you know your Windows drive letter.

bcdboot X:\Windows

Replace X: with the letter that contains your Windows folder. Reboot and test.

Check Disk And System Files Offline

If the boot map rebuilds but Windows still won’t start, the disk or system files may be damaged. These checks run from WinRE against your offline Windows installation.

1. Run a disk scan — In Command Prompt, run chkdsk X: /f /r using the Windows drive letter.
2. Repair system files — Run sfc /scannow /offbootdir=X:\ /offwindir=X:\Windows.
3. Reboot and retest — If it boots, let Windows settle for a minute before launching heavy apps.

Deeper Recovery Moves When Repair Keeps Failing

If the PC keeps returning to Recovery, shift to actions that roll back recent changes. This is a good path when the problem started right after a driver install or update cycle.

Uninstall Recent Updates From WinRE

Windows updates come in two main types: small monthly quality updates and larger feature updates. Try removing the small one first.

1. Open update rollback — WinRE → Troubleshoot → Advanced options → Uninstall Updates.
2. Remove the latest quality update — Reboot and test startup.
3. Remove the latest feature update — Do this only if the quality rollback didn’t change anything.

Use System Restore If It Exists

System Restore rolls back system settings and drivers while keeping personal files. It only works if restore points were created earlier.

1. Open System Restore — WinRE → Troubleshoot → Advanced options → System Restore.
2. Select a restore point — Pick a point dated before the boot failures began.
3. Let it finish and reboot — The first reboot can take longer than normal.

Try Safe Mode For A Targeted Cleanup

If Windows can start in Safe Mode, you can remove a problematic driver, undo a startup app, or run diagnostics from inside Windows.

1. Open Startup Settings — WinRE → Troubleshoot → Advanced options → Startup Settings → Restart.
2. Choose Safe Mode — Press 4 for Safe Mode or 5 for Safe Mode with Networking.
3. Remove the recent change — Uninstall the driver/app you added right before the issue began.

Check BIOS And Hardware Before You Keep Repairing

If WinRE can’t see your Windows drive, or repairs claim no Windows installation exists, pause and confirm the hardware path is solid. Endless repair runs on a failing drive can make recovery harder.

Confirm The Drive Shows Up In BIOS

Restart and enter BIOS/UEFI (often Del, F2, or Esc). Look for storage or NVMe information. If the drive is missing, Windows repair tools won’t succeed until the drive is detected.

• Reseat the drive — Power off, unplug, and reseat the NVMe/SATA connection if you’re comfortable opening the system.
• Try another port or cable — For SATA drives, swap the cable and port to rule out a flaky link.
• Run vendor diagnostics — Many BIOS menus have a basic storage test; use it if present.

Check Boot Mode And Boot Order

A boot mode mismatch can block startup, especially after a BIOS reset.

• Use UEFI when Windows was installed in UEFI — Most Windows 10/11 installs use UEFI with GPT partitions.
• Place Windows Boot Manager first — If you see it, set it above USB and network boot.
• Disable unused boot options — Removing network boot from the top can stop confusing loops.

Review Storage Controller Settings

Switching SATA mode (AHCI vs RAID/Intel RST) can make Windows unable to access the disk even if the disk is detected. If you changed that setting recently, set it back to what it was when Windows last booted normally.

After You Boot, Lock In A Clean Finish

Once Windows loads again, don’t rush back to normal use. Spend a few minutes confirming the system is stable and the disk is healthy. That reduces the chance of seeing error code 0xc00185 again on the next restart.

Run These Health Checks In Windows

1. Check the disk — Open Terminal as admin and run chkdsk C: /scan.
2. Repair Windows files — Run sfc /scannow, then reboot once.
3. Use DISM for component repair — Run DISM /Online /Cleanup-Image /RestoreHealth.

Back Up Before The Next Update Cycle

A boot failure is a reminder that your files need a safety copy that does not rely on that same Windows install. Aim for one local backup (external drive) and one cloud copy if you use those services.

• Copy irreplaceable folders — Documents, Photos, Desktop, and any project folders you can’t recreate.
• Create a restore point — Turn on System Protection and create one before major driver changes.
• Keep a recovery USB — A current installer USB makes WinRE access painless.

Reduce The Usual Triggers

Most boot data corruption starts with abrupt shutdowns or disk trouble. You can’t prevent every outage, but you can reduce the odds.

• Use proper shutdown — Let Windows close cleanly before cutting power.
• Watch free space — Keep breathing room on the system drive so updates and logs don’t choke.
• Update storage firmware — Check your SSD maker’s tool for firmware updates tied to stability.

When To Switch From Repair To Data Rescue

If the drive disappears in BIOS, makes clicking sounds (HDD), or causes WinRE to freeze during scans, treat it like a failing disk. At that point, repeated repair attempts can stress the hardware and reduce the chance of a clean file copy.

If you need files first, use a second PC and a USB adapter/enclosure to connect the drive, then copy your data off. For BitLocker-protected drives, you’ll need the recovery key to access files. If the drive is readable only in bursts, prioritize your most valuable folders first and copy in smaller batches.

If you don’t have another PC, you can boot a Linux live USB and copy files to an external drive. If the disk is not readable there either, professional recovery may be the safer path. That choice costs money, so make it only after you confirm the drive is failing, not just misconfigured.

If you’re still stuck after the steps above, write down what you see on screen, including any file paths and whether WinRE detects your Windows installation. That info lets a technician diagnose fast without guesswork, and it keeps you from repeating the same repair loop.

Most people who hit this wall get back to a working PC once the boot map is rebuilt and the disk is confirmed healthy. If the code returns again after a week or two, treat it as a disk warning and plan a drive replacement before you’re forced into it.

Send us your feedbackTell us what you thought about this post

Name * Email *

Your comment *

Quick check — what is …? *

Send feedback