Laptop screen showing Windows Update error with technician troubleshooting
0x80070003Windows UpdateWindows

Fix Windows Update Error 0x80070003 – Windows 10, Windows 11 2026

Windows Update error 0x80070003 indicates file system corruption or missing update components. This comprehensive guide provides five proven methods to resolve the error, from basic troubleshooting to advanced system repairs.

Emanuel DE ALMEIDAEmanuel DE ALMEIDA
10 Mar 202612 min read1 views

Last updated 11 Mar 2026

Error Code0x80070003
ProductWindows Update
KB ArticleKB5034441
Solutions5 methods
Sources2 official
Affected SystemsWindows 10, Windows 11
Quick Fix

Run the Windows Update Troubleshooter from SettingsSystemTroubleshootOther troubleshootersWindows Update. If that fails, execute sfc /scannow in an elevated Command Prompt to repair corrupted system files.

Symptoms

  • Windows Update fails with error code 0x80070003
  • Update downloads but fails during installation
  • System shows 'Something went wrong' message during updates
  • Windows Update service stops responding
  • Cumulative updates fail repeatedly
  • Feature updates cannot be installed

Possible Causes

  • Corrupted Windows Update components or cache files
  • Missing or damaged system files required for updates
  • Insufficient disk space in the Windows partition
  • Third-party antivirus interference with update processes
  • Registry corruption affecting Windows Update services
  • Network connectivity issues during download
  • Conflicting pending updates or incomplete installations
1

Run Windows Update Troubleshooter

Windows includes a built-in troubleshooter specifically designed to resolve update-related issues.

  1. Press Windows + I to open Settings
  2. Navigate to SystemTroubleshootOther troubleshooters
  3. Locate Windows Update and click Run
  4. Allow the troubleshooter to scan and detect issues
  5. Follow the on-screen prompts to apply recommended fixes
  6. Restart your computer when prompted
  7. Open Windows Update and attempt to install updates again

Verification: Navigate to SettingsWindows Update and click Check for updates. The error should no longer appear.

2

Reset Windows Update Components

This method manually resets all Windows Update services and clears the update cache.

Warning: Run Command Prompt as Administrator for these commands to work properly.
  1. Press Windows + X and select Terminal (Admin)
  2. Stop Windows Update services by running these commands:
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
  1. Rename the SoftwareDistribution and catroot2 folders:
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
  1. Restart the Windows Update services:
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
  1. Close Command Prompt and restart your computer
  2. Open Windows Update and check for updates

Verification: Run Get-Service wuauserv,cryptsvc,bits,msiserver in PowerShell to confirm all services are running.

3

Run System File Checker and DISM

System file corruption often causes update failures. Use SFC and DISM to repair damaged files.

  1. Open Command Prompt as Administrator
  2. Run the System File Checker:
sfc /scannow
  1. Wait for the scan to complete (this may take 15-30 minutes)
  2. If SFC finds issues, run DISM to repair the Windows image:
DISM /Online /Cleanup-Image /RestoreHealth
  1. After DISM completes, run SFC again to ensure all files are repaired:
sfc /scannow
  1. Restart your computer
  2. Attempt Windows Update installation
Pro tip: If DISM fails, you can specify a Windows installation media as the source using DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\Sources\install.wim

Verification: Check the SFC log at %windir%\Logs\CBS\CBS.log to confirm no integrity violations remain.

4

Clear Windows Update Cache and Registry

Manual cache clearing and registry cleanup can resolve persistent update issues.

Warning: Back up your registry before making changes. Incorrect modifications can cause system instability.
  1. Create a registry backup by running:
reg export HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate C:\backup_wu_registry.reg
  1. Stop Windows Update services:
net stop wuauserv
net stop bits
net stop cryptsvc
  1. Delete Windows Update cache folders:
rd /s /q C:\Windows\SoftwareDistribution
rd /s /q C:\Windows\System32\catroot2
  1. Open Registry Editor (regedit) and navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate
  1. Delete the AU subkey if present
  2. Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update
  1. Delete the RebootRequired value if it exists
  2. Restart Windows Update services:
net start wuauserv
net start bits
net start cryptsvc
  1. Restart your computer and test Windows Update

Verification: Run Get-WindowsUpdateLog in PowerShell to generate a readable update log and check for errors.

5

Perform In-Place Windows Upgrade

If all previous methods fail, an in-place upgrade repairs Windows while preserving your files and applications.

  1. Download the Windows 11 Installation Assistant or Media Creation Tool from Microsoft's official website
  2. Run the installation tool and select Upgrade this PC now
  3. Choose Keep personal files and apps when prompted
  4. Follow the installation wizard to complete the upgrade
  5. After the upgrade completes, check Windows Update functionality

Alternative method using ISO file:

  1. Download the latest Windows ISO file
  2. Mount the ISO by double-clicking it
  3. Run setup.exe from the mounted drive
  4. Select Download updates, drivers and optional features
  5. Choose Keep personal files and apps
  6. Complete the installation process
Pro tip: Before starting the in-place upgrade, run Get-ComputerInfo | Select WindowsProductName, WindowsVersion to document your current Windows version.

Verification: After the upgrade, run winver to confirm the new Windows version, then test Windows Update functionality.

Verification

To confirm the error 0x80070003 has been resolved, perform these verification steps:

  1. Open SettingsWindows Update
  2. Click Check for updates and wait for the scan to complete
  3. Verify that updates download and install without error codes
  4. Run this PowerShell command to check Windows Update service status:
Get-Service wuauserv,bits,cryptsvc | Format-Table Name,Status,StartType

All services should show 'Running' status. Additionally, check the Windows Update history by clicking Update history to ensure recent updates installed successfully.

Still Having Issues?

If the above methods didn't resolve error 0x80070003, try these advanced alternatives:

Advanced Registry Repair

Use the Registry Editor to manually clean Windows Update entries:

reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /f
reg delete "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /f

Clean Boot Troubleshooting

Perform a clean boot to isolate software conflicts:

  1. Run msconfig
  2. Select Selective startup and uncheck Load startup items
  3. Go to Services tab, check Hide all Microsoft services, then Disable all
  4. Restart and test Windows Update

Windows Update Standalone Installer

Download specific updates manually from the Microsoft Update Catalog and install using:

wusa.exe KB5034441.msu /quiet /norestart

If these advanced methods fail, consider contacting Microsoft Support or performing a clean Windows installation while backing up your data.

Frequently Asked Questions

What does Windows Update error 0x80070003 mean exactly?
Error 0x80070003 is a system error code that translates to 'The system cannot find the path specified.' In the context of Windows Update, this typically indicates that the update service cannot locate required files, registry entries, or system components needed to complete the update installation. This often occurs due to corrupted Windows Update cache, missing system files, or registry corruption affecting the update process.
Can I safely delete the SoftwareDistribution folder to fix this error?
Yes, it's safe to delete or rename the SoftwareDistribution folder, but you should stop Windows Update services first. The SoftwareDistribution folder contains the Windows Update cache and download history. When you delete it, Windows will automatically recreate it with fresh cache files. Always stop the wuauserv, bits, and cryptsvc services before deleting this folder, then restart them afterward. This process clears corrupted update files that may be causing the 0x80070003 error.
Why does error 0x80070003 keep coming back after I fix it?
Recurring 0x80070003 errors usually indicate an underlying system issue that wasn't fully resolved. Common causes include persistent registry corruption, hardware problems affecting file system integrity, third-party software conflicts, or incomplete system file repairs. If the error returns, run a comprehensive system check using both SFC and DISM commands, check your hard drive for errors using chkdsk, and consider performing a clean boot to identify conflicting software.
Will running SFC and DISM commands affect my personal files?
No, both SFC (System File Checker) and DISM (Deployment Image Servicing and Management) commands only repair system files and Windows components. They do not modify, delete, or affect your personal files, documents, photos, or installed applications. These tools specifically target corrupted Windows system files and the Windows image integrity. However, it's always good practice to maintain regular backups of important data before performing any system repairs.
How long should I wait for the SFC and DISM scans to complete?
SFC scans typically take 15-30 minutes on modern systems with SSDs, but can take up to an hour on older systems with traditional hard drives. DISM RestoreHealth operations usually take 20-45 minutes, depending on your internet connection speed and system performance, as it may need to download files from Windows Update. Don't interrupt these processes even if they appear stuck at certain percentages - they often pause while performing intensive operations. If a scan takes longer than 2 hours, restart your computer and try again.

Which method worked?

Vote to help others

Official Resources

About the Author

Emanuel DE ALMEIDA

Emanuel DE ALMEIDA

Senior IT Journalist & Cloud Architect

Microsoft MCSA-certified Cloud Architect | Fortinet-focused. I modernize cloud, hybrid & on-prem infrastructure for reliability, security, performance and cost control - sharing field-tested ops & troubleshooting.

Discussion

Share your thoughts and insights

You must be logged in to comment.

Loading comments...