Fix Microsoft Store Error 0x8007422 & 0x80070422

Microsoft Store errors 0x8007422 and 0x80070422 usually appear together and point to a problem with Windows services that the Store depends on, particularly the Windows Update service and the Background Intelligent Transfer Service (BITS). When these services are disabled, corrupted, or set to manual startup, the Store cannot connect to Microsoft’s servers, so downloads fail and the error codes show up. This guide walks you through the fixes that work for most users, from re-enabling the services to clearing the Store cache.

What You’ll Need

• Administrator access to the Windows PC (you’ll need to confirm UAC prompts)
• An internet connection
• About 15 minutes of time

Step-by-Step

1. Run the Windows Store Apps troubleshooter. Open Settings (Win + I) → System → Troubleshoot → Other troubleshooters. Find “Windows Store Apps” and click Run. Let it scan and apply any fixes it suggests. This often resolves the 0x80070422 error by resetting the Store’s internal state.
2. Check the required services. Press Win + R, type services.msc, and press Enter. Look for these services and set each one as follows:
   • Windows Update (wuauserv) – Startup type: Manual, Status: Running
   • Background Intelligent Transfer Service (BITS) – Startup type: Manual, Status: Running
   • Cryptographic Services – Startup type: Automatic, Status: Running
   • Microsoft Store Install Service (InstallService) – Startup type: Manual, Status: Running (if present)

   To change a service, right-click it → Properties → set Startup type → click Start (if not running) → Apply → OK.

3. Force-start the services if they won’t start. If a service is stuck, open an elevated Command Prompt (right-click Start → Terminal (Admin) or Command Prompt (Admin)) and run:

   net start wuauserv
   net start bits

   If you get an error, note the message – it often points to a corrupted service configuration.

4. Reset the Windows Update components. In the same admin Command Prompt, stop the services and rename the update cache folders:

   net stop wuauserv
   net stop bits
   ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
   ren C:\Windows\System32\catroot2 catroot2.old
   net start wuauserv
   net start bits

   This clears corrupted update files that can trigger both error codes.

5. Clear the Microsoft Store cache. Press Win + R, type wsreset.exe, and press Enter. A blank window will open and close automatically. This resets the Store’s cache without deleting your apps or account.
6. Re-register the Store app. In the same admin PowerShell or Terminal window, run:

   Get-AppxPackage -AllUsers Microsoft.WindowsStore | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

   Wait for it to finish, then restart your PC.

7. Check for system file corruption. Run sfc /scannow in the admin Command Prompt. If it finds issues, run DISM /Online /Cleanup-Image /RestoreHealth afterward, then restart.
8. Verify the date and time. Right-click the clock → Adjust date/time → ensure “Set time automatically” is on. Incorrect time can cause certificate errors that show up as 0x8007422.
9. Create a new user account as a last resort. If nothing works, create a new local administrator account (Settings → Accounts → Family & other users → Add account) and try the Store there. If it works, migrate your files and apps.

Common Mistakes

• Setting Windows Update to Disabled. Some “optimization” guides tell you to disable Windows Update. That directly causes 0x80070422. Always leave it on Manual or Automatic.
• Skipping the service check. Jumping straight to wsreset.exe won’t help if the underlying services are off. Fix the services first.
• Running commands without admin rights. The net start and DISM commands fail with “access denied” if you don’t open the terminal as administrator.
• Deleting the SoftwareDistribution folder instead of renaming. Renaming is safer – if something goes wrong, you can rename it back. Deleting forces Windows to rebuild it, which is fine but irreversible.

Tips

• After fixing the services, restart your PC before opening the Store – this ensures all changes take effect.
• If you use a VPN or proxy, turn it off temporarily. Some VPNs interfere with the Store’s connection and trigger these errors.
• Keep Windows Update itself updated. Run Settings → Windows Update → Check for updates after the fix, as the Store relies on the same infrastructure.
• If you have third-party antivirus, temporarily disable its firewall or add the Store to exceptions – it can block the Store’s background service.

Troubleshooting

If the steps above don’t resolve the issue, try these in order:

• Check the service dependencies. BITS depends on the COM+ Event System and Remote Procedure Call (RPC) services. If those are stopped, BITS won’t start. Open the BITS Properties → Dependencies tab to see what it needs.
• Use the Windows Update troubleshooter. Go to Settings → System → Troubleshoot → Other troubleshooters → Windows Update → Run. It may fix deeper update service issues.
• Perform a clean boot. Disable all non-Microsoft startup items (msconfig → Services → hide all Microsoft services → Disable all) and restart. If the Store works, a third-party app is interfering.
• Check the Windows event logs. Open Event Viewer → Windows Logs → System, and look for errors from the Service Control Manager. The error details often name the exact service that failed to start.
• If the error persists, consider an in-place upgrade repair. Download the Windows 11 Installation Assistant from Microsoft’s official site and run it – it reinstalls Windows while keeping your files and apps. This is a more aggressive fix but often clears stubborn service corruption.

Frequently Asked Questions

Why do I get both 0x8007422 and 0x80070422 at the same time?

They share the same root cause: the Windows Update service (or BITS) is not running. The 0x80070422 error is the generic “service could not be started” code, while 0x8007422 is often tied to the Store’s inability to reach its update server because that service is down.

I set Windows Update to Manual, but it still doesn’t start. What now?

Try restarting the PC first. If it still won’t start, run the DISM and SFC commands from the steps – corrupted system files can prevent the service from starting. If that fails, the service registry keys may be damaged, and an in-place upgrade repair is the most reliable fix.

Will wsreset.exe delete my downloaded apps?

No. wsreset.exe only clears the Store’s cache and temporary files. Your installed apps and their data remain untouched. It may sign you out of the Store, but you can sign back in.

Can a third-party antivirus cause this error?

Yes. Some antivirus suites block the BITS service or the Store’s network access. Temporarily disable the antivirus’s real-time protection or firewall, then try the Store. If it works, add exceptions for the Store and BITS.

Is there a way to avoid this error in the future?

Keep Windows Update enabled (Manual or Automatic), avoid “debloater” scripts that disable services, and periodically run the Windows Update troubleshooter. Also, make sure your system date and time are correct.

Do I need to reinstall Windows to fix this?

Usually no. The steps above resolve it for most users. Only if you’ve tried everything, including the in-place upgrade repair, and the error persists would a full reinstall be considered – but that’s rare.

Related

• Hidden Folders in macOS: Show, Create, Use
• WhatsApp Chat Export Not Working: Fixes
• Router Bit in a Drill? What You Need to Know