How to Resolve 'Windows Update Failed: Code 0x80070057' by Resetting Component Store
This guide provides a comprehensive, multi-stage process to resolve the persistent 'Windows Update Failed: Code 0x80070057' error by systematically resetting corrupted Windows Update components and rebuilding the core system image.
Direct Diagnostic & Remediation Summary
- Action 1: Run System File Checker (SFC) to check integrity: Open elevated CMD and execute
sfc /scannow. - Action 2: Reset Update Components via PowerShell: Use the provided sequence of commands to stop services, rename folders, and restart them.
- Action 3: Run DISM tool for component store repair: Execute
DISM /Online /Cleanup-Image /RestoreHealthin an elevated command prompt.
Initial Triage & Environment Isolation (Stopping Services)
Before making changes, we must isolate the update mechanism by stopping associated services to prevent them from interfering with our repairs. This ensures a clean slate for component manipulation.
net stop wuauserv
net stop bits
net stop cryptSvc
net stop msiserver
After executing the above commands, proceed to manually rename the SoftwareDistribution and Catroot2 folders. These folders hold cached update data that might be corrupted.
- Action: Open File Explorer (Win + E).
- Action: Navigate to
%windir%(usually C:\\Windows). - Action: Locate the folders named
SoftwareDistributionandCatroot2. - Action: Rename both of these folders to include a suffix, for example,
SoftwareDistribution.oldandCatroot2.old.
Diagnostic Scans & Hardware Isolation (System Integrity Check)
With the update cache cleared, we must verify the core operating system files. We use two critical built-in tools: System File Checker (SFC) and Deployment Image Servicing and Management (DISM).
Open Command Prompt or PowerShell as Administrator (Right-click Start Menu -> Terminal/CMD (Admin)). Execute SFC first:
sfc /scannow
Wait for this scan to complete. If it reports any repairs, restart your machine immediately before proceeding. Next, run DISM. This tool checks and repairs the component store itself.
DISM /Online /Cleanup-Image /CheckHealth
If CheckHealth passes, proceed to the full repair:
DISM /Online /Cleanup-Image /RestoreHealth
This process requires internet access and can take significant time (up to 30 minutes or more). Do not interrupt it.
Targeted Remediation & Fixes (Restarting Services)
The final step in the repair sequence is to restart all necessary Windows Update services, allowing them to rebuild their necessary pointers using the clean component store.
net start wuauserv
net start bits
net start cryptSvc
net start msiserver
After starting the services, perform a full system reboot. This allows all services to load their new configurations against the repaired component store.
- Action: Restart your computer normally (Do not use Shutdown if possible).
- Action: Once logged back in, attempt to run Windows Update manually through Settings.
Common Pitfalls & Advanced Diagnostics
If the 0x80070057 error persists after completing Steps 1-3, consider these advanced checks:
- Pitfall: User Profile Corruption: If multiple users report issues, the problem might be system-wide. Try creating a new local administrator profile and testing updates under that account to rule out user profile corruption.
- Pitfall: Third-Party Security Software: Aggressive antivirus or firewall suites (especially corporate endpoint protection) can sometimes block necessary update traffic. Temporarily disable them during the final update attempt only.
- Advanced Diagnostic (Registry Check): Verify that the following keys exist and are not corrupted in the Registry Editor (Regedit):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate. Manual registry edits are highly risky; proceed with caution or consult advanced support if unsure.
Verification, Results & Long-Term Stability Validation
To confirm the resolution, you must simulate a full update cycle. Do not just check if it "runs"; verify that updates download, install, and complete successfully.
- Initiate Update: Go to Settings -> Windows Update and click 'Check for updates'.
- Monitor Progress: Observe the entire process from start to finish. If multiple cumulative or optional updates are found, allow them to install fully.
- Check Reliability: After all updates complete and the system reboots, check the Event Viewer (Windows Logs -> System) for any critical errors related to 'UpdateOrchestrator' or 'WUDF'. A clean log indicates success.
For long-term stability, ensure that your hardware drivers (especially Chipset and Network Adapters) are updated directly from the PC manufacturer's website (Dell Support, HP Support, etc.), rather than solely relying on Windows Update.
Frequently Asked Questions
Q: Can I fix this without using Administrator rights?
A: No. The commands used to stop services, rename protected system folders, and run DISM require elevated administrative privileges to modify core operating system components safely.Q: What if the folder renaming in Step 1 fails because Windows locks the files?
A: If the service cannot be stopped (Step 1), you must reboot into Safe Mode first. Once in Safe Mode, repeat the process of stopping services and renaming folders. Safe Mode loads only essential drivers, often bypassing lockouts.Q: Is running SFC/DISM too resource-intensive?
A: While these scans are intensive, they are necessary for repair. They read and write to critical system areas; thus, the temporary high CPU/Disk usage is expected and indicates that the diagnostic tools are functioning correctly.net stop wuauserv
net stop bits
net stop cryptSvc
net stop msiserver
sfc /scannow
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /RestoreHealth
net start wuauserv
net start bits
net start cryptSvc
net start msiserver
Frequently Asked Questions
Can I fix this without using Administrator rights?
No. The commands used to stop services, rename protected system folders, and run DISM require elevated administrative privileges to modify core operating system components safely.
What if the folder renaming in Step 1 fails because Windows locks the files?
If the service cannot be stopped (Step 1), you must reboot into Safe Mode first. Once in Safe Mode, repeat the process of stopping services and renaming folders. Safe Mode loads only essential drivers, often bypassing lockouts.
Is running SFC/DISM too resource-intensive?
While these scans are intensive, they are necessary for repair. They read and write to critical system areas; thus, the temporary high CPU/Disk usage is expected and indicates that the diagnostic tools are functioning correctly.
Need help implementing this solution?
Our cybersecurity and infrastructure engineers can audit, harden, or configure your systems directly.
Community Discussion & Confirmations (0)
Technical questions, hardware findings, and verified fix reports.
No reader questions posted yet. Have you tried this solution or experienced an edge case? Post below.