If you’re seeing “Something went wrong” with error 0x8024a105 while checking for or installing Windows updates, you’re not alone. This Windows Update error is common on Windows 10 and Windows 11 and typically appears when the update engine, its services, or the network stack run into trouble. Fixing it matters because stalled updates can leave your system unpatched, unstable, or vulnerable. This practical reset sequence goes beyond generic tips and provides a structured, step-by-step path to diagnose and resolve 0x8024a105 for good.
Understanding the Error
What 0x8024a105 means in plain language
– Error 0x8024a105 is a Windows Update client failure. In many cases, it indicates that the Automatic Updates component (AU) or update orchestration (USO) can’t communicate properly with the Windows Update service or its metadata cache.
– The result: the Settings app throws “Something went wrong,” the update scan/install process stops, or you receive repeat failures for cumulative or feature updates.
Typical triggers
– Corrupted Windows Update cache (SoftwareDistribution, Catroot2) or BITS job queue
– Network/proxy/VPN issues blocking Microsoft update endpoints
– Third-party antivirus/firewall interference
– System file corruption (CBS/servicing stack issues)
– Orphaned pending updates after a forced shutdown
– Insufficient disk space
– Misconfiguration from prior WSUS or policy settings (common in ex-corporate devices)
– Occasionally, storage or RAM errors surface during update apply
Quick Reference Table
Cause | Symptom | Recommended Fix
—|—|—
Corrupted Windows Update cache (SoftwareDistribution/Catroot2) | “Something went wrong” 0x8024a105 on scan/install | Reset update components; rename SoftwareDistribution and Catroot2; restart services
BITS queue corruption (qmgr*.dat) | Stuck at “Downloading” or never starting | Clear BITS queue; restart BITS and WU services
Network/proxy/VPN issues | Error occurs only on specific networks | Disable VPN/proxy; reset WinHTTP proxy; flush DNS; reset Winsock
Third-party AV/firewall interference | Update fails after installing security suite | Temporarily disable or uninstall AV/firewall; retry updates
System file/servicing corruption | SFC/DISM report errors; updates repeatedly fail | Run SFC and DISM; consider StartComponentCleanup; revert pending actions in Safe Mode
Insufficient disk space | Update stuck at 0% or fails near end | Free 20–30 GB for feature updates; 5–10 GB for cumulative updates
Incorrect date/time or region | Random update failures; Store also fails | Sync time; correct time zone/region; retry
WSUS/policy leftovers | Updates fail off-domain | Reset UseWUServer policy; point back to Microsoft Update
Orphaned pending update state | “We couldn’t complete the updates. Undoing changes” | Boot Safe Mode; DISM revertpendingactions; reset components
Hardware instability (disk/RAM) | Crashes or freezes during update | Run CHKDSK, SMART, and Windows Memory Diagnostic; replace failing hardware
Common Causes
– Corrupted update cache
– SoftwareDistribution folder cache or Catroot2 catalog becomes inconsistent after aborted updates or power loss.
– Background Intelligent Transfer Service (BITS) issues
– Stale qmgr*.dat files or misbehaving jobs stall downloads.
– Network and proxy configuration
– Corporate proxies, VPN clients, or custom WinHTTP proxy settings block connections.
– Third-party security software
– AV/firewalls inject network filters or lock system files.
– System file or servicing stack corruption
– Corrupt CBS/WinSxS components or pending.xml blocks the update pipeline.
– Disk space and storage health
– Low space or SMART warnings cause apply failures or rollbacks.
– Group Policy/registry remnants (WSUS)
– UseWUServer pointing to a dead or non-existent WSUS server.
– Malware or PUPs
– Hijacked networking stack or tampered Windows Update components.
– Firmware and drivers
– Outdated BIOS/UEFI or chipset/storage drivers can break feature updates.
Preliminary Checks
Boot to Safe Mode (if normal mode is unstable)
– From Windows: Settings > System > Recovery > Advanced startup > Restart now. Then Troubleshoot > Advanced options > Startup Settings > Restart > Press 4 for Safe Mode or 5 for Safe Mode with Networking.
– From login screen: Hold Shift, select Power > Restart; then same path as above.
– From MSCONFIG: Win + R > msconfig > Boot tab > Safe boot > Minimal. After fixing, uncheck Safe boot and reboot.
Back up important data
– Use File History, OneDrive, or manually copy Documents, Desktop, and Pictures.
– Command-line copy (replace USERNAME):
– robocopy “C:\Users\USERNAME” “E:\Backup\USERNAME” /MIR /XD AppData /R:1 /W:1
Run basic health checks
– Check disk (no reboot):
– chkdsk C: /scan
– System file checker:
– sfc /scannow
– Repair servicing component store:
– DISM /Online /Cleanup-Image /RestoreHealth
– If DISM fails, try:
– DISM /Online /Cleanup-Image /StartComponentCleanup
Step-by-Step Troubleshooting (The Practical Reset Sequence)
Follow these steps in order. Test Windows Update after each major block.
1) Verify time, date, and region
– Incorrect time can break SSL/TLS with Microsoft servers.
– Sync time:
– timedate.cpl
– In Windows Time settings, choose “Sync now.”
– Ensure correct time zone and region in Settings > Time & language.
2) Free up disk space
– Aim for 20–30 GB free for feature updates, 5–10 GB for cumulative updates.
– Use Storage Sense: Settings > System > Storage > Storage Sense.
– Remove old Windows installations:
– cleanmgr as admin > Clean up system files > check Windows Update Cleanup, Temporary files, etc.
– Optional PowerShell to list large folders:
– Get-ChildItem C:\ -Recurse -ErrorAction SilentlyContinue | Sort-Object Length -Descending | Select-Object FullName,Length -First 20
3) Disconnect VPN and disable proxy
– Disable VPN clients and third‑party firewalls during update.
– Reset WinHTTP proxy:
– netsh winhttp show proxy
– netsh winhttp reset proxy
– Flush DNS and reset the network stack (reboot after):
– ipconfig /flushdns
– netsh winsock reset
– netsh int ip reset
4) Run the built-in Windows Update troubleshooter
– Settings > System > Troubleshoot > Other troubleshooters > Windows Update > Run.
– Accept fixes it proposes (resets services, repairs registry, etc.). Then retest.
5) Restart update services and clear BITS queue
Open Command Prompt (Admin) or Windows Terminal (Admin) and run:
– net stop wuauserv
– net stop bits
– net stop cryptsvc
– net stop msiserver
– del “%ALLUSERSPROFILE%\Microsoft\Network\Downloader\qmgr*.dat” /Q
6) Reset the Windows Update cache (SoftwareDistribution and Catroot2)
– ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
– ren C:\Windows\System32\catroot2 Catroot2.old
– net start cryptsvc
– net start bits
– net start msiserver
– net start wuauserv
Then open Settings > Windows Update > Check for updates.
7) Repair system files (again) after resets
– sfc /scannow
– DISM /Online /Cleanup-Image /RestoreHealth
8) Kick-start the scan from the command line (Windows 10)
– UsoClient StartScan
– UsoClient StartDownload
– UsoClient StartInstall
Note: On some builds, these are restricted to system context and may not show output. You can still rely on Settings > Windows Update > Check for updates.
9) Clear “pending” update state (if you recently had a failed apply)
Only if updates repeatedly roll back or you see “Undoing changes” on boot:
– Boot into Safe Mode.
– DISM /Online /Cleanup-Image /RevertPendingActions
– Reboot normally and run Steps 5–7 again.
10) Check Group Policy/WSUS remnants (ex-corporate machines)
– Win + R > gpedit.msc (Pro/Enterprise) > Computer Configuration > Administrative Templates > Windows Components > Windows Update. Set “Specify intranet Microsoft update service location” to Not Configured.
– Registry (be careful):
– reg query “HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU” /v UseWUServer
– If UseWUServer exists and is 1, set to 0 or remove policy keys (backup first):
– reg add “HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU” /v UseWUServer /t REG_DWORD /d 0 /f
Restart the Windows Update service afterward:
– net stop wuauserv && net start wuauserv
11) Temporarily remove third‑party AV/firewall
– Disable shields or uninstall using the vendor’s cleanup tool.
– Reboot, run Windows Update. Reinstall AV after updates succeed.
12) Manually install the latest Servicing Stack Update (SSU) and Cumulative Update (LCU)
– Identify your OS build: winver
– Download the latest SSU/LCU for your build from the Microsoft Update Catalog. Install SSU first (if separate), then LCU. Reboot and re-check updates.
13) Repair Windows Update configuration via in-place upgrade (repair install)
– Download the Windows 10/11 ISO (same edition and language).
– Mount the ISO > run setup.exe > Choose “Keep personal files and apps.”
– This refreshes the Windows servicing stack and update components without wiping your data.
14) Network-level checks (routers, DNS)
– Try a different network (mobile hotspot) to rule out ISP or router issues.
– Set DNS to a public resolver (e.g., 1.1.1.1 or 8.8.8.8) in your adapter settings and retry.
15) Storage and memory diagnostics
– SMART and disk scan:
– wmic diskdrive get status
– or use your SSD/HDD vendor’s tool
– Check again:
– chkdsk C: /scan
– Memory:
– mdsched.exe > Restart now and check for problems
Replace failing hardware if errors are found.
Minidump Analysis (only if updates trigger BSODs)
Windows Update error 0x8024a105 itself does not produce a BSOD or minidump. However, if the update process crashes your system, minidumps help identify faulty drivers/modules.
How to enable/find minidumps
– Enable small memory dumps: Control Panel > System > Advanced system settings > Advanced tab > Startup and Recovery > Settings > Write debugging information: Small memory dump (256 KB). Ensure the path is %SystemRoot%\Minidump.
– After a crash, dumps appear in C:\Windows\Minidump.
Analyze with BlueScreenView (simple) or WinDbg (detailed)
– BlueScreenView: Quick view of the driver/module causing the crash.
– WinDbg (Preview from Microsoft Store):
– Open dump > run: !analyze -v
– Look for “Probably caused by” and driver names (e.g., nvlddmkm.sys, iaStorAC.sys).
– Update or roll back the offending driver; then retry updates.
Advanced Diagnostics
Use Event Viewer to read Windows Update and servicing logs
– Event Viewer: Applications and Services Logs > Microsoft > Windows >
– WindowsUpdateClient > Operational
– Windows > WindowsUpdate > Operational
– Setup > SetupDiag (if present)
– Look for error events around the time of failure. Note error codes beyond 0x8024a105, such as delivery or install errors.
Merge WindowsUpdate.log (Windows 10/11)
– Windows 10/11 store Windows Update traces as ETL. Generate a readable log:
– PowerShell (Admin):
– Get-WindowsUpdateLog
– This creates WindowsUpdate.log on your desktop. Search for 0x8024a105, BITS, or content download failures.
CBS and DISM logs
– C:\Windows\Logs\CBS\CBS.log captures servicing actions (SFC/DISM/install attempts).
– Review for repeated failures or corrupt packages.
Driver Verifier (use with caution)
– Purpose: Catch misbehaving third‑party drivers that could crash during updates.
– Enable:
– verifier
– Choose “Create standard settings” > “Automatically select unsigned drivers” (or all non-Microsoft drivers) > Finish > Reboot.
– If it triggers a BSOD, note the driver in the minidump and update/remove it.
– Disable:
– Boot Safe Mode (if needed), then run: verifier /reset
Warning: Driver Verifier can cause boot loops if unstable drivers are present. Use only if you suspect driver-caused crashes during update applies.
Post-Fix Checklist
– Run Windows Update successfully twice
– First to catch up on the main cumulative update, second to fetch follow-up patches.
– Confirm a clean Event Viewer
– No new critical errors in WindowsUpdateClient after the fix.
– Re-run integrity checks
– sfc /scannow returns “no integrity violations.”
– DISM /Online /Cleanup-Image /RestoreHealth completes without errors.
– Verify Store and Microsoft account services
– Open Microsoft Store > Get updates; ensure it also functions (often affected by network/proxy issues).
– Create a fresh restore point
– SystemPropertiesProtection.exe > Create.
When to Seek Professional Help
– Persistent update failures after an in-place repair install
– SMART errors, repeated CHKDSK repairs, or memory diagnostics failures
– Feature update repeatedly fails with multiple error codes, even from ISO
– Enterprise/WSUS-managed devices where policies are enforced by your organization
– You suspect malware or rootkits that standard tools can’t remove
Prevention Tips
– Keep drivers tidy
– Prefer vendor-signed drivers; avoid unnecessary driver “booster” tools.
– Regular maintenance
– Run SFC and DISM occasionally; clean temporary files; keep 20% of system drive free.
– Backup strategy
– Periodic system image (e.g., using built-in Backup and Restore or third-party imaging); file-level backups with File History or OneDrive.
– Update cadence
– Apply cumulative updates monthly; defer feature updates a few weeks to let early issues surface and resolve.
– Network hygiene
– Avoid always-on VPN/proxy for general use; whitelist Microsoft update domains on your firewall if needed.
– Avoid registry hacks and “tweakers”
– Many cause Windows Update and servicing stack inconsistencies.
Conclusion
Windows Update error 0x8024a105 (“Something went wrong”) is usually fixable by cleaning up the update cache, repairing the servicing stack, resetting the network/proxy configuration, and ensuring services and policies point to Microsoft’s update servers. Follow the practical reset sequence in order—from basic network and disk checks to component resets and, if necessary, an in-place repair. With patience and a methodical approach, most systems return to normal update behavior without data loss.
FAQ
#### What causes Windows Update error 0x8024a105?
It most often stems from a corrupted SoftwareDistribution/Catroot2 cache, network/proxy blocks, third‑party security software, or servicing stack corruption. Less commonly, it’s due to WSUS policy remnants, low disk space, or failing hardware.
#### Is 0x8024a105 a Windows 10 or Windows 11 issue?
Both. It’s a Windows Update client error that can appear on Windows 10 and Windows 11 when the update engine can’t properly scan/download/install updates.
#### Can I fix 0x8024a105 without losing my files?
Yes. The steps in this guide (resetting update components, SFC/DISM repairs, and even an in‑place repair install) preserve personal files and apps. Always back up first, just in case.
#### Do I need to analyze minidumps for this error?
Only if updates trigger blue screens. The error itself doesn’t generate dumps. If you see BSODs during updates, enable small memory dumps and analyze with BlueScreenView or WinDbg to find the offending driver.
#### What if the error persists after all steps?
Try manual SSU/LCU installation and the in-place repair. If it still persists, suspect hardware (disk/RAM), stubborn policy remnants, or rare malware. Seek professional support if diagnostics indicate hardware faults or if enterprise policies apply.
Appendix: One-Command Windows Update Reset Script (optional, run as Admin)
Use at your own risk; it performs Steps 5–7 automatically.
– net stop wuauserv
– net stop bits
– net stop cryptsvc
– net stop msiserver
– del “%ALLUSERSPROFILE%\Microsoft\Network\Downloader\qmgr*.dat” /Q
– ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
– ren C:\Windows\System32\catroot2 Catroot2.old
– ipconfig /flushdns
– netsh winsock reset
– net start cryptsvc
– net start bits
– net start msiserver
– net start wuauserv
Stay patient and methodical. With the practical reset sequence, most “Something went wrong” 0x8024a105 errors can be resolved without a clean install. If you need help, don’t hesitate to ask a professional—your time and data are worth it.
