STATUS_IO_TIMEOUT 0XC00000B5: Real Fix for Stuck Drives

Yeah, this error is annoying

You're trying to copy a file, load a game, or boot up, and Windows throws STATUS_IO_TIMEOUT (0XC00000B5). It usually means a drive or USB device just gave up talking to your PC. Let's fix it.

The real fix: Find the slow device and make it answer

What's actually happening here is Windows sent a command to a storage device (HDD, SSD, USB stick, external drive) and waited for a reply. The device took too long — more than the timeout value — so Windows killed the operation and showed this error. The culprit is almost always a failing drive, a bad cable, or a USB power saving setting.

Step 1: Check the obvious — cables and ports

1. If it's an internal SATA drive, open your PC case. Unplug the SATA data cable and the power cable. Plug them back in firmly. Try a different SATA port on your motherboard.
2. If it's an external USB drive, try a different USB port. Use a USB 3.0 port (usually blue) if available. Avoid USB hubs — plug directly into the PC.
3. If you have a spare cable, swap the SATA cable. Bad cables cause these errors all the time.

Step 2: Disable USB selective suspend (for USB devices)

Windows has a power saving feature that puts USB ports to sleep. This can cause timeouts. Turn it off.

Control Panel -> Power Options -> Change plan settings -> Change advanced power settings
USB settings -> USB selective suspend setting -> Set to "Disabled"

No reboot needed. Try your device again.

Step 3: Update or roll back the driver

For internal drives, update the storage controller driver. For external drives, update the USB controller driver. But also — sometimes a new driver breaks things. If the error started after a Windows Update, roll back the driver.

Device Manager -> Storage controllers -> Right-click your controller -> Driver tab -> Roll Back Driver (if available)

Step 4: Check disk health

Run this in Command Prompt as admin:

wmic diskdrive get status
chkdsk C: /f /r

wmic shows you if the drive's health status is "OK" or "Pred Fail". If it says "Pred Fail", replace the drive. chkdsk fixes file system errors that can cause timeouts.

Why this works

Let's break down why step 3 works. When Windows sends a read or write request to a drive, it waits for an IRP (I/O Request Packet) to complete. The default timeout for storage devices is typically 60 seconds for SCSI/ATA commands, but USB devices have shorter timeouts — often 10 seconds. If the device doesn't respond within that window, the STATUS_IO_TIMEOUT is returned. By disabling USB selective suspend, you stop Windows from putting the USB port into a low-power state mid-operation, which was causing the device to miss the deadline. For SATA drives, a loose cable or faulty port adds electrical noise or breaks the signal entirely — the drive never gets the command, so it never replies. Reseating the cable restores the physical connection.

Less common variations of the same issue

Variation 1: External drive works on one PC but not another

This happens when the other PC has a newer USB controller that uses UASP (USB Attached SCSI Protocol). UASP has shorter timeouts. Your drive might be too old or slow. Fix: Force the drive into BOT (Bulk-Only Transport) mode — you can't do this from Windows, you need a registry tweak or a third-party tool. Simpler: use a USB 2.0 port, which forces BOT mode naturally.

Variation 2: Error only during heavy file transfers

This points to overheating or a dying drive. When a drive gets hot, its firmware slows down to protect itself. If it slows down too much, it misses the timeout. Check drive temps with CrystalDiskInfo. If temps hit 60°C or more, improve airflow or replace the drive.

Variation 3: Error with SATA SSDs after sleep/wake

Some SSDs don't wake up properly from the sleep state. Windows tries to access the drive before it's ready. Fix: Disable drive sleep in Windows.

Control Panel -> Power Options -> Change plan settings -> Change advanced power settings
Hard disk -> Turn off hard disk after -> Set to "0" (never)

Prevention

Don't let things get that hot. Keep your drives cool. Back up often — a drive throwing timeouts is a drive that will die soon. Check your cables every few months if you move your PC around. And for USB devices, avoid cheap hubs. A $5 hub can cause timeouts that look like a broken drive.

Do not run chkdsk on an SSD too often — it wears it out. Only run it if you have errors.

That's it. No magic. Find the slow device, fix the connection, or replace the drive. The error tells you exactly what's wrong: something didn't answer in time.