How to Fix Windows Update Error 0x8024a105 Safely

Windows Update error 0x8024a105 usually means that Windows cannot download, verify, or install an update because the update cache, a required service, or system files are damaged. Restart the computer, run the Windows Update troubleshooter, reset the update cache, and repair Windows files; these steps do not delete your personal documents, photos, or installed applications.

What error 0x8024a105 means and when these fixes apply

The error commonly appears when Windows cannot download, verify, or install an update. Usual causes include an inconsistent SoftwareDistribution cache, a problem with services such as Windows Update or Background Intelligent Transfer Service (BITS), damaged system files, or a temporary network problem.

0x8024a105

You may see the code in Settings after an update download or installation fails. These instructions apply to supported Windows 10 and Windows 11 systems. You need an account with Administrator permission for the service-reset and repair commands. Restarting the computer is useful and may be required after Windows installs a pending update.

The steps rename update cache folders instead of deleting personal files. Save open work before restarting. Do not use a registry cleaner, format the drive, or permanently disable security software to address this code.

Before you start

These fixes apply to supported Windows 10 and Windows 11 systems. The restart, connection check, clock check, and Windows Update troubleshooter generally do not require Administrator permission. The service-reset commands, DISM, and SFC must run in Command Prompt opened with Run as administrator.

Save open work before restarting. The procedures below do not remove documents, photos, personal settings, or installed applications, but back up important files before an in-place repair installation. First confirm that the system drive has free space and that your internet connection is working normally.

Start with the safest fixes

Begin with these reversible checks. A restart can clear a stuck update process and finish maintenance that is waiting for a reboot.

1. Restart the computer. After signing in, wait a few minutes before opening Windows Update so background services can start.
2. Check your internet connection and disconnect a VPN temporarily if it is interfering with Microsoft’s update servers. Make sure the system drive has free space; Windows needs room to download and unpack updates.
3. Run the Windows Update troubleshooter.

Windows 11: Settings > System > Troubleshoot > Other troubleshooters > Windows Update > Run
Windows 10: Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update > Run the troubleshooter

4. Apply any repair the troubleshooter offers, then restart the computer. If it reports that it could not identify the problem, continue; that result does not rule out a damaged cache.
5. Confirm that Windows is using the correct date, time, and time zone. An incorrect clock can cause update validation or secure-connection failures.

Settings > Time & language > Date & time

Turn on Set time automatically and, if available, Set time zone automatically, then select Sync now. On Windows 10, the equivalent options are under Settings > Time & Language > Date & time. If the clock immediately becomes incorrect again, fix that underlying time-setting problem before retrying Windows Update.

Reset Windows Update without deleting personal files

If the basic checks did not help, reset the local update cache. This requires an elevated Command Prompt, meaning Command Prompt must be opened with Run as administrator. Renaming the folders lets Windows create clean replacements while preserving the old folders as a fallback until you remove them later.

Close Settings and other programs that may be installing updates before starting. Do not type these commands in a regular, non-administrator Command Prompt.

1. Open Start, type Command Prompt, right-click it, and select Run as administrator. Approve the User Account Control prompt.
2. Stop the services that use the update folders.

net stop wuauserv
net stop bits
net stop cryptsvc
net stop msiserver

Each service should report that it stopped successfully. If a service was not running, that is normally safe to continue past. If Windows says the service cannot be stopped, restart the computer and repeat this step before proceeding.

3. Rename the update cache folders.

ren %windir%\SoftwareDistribution SoftwareDistribution.old
ren %windir%\System32\catroot2 catroot2.old

A successful command returns to the prompt without an error. If you see that a file is in use, one of the services did not stop; do not delete the folder. Recheck the stop commands and try again.

4. Start the services again.

net start msiserver
net start cryptsvc
net start bits
net start wuauserv

Windows will create new cache folders when you check for updates. Restart the computer, open Windows Update, and select Check for updates. The first scan may take longer because Windows is rebuilding its local update data. If the update still fails, continue to the system-file repair section. Once the update works, leave the .old folders in place temporarily; remove them only after confirming that no rollback is needed and that they are no longer being used.

Repair Windows files if the error remains

If resetting the update components did not solve 0x8024a105, repair the Windows component store before running System File Checker. Use an elevated Command Prompt. DISM supplies the repair source for Windows components, and SFC then checks protected system files against that repaired store.

Do not close the Command Prompt, restart the computer, or interrupt either scan while it is running. The percentage can pause for a while, especially during component-store repair.

1. Open Command Prompt as administrator.
2. Run DISM first.

DISM.exe /Online /Cleanup-Image /RestoreHealth

Wait for DISM to finish and report that the restore operation completed successfully. It may need Windows Update or another configured repair source. If DISM reports that source files could not be found, the repair did not complete; resolve that source problem before relying on SFC alone.

3. After DISM completes successfully, run System File Checker.

sfc /scannow

SFC should report one of these outcomes: no integrity violations were found; corrupted files were found and repaired; or corrupted files were found but some could not be repaired. Restart Windows after the scan, then check for updates again. If SFC could not repair everything, review the result in the CBS log or proceed to the in-place repair option rather than repeatedly running the same command.

How to confirm the repair worked

After the restart, open Windows Update and select Check for updates. Let the download and installation finish without forcing a shutdown. The repair worked when the update reaches an installed state and Windows no longer displays error 0x8024a105.

Windows 11: Settings > Windows Update > Update history
Windows 10: Settings > Update & Security > Windows Update > View update history

Check the history for the update’s installed entry. If it failed again, record the exact update name or KB number and the time of the failure. That information is more useful than the error code by itself.

If the code returns after the cache reset and file repairs, retry the update once after a normal restart. Then consider an in-place repair installation using official Windows installation media or the supported recovery option for your Windows version. An in-place repair can replace Windows components while keeping personal files and, when the correct option is selected, installed applications; read each screen carefully and back up important files first. If that is unavailable or the failure is managed by an organisation, contact Microsoft Support or your administrator with the recorded KB number, update history, and DISM/SFC results.

Conclusion

Restart once, run Windows Update, and verify the result in Update history. If 0x8024a105 returns, record the exact KB number and repair results, then use an in-place repair or contact Microsoft Support instead of repeatedly deleting folders or changing unrelated system settings.

Frequently Asked Questions

Will resetting Windows Update delete my personal files?

No. Stopping the services and renaming `SoftwareDistribution` and `catroot2` resets temporary update data. It does not remove documents, photos, personal settings, or installed applications.

Do I need Administrator permission for every step?

No. Restarting, checking the connection, correcting the clock, and running the Settings troubleshooter generally do not require it. The service-reset commands, DISM, and SFC must run from an elevated Command Prompt.

What if DISM or SFC reports that it could not repair Windows?

If DISM did not complete because source files could not be found, resolve that source problem before relying on SFC alone. If the error persists after a successful DISM run and the SFC scan, record the messages and use an in-place repair installation or contact Microsoft Support.