Free tools Windows power users keep installed
One-click scans. No signup required.
Error 0x8007045D means Windows encountered an input/output (I/O) device error while reading or writing update data. It can be caused by a failing internal disk, damaged USB or other removable media, a bad cable or port, a corrupted download, or damaged Windows files. Back up important data first, then isolate external hardware, run the Windows Update troubleshooter, check the affected volume, repair system files, and reset the update cache in that order.
What error 0x8007045D means
Windows uses the code 0x8007045D for ERROR_IO_DEVICE: “The request could not be performed because of an I/O device error.” During an update, the operating system must repeatedly read existing files, write temporary packages, verify data, and commit changes. A failure anywhere along that path can produce the same code.
As an Amazon Associate I earn from qualifying purchases.
The code identifies a failed read or write operation, not one specific defective component. Possible causes include:
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11- A degrading internal HDD or SSD, bad sectors, or a controller problem.
- A damaged USB flash drive, external disk, SD card, CD, or DVD involved in the operation.
- A loose or defective USB cable, port, card reader, dock, or hub.
- An incomplete or corrupted update download.
- Corrupted Windows component-store or system files.
- Firmware, burner, or unsupported media-speed problems when optical or removable media is involved.
Consequently, the error does not by itself prove that your hard drive is failing. The troubleshooting goal is to determine whether the failure follows Windows software or follows a particular storage device or connection.
#1 Best Overall
- Dual USB-A & USB-C Bootable Drive – compatible with nearly all Windows PCs, laptops, and tablets (UEFI & Legacy BIOS). Works with Surface devices and all major brands.
- Fully Customizable USB – easily Add, Replace, or Upgrade any compatible bootable ISO app, installer, or utility (clear step-by-step instructions included).
- Complete Windows Repair Toolkit – includes tools to remove viruses, reset passwords, recover lost files, and fix boot errors like BOOTMGR or NTLDR missing.
- Reinstall or Upgrade Windows – perform a clean reinstall of Windows 7 (32bit and 64bit), 10, or 11 (amd64 + arm64) to restore performance and stability. (Windows license not included.). Includes Full Driver Pack – ensures hardware compatibility after installation. Automatically detects and installs drivers for most PCs.
- Premium Hardware & Reliable Support – built with high-quality flash chips for speed and longevity. TECH STORE ON provides responsive customer support within 24 hours.
Protect your files before changing anything
Copy documents, photographs, project files, browser exports, and other irreplaceable data to a separate location before running disk repairs or repeatedly retrying an update. A USB drive can be used for this backup if it is known to be healthy; eject it properly when the copy finishes. If a drive is making unusual noises, disappearing, or producing repeated read errors, prioritize copying recoverable files rather than testing it aggressively.
- Keep the computer connected to reliable power. Do not begin a long disk check on a laptop with a nearly empty battery.
- Use an administrator account for the repair steps.
- Do not format a suspect drive until you have copied data you still need.
- Do not interrupt a running disk check unless the computer is in immediate danger of overheating or losing power.
Record exactly where the update failed
Knowing whether the error appeared during download, verification, or installation helps distinguish a network/cache problem from a storage-path problem.
- Open Settings.
- On Windows 11, select Windows Update; on Windows 10, select Update & Security, then Windows Update.
- Open Update history and locate the failed entry.
- Write down the complete error text, the failed KB number (if shown), and whether the failure occurred while downloading, installing, or restarting.
Keep the KB number and your Windows edition/build available if you later need manufacturer or Microsoft support. A single failed KB can have different prerequisites from a feature upgrade.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsRemove variables and retry once
Shut down the computer, disconnect hardware that is not required to boot or install updates, and start it again. In particular, remove extra USB drives, external hard disks, card readers, docks, printers, optical media, and USB hubs. Leave only the keyboard, mouse, display, network connection, and any device Windows needs to operate.
Connect the PC to a stable network and retry the update once. If it succeeds with the extra hardware removed, reconnect devices one at a time and test again. The last device or connection added is a strong suspect. If the update still fails with a minimal setup, continue with the software and storage checks below.
Run the Windows Update troubleshooter
Windows 11
- Open Settings and choose System.
- Select Troubleshoot, then Other troubleshooters.
- Find Windows Update and select Run. On current Windows 11 releases, Microsoft may direct you to the automated troubleshooter in the Get Help app; follow its prompts.
- Allow the checks and any offered repairs to complete, restart the PC, and try the same update again.
Windows 10
- Open Settings.
- Go to Update & Security > Troubleshoot > Additional troubleshooters.
- Select Windows Update, choose Run the troubleshooter, and apply its recommendations.
- Restart Windows and retry the update.
The troubleshooter can correct common service, configuration, and cache conditions. It cannot repair a physically failing disk or a broken cable, so continue to hardware isolation if the same I/O code returns.
Isolate a removable drive, card, port, or cable
If the error appears only when a removable device is connected, or if the update is being read from or written to that device, test the entire I/O path rather than replacing parts at random.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
| Test | How to perform it | What the result suggests |
|---|---|---|
| Different USB port | Move the device directly to another port on the computer. Avoid a hub or dock for the test. | If only one port fails, the port, hub, or its power delivery may be at fault. |
| Different cable | Use a known-good cable with the same connector and data capability. | If the error disappears, replace the cable. |
| Different reader or adapter | Test an SD card or similar media in another reader or adapter. | A working card in one reader but not another points to the reader or adapter. |
| Different computer | Connect the suspect drive or card to another known-good computer. | If the error follows the device, copy data and plan service or replacement. If it works elsewhere, investigate the original PC’s port, driver, or controller. |
| Minimal configuration | Disconnect every nonessential external device and retry the update. | Success identifies an external-device or connection conflict rather than proving the internal disk is bad. |
Do not repeatedly reconnect a device that is disconnecting, becoming unusually hot, or reporting that it must be formatted. Preserve data first. Optical-media errors can also involve a defective burner, firmware, damaged disc, or media written at an unsupported speed.
Rank #2
- High-speed USB 3.0 performance of up to 150MB/s(1) [(1) Write to drive up to 15x faster than standard USB 2.0 drives (4MB/s); varies by drive capacity. Up to 150MB/s read speed. USB 3.0 port required. Based on internal testing; performance may be lower depending on host device, usage conditions, and other factors; 1MB=1,000,000 bytes]
- Transfer a full-length movie in less than 30 seconds(2) [(2) Based on 1.2GB MPEG-4 video transfer with USB 3.0 host device. Results may vary based on host device, file attributes and other factors]
- Transfer to drive up to 15 times faster than standard USB 2.0 drives(1)
- Sleek, durable metal casing
- Easy-to-use password protection for your private files(3) [(3)Password protection uses 128-bit AES encryption and is supported by Windows 7, Windows 8, Windows 10, and Mac OS X v10.9 plus; Software download required for Mac, visit the SanDisk SecureAccess support page]
Check the affected volume with CHKDSK
CHKDSK can find file-system errors and unreadable sectors on a volume. Use it only after confirming the correct drive letter and copying recoverable data.
- Press Win, type
TerminalorCommand Prompt, right-click the result, and select Run as administrator. - At the elevated prompt, enter
chkdsk X: /r, replacingXwith the letter of the affected volume. For example, a removable drive shown asE:would usechkdsk E: /r. - Read the volume name and confirmation prompt carefully. If Windows says the volume is in use and offers to schedule the check for the next restart, type
Yonly when the drive letter is correct, then restart. - Let the scan finish. The
/roption can take a long time, especially on a large or damaged hard disk.
Review the final report. Repairs to the file system may explain the update failure, but CHKDSK cannot restore data that has already become unreadable and cannot guarantee that a deteriorating drive will remain reliable. If errors return, use the drive manufacturer’s diagnostic utility and prepare to replace the component after securing your files.
Repair Windows component and system files
Run these commands when the storage path passes its basic checks or when the failure occurs with no removable hardware attached. They require an elevated Terminal or Command Prompt.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →- Open Terminal (Admin) or Command Prompt (Admin).
- Run
DISM.exe /Online /Cleanup-image /Restorehealthand wait for it to reach completion. DISM repairs the Windows component store that servicing uses. - After DISM completes, run
sfc /scannow. System File Checker compares protected Windows files with their expected versions and replaces corrupt copies when possible. - Restart the computer, check Update history, and retry the failed KB.
Do not close the terminal merely because progress appears paused; both operations can spend several minutes on one percentage. If DISM reports that it cannot find source files, note the exact message and Windows build rather than downloading an unverified system image. The result may require build-specific Microsoft servicing guidance.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Reset the Windows Update download cache
A damaged update package or cache can keep producing the same error even when the disk and system files are healthy. Reset the cache only after backing up and completing the checks above, because Windows will need to download the update again.
- Open Terminal (Admin) or Command Prompt (Admin).
- Stop the Windows Update service by running
net stop wuauserv. Wait for confirmation that the service has stopped. - Open File Explorer and browse to
C:WindowsSoftwareDistribution. - Delete the contents inside
SoftwareDistribution, not the parentWindowsfolder. If a file is locked, close Settings and other update-related windows and try again after confirming the service is stopped. - Return to the elevated terminal and run
net start wuauserv. - Restart Windows, reconnect only essential hardware, and check for updates again.
Windows rebuilds the cleared cache as it checks for updates. The first scan after the reset may take longer because packages must be downloaded again. If the same KB fails immediately with the I/O code, the cache is less likely to be the root cause than the storage path or update prerequisite state.
Use the failure pattern to choose the next step
| Observed pattern | Most useful next action | Data risk |
|---|---|---|
| Update succeeds after unplugging one external device | Stop using that device until its data is copied; test another cable, port, or computer, then replace or service the failing part. | High if the device is disconnecting or unreadable; copy files before more tests. |
| CHKDSK reports errors on one volume | Review the report, run the manufacturer’s diagnostics, and plan replacement if errors recur. | High on a degrading disk. |
| No external devices are attached; DISM or SFC reports corruption | Allow both repairs to finish, restart, and retry the exact KB. | Usually low, but keep the backup. |
| Only one KB fails after hardware and file checks pass | Use the KB number and Windows build to review Microsoft’s update or upgrade-installation requirements and prerequisites. | Low from troubleshooting itself; avoid unofficial packages. |
| The error follows an internal disk across repeated attempts | Secure data, run the disk manufacturer’s diagnostics, and replace the disk or obtain professional recovery help. | Very high; stop unnecessary writes. |
When to stop troubleshooting and escalate
Arrange hardware service or replacement when a drive disappears from File Explorer, produces repeated I/O errors on more than one computer, develops abnormal noises, or fails its manufacturer’s diagnostic tests. Keep the original drive powered off when possible after data recovery; continued operation can make recovery harder.
If storage tests pass, external hardware is removed, DISM and SFC complete, and the same KB still fails, record the Windows edition, build number, KB number, and complete error text. Consult Microsoft’s Windows Update and upgrade-installation guidance for that exact build. Requirements can differ between monthly quality updates and larger feature upgrades, so do not apply a generic package intended for another release.
Quick Recap
Common mistakes that make 0x8007045D harder to fix
- Skipping the backup: disk repair and repeated retries can add stress to failing media.
- Testing through a hub: a hub or dock introduces another power and connection variable. Test directly on the computer first.
- Using the wrong drive letter: verify the volume in File Explorer before running CHKDSK; a wrong letter can check a different disk.
- Formatting too early: formatting destroys the file-system structures needed for many recovery attempts.
- Interrupting CHKDSK, DISM, or SFC: apparent pauses do not necessarily mean the process has stopped.
- Repeating the same update without recording the KB: the KB number and failure stage determine which prerequisites and logs matter.
- Assuming the code proves a virus or a dead hard drive: it indicates an I/O failure; hardware isolation and file checks are needed to identify the cause.
Optional shortcut after the manual checks
As an optional shortcut, Outbyte PC Repair can look for more than 100 common Windows issues, adjust settings that affect CPU, RAM, and disk load, clean temporary and cache files, check Windows settings and missing updates, and provide an app-crash log. It runs on Windows 11, 10, 8, and 7, with a free trial by category (at least two days) followed by a subscription. It complements antivirus software rather than replacing it; results vary, and no tool repairs every update or hardware failure.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
