Fix 0x8007045d Windows 10 Error: Step-by-Step

This guide walks you through fixing the Windows 10 error 0x8007045d (often seen as 0x800704sd due to a typo). This error usually appears when copying, moving, or installing files, and it means Windows couldn’t read data from a device—often a USB drive, external hard drive, or DVD. We’ll cover the most effective fixes, from simple driver updates to deeper system checks, so you can get back to work quickly.

What You’ll Need

Administrator access to your Windows 10 PC
The device that’s causing the error (USB, external drive, etc.)
An internet connection (for driver updates and Windows updates)
Patience—some steps involve scanning that can take time

Step-by-Step

Restart your computer and the device. This clears temporary glitches. Unplug the external device, restart your PC, and reconnect the device. Try the operation again.
Run Windows Update. Go to Settings > Update & Security > Windows Update and click Check for updates. Install any pending updates, restart, and try again. This fixes known bugs that cause the error.
Update your device drivers. Right-click the Start button and select Device Manager. Expand Disk drives and Universal Serial Bus controllers. Right-click each device (especially the one causing the error) and select Update driver > Search automatically for drivers. Restart after updating.
Check the device’s file system for errors. Open File Explorer, right-click the problematic drive (e.g., your USB drive), select Properties, go to the Tools tab, and under Error checking click Check. Follow the prompts to scan and repair the drive. This fixes corrupted file system structures that cause read errors.
Run the System File Checker (SFC). Open Command Prompt as administrator (type “cmd” in the Start menu, right-click it, and choose Run as administrator). Type sfc /scannow and press Enter. Wait for the scan to finish (it can take 15-30 minutes). If it finds corrupted files, restart and try again.
Run the DISM tool. In the same Command Prompt, type DISM /Online /Cleanup-Image /RestoreHealth and press Enter. This repairs Windows system image issues that SFC might miss. Restart after completion.
Try a different USB port or cable. If using an external drive, connect it directly to a rear USB port (not a hub). If possible, swap the cable. Faulty connections cause intermittent read errors.
Check the drive’s health. If the error persists, the drive may be failing. Use a tool like CrystalDiskInfo (free) to check the drive’s SMART status. If it shows “Caution” or “Bad”, back up your data immediately and replace the drive.
Disable the USB selective suspend setting. Go to Control Panel > Power Options > Edit plan settings > Change advanced power settings. Expand USB settings > USB selective suspend setting and set it to Disabled for both battery and plugged in. Restart and try again.
Perform a Clean Boot. This starts Windows with minimal drivers and programs, isolating software conflicts. Type msconfig in the Start menu, go to the Services tab, check Hide all Microsoft services, then click Disable all. Go to the Startup tab and click Open Task Manager, disable all startup items, and restart. If the error is gone, re-enable services one by one to find the culprit.

Common Mistakes

Skipping the restart after driver updates. Many fixes require a reboot to take effect. Always restart before testing.
Using the wrong drive letter. When running chkdsk or other commands, double-check you’re targeting the correct drive. Running it on your system drive (C:) is fine, but be careful not to format the wrong disk.
Ignoring the device’s physical condition. A bent USB connector or a damaged cable can cause this error. Inspect the device and try another cable/port before deep troubleshooting.
Not backing up data. If the drive is failing, every attempt to read it could further damage it. Back up important files before running repairs.

Tips

Use the original USB cable that came with your device—third-party cables may not support the required data transfer speeds.
Keep your system updated—Windows 10 updates often include fixes for storage-related errors.
If the error occurs during a Windows installation, try using a different USB port (preferably USB 2.0) and ensure the installation media is created with the official Media Creation Tool.
For large file transfers, use a tool like Robocopy that can resume interrupted transfers, reducing the chance of hitting this error.

Troubleshooting

If you’ve tried all the steps and the error persists, consider these additional checks:

Check the Event Viewer for more details. Press Win + X and select Event Viewer. Look under Windows Logs > System for errors around the time the error occurred. The details can point to the specific driver or hardware.
Test the device on another computer. If it works there, the issue is with your system’s configuration. If it fails, the device itself is likely faulty.
Try a different file manager. Sometimes Windows Explorer has issues. Use a third-party file manager like Total Commander to see if the transfer goes through.
Check for BIOS/UEFI updates. Visit your motherboard or laptop manufacturer’s website and see if a BIOS update addresses storage controller issues. Only do this if you’re comfortable—a failed BIOS update can brick your system.
As a last resort, reset Windows. Go to Settings > Update & Security > Recovery and choose Reset this PC. Choose Keep my files to preserve personal data, but reinstall apps. This fixes deep system corruption.

Frequently Asked Questions

What exactly causes error 0x8007045d?

The error means “ERROR_IO_DEVICE”—Windows couldn’t read data from the device. Common causes include faulty cables, outdated drivers, corrupted file systems, or a failing drive.

Can this error damage my files?

Yes, if the drive is failing, it can cause data corruption. That’s why it’s crucial to back up important files as soon as you see this error.

Does this error only happen with external drives?

No, it can also occur with internal drives, DVD drives, or even network drives. The fixes are similar, but for internal drives, check SATA cables and connections.

Will running chkdsk fix the error?

Often, yes. Chkdsk repairs file system errors that can cause read failures. But if the drive has physical damage, chkdsk might not help and could make it worse.

Is it safe to ignore this error if it only happens occasionally?

It’s risky. Occasional errors might be due to a loose connection, but they could also be early signs of drive failure. Investigate before it becomes a bigger problem.

How long does the DISM command take?

It can take anywhere from 10 minutes to over an hour, depending on your system’s speed and the extent of corruption. Let it run to completion.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →