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

The fast answer. 0xc0000185 is Windows’ STATUS_IO_DEVICE_ERROR: “The I/O device reported an I/O error.” The screen usually reads “A required device isn’t connected or can’t be accessed” or “The Boot Configuration Data for your PC is missing or contains errors.” Either way, the boot disk failed a read. Treat it as a hardware problem first: unplug all USB drives, reseat the drive or its cable, and confirm the drive shows up in BIOS. Then, from Windows Recovery (WinRE), check the disk before rebuilding anything:

chkdsk C: /f /r

If chkdsk hits bad sectors, can’t finish, or the disk shows as read-only, the drive is failing. Copy your data off and replace it — rebuilding boot files won’t hold on a dying disk.

Why this happens

Failing drive — bad sectors on a hard drive, or a worn SSD. Some SSDs lock themselves read-only near end of life, so every repair returns “The media is write protected.”
Loose or bad connection — a loose SATA data or power cable, a bad port, or an unseated M.2 drive. Microsoft’s KERNEL_DATA_INPAGE_ERROR documentation, for example, points to disk cabling when the I/O status is C0000185.
Boot attempted from the wrong device — a USB drive left plugged in, or a boot order pointing away from the Windows disk.
Corrupted boot data — the BCD store or winload.efi damaged by a hard power-off or by the bad sectors above.

Step-by-step fix

Step 1 — Unplug external devices and reboot

Power off. Disconnect every USB drive, external disk, SD card, and dock, plus any hardware you added recently. Power on. If Windows boots, reconnect devices one at a time.

Step 2 — Check the drive connection and run hardware diagnostics

On a desktop, unplug from the wall and reseat both ends of the SATA data and power cables; try another port or cable. On M.2 systems, reseat the drive. Enter BIOS/UEFI setup (usually Del, F2, or F10) and confirm the drive is detected and first in the boot order. Then run the manufacturer’s built-in drive test — for example Dell’s preboot diagnostics from the F12 one-time boot menu, or HP PC Hardware Diagnostics UEFI. If the drive isn’t detected or fails the test, no command below will fix it.

Step 3 — Get into Windows Recovery (WinRE)

Force three failed boots (hold the power button as the Windows logo appears, three times) to open Automatic Repair. Because this error means the disk can’t be read, the recovery tools on that disk often won’t load either — the error screen itself tells you to use installation media. In that case boot a Windows 10/11 install USB and choose Repair your computer. Then go to Troubleshoot → Advanced options.

Step 4 — Run Startup Repair

Choose Startup Repair and let it finish. It repairs many damaged boot stores automatically. Reboot and test.

Step 5 — Check the disk

Open Advanced options → Command Prompt. First confirm the disk is present and writable:

diskpart
list disk
select disk 0
attributes disk
exit

If it reports Current Read-only State : Yes and attributes disk clear readonly fails, stop repairing: copy your data off and replace the drive. Otherwise find the Windows volume (letters differ in WinRE — try dir C:\Windows, then dir D:\Windows) and check it:

chkdsk C: /f /r

/f fixes file-system errors; /r finds bad sectors and recovers readable data. It can take hours. Bad sectors or a stalled run mean the drive is failing.

Step 6 — Rebuild the boot files

If the disk checks clean, rebuild the boot data. On a legacy BIOS/MBR system:

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

Type Y when /rebuildbcd lists a Windows installation.

UEFI/GPT note: bootrec /fixboot commonly returns “Access is denied” on UEFI systems. Instead, give the EFI System Partition a letter and rewrite the boot files with bcdboot:

diskpart
list disk
sel disk 0
list vol
sel vol <EFI-FAT32-vol#>
assign letter=S:
exit
bcdboot C:\Windows /s S: /f UEFI

The EFI partition is the small (about 100–500 MB) FAT32 volume. Use the Windows letter from Step 5. You should see “Boot files successfully created.” Full walkthrough: 0xc000000e page.

Step 7 — If it started after an update or driver install, use System Restore

In Advanced options → System Restore, pick a restore point from before the problem. It removes apps, drivers, and updates installed after that point but leaves personal files alone.

Data safety: This code is literally a disk I/O error, so assume the drive may be dying. Get your data off first if you have no backup. chkdsk /r reads every sector and can push a weak drive over the edge — on a drive that clicks, disappears from BIOS, or has gone read-only, skip it: pull the drive and image or copy it from a working PC. Never run clean or format in diskpart for this error, and never run repairs on the only copy of irreplaceable data.

GRAM tip: These repairs run in Windows Recovery or from a Windows install USB. Once the machine boots again, plug in GRAM — a free portable repair toolkit that runs from a USB inside Windows — to read the drive’s SMART health, check the event logs for disk and controller errors, and let its AI agent confirm whether it was the cable, the drive, or corrupted boot files so the error doesn’t come back.

Download GRAM free See AI pricing →

FAQ

Can I fix this without a second working computer?

Usually. WinRE lives on the broken PC itself — three failed boots open Automatic Repair. With this error the on-disk recovery tools often can’t load, so you may need a Windows install USB (made on any PC, even a borrowed one). The repair needs no second computer. The exception is a physically failing or read-only drive: then pull it and copy your data from a healthy PC. (GRAM runs inside Windows rather than from boot media — use it once the machine boots to verify disk health and confirm the root cause.)

Is 0xc0000185 a hardware or software problem?

Most often hardware. The code means the storage device reported an I/O error. A bad cable or failing drive is the usual reason; corrupted boot files are frequently a side effect of the same bad sectors or a hard power-off. That’s why cable checks, diagnostics, and chkdsk come before bootrec here.

Why do my repair commands say “The media is write protected”?

The disk is in a read-only state. Check with attributes disk in diskpart and try attributes disk clear readonly. If that fails, the drive has likely locked itself — common with SSDs near end of life. Copy your files off and replace it.

Will these repairs delete my files?

No. bootrec and bcdboot rewrite boot data only, and System Restore leaves personal files alone. chkdsk /f /r can move damaged fragments into FOUND.000 folders but doesn’t wipe the drive. The real risk is stressing a dying drive, so copy the data first.