Fix 0xC0000222 Delayed Write Failed Error

The 30-second check: Reseat your cables

What's actually happening here is that Windows tried to write cached data to the drive, but the drive vanished mid-write. 90% of the time, the culprit is a loose or failing connection.

Power down your machine completely. Not sleep, not hibernate — full shutdown.
Unplug both ends of the data cable (SATA or USB) and the power cable. Wait 10 seconds.
Plug everything back in firmly. You're looking for a solid click on SATA connectors.
Reboot. If the error doesn't reappear, you're done. If it does, move on.

On external USB drives: try a different USB port, preferably one on the back of the PC (those are connected directly to the motherboard). Avoid USB hubs — they're notorious for voltage drops that cause this exact error.

The 5-minute fix: Run chkdsk and check the file system

If reseating didn't help, the file system might be corrupt. The error message tells you the exact file that failed — note it down. That file's metadata might be toast.

# Run as Administrator in Command Prompt or PowerShell
chkdsk C: /f /r

For an external drive, replace C: with the actual drive letter. The /f flag fixes file system errors. /r locates bad sectors and recovers readable data. Expect this to take a while — 20 minutes to an hour depending on drive size.

Why /r matters: it doesn't just mark bad sectors; it tries to read them first. This gives you a chance to save the data, which /f alone doesn't attempt.

After chkdsk finishes, check the Windows System Event Log. Event ID 50 under 'Disk' or 'Ntfs' will give you the specific file and error context. Press Win + X, select Event Viewer, then go to Windows Logs > System. Filter by Event ID 50 or source 'Disk'. You're looking for a warning that says 'An error was detected on device \Device\HarddiskX\DRX' — that X tells you which physical disk is failing.

The 15-minute advanced fix: Check disk health, power, and driver settings

Drive health — is it dying?

Run CrystalDiskInfo (free, portable). Look at the raw values for 'Reallocated Sectors Count', 'Current Pending Sector Count', and 'Uncorrectable Sector Count'. Any non-zero value means the drive is on its way out. Back up everything immediately. Replace the drive.

SSDs have their own failure modes. For NVMe drives, check 'Media and Data Integrity Errors'. Any value above 0 suggests the drive's NAND is degrading. I've seen a single reallocated sector cause intermittent 0xC0000222 errors that drove people crazy for weeks.

Power supply — the silent killer

If you have multiple drives or power-hungry components, your PSU might be struggling. The delayed write error happens when a drive momentarily loses power — even for 100 milliseconds. Symptoms include random reboots, USB devices disconnecting, and this exact error.

Test: unplug any non-essential drives or USB devices. If the error stops, you're overloading your power supply. Upgrade to a unit from Seasonic, Corsair, or EVGA with at least 20% headroom over your peak draw.

Disable write caching on the problematic drive

This is a band-aid, not a fix. Write caching is what causes the delayed write error — without it, Windows writes data immediately instead of queuing it. You'll take a performance hit, but the error will stop.

# Open Device Manager (devmgmt.msc)
# Expand 'Disk drives'
# Right-click your drive > Properties
# Go to 'Policies' tab
# Select 'Quick removal' (for USB) or uncheck 'Enable write caching on the device' (for internal)
# Click OK and reboot

I only recommend this if you can't replace the drive right now. It reduces performance noticeably, especially on mechanical hard drives. If you're on an SSD or NVMe, the hit is smaller but still real — think 10-15% slower writes.

Update or roll back your storage driver

Outdated or buggy storage drivers can cause this. Check your motherboard manufacturer's site for the latest chipset and storage driver (Intel RST, AMD RAID, or plain AHCI driver). If you recently updated and the error started, roll back: Device Manager > Storage Controllers > right-click your controller > Properties > Driver > Roll Back Driver.

When to just give up and replace the hardware

If you've done all three sections and the error persists, your drive or motherboard SATA controller is failing. I've seen exactly one case where a motherboard firmware update fixed it. That's the exception, not the rule. Back up your data now — not tomorrow. Drives with bad sectors die suddenly, and a delayed write error is often the first symptom.

One last thing: if you're on a laptop, check the power settings. Go to Control Panel > Power Options > Change plan settings > Change advanced power settings > Hard disk > Turn off hard disk after. Set it to 'Never'. Windows turning off the hard drive after 20 minutes of inactivity can trigger this error on some drives, especially older ones.