Disk Read Timed Out During Backup – Quick Fix
This happens when the drive can't keep up with backup software. The fix is usually adjusting timeout settings or checking for bad sectors.
You're running a backup and then bam – disk read operation timed out.
I've seen this on Windows Server 2016, 2019, and even on regular Windows 10 machines with external USB drives. The backup software – could be Windows Backup, Veeam, or even robocopy – just stops and throws this error. Here's what I do every time.
The Go-To Fix: Adjust the Disk Timeout in Registry
This isn't a driver issue. It's a timeout setting. Windows has a default timeout for disk operations – usually 30 seconds. If the drive takes longer (old drives, USB drives, or drives under heavy load), it fails. The culprit is almost always that timeout.
Open Regedit as admin. Go to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Disk\TimeOutValueIf TimeOutValue doesn't exist, create it as a DWORD (32-bit). Set the value to 120 (that's 120 seconds). Reboot. Run the backup again. I've fixed dozens of machines with just this one change.
Don't bother with IoTimeOutValue or other registry keys unless you're on an old Windows 2003 box – they rarely help.
Why This Works
The drive isn't dead. It's just slow. USB drives, especially WD My Passport or Seagate Backup Plus, can have delays when the backup software hits a bad spot or when the drive is spinning up from sleep. The registry change gives it more time to respond. Simple as that.
Less Common Variations
If the registry fix doesn't help, here are two other things I've seen cause this:
1. USB Controller Power Saving
Windows might turn off the USB port. Go to Device Manager, find USB Root Hub, right-click, Properties, Power Management, uncheck "Allow the computer to turn off this device". Do this for all USB hubs. This is especially common on laptops.
2. Bad Sectors on the Drive
If the timeout only happens on certain files, you might have bad sectors. Run chkdsk /f /r on the drive. It takes hours, but it finds and marks bad sectors. Then backup software won't time out trying to read them.
Prevention for Next Time
Three things you can do now:
- Set a longer timeout (like we did above) before backup starts. It's a five-minute fix.
- Use a backup tool that allows timeouts. Veeam and Acronis let you set read/write timeouts. Windows Backup does not – so the registry hack is your only option there.
- Check drive health monthly. Use CrystalDiskInfo or SMART data. If reallocated sectors go up, replace the drive. Don't wait.
One last thing – if you're backing up over network, also check the network card's power saving settings and set a larger SMB timeout. But that's a different error code entirely.
Was this solution helpful?