Windows Update keeps your system secure, but error codes like 0x80070422 can leave your PC stuck on a loading screen or rolling back changes. This specific code usually means the Windows Update service is disabled, blocked, or unable to communicate with Microsoft servers. Other frequent failures like 0x80070002, 0x80070643, and 0x80240034 follow similar root causes, which means a systematic approach will resolve them faster than guessing.
Before You Start: Back up your important files before modifying system services or running command-line scripts. These steps work on Windows 11 and Windows 10, including Pro, Enterprise, and Education editions. You will need an active internet connection and administrator privileges to complete the component reset.
Step 1: Verify the Windows Update Service Is Enabled
Open the Services console by pressing Win + R, typing services.msc, and hitting Enter. Locate Windows Update in the alphabetical list, double-click it, and change the Startup type to Automatic (Delayed Start). Click Start under the Service status section, then select Apply and OK. You will see the service transition to a running state, which removes the primary block causing error 0x80070422. If the service refuses to start or immediately stops, check the Event Viewer for dependent service failures before moving to the next step.
Step 2: Clear the Corrupted Update Cache
Navigate to C:\Windows\SoftwareDistribution and delete the contents of the DataStore and Download folders. These folders store downloaded update files and database records that frequently become corrupted after interrupted installations. You will need to stop the Windows Update service first, which you can do by right-clicking the service in services.msc and selecting Stop, or by running net stop wuauserv in an elevated Command Prompt. After clearing the folders, restart the service and attempt the update again. If Windows blocks you from deleting files due to active processes, reboot into Safe Mode and repeat the deletion.
Step 3: Run the Built-in Windows Update Troubleshooter
Open Settings, navigate to System > Troubleshoot > Other troubleshooters, and click Run next to Windows Update. The diagnostic tool scans for misconfigured update components, broken registry keys, and service dependencies automatically. You will watch a progress bar while it tests the update agent, and Windows will display a summary of any fixes it applied. If the troubleshooter reports no issues but the error persists, rely on the manual component reset in Step 4 instead.
Step 4: Reset Windows Update Components via Command Prompt
Open an elevated Command Prompt by right-clicking the Start button and selecting Terminal (Admin) or Command Prompt (Admin). Paste the following commands one by one, pressing Enter after each line: net stop wuauserv, net stop cryptSvc, net stop bits, net stop msiserver, ren C:\Windows\SoftwareDistribution SoftwareDistribution.old, ren C:\Windows\System32\catroot2 catroot2.old, net start wuauserv, net start cryptSvc, net start bits, net start msiserver. You are renaming the corrupted folders to force Windows to recreate fresh copies on the next update cycle. The command window will return to the prompt without displaying success messages, which is normal behavior. If any command returns an access denied error, ensure you are running the terminal with administrator privileges.
Step 5: Check for Conflicting Third-Party Software
Open Settings > Apps > Installed apps and look for antivirus, firewall, or system optimization tools you recently added. Security software frequently blocks update traffic by flagging Microsoft servers as untrusted or quarantining update payloads. Temporarily disable the real-time protection feature, run Windows Update again, and then re-enable the security software immediately after. You will know the conflict is resolved when the update downloads and installs without rolling back. If the error returns only after re-enabling the security tool, add an exclusion for C:\Windows\SoftwareDistribution in that program’s settings.
Troubleshooting Common Failure Points
Error 0x80070002 (File Not Found): This code indicates missing system files that the update agent cannot locate. Open an elevated terminal and run sfc /scannow followed by DISM /Online /Cleanup-Image /RestoreHealth. These commands repair the component store and restore missing Windows files. If DISM reports the component store is corrupted, you will need to perform an in-place upgrade using a Windows ISO.
Error 0x80070643 (Fatal Error During Installation): This usually points to a failed previous update leaving registry locks in place. Open regedit and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update. Delete the RebootRequired and LastWaitTimeout keys, then restart your PC and retry the update. Always export the registry key before deleting anything.
Error 0x80240034 (No Space Left): Windows requires roughly 6 to 9 GB of free space to install major updates. Open Settings > System > Storage, enable Storage Sense, and manually clear the Temporary files section. If you still lack space, expand your C: drive using Disk Management or move large media files to an external drive.
Pro Tip: If you manage multiple PCs or use Windows 11 Enterprise, you can push updates through Microsoft Endpoint Configuration Manager (MECM) or Windows Update for Business to bypass local service issues entirely. Group Policy settings under Computer Configuration > Administrative Templates > Windows Components > Windows Update also let you control update behavior without touching the registry.
Windows Update errors rarely stem from a single broken file. By verifying service status, clearing corrupted caches, and removing software conflicts, you address the root cause instead of masking symptoms. Keep your system patched, and you will avoid the security vulnerabilities that drive most of these error codes in the first place.
Over to you: Which Windows Update error code has caused you the most headaches?
