Fix Windows Error 0x80070422 (and 0x800704022)

Windows error 0x80070422 stops updates, the Microsoft Store, and Windows Defender from working. The closely related 0x800704022 is usually a typo of the same code, and the fixes below cover both. This guide walks through the most common causes—disabled services, corrupted system files, and network issues—and gives you clear steps to resolve them.

What You’ll Need

• Administrator access to your Windows PC (you’ll need to approve User Account Control prompts)
• An internet connection (for downloading updates and running online scans)
• About 20–30 minutes of time

Step-by-Step

1. Restart your PC. A simple reboot clears temporary glitches that can trigger this error. Save your work and restart, then try the update or Store download again.
2. Run the Windows Update troubleshooter. Go to Settings > System > Troubleshoot > Other troubleshooters (Windows 11) or Settings > Update & Security > Troubleshoot > Additional troubleshooters (Windows 10). Select Windows Update and click Run. Follow the prompts and restart if asked.
3. Check the required Windows services. The error often appears when the Windows Update service or the Background Intelligent Transfer (BITS) service is disabled. Press Win + R, type services.msc, and press Enter. Find each of these services, right-click, and select Properties:
   • Windows Update (wuauserv) – Startup type: Automatic
   • Background Intelligent Transfer Service – Startup type: Automatic
   • Cryptographic Services – Startup type: Automatic
   • Windows Installer – Startup type: Manual

   For each, set the startup type as listed, click Start if the service is not running, then click Apply and OK. Restart your PC.

4. Run the System File Checker (SFC). Corrupted system files can cause this error. Open Command Prompt as administrator (right-click Start and choose Terminal (Admin) or Command Prompt (Admin)). Type sfc /scannow and press Enter. Wait for the scan to finish (it can take 15 minutes). If it finds issues, restart and run the same command again.
5. Run DISM to repair the system image. If SFC doesn’t fix everything, run DISM. In the same admin Command Prompt window, type these commands one at a time, pressing Enter after each:
   
   DISM /Online /Cleanup-Image /CheckHealth

DISM /Online /Cleanup-Image /ScanHealth

DISM /Online /Cleanup-Image /RestoreHealth
   
   Wait for each to finish (the last one can take 20+ minutes). Restart your PC afterward.
6. Reset the Windows Update components manually. If the error persists, stop the relevant services, clear the update cache, and restart them. In an admin Command Prompt, run these commands in order:
   
   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
   
   Restart your PC and try the update again.
7. Check your date, time, and time zone. An incorrect system clock breaks the secure connection Windows uses for updates. Right-click the clock in the taskbar, choose Adjust date and time, and ensure Set time automatically and Set time zone automatically are both on. If they are, toggle them off and on again to force a resync.
8. Temporarily disable third-party antivirus or firewall. Security software can block Windows Update. Right-click the antivirus icon in the system tray and look for a Pause protection or Disable option. Try the update again. Re-enable the software immediately afterward—do not leave it off.
9. Run the Windows Update again. Go to Settings > Windows Update and click Check for updates. If the error appears, note the exact text and try the next step.
10. Perform a clean boot. This starts Windows with only essential drivers and services, isolating the cause. Press Win + R, type msconfig, and press Enter. On the Services tab, check Hide all Microsoft services, then click Disable all. On the Startup tab, click Open Task Manager, disable each startup item, then close Task Manager. Click OK and restart. Try the update. When done, reverse these changes (re-enable services and startup items) and restart.

Common Mistakes

• Skipping the restart after changing services. Service changes often don’t take effect until you reboot.
• Running SFC but not DISM. If the system image itself is corrupt, SFC can’t fix it—DISM must run first or after.
• Deleting the SoftwareDistribution folder instead of renaming it. Renaming is safer; if something goes wrong, you can rename it back.
• Leaving third-party antivirus disabled. Only pause protection during the update attempt, then re-enable it.
• Ignoring disk space. Windows Update needs several gigabytes of free space. Check that you have at least 10 GB free on the system drive.

Tips

• Run the Windows Update troubleshooter first—it often fixes the issue without manual steps.
• Use the Windows Update Assistant from Microsoft’s official site if regular updates still fail after these steps. It forces a manual update to the latest version.
• Keep your device plugged in during updates to avoid interruptions from power saving.
• If you’re on a metered connection, go to Settings > Network & Internet > Properties and turn off Metered connection or allow downloads over it.
• Check if the error appears only when using a VPN. Disconnect the VPN and try again.

Troubleshooting

If the steps above don’t resolve the error:

• Check the exact error code. If it’s truly 0x800704022 (with three digits after the 04), it’s almost certainly a typo of 0x80070422. If you see a different code like 0x80070002 or 0x800f081f, the fixes differ—search specifically for that code.
• Look at the Windows Update log. Open Event Viewer (press Win + R, type eventvwr.msc), go to Windows Logs > System, and filter by source WindowsUpdateClient. The details may point to a specific failing component.
• Try the update in Safe Mode with Networking. Restart while holding Shift, choose Troubleshoot > Advanced options > Startup Settings > Restart, then press 5 for Safe Mode with Networking. Attempt the update there. If it works, a third-party driver or service is the culprit.
• Use System Restore. If the error started recently, roll back to a restore point before the problem began. Search for Create a restore point, click System Restore, and follow the wizard.
• Consider a repair install. Download the Windows 10 or 11 installation media from Microsoft’s official site, run it, and choose Keep personal files and apps. This reinstalls Windows without deleting your data and often fixes deep system corruption.

Frequently Asked Questions

Q: Is 0x800704022 a different error from 0x80070422?
A: No. The extra zero in the middle is almost always a typo. Both refer to the same problem: Windows Update or a related service failed to start or connect.

Q: Will I lose my files if I run DISM or SFC?
A: No. Both tools only repair Windows system files. Your documents, photos, and installed programs are untouched.

Q: Why does this error keep coming back after I fix it?
A: It usually returns because a third-party service or app re-disables the Windows Update service, or because the system image is still corrupt. A clean boot test can help identify the culprit.

Q: Can I fix this error without admin rights?
A: No. Changing services, running SFC/DISM, and resetting update components all require administrator privileges. You’ll need an account in the Administrators group.

Q: How long does the DISM RestoreHealth command take?
A: Typically 15–30 minutes, but it can take longer on slower machines. Let it finish completely—don’t close the Command Prompt window mid-scan.

Q: What if the Microsoft Store is also broken?
A: The same fixes apply. After repairing Windows Update, open PowerShell as admin and run Get-AppxPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} to re-register Store apps.

Related

• Troubleshoot a Broken PC With ChatGPT Step by Step
• What Is a Quantum Computer? How It Works
• How to Create a Custom Android Mascot