How to Fix ‘The Request Could Not Be Performed Because of an I/O Device Error’ (0x8007045D) in Windows 11

Attempting to copy documents, run backups, clone disk images, or install software onto an internal solid-state drive or external USB hard disk in Windows 11 can abruptly freeze the file system and trigger error code 0x8007045D: ‘The request could not be performed because of an I/O device error’. Input/Output (I/O) errors represent critical communication breakdowns where the operating system sends a low-level hardware read or write instruction, but the physical storage controller fails to return a confirmation within the allotted driver timeout window.

What Causes Error 0x8007045D in Windows 11?

Because I/O device errors occur at the physical interface between hardware and Windows kernel drivers, common culprits include:

  • Damaged Sectors (Bad Blocks): Physical degradation or magnetic platter damage on spinning hard drives, or worn-out NAND flash memory cells on USB drives and SSDs.
  • Unstable USB Cables or Power Dropouts: Low-quality USB cables, worn-out USB-C ports, or unpowered hubs failing to deliver sustained electrical voltage during heavy write queues.
  • Corrupted Storage Controller Drivers: Outdated or broken AHCI, NVMe, or USB mass storage host controller drivers mismanaging transfer buffers.
  • File System Inconsistencies: Damaged Master File Tables (MFT) or corrupted directory pointers preventing Windows from locating file boundaries.
  • Antivirus Deep Scanning Locks: Real-time security software locking files mid-transfer to evaluate signatures, causing driver time-outs.

Step 1: Check Physical Connections and Change USB Ports

Hardware signal degradation accounts for over half of all external I/O device failures.

  1. Disconnect the drive from any external USB splitter or desktop front-panel port.
  2. Connect the storage device directly into a rear motherboard USB 3.0 / 3.2 port.
  3. Replace the USB cable connecting your external drive enclosure. Faulty micro-B or USB-C cables frequently drop signal under heavy data load.
  4. If the drive uses an external AC power adapter, verify the power brick is plugged into a wall outlet rather than an overloaded surge strip.

Step 2: Run CHKDSK in Repair Mode via Command Prompt

Check Disk verifies sector health and reallocates data stored in failing blocks to spare reserve sectors.

  1. Press Windows Key + S, type cmd, right-click Command Prompt, and select Run as administrator.
  2. Identify the drive letter displaying the I/O error in File Explorer (e.g., drive D:).
  3. Type the following command, substituting your drive letter:
    chkdsk D: /f /r /x
  4. Press Enter.
    • The /f parameter fixes logical filesystem errors.
    • The /r parameter locates bad sectors and recovers readable information.
    • The /x parameter forces the volume to dismount before scanning begins.
  5. Allow the scan to finish. If scanning an internal system drive (C:), type Y and reboot your PC to allow the check to run during boot.

Step 3: Update Storage Controller and Chipset Drivers

Outdated SATA AHCI or NVMe storage drivers can cause I/O command timeouts under modern Windows 11 updates.

  1. Right-click the Start button and select Device Manager.
  2. Expand the IDE ATA/ATAPI controllers and Storage controllers sections.
  3. Right-click your storage controller (e.g., Standard NVM Express Controller or Intel Chipset SATA RAID Controller) and choose Update driver.
  4. Select Search automatically for drivers.
  5. Expand Universal Serial Bus controllers, right-click USB Mass Storage Device, and select Uninstall device.
  6. Unplug the external drive, restart your computer, and reconnect the drive. Windows will reload clean driver binaries.

Step 4: Check S.M.A.R.T. Health Status via PowerShell

Querying the drive’s built-in self-monitoring reporting system reveals whether the disk is physically dying.

  1. Right-click the Start button and select Terminal (Admin) or PowerShell (Admin).
  2. Execute the following command to retrieve hardware health telemetry:
    Get-PhysicalDisk | Select-Object DeviceId, FriendlyName, OperationalStatus, HealthStatus
  3. Examine the HealthStatus column:
    • If it reports Healthy: The error is caused by logical filesystem corruption or driver communication issues.
    • If it reports Warning or Unhealthy: The drive has exhausted its spare sectors and is physically failing. Backup your readable data immediately before the drive ceases functioning entirely.

Step 5: Perform a Clean Boot to Eliminate Driver Conflicts

Third-party disk encryption tools, virtual drive emulators, and antivirus software can block I/O requests.

  1. Press Windows Key + R, type msconfig, and press Enter.
  2. Go to the Services tab.
  3. Check the box labelled Hide all Microsoft services.
  4. Click Disable all.
  5. Navigate to the Startup tab and click Open Task Manager. Disable all non-essential startup programmes.
  6. Restart Windows 11 and attempt your file operation. If it succeeds, re-enable services progressively to isolate the conflicting utility.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.