Updated 2026-11-19 · 6 min read
I/O Device Error on an External Drive or USB: Causes, Fixes and Data Recovery
“The request could not be performed because of an I/O device error” (0x8007045D) usually means a bad cable, port or driver, or failing sectors. Fix the cheap causes first and protect your data.
You copy a file to an external hard drive or open a USB stick, and Windows stops with “The request could not be performed because of an I/O device error.” Sometimes the drive disappears from File Explorer, sometimes it freezes the whole computer for a minute.
The error means that Windows could not talk to the drive. The cause is often cheap to fix, such as a cable or a port, but it can also be an early warning that the drive is failing. This guide separates the two and keeps your data safe while you find out.
What causes an I/O device error
The error code 0x8007045D is Windows’ ERROR_IO_DEVICE. It appears when a command sent to the drive does not complete. The usual causes, from most to least harmless, are a loose or damaged USB cable, a weak USB port or hub that cannot supply enough power, a corrupted driver, a disconnected power adapter on a 3.5-inch external drive, bad sectors on the drive, and finally a failing drive controller or head.
Because the same message covers harmless and serious causes, the order of your checks matters.
Step 1: try the cheap fixes
Shut down any program using the drive and remove it safely. Reconnect it with a different cable and into a port directly on the computer, preferably a rear port on a desktop. For a drive with its own power adapter, check that it is plugged in. Connect it to another computer. If the error disappears there, the cause was the first computer’s port, driver or power, and the drive is fine.
If the drive still fails, open Device Manager, expand Disk drives, right-click the drive, choose Uninstall device and unplug and reconnect the drive. Windows reinstalls the driver on its own.
Step 2: check the drive’s health
Open PowerShell and run:
Get-PhysicalDisk | Select-Object FriendlyName, HealthStatus, OperationalStatus
HealthStatus Healthy is reassuring but not a guarantee. Warning or Unhealthy, repeated I/O errors, files that copy slowly and then fail, or a drive that keeps disconnecting all point to a failing drive. In that case stop writing to it and move on to the data protection step.
Step 3: protect your data first
Do not run chkdsk /r on a drive with read errors. It tries to read every sector, repeats attempts on bad ones and can push a weak drive over the edge; chkdsk /f can also rewrite the file system. Our CHKDSK guide explains why recovery should come first.
Connect the drive to a Windows computer and open DiskMend. When its pre-check finds read errors, it recommends creating a disk image before scanning: the drive is read once, in two passes that skip around weak areas first and come back to them later, and the scan and recovery then use the copy. Read our guide on failing hard drives for the full procedure. If the drive is healthy and only the file system is damaged, scan it directly and save the files to a different drive.
Step 4: repair or replace
Once your files are safe, you can run chkdsk /f on the drive. If the I/O errors return on different cables and computers, the drive is on its way out. Keep the recovered copy, replace the drive and do not trust it with the only copy of anything again.
Step by step
- 1
Stop writing to the drive
Close programs using it and remove it safely.
- 2
Change cable, port and computer
Use a different cable and a port directly on the computer, and test on a second computer.
- 3
Check power
Make sure a 3.5-inch external drive’s power adapter is connected.
- 4
Reinstall the driver
In Device Manager uninstall the drive under Disk drives, then reconnect it.
- 5
Check health
Run Get-PhysicalDisk in PowerShell and read HealthStatus.
- 6
Protect the data
If the drive has read errors, create a disk image first, then scan and recover from the image.
| Symptom | Likely cause | What to do |
|---|---|---|
| Works on another computer | Port, driver or power of the first computer | Fix the first computer; drive is fine |
| Error only with one cable | Damaged cable | Replace the cable |
| External HDD clicks or spins up repeatedly | Insufficient power or failing hardware | Check the power adapter; if it persists, stop and use a lab |
| Copying stalls, then fails | Bad sectors | Create a disk image first |
| Health status Warning or Unhealthy | Failing drive | Image and recover, then replace |
| Error appears only after a crash or unplugging | Damaged file system | Recover first, then chkdsk /f |
Frequently asked questions
What is an I/O device error?+
It is the message Windows shows when a read or write command to a drive does not complete. It points to the connection, the driver, the power or the drive hardware.
Does an I/O device error mean my drive is dead?+
Not necessarily. A bad cable, port or driver causes many of these errors. A drive that fails on several cables and computers is more likely damaged.
Can I fix the error with chkdsk?+
chkdsk can repair file system errors but cannot repair a bad cable, and on a drive with bad sectors it can do harm. Check the connection and make a copy of your data before using it.
How can I recover files from a drive that throws I/O errors?+
Create a disk image so the drive is read only once, then scan and recover from the image and save the files to a different drive.
Can DiskMend read a drive with an I/O error?+
Yes, if the drive can still be read at least partly. DiskMend reads without writing to the drive, retries unreadable areas patiently while imaging, and saves the files to another drive; areas the hardware cannot return stay empty.