Driver Cancel Timeout (0x252): Why It Happens and How to Fix

When This Error Appears

You're copying a large file from an external USB drive to your desktop. Halfway through, the copy stalls. You press Cancel. Nothing happens for 45 seconds, then the system spits out a blue screen or a crash with error 0x00000252. The exact text: "The driver %hs failed to complete a canceled I/O request in the allotted time."

I've seen this most often with external Seagate and WD drives during large transfers over USB 3.0, especially on Windows 10 build 1909 and later. It also shows up with internal SATA drives that are starting to fail, or with buggy NVMe controller drivers.

Root Cause: Why the Driver Won't Let Go

What's actually happening here is a timeout inside the Windows I/O manager. When you cancel a file operation, the OS tells the driver to abort the pending I/O request. The driver then has a limited window—default is 60 seconds—to complete the cancellation. If the drive is slow, stuck, or the driver itself is buggy, the cancellation never finishes. Windows gives up and fires this error.

Three common culprits:

• Failing hard drive: Bad sectors or a dying controller prevent the drive from acknowledging the cancel command. The driver waits, the timer runs out.
• Buggy storage driver: Some generic Microsoft drivers or old OEM drivers don't handle cancellation properly. They just hang.
• Power management conflicts: USB selective suspend can put a drive to sleep mid-transfer. The driver can't cancel because the device isn't responding.

How to Fix It

Skip the generic "run SFC" advice. It never helps here. Instead, work through these steps in order. Stop when the error stops.

1. Check the drive's health with raw SMART data: Don't trust Windows' "healthy" status. Download CrystalDiskInfo (free, no ads). Look for Reallocated Sectors, Current Pending Sector Count, or UltraDMA CRC Errors. If any of these are yellow or red, your drive is dying. Replace it. No driver fix will save a failing disk.
2. Update the storage driver manually: Go to Device Manager, expand Disk drives, right-click your drive, select Update driver, then Browse my computer for drivers, then Let me pick from a list. Try Standard NVM Express Controller for NVMe drives, or Microsoft Storage Spaces Controller for SATA. Don't use the "Search automatically" option—it often finds nothing useful. If you have a specific vendor driver (Intel RST, AMD StoreMI), uninstall it first and fall back to the Microsoft inbox driver. I've seen Intel RST drivers cause this exact hang.
3. Disable USB selective suspend for the problematic device: In Device Manager, find your USB controller under Universal Serial Bus controllers. Right-click each USB Root Hub entry, go to Power Management, uncheck Allow the computer to turn off this device to save power. Do this for all hubs. Reboot. This alone fixes about 30% of external drive cases.
4. Increase the cancel timeout via registry (if you can't change hardware): Open Regedit, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\disk\Parameters. Create a new DWORD (32-bit) called IoTimeout. Set it to decimal 120 (that's 120 seconds). Reboot. This gives the driver twice as long to finish cancellation. It doesn't fix the underlying problem, but it buys you time to copy data off a dying drive.
5. Replace the cable or port: For external drives, try a different USB cable—especially if you see UltraDMA CRC Errors in SMART. Also try a different USB port. Some motherboard USB ports have flaky power delivery that causes timeouts.

If It Still Fails

If you've done all the above and the error persists, you're looking at a hardware problem, not a software one. The drive is almost certainly going bad. Back up all critical data immediately using a tool that can skip bad sectors—try ddrescue on Linux or Roadkil's Unstoppable Copier on Windows. Then replace the drive.

One edge case: RAID controllers. If you're using a hardware RAID card (LSI, Adaptec), update its firmware. Some older firmware versions have a known bug where cancellation requests are never forwarded to the underlying disk. Check the vendor's site for a firmware update.

Don't waste time reinstalling Windows—this error is driver or hardware specific. A clean install won't help if the disk is failing.