0XC0000120

STATUS_CANCELLED 0xC0000120: Fix I/O Request Canceled Fast

STATUS_CANCELLED means Windows canceled an I/O request — often a dying drive or rogue app. Here's how to fix it fast, from 30-second checks to advanced diagnostics.

I know this error is infuriating. You're copying files, saving a document, or booting up, and bam — STATUS_CANCELLED (0xC0000120) pops up or crashes your PC. The good news: it's almost always fixable. The bad news: it sometimes means your drive is dying, so don't ignore it.

STATUS_CANCELLED is a Windows NT status code. It means an I/O request — a read or write to a disk, USB drive, network share, or device — was canceled before it completed. Windows doesn't cancel these for fun. Something interrupted it: a timeout, a hardware fault, a driver that hung, or a program that gave up waiting. That's why the fix depends on where the error shows up.

First: The 30-Second Fix (For External Drives)

If the error appears when you're moving files to a USB stick, external SSD, or SD card, your first move is embarrassingly simple. Unplug it. Wait 10 seconds. Plug it back into a different port. Not the same port — a different one, ideally on the back of a desktop instead of the front panel.

Front-panel USB ports on cheap cases are notoriously flaky. I've seen STATUS_CANCELLED vanish just by moving a drive from a front port to a rear one. If it's a laptop, try a different USB port and skip any unpowered hub. Bus-powered 2.5" drives draw more current than people expect, and a weak hub will cancel I/O requests under load.

If the drive is a network share (mapped drive, NAS), disconnect it and reconnect. A dropped SMB session triggers this error constantly.

Stop here if it works. If the error comes back, move on.

The 5-Minute Fix: Check the Drive and the Disk Health

This is where most cases get solved. STATUS_CANCELLED on an internal drive usually points to one of two culprits: a filesystem problem or failing hardware. Let's rule out the filesystem first.

Step 1: Run CHKDSK on the affected volume

Open an elevated Command Prompt (right-click Start, choose Terminal (Admin) or Command Prompt (Admin)). Then run this, replacing C: with the drive letter that's throwing the error:

chkdsk C: /f /r

If Windows says the volume is in use, type Y to schedule it for the next reboot. The /r flag scans for bad sectors and tries to recover readable data — that's the one that matters here. It can take an hour on a big drive, so start it before you walk away.

Step 2: Check SMART status

While you're in a terminal, run:

wmic diskdrive get model,status,size

If Status says anything other than OK, your drive is on borrowed time. Back up immediately — before running any more diagnostics. A drive that returns STATUS_CANCELLED under load and fails SMART is not a drive you want to keep using.

Step 3: Update the storage driver

Outdated SATA, NVMe, or chipset drivers cause canceled I/O requests on Windows 10 and 11, especially after a feature update. Grab the latest storage driver from your motherboard or laptop maker — not from Windows Update, which often ships stale versions. For NVMe drives, check the drive manufacturer's site too (Samsung Magician, Crucial Storage Executive, WD Dashboard).

The 15-Minute Fix: Dig Into Event Viewer and Drivers

Still happening? Time to find out what canceled the request. Windows logs it. The trick is knowing where to look.

Check Event Viewer for the canceling process

  1. Press Win + R, type eventvwr.msc, hit Enter.
  2. Go to Windows Logs → System.
  3. Click Filter Current Log on the right.
  4. In the Event sources box, check disk, Ntfs, and storahci.

Look for events with IDs 7, 11, 51, or 153. Event ID 51 ("An error was detected on device during a paging operation") almost always means a bad cable or dying drive. Event ID 153 means the storage stack gave up on a request — the same thing STATUS_CANCELLED reports.

Real-world trigger: I saw this exact error on a Dell XPS 15 where the user's aftermarket NVMe drive was overheating under sustained writes. Once it hit 80°C, the controller dropped I/O requests and Windows threw 0xC0000120. A thermal pad fixed it. If your drive gets hot, that's your culprit.

Replace the SATA cable (yes, really)

On a desktop, a marginal SATA cable is a classic cause of canceled I/O. They cost $3. Swap it. Also reseat the drive's power connector. This is old advice for a reason — it works.

Check for failing RAM with a storage-side effect

Sometimes the I/O gets canceled because the request itself was corrupted in memory. Bad RAM causes this. Run mdsched.exe (Windows Memory Diagnostic) or, better, MemTest86 from a USB stick overnight. If you get errors, pull one stick at a time and retest.

Disable aggressive power management

Windows 10 and 11 may spin down drives or put them into low-power states aggressively, and some drives don't respond fast enough. In Control Panel → Power Options → Change plan settings → Change advanced power settings → Hard disk → Turn off hard disk after, set it to 0 (Never). Also, in Device Manager, expand Disk drives, open your drive's Properties → Policies, and uncheck Enable write caching on the device if you're seeing data loss. That last one costs a little performance but stops a lot of canceled writes.

When You Should Stop and Back Up

If none of this fixes it and the drive is older than three years, stop troubleshooting and start copying. STATUS_CANCELLED that persists through a cable swap, driver update, and CHKDSK is a strong signal of imminent drive death. Clone it with Macrium Reflect Free or Clonezilla, replace the hardware, and thank yourself later.

A canceled I/O request isn't a software bug you can patch around forever. If the drive is failing, no amount of sfc /scannow will save your data. Protect it first, then diagnose at leisure.

Related Errors in Windows Errors
Service not started: Task Scheduler (Event ID 101) Task Scheduler Service Won't Start — Fix in 5 Minutes 0XC00D28B2 Fix NS_E_DRM_ATTRIBUTE_TOO_LONG (0XC00D28B2) in Windows 0X0000051B Fixing ERROR_INVALID_OWNER (0x0000051B) on Windows 0XC0220017 0XC0220017: Can't Delete Built-In Firewall Object — Fix

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.