How to Resolve Windows Update Error 0x8007003B

Error 0x8007003B blocking Windows Update? Run the troubleshooter, reset update components, and repair system files.

Founder & Lead Technician

May 18, 2026 at 10:37 AM IST 6 min

how-to-resolve-error-0x8007003b-on-windows

Quick answer

To fix Windows Update error 0x8007003B, run the Windows Update troubleshooter under Settings, reset update components by stopping the Windows Update service and clearing the SoftwareDistribution folder, then run sfc /scannow in an admin Command Prompt.

Error 0x8007003B usually appears during Windows Update or when copying large files, and it almost always traces back to corrupted system files or a broken Windows Update cache. The fastest reliable path is to run the built-in Windows Update troubleshooter, reset the update components by clearing the SoftwareDistribution folder, and run a System File Checker scan. One of those three clears it in most cases.

Despite the cryptic hex code, this isn't a hardware death sentence. It's Windows tripping over its own damaged files. Work the methods below in order and stop when updates start flowing again.

What causes error 0x8007003B

Corrupted system files — damaged files that Windows needs to apply updates.
Outdated device drivers — drivers that no longer bridge hardware and OS correctly.
Insufficient disk space — not enough room to download and stage the update.
Incompatible software — a third-party app, often antivirus, conflicting with the update.
A bad update state — a previous update left the system in a half-applied condition.

Method 1: Check for updates

Sometimes a later cumulative update supersedes the one that's failing.

Open Settings from the Start menu.
Go to Update & Security.
Click Check for updates and install whatever appears.
Restart if prompted, then retry the failed update.

Method 2: Run the Windows Update troubleshooter

Open Settings > Update & Security.
Select Troubleshoot, then Windows Update.
Run the troubleshooter and apply every recommended fix.
Check for updates again once it finishes.

The troubleshooter is underrated. It automatically stops update services, repairs the queue, and restarts them — the same thing you'd do manually, with less chance of a typo. Always try it before the command-line route.

Method 3: Reset Windows Update components

A corrupted update cache is one of the most common causes. Clearing it forces Windows to re-download clean files.

Open services.msc and stop the Windows Update service.
Browse to C:\Windows\SoftwareDistribution and delete the contents of that folder.
Go back to Services and restart the Windows Update service.
Run Check for updates so Windows rebuilds the cache.

Method 4: Run a System File Checker scan

If corrupted system files are the cause, SFC repairs them.

Open Command Prompt as administrator.
Run sfc /scannow and let it finish without interrupting.
Restart the PC and retry the update.

If SFC can't repair everything, run DISM /Online /Cleanup-Image /RestoreHealth first to fix the component store, then run sfc /scannow again.

Quick reference

Method	Best for	Effort
Check for updates	A failing update already superseded	Low
Update troubleshooter	Most general cases	Low
Reset update components	Corrupted update cache	Medium
SFC / DISM scan	Corrupted system files	Medium

Update drivers before assuming it's corruption

Outdated drivers are one of the listed causes, and they're easy to overlook because the error mentions nothing about hardware. A stale storage controller or chipset driver can break the staging step of an update in a way that looks exactly like file corruption. Before you spend twenty minutes on sfc and DISM, spend two on drivers:

Right-click the Start button and open Device Manager.
Expand Disk drives and IDE ATA/ATAPI controllers, right-click each device, and choose Update driver.
For the most current versions, download drivers directly from your PC or motherboard maker rather than relying on Windows' generic ones.
Restart and retry the update.

Why this matters: if a driver is the cause, every system-file repair in the world won't fix it — and you'll wrongly conclude your Windows install is beyond saving when a five-minute driver update was all it needed.

When 0x8007003B hits during file copies, not updates

This error isn't exclusive to Windows Update. Plenty of people meet it while copying large files to or from a network share, and there the cause is different. The most common trigger in that scenario is antivirus real-time scanning choking on a big transfer, followed by SMB protocol mismatches between machines.

If that's your situation, try these targeted fixes instead:

Temporarily pause real-time antivirus scanning and retry the copy. If it succeeds, add the source or destination folder to your antivirus exclusions rather than leaving protection off.
Copy in smaller batches. A single huge transfer is more likely to trip the error than several smaller ones; this is a reliable workaround for one-off jobs.
Check the SMB version on both machines. An old client talking to a newer server (or vice versa) can throw this during sustained transfers.
Use robocopy with the /Z flag for restartable mode, which survives interruptions far better than drag-and-drop copying.

If only large files fail and small ones succeed, stop blaming Windows Update entirely. That pattern almost always points to antivirus scanning or a flaky network link, not corrupted system files.

The advanced fix: DISM in depth

When the basic methods stall, DISM (Deployment Image Servicing and Management) is the heavy artillery. It repairs the Windows image that sfc draws its replacement files from, so the two work as a pair.

Open Command Prompt as administrator.
Run DISM /Online /Cleanup-Image /CheckHealth for a fast status check.
Run DISM /Online /Cleanup-Image /ScanHealth for a deeper scan (a few minutes).
Run DISM /Online /Cleanup-Image /RestoreHealth to actually repair the image.
Follow with sfc /scannow, then restart and retry the update.

If DISM itself fails to download repair files (common when Windows Update is the very thing that's broken), point it at a mounted Windows ISO with the /Source parameter so it pulls clean files locally instead of from the network.

Order matters: run DISM /RestoreHealth before sfc /scannow, not after. SFC fixes individual files using the component store, so the store has to be healthy first or SFC just pulls from corrupted source files.

Common mistakes that make this worse

Deleting SoftwareDistribution without stopping the service. Windows holds those files open. Stop the Windows Update service first, or the delete fails and you assume the fix didn't work.
Interrupting sfc /scannow. The scan can take 10-20 minutes and may appear stuck at a percentage. Let it finish — killing it mid-repair can leave files in a worse state.
Ignoring disk space. Cumulative updates can need several gigabytes of free space to download and stage. A nearly full drive produces errors that look like corruption but aren't.

Manually resetting every update component

The folder-delete method handles most cases, but a stubborn 0x8007003B sometimes needs a full component reset. This rebuilds the entire Windows Update machinery from scratch. Run each line in an administrator Command Prompt:

net stop wuauserv — stops the Windows Update service.
net stop cryptsvc — stops the Cryptographic service.
net stop bits — stops the Background Intelligent Transfer service.
net stop msiserver — stops the Windows Installer service.
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old — renames the update cache.
ren C:\Windows\System32\catroot2 catroot2.old — renames the catalog store.
Restart all four services with their matching net start commands.
Run Check for updates so Windows rebuilds both folders cleanly.

Renaming rather than deleting is the safe play here. If anything goes sideways, you can stop the services again and rename the .old folders back, restoring your previous state instantly.

Why this matters: the simple SoftwareDistribution delete only refreshes the download cache. Resetting catroot2 as well clears corrupted update signatures, which is often the missing piece when 0x8007003B refuses to budge.

How to stop it happening again

A few habits keep 0x8007003B from returning. Keep at least 15-20 GB free on your system drive so updates always have room to stage. Update your device drivers periodically through Device Manager or your hardware maker's tool, since outdated storage and chipset drivers are a quiet contributor. And if you run a third-party security suite, add Windows Update's processes and your common network shares to its exclusions so its real-time scanner stops fighting legitimate file operations.

Why this matters: 0x8007003B is a symptom, not a single bug. Each method targets a different root cause, so running them in order systematically eliminates the possibilities instead of leaving you rebooting and hoping. If all four update methods fail, free up at least 10 GB of disk space and temporarily disable third-party antivirus before trying the update once more.

Frequently asked questions

What does Windows error 0x8007003B mean?＋

It signals a failure during Windows Update or when copying large files, typically caused by corrupted system files or a broken Windows Update cache. Outdated drivers, low disk space, and conflicting antivirus software can also trigger it. It's a fixable software issue, not a sign of failing hardware.

Is it safe to delete the SoftwareDistribution folder contents?＋

Yes, as long as you stop the Windows Update service first. The folder only holds temporary update files, and Windows rebuilds it automatically the next time you check for updates. Clearing it removes corrupted cached data that commonly causes Error 0x8007003B, without affecting your personal files.

What should I do if sfc /scannow can't fix the error?＋

Run DISM /Online /Cleanup-Image /RestoreHealth in an admin Command Prompt first to repair the component store that SFC relies on, then run sfc /scannow again. If the error persists, free up at least 10 GB of disk space and temporarily disable third-party antivirus before retrying.

#error0x8007003b#windowsupdateerror#fix0x8007003b#sfcscannow

Harjindar Singh

Founder & Lead Technician

Harjindar founded Ask Technicians to cut through bad tech advice. He writes hands-on troubleshooting guides drawn from years of real-world repair and support work.