Error 0x84000010 typically appears when Windows Update or the Microsoft Store fails to install an update, often due to corrupted system files, misconfigured services, or a stalled update cache. This guide walks through a series of safe, step-by-step fixes that resolve the error on both Windows 11 and Windows 10, from running built-in troubleshooters to resetting update components manually.
What You’ll Need
- Administrator access to the PC (you’ll need to approve UAC prompts).
- A stable internet connection.
- About 15–30 minutes of time, depending on which steps are needed.
- Optional: a backup of important files before proceeding with system file repairs.
Step-by-Step
- Run the Windows Update Troubleshooter
Open Settings (Win + I) → System → Troubleshoot → Other troubleshooters. Click Run next to “Windows Update.” Let it scan and apply any fixes it suggests. Restart your PC and try updating again. - Run the Microsoft Store Troubleshooter (if Store apps are affected)
Go to Settings → System → Troubleshoot → Other troubleshooters → “Microsoft Store Apps” → Run. This addresses corrupted app cache or permissions that might trigger the same error code. - Check Windows Update Services
Press Win + R, typeservices.msc, and press Enter. Locate these services and ensure each is set to Automatic and Running (right-click → Properties to change):
• Windows Update
• Cryptographic Services
• Background Intelligent Transfer Service (BITS)
• Windows Installer
If any is stopped, click Start. Restart your PC afterward. - Clear the SoftwareDistribution Folder
Open Command Prompt as administrator (right-click Start → Terminal (Admin) or Command Prompt). Type the following commands one by one, pressing Enter after each:net stop wuauservnet stop cryptSvcnet stop bitsnet stop msiserver
Then rename the cache folder:ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
And the catroot2 folder:ren C:\Windows\System32\catroot2 catroot2.old
Restart the services with:net start wuauservnet start cryptSvcnet start bitsnet start msiserver
Close the prompt and restart your PC. - Run System File Checker (SFC) and DISM
Open Terminal (Admin) again. First runDISM /Online /Cleanup-Image /RestoreHealthand wait for it to complete (may take 10–20 minutes). Then runsfc /scannow. If SFC finds corrupted files, it will repair them automatically. Restart after both complete. - Reset Windows Update Components Manually (if above fails)
Open Notepad and paste the following batch script:@echo off 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 pause
Save it as
resetwu.baton your desktop. Right-click the file and select “Run as administrator.” After it finishes, restart your PC. - Perform a Clean Boot
Press Win + R, typemsconfig, and go to the “Services” tab. Check “Hide all Microsoft services,” then click “Disable all.” Next, go to the “Startup” tab and click “Open Task Manager.” Disable all startup items. Restart your PC and try updating. If it works, re-enable services/startup items one by one to find the culprit. - Use the Media Creation Tool (last resort)
If nothing else works, download the Media Creation Tool from Microsoft’s official website. Run it and choose “Upgrade this PC now.” This reinstalls Windows while keeping your files and apps. It often clears deep corruption that causes error 0x84000010.
Common Mistakes
- Skipping the DISM step before SFC – SFC can fail if the system image is corrupted. Always run DISM first.
- Not stopping services before renaming folders – If you rename SoftwareDistribution while Windows Update is running, you’ll get a “file in use” error. Ensure you stop the services exactly as shown.
- Deleting the SoftwareDistribution folder instead of renaming – Renaming is safer; deleting can cause issues if the system still references it.
- Forgetting to restart after each step – Many fixes require a reboot to take effect. Restarting after each major step prevents confusion.
- Running commands without admin rights – Commands like
net stopandsfcmust be run in an elevated prompt, or they’ll fail.
Tips
- Always create a system restore point before making changes (search “Create a restore point” in Start).
- If the error occurs only when installing a specific update, try downloading that update manually from the Microsoft Update Catalog and installing it.
- Keep your PC plugged in during updates to avoid interruptions.
- Use the “Check online for updates” option in Windows Update after each fix to test quickly.
- If you have third-party antivirus, temporarily disable it during the update process—some security suites interfere with Windows Update.
Troubleshooting
If the error persists after all steps, try the following:
- Check disk errors – Open Command Prompt as admin and run
chkdsk /f /r. You’ll need to restart; let it scan and repair your drive. - Review event logs – Open Event Viewer (Win + R, type
eventvwr). Go to Windows Logs → System and look for errors around the time of the failed update. Note the source (e.g., “Windows Update Client”) and search that specific source online. - Use the Windows Update Assistant – Download the official Windows Update Assistant from Microsoft and run it to force the latest feature update.
- Repair install via ISO – Download the Windows 11/10 ISO from Microsoft, mount it, and run
setup.exe. Choose “Keep personal files and apps” to do an in-place repair. - Check for third-party conflicts – Boot into Safe Mode (Shift + Restart → Troubleshoot → Advanced options → Startup Settings → Restart → 4) and try updating there. If it works, a background app is the cause.
Frequently Asked Questions
- What causes error 0x84000010?
It’s usually caused by corrupted update cache, broken system files, or services like Windows Update not running properly. Sometimes third-party security software or a pending update that got stuck can trigger it. - Will I lose my files if I use the Media Creation Tool?
No, if you choose “Upgrade this PC now” and select “Keep personal files and apps,” your documents, photos, and installed programs remain intact. However, it’s wise to back up important data beforehand. - How long does the DISM command take?
It can take anywhere from 10 to 30 minutes depending on your system speed and internet connection. Don’t close the window; let it finish. - Can I skip the clean boot step?
Yes, but if the error is caused by a background service, clean boot is the fastest way to identify it. If you’re short on time, you can try the other steps first. - Why do I need to rename catroot2?
Catroot2 stores signatures for Windows Update components. Renaming it forces Windows to recreate a fresh copy, eliminating any corruption that might be blocking updates. - Is it safe to use third-party update fix tools?
Generally, it’s safer to stick with built-in Windows tools. Third-party tools may not be up-to-date and could cause more harm. If you do use one, choose a reputable source and create a restore point first.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Clone a Hard Drive That Won’t Boot: Full Guide
- Gboard Not Working on iPhone? 8 Fixes That Actually Work
- Fix Unable to Start the Bluetooth Stack Service
- Destiny 2 Connection Error Codes: Step-by-Step Fix
- Fix Discord Picking Up Game Audio on Windows
- How to Sign in to Third-Party Apps with Your Apple ID