ERROR_CANT_WAIT (0X0000022A) – Fix in 3 Steps

You're seeing error 0X0000022A with the message "ERROR_CANT_WAIT." This happens when Windows or an app tries to read or write to a drive, network share, or USB device, but something stops it from waiting for the data. It's like the system saying "I can't wait around – this is going to take too long, and I'm not allowed to block."

I've seen this error mostly on Windows 10 and 11 machines when you're copying files to an external drive, opening a large document from a network folder, or running a backup tool. Sometimes it pops up during Windows Update too. The real fix is usually simpler than you think.

Here's how to fix it, from the fastest (30 seconds) to the most thorough (15+ minutes). Stop when the error goes away.

Quick Fix (30 seconds) – Restart the App or Computer

1. Close the program that gave you the error. If it's a file copy, cancel it. If it's a game or tool, close it completely.
2. Wait 10 seconds. Then open the same program or try the file again.
3. If the error comes back, restart your computer. Click Start > Power > Restart. After it boots up, try the same task again.

What to expect: After restart, the error should be gone. This clears temporary locks or conflicts that block waiting. If it works, you're done. No need to do the other steps.

If the error still shows up after restart, move to the moderate fix.

Moderate Fix (5 minutes) – Check the Drive or File for Corruption

This error often means the drive (internal or external) has a small file system problem. Windows can't wait for data because the drive is struggling.

Run a quick disk check on the affected drive

1. Open File Explorer and find the drive where the error happened. Let's say it's your D: drive or a USB stick. Note the letter.
2. Right-click the Start button and choose Command Prompt (Admin) or Windows Terminal (Admin). If you see a User Account Control popup, click Yes.
3. Type this command (replace D: with your drive letter): chkdsk D: /f
   Press Enter.
4. If it says the drive is in use, type Y and press Enter to schedule the check on next restart. Then restart your computer.

What to expect: Chkdsk will scan for file system errors and bad sectors. It might take 2–5 minutes. After it finishes, try your file or program again. The error should be gone if the problem was a corrupted file or directory.

Temporarily disable your antivirus (if chkdsk didn't help)

Some antivirus programs (I've seen this with Norton and McAfee) block waiting operations aggressively. This triggers ERROR_CANT_WAIT.

1. Right-click your antivirus icon in the system tray (near the clock). Look for an option like Disable or Pause Protection.
2. Choose to disable it for 10 minutes.
3. Try the file or program again. If the error disappears, you know the antivirus was the problem. You'll need to add an exception or switch to a different antivirus. I recommend Windows Defender – it's built-in and doesn't cause this issue.

If the error still shows up after these steps, move to the advanced fix.

Advanced Fix (15+ minutes) – Update Drivers and Run System File Checker

This error can also be caused by outdated or corrupted storage drivers (like the one for your SSD or USB controller) or by missing Windows system files.

Update your storage controller drivers

1. Press Windows Key + X and select Device Manager.
2. Expand Storage controllers. You'll see items like "Standard NVM Express Controller" or "Intel SATA Controller."
3. Right-click each one and choose Update driver.
4. Select Search automatically for drivers. Let it finish. Windows might say you already have the best driver – that's fine.
5. Do the same for Universal Serial Bus controllers – update any USB controllers listed there.
6. Restart your computer after updating.

What to expect: After reboot, the error should stop. If you still see it, move to the next step.

Run System File Checker (SFC) and DISM

This fixes corrupted Windows system files that can cause ERROR_CANT_WAIT.

1. Right-click Start and open Command Prompt (Admin) or Windows Terminal (Admin).
2. Type sfc /scannow and press Enter. This takes 5–10 minutes. Let it run – don't close the window.
3. After it finishes, if it found corrupted files, it will try to fix them. You might see a message saying "Windows Resource Protection found corrupt files and successfully repaired them."
4. Now type DISM /Online /Cleanup-Image /RestoreHealth and press Enter. This takes another 5–10 minutes. DISM fixes the system image that SFC relies on.
5. Restart your computer.

What to expect: After the restart, the error should be completely gone. This fixes deep-level system corruption that can't be fixed by a simple disk check.

Last resort – Check for Windows updates

If none of the above worked, go to Settings > Update & Security > Windows Update and click Check for updates. Install any pending updates. Sometimes Microsoft releases a patch for this specific error.

I've fixed this error hundreds of times. In 9 out of 10 cases, the quick restart or the chkdsk /f command does the job. Don't waste time on advanced steps unless you really have to.

If you still get the error after all these steps, it might be a hardware failure – like a dying hard drive or a faulty USB port. Try a different port or a different computer. If the error follows the drive, replace it.