Fix 0x80070422 on Windows Server (Step-by-Step)

Error 0x80070422 on Windows Server typically appears when Windows Update, the firewall, or certain background services fail to start, often due to disabled services or corrupted system files. This guide walks you through the most effective fixes, from re-enabling critical services to using built-in repair tools, so you can restore updates and system stability.

What You’ll Need

• Administrator access to the Windows Server (local or via RDP).
• Internet connection (for downloading updates or running online repairs).
• Optional: Windows Server installation media (ISO or USB) if the system file checker cannot repair files.

Step-by-Step

1. Restart the Windows Update service and related services. Press Win + R, type services.msc, and press Enter. Locate Windows Update, Background Intelligent Transfer (BITS), Cryptographic Services, and Windows Installer. For each, right-click and choose Start (if not running) or Restart. Set their startup type to Automatic by double-clicking, changing the “Startup type” dropdown, and clicking OK.
2. Run the Windows Update troubleshooter. Open Settings > Update & Security > Troubleshoot (or Control Panel > Troubleshooting > Fix problems with Windows Update). Run it and apply any suggested fixes.
3. Check the firewall service. Error 0x80070422 often appears when the Windows Firewall service is disabled. In services.msc, find Windows Defender Firewall. If it is stopped, start it and set its startup type to Automatic. If it is already running, restart it.
4. Verify that the required services are not disabled in the registry. Press Win + R, type regedit, and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wuauserv. Double-click Start and set the value to 2 (Automatic). Do the same for BITS (under ...\Services\BITS) and MpsSvc (firewall service). Restart the server after making changes.
5. Run System File Checker (SFC). Open Command Prompt as administrator. Type sfc /scannow and press Enter. Wait for the scan to complete. If it finds corrupted files and repairs them, restart the server.
6. Run DISM to repair the system image. In the same Command Prompt, type DISM /Online /Cleanup-Image /RestoreHealth and press Enter. This may take several minutes. After completion, restart the server and try Windows Update again.
7. Reset Windows Update components manually. Stop the Windows Update, BITS, and Cryptographic services (using net stop wuauserv, net stop bits, net stop cryptSvc in an elevated Command Prompt). Then rename the SoftwareDistribution and catroot2 folders (e.g., ren C:\Windows\SoftwareDistribution SoftwareDistribution.old and ren C:\Windows\System32\catroot2 catroot2.old). Restart the services with net start wuauserv, net start bits, net start cryptSvc. Try updating again.
8. Check for third-party security software conflicts. Temporarily disable any third-party antivirus or firewall, then attempt the update. If it works, re-enable the software and add exceptions for Windows Update processes.
9. Perform a clean boot. Run msconfig, go to the Services tab, check “Hide all Microsoft services”, then click “Disable all”. On the Startup tab, open Task Manager and disable all startup items. Restart and try the update. If it succeeds, re-enable services one by one to identify the culprit.

Common Mistakes

• Only restarting services without setting them to Automatic. The error recurs after a reboot if the startup type remains disabled or manual.
• Running SFC without DISM. If the system image is corrupted, SFC may fail to repair files. Always run DISM first or after SFC.
• Deleting the SoftwareDistribution folder without stopping services. This can cause file locks and errors. Always stop the services first.
• Skipping the firewall service. Many users focus only on Windows Update and BITS, but the firewall service being disabled is a common cause of 0x80070422.

Tips

• Use PowerShell for faster service checks. Run Get-Service wuauserv, bits, mpsSvc to see their status in one line.
• Create a restore point before making registry changes or renaming folders.
• Keep the server updated with the latest cumulative updates to avoid known issues that Microsoft patches.
• If this is a domain controller, ensure Group Policy does not disable Windows Update. Check gpedit.msc under Computer Configuration > Administrative Templates > Windows Components > Windows Update.

Troubleshooting

If the error persists after following all steps, try these additional measures:

• Check the event logs. Open Event Viewer (eventvwr.msc) and look under Windows Logs > System for errors around the time of the failure. The details may point to a specific service or driver.
• Use the Media Creation Tool to repair in-place. Download the Windows Server ISO (matching your version), mount it, run setup.exe, and choose “Keep personal files and apps”. This reinstalls the OS without losing data.
• Verify that the server is activated. An unactivated Windows Server can sometimes block updates. Check under Settings > Update & Security > Activation.
• If the error occurs only on a specific app (e.g., Store), reset the app cache via wsreset.exe or reinstall the app.
• As a last resort, consider a full reinstall if the server is not critical and backups exist.

Frequently Asked Questions

What causes error 0x80070422 on Windows Server?

It is most often caused by the Windows Update service, BITS, or Windows Firewall service being disabled or not set to automatic. Corrupted system files or registry misconfigurations can also trigger it.

Can I fix this without rebooting the server?

Yes, restarting the services and running DISM may resolve it without a reboot. However, a reboot is recommended after registry changes to ensure all services start correctly.

Is it safe to rename the SoftwareDistribution folder?

Yes, that folder holds temporary update files. Renaming it forces Windows to recreate it. Just stop the Windows Update service first.

Will this error affect other server roles?

Not directly, but if Windows Update is broken, security patches won’t install, leaving the server vulnerable. The error itself does not stop other services.

How long does DISM take?

Typically 5 to 15 minutes, but it can take longer on slower systems or if the image is severely corrupted.

Do I need to reinstall Windows if nothing works?

Not necessarily. An in-place repair upgrade (using the ISO) often fixes stubborn issues without losing data. A full reinstall is a last resort.

Related

• Alexa Find Missing Phone: How to Use It
• Enable, Configure & Secure Linux on a Chromebook
• Fix Windows Store Problems in Windows 10