If you have ever tried to check for updates and received a sudden error code, you know how quickly it disrupts your workflow. Error 0x80070422 is one of the most frequent Windows Update failures, and it almost always points to the same root cause: the Windows Update service is disabled or has become unresponsive. Rather than waiting for an automatic patch cycle or reinstalling Windows, you can resolve this issue directly from your current desktop. This guide covers the exact sequence of fixes that restore the update pipeline safely and permanently.
Before You Start: Make sure you are signed in with an account that has administrator privileges. You will also need an active internet connection, as some repair steps require downloading fresh update files from Microsoft servers.
Step 1: Verify the Windows Update Service Status
Open the Services console by pressing Win + R, typing services.msc, and hitting Enter. This utility displays every background process running on your machine. Locate the entry labeled Windows Update in the alphabetical list. Double-click the entry to open its properties window. Look at the Startup type dropdown and the Service status field. If the status reads Stopped or the startup type is set to Disabled, the system cannot communicate with Microsoft’s update servers. Change the startup type to Automatic (Delayed Start) and click the Start button. Click Apply and OK to save the changes. You will see the status switch to Running within a few seconds. If the Start button remains grayed out, proceed to Step 2, as a deeper corruption likely exists.

Step 2: Restart Windows Update Components via Command Prompt
Right-click the Start button and select Terminal (Admin) or Command Prompt (Admin) from the menu. Running commands with elevated privileges allows the system to stop and restart protected background services. You will see a blue or black window with a blinking cursor and an administrator header. Type the following commands one by one, pressing Enter after each line. Wait for each command to finish before typing the next one.
net stop wuauservnet stop cryptSvcnet stop bitsnet stop msiserver
These commands manually halt the Windows Update service, the Cryptographic service, the Background Intelligent Transfer Service, and the Windows Installer. Stopping them clears any locked files that might be blocking the update process. Next, you will rename the folders where Windows stores downloaded update data. Type the following commands to rename the cache directories. Renaming forces Windows to create fresh, uncorrupted folders the next time it runs.
ren C:\Windows\SoftwareDistribution SoftwareDistribution.oldren C:\Windows\System32\catroot2 catroot2.old
Once the folders are renamed, restart the services you stopped earlier. Type these commands and press Enter after each one.
net start wuauservnet start cryptSvcnet start bitsnet start msiserver
You will see a message confirming each service started successfully. Close the terminal window and return to Settings > Windows Update to check for updates again. This process resolves the majority of 0x80070422 occurrences because it rebuilds the communication channel between your PC and Microsoft’s servers.
Step 3: Run the Built-in Windows Update Troubleshooter
Navigate to Settings > System > Troubleshoot > Other troubleshooters and click Run next to Windows Update. Windows includes a diagnostic tool designed to detect and repair common update configuration issues automatically. The troubleshooter scans your service settings, registry keys, and network connections related to the update pipeline. You will see a progress bar followed by a results screen that lists any problems it found and fixed. If the troubleshooter reports that it repaired a disabled service or reset a corrupted component, click Close and attempt another update check. This step is particularly useful when the error appears after a recent Windows feature update or driver installation.
Step 4: Check Group Policy Settings (Pro and Enterprise Editions)
Press Win + R, type gpedit.msc, and press Enter to open the Local Group Policy Editor. This step applies only if you are running Windows 10/11 Pro, Enterprise, or Education. Home edition users can skip this section because they do not have access to local group policies. In the left navigation pane, expand Computer Configuration > Administrative Templates > Windows Components > Windows Update. Look for the policy named Configure Automatic Updates in the right pane. Double-click it and verify that the setting is configured to Not Configured or Enabled. If it is set to Disabled, Windows will actively block all update installations. Change the setting to Enabled, select your preferred update schedule from the dropdown, and click OK. Close the Group Policy Editor and restart your computer. After the reboot, return to Settings to trigger a manual update check.
Pro Tip: If you frequently manage update schedules across multiple devices, consider enabling the Manage updates from other PCs option in Group Policy. It allows your network to download updates once and distribute them locally, saving bandwidth and ensuring consistent patching.
Step 5: Reset Windows Update via PowerShell
Open an elevated PowerShell window and paste the following script to force a complete reset of the update infrastructure. This method acts as a comprehensive fallback when the previous steps do not clear the error. The script stops all update-related services, clears the download cache, re-registers the update DLL files, and restarts the services in the correct order. Copy and paste the block below directly into the PowerShell window, then press Enter.
Get-Service wuauserv | Stop-Service
Get-Service bits | Stop-Service
Get-Service cryptsvc | Stop-Service
Get-Service msiserver | Stop-Service
Remove-Item 'C:\Windows\SoftwareDistribution' -Recurse -Force -ErrorAction SilentlyContinue
Remove-Item 'C:\Windows\System32\catroot2' -Recurse -Force -ErrorAction SilentlyContinue
Get-Service wuauserv | Start-Service
Get-Service bits | Start-Service
Get-Service cryptsvc | Start-Service
Get-Service msiserver | Start-Service
Wait for the command prompt to return to the ready state. You will see no output if the script runs successfully. Navigate back to Settings > Windows Update and click Check for updates. The system will begin downloading fresh update manifests from Microsoft. This process may take several minutes the first time, as Windows rebuilds its local update database.
Troubleshooting: Common Failure Points
If the error persists after completing all steps above, check these specific failure scenarios.
- Services refuse to start: If the Windows Update service immediately stops after you start it, a third-party antivirus or firewall is likely blocking it. Temporarily disable your security software, attempt the update, and then re-enable protection. If the update succeeds, add Windows Update to your antivirus exclusion list.
- Error returns after a reboot: This usually indicates a corrupted system file. Open an elevated terminal and run
sfc /scannow. Wait for the scan to complete. If it reports corrupted files that it could not repair, follow up withDISM /Online /Cleanup-Image /RestoreHealth. Restart your PC after both scans finish. - Update gets stuck at a certain percentage: Clear the browser cache and DNS settings by running
ipconfig /flushdnsin an elevated terminal. Then, navigate to Settings > Network & Internet > Advanced network settings > Network reset. Click Reset now and wait for the machine to reboot. This restores all network adapters to their default state and often unblocks update downloads.
Following this sequence resolves the vast majority of 0x80070422 failures. Keep your system updated regularly to maintain security patches and performance improvements. If you encounter a different error code after applying these fixes, the underlying cause likely differs and requires a separate diagnostic path.
Over to you: Which step finally cleared the error on your machine?



