Windows 11 Error 0xC0000185: How to Fix It

Windows 11 error 0xC0000185 appears before the normal desktop loads. You may see a blue Recovery screen saying:

Your PC/Device needs to be repaired

The screen may also mention:

The Boot Configuration Data for your PC is missing or contains errors.

or show a path such as:

\EFI\Microsoft\Boot\BCD

This does not automatically mean Windows or your personal files are gone.

The failure is happening in the startup path. The safest approach is to confirm that the Windows drive is still detected, use the built-in recovery tools first, and rebuild boot files only when those simpler repairs do not work.

Protect Your Files Before Making Major Changes

Do not start by formatting partitions, resetting the PC, or performing a clean Windows installation.

Error 0xC0000185 can occur while the Windows installation and personal files are still intact.

Before advanced repairs:

• keep a laptop connected to power
• disconnect unnecessary USB drives and memory cards
• have your BitLocker recovery key available if device encryption is enabled
• avoid changing several BIOS settings at once
• do not format the EFI System Partition because an old tutorial tells you to

If you recently installed another operating system or changed the bootloader, the problem may simply be that Windows Boot Manager is no longer being started correctly.

Check Whether the Windows Drive Is Still Detected

Before rebuilding boot files, confirm that the SSD or hard drive containing Windows is visible to the computer.

Enter BIOS or UEFI and look under a section such as:

• Storage
• NVMe
• SATA
• System information
• Boot devices

The Windows Drive Is Missing

Stop treating this as a BCD-only problem.

A drive that disappears from BIOS or UEFI may have:

• a loose connection
• a failing SSD
• a controller problem
• a power problem
• a hardware fault

Repeatedly rebuilding Windows boot files will not fix a storage device the firmware cannot detect.

If the drive appears intermittently or hardware diagnostics report a failure, protect important data as soon as possible.

The Drive Is Detected

Continue to Windows Recovery Environment.

A detected drive can still have damaged boot files, file-system errors, or an incorrect boot configuration.

Enter Windows Recovery Environment

Windows may enter recovery automatically after repeated startup failures.

If it does not, use Windows installation media or the recovery method provided by the PC manufacturer.

Once you reach Windows Recovery Environment, choose:

Troubleshoot > Advanced options

You may see tools including:

• Startup Repair
• System Restore
• Uninstall Updates
• Command Prompt
• UEFI Firmware Settings

If BitLocker is enabled, Windows may request the recovery key before allowing access to some tools.

Start With Startup Repair

For most users, this should be the first real repair attempt.

Open:

Troubleshoot > Advanced options > Startup Repair

Choose the Windows installation if prompted.

Microsoft says Startup Repair can diagnose and repair several startup problems, including damaged system files and corrupted Boot Configuration Data.

Let it finish and restart the computer.

If Windows starts normally, back up important files and restart once more to confirm that the repair is stable.

If Startup Repair says it could not repair the PC, continue without resetting Windows.

Think About What Happened Immediately Before the Error

The next recovery option should match the timing.

The Error Began After a Windows Update

Open:

Troubleshoot > Advanced options > Uninstall Updates

Windows may offer options to remove the latest quality update or feature update.

Start with the most recent relevant update rather than removing updates at random.

The Error Began After a Driver or System Change

Use:

Troubleshoot > Advanced options > System Restore

Choose a restore point from before the problem began.

System Restore normally leaves personal documents alone, but applications, drivers, and updates installed after the selected restore point can be removed.

If there are no restore points, move on.

Check Windows Boot Manager

Enter BIOS or UEFI and inspect the boot order.

On a normal modern Windows 11 installation, you will usually see an entry named:

Windows Boot Manager

Make sure the correct Windows Boot Manager entry is ahead of unrelated storage devices.

This is especially relevant after:

• adding another SSD
• installing Linux
• cloning Windows to another drive
• resetting BIOS settings
• changing boot mode

If Windows Boot Manager is missing entirely, the Windows installation may still exist. The boot files may simply need repair.

Do not randomly switch:

• AHCI
• RAID
• Intel RST
• VMD
• UEFI/Legacy mode
• CSM

If the problem began immediately after one of those settings was changed, restore the previous configuration first.

Identify the Windows Partition Before Running Boot Commands

Drive letters can change inside Windows Recovery Environment.

Your normal C: drive may appear as D: or another letter.

Open:

Troubleshoot > Advanced options > Command Prompt

Test likely Windows partitions:

dir C:\Windows
dir D:\Windows
dir E:\Windows

You are looking for the real Windows installation containing directories such as:

Windows
Users
Program Files

Suppose:

dir D:\Windows

shows the correct Windows folder.

For the rest of the example, the Windows installation is on D:.

Do not copy that letter blindly. Use the drive letter you identify on your own PC.

Repair Modern UEFI Boot Files With BCDBoot

Most Windows 11 PCs use UEFI firmware and an EFI System Partition.

Microsoft documents BCDBoot as a tool for recreating boot files on the system partition from an existing Windows installation.

First identify the EFI System Partition.

At the recovery Command Prompt, run:

diskpart
list volume

Look for the small FAT32 system volume associated with the EFI partition.

Do not guess when several similar volumes exist.

Once you are certain which volume is the EFI System Partition:

select volume <number>
assign letter=S
exit

Replace <number> with the actual EFI volume number.

If your Windows installation is on D:, run:

bcdboot D:\Windows /s S: /f UEFI

Replace D: with the actual Windows partition letter you found earlier.

BCDBoot copies fresh boot-environment files from the Windows installation to the EFI System Partition.

Restart the PC afterward.

Microsoft’s BCDBoot documentation specifically supports using the tool to repair a damaged system partition and recreate Windows boot files.

Why I Would Not Start With a Long Bootrec Command List

Older tutorials commonly tell users to immediately run:

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

Those commands still have uses, but they should not be treated as a universal Windows 11 recipe.

Modern Windows 11 PCs normally use UEFI firmware and an EFI System Partition rather than the older BIOS/MBR arrangement many legacy guides were written for.

For a typical Windows 11 UEFI installation, I prefer this order:

Startup Repair → confirm Windows partition → confirm EFI partition → BCDBoot when boot files need rebuilding

That reduces the chance of applying the wrong repair model to the system.

Check the File System When Boot Corruption Returns

If boot files keep becoming damaged, the BCD may not be the root cause.

From Recovery Command Prompt, run CHKDSK against the Windows partition you identified.

For example:

chkdsk D: /f

Replace D: with the correct drive letter.

Pay attention to recurring problems such as:

• repeated file-system errors
• an SSD disappearing intermittently
• very slow reads
• boot corruption returning after repair
• storage-related hardware diagnostic failures

A temporary boot repair cannot make failing storage reliable.

If the PC reports a missing boot device rather than 0xC0000185, see Boot Device Not Found on HP: How to Fix the 3F0 Error for the storage-detection side of startup troubleshooting.

If the Error Appeared After Dual Boot or Another Operating System

Windows may still be completely intact.

Check whether another boot menu still contains:

Windows Boot Manager

If selecting it starts Windows, the main problem may be the default firmware boot order.

If Windows Boot Manager disappeared, Startup Repair or BCDBoot can recreate the Windows boot entry when the Windows and EFI partitions are still healthy.

Do not delete Linux partitions or format the EFI partition simply to make Windows the default boot option.

If the problem followed a Bazzite or Linux setup, How to Go Back to Windows 11 From Bazzite covers that bootloader-specific situation.

When Reinstalling Windows Becomes Reasonable

A clean installation should come late, not first.

Consider reinstalling only after you have established that:

• the storage drive is healthy
• Startup Repair cannot fix the startup environment
• restore and update rollback options do not help
• the correct Windows installation still cannot be made bootable
• important files are backed up
• you understand which physical drive contains Windows

If the storage drive is failing, reinstalling Windows onto the same failing drive may only produce another startup failure.

If the Windows installation itself is badly damaged but the drive is healthy, manufacturer recovery or Windows installation media may be appropriate.

If 0xC0000185 Keeps Returning

A recurring error is more important than a one-time damaged BCD.

Look for an underlying cause such as:

• SSD or hard-drive failure
• unstable storage connection
• incorrect controller configuration
• repeated unsafe shutdowns
• firmware problems
• another operating system altering the boot configuration
• recurring file-system corruption

Rebuilding the BCD every few days is not a real fix.

The boot configuration is often the part that fails visibly, while the storage or firmware problem underneath it continues.

The safest repair is the one that matches the evidence: use Startup Repair for ordinary startup corruption, BCDBoot when a modern UEFI system has damaged boot files, and hardware investigation when the Windows drive itself is unreliable.