Error 0x8024a11a when updating Windows 10: solutions

During the process of updating your computer to Windows 10, you may encounter error 0x8024a11a. The following messages are also attached to the code itself:

Everything is ready to install the latest component update for Windows! Your actions are pending. These improvements will ensure that Windows runs smoothly and safely.

We are having problems restarting the device to complete the update installation, error 0x8024a11a.

If you get these messages, don’t worry! Use the methods below to get rid of error 0x8024a11a and continue using your PC normally.

Troubleshooting error 0x8024a11a


Method # 1 Many reboots in a row

The best solution for this problem is many reboots in a row. Sometimes the installation of an update gets stuck due to a small bug in the Update Center (WU), which can be resolved by the most ordinary restart of the computer.

Click on the “Reboot Now” button in WU to start rebooting your PC. If for some reason this did not work, then try performing a manual restart using the Start menu or combinations such as Win + X and ALT + CTRL + DEL.

We also strongly recommend that you try to restart your PC from Safe Mode or even from under the so-called “clean boot”. This is done so that no third-party software interferes with the completion of the update installation. Error 0x8024a11a will disappear if everything goes well.

Method # 2 Starting the Windows Modules Installer Service

The Windows Modules Installer is a system service of the Windows operating system that actively participates in the installation of various updates. You need to make sure that this service has the value “Automatic” in the startup type parameters.

This can be done through a special window with all system services or through the Command Line. Press Win + X, and then click on “Command Prompt (Administrator)”. Enter the command in the window SC config trustedinstaller start = auto and press Enter.

Once the command has completed successfully, try updating your Windows again. If earlier the launch parameter of the module installer was different, then the error 0x8024a11a should disappear.

Method # 3 Run DISM Tool

You can also try to solve the problem by using the DISM system tool – Deployment Image Servicing and Management. This tool is able to restore the system image and the Windows 10 Component Store.

Call the Command Line in front of you (it was shown above) and run the following set of commands:

  • Dism / Online / Cleanup-Image / ScanHealth
  • Dism / Online / Cleanup-Image / CheckHealth
  • Dism / Online / Cleanup-Image / RestoreHealth

Wait for each command to complete, then restart your computer and check for error 0x8024a11a.

Method # 4 Running SFC

Corrupted Windows system files is a serious problem that can cause a whole wagon and a small cart of problems for the user. You can try to repair this damage by using the System File Checker.

Open Command Prompt and run the following command in it:

Wait until the SFC finishes, after which it will become clear to you whether any damage was found and whether they were repaired. Restart your computer and check your Windows for 0x8024a11a.

Method # 5 Run the troubleshooter

Let’s now try to access the services of the Windows Update Troubleshooter. Don’t worry, you won’t have to download anything, because the tool is already built into the system. Open Settings (Win + X) and go to the Update & Security section.

Next, go to the “Troubleshooting” subsection. Here you will see a large list with various system components – find the item “Windows Update” and select it. Now click on the Run the troubleshooter button. Follow the instructions on the screen.

Method # 6 Resetting the Update Center components

We have reviewed with you as many as five methods to eliminate error 0x8024a11a. If none of them worked for you (and this is quite possible), then we strongly advise you to try to reset the components of your Windows Update.

This can be done in two ways: through the Command Line or through a small BAT file of our own production. Today we will see how to do it in the second way. Create a plain text (.txt) file anywhere on your computer. Open it and paste ALL of the following commands into it:

set b = 0

: bits
set / ab =% b% + 1
if% b% equ 3 (
goto end1
net stop bits
echo Checking the bits service status.
sc query bits | findstr / I / C: “STOPPED”
if not% errorlevel% == 0 (
goto bits
goto loop2

: end1
echo Failed to reset Windows Update due to bits service failing to stop
echo Please run the script as administartor by right clicking the WuReset file or your BITS service isn’t responding.
goto Start

: loop2
set w = 0

: wuauserv
set / aw =% w% + 1
if% w% equ 3 (
goto end2
net stop wuauserv
echo Checking the wuauserv service status.
sc query wuauserv | findstr / I / C: “STOPPED”
if not% errorlevel% == 0 (
goto wuauserv
goto loop3

: end2
echo Failed to reset Windows Update due to wuauserv service failing to stop.
goto Start

: loop3
set app = 0

: appidsvc
set / a app =% app% + 1
if% app% equ 3 (
goto end3
net stop appidsvc
echo Checking the appidsvc service status.
sc query appidsvc | findstr / I / C: “STOPPED”
if not% errorlevel% == 0 (
goto appidsvc
goto loop4

: end3
echo Failed to reset Windows Update due to appidsvc service failing to stop.
goto Start

: loop4
set c = 0

: cryptsvc
set / ac =% c% + 1
if% c% equ 3 (
goto end4
net stop cryptsvc
echo Checking the cryptsvc service status.
sc query cryptsvc | findstr / I / C: “STOPPED”
if not% errorlevel% == 0 (
goto cryptsvc
goto reset

: end4
echo Failed to reset Windows Update due to cryptsvc service failing to stop.
goto Start

: Reset
Ipconfig / flushdns
del / s / q / f “% ALLUSERSPROFILE% Application Data Microsoft Network Downloader qmgr * .dat”

cd / d% windir% system32

if exist “% SYSTEMROOT% winsxs pending.xml.bak” del / s / q / f “% SYSTEMROOT% winsxs pending.xml.bak”
if exist “% SYSTEMROOT% winsxs pending.xml” (
takeown / f “% SYSTEMROOT% winsxs pending.xml”
attrib -r -s -h / s / d “% SYSTEMROOT% winsxs pending.xml”
ren “% SYSTEMROOT% winsxs pending.xml” pending.xml.bak

if exist “% SYSTEMROOT% SoftwareDistribution.bak” rmdir / s / q “% SYSTEMROOT% SoftwareDistribution.bak”
if exist “% SYSTEMROOT% SoftwareDistribution” (
attrib -r -s -h / s / d “% SYSTEMROOT% SoftwareDistribution”
ren “% SYSTEMROOT% SoftwareDistribution” SoftwareDistribution.bak

if exist “% SYSTEMROOT% system32 Catroot2.bak” rmdir / s / q “% SYSTEMROOT% system32 Catroot2.bak”
if exist “% SYSTEMROOT% system32 Catroot2” (
attrib -r -s -h / s / d “% SYSTEMROOT% system32 Catroot2”
ren “% SYSTEMROOT% system32 Catroot2” Catroot2.bak

if exist “% SYSTEMROOT% WindowsUpdate.log.bak” del / s / q / f “% SYSTEMROOT% WindowsUpdate.log.bak”
if exist “% SYSTEMROOT% WindowsUpdate.log” (
attrib -r -s -h / s / d “% SYSTEMROOT% WindowsUpdate.log”
ren “% SYSTEMROOT% WindowsUpdate.log” WindowsUpdate.log.bak


regsvr32.exe / s atl.dll
regsvr32.exe / s urlmon.dll
regsvr32.exe / s mshtml.dll
regsvr32.exe / s shdocvw.dll
regsvr32.exe / s browseui.dll
regsvr32.exe / s jscript.dll
regsvr32.exe / s vbscript.dll
regsvr32.exe / s scrrun.dll
regsvr32.exe / s msxml.dll
regsvr32.exe / s msxml3.dll
regsvr32.exe / s msxml6.dll
regsvr32.exe / s actxprxy.dll
regsvr32.exe / s softpub.dll
regsvr32.exe / s wintrust.dll
regsvr32.exe / s dssenh.dll
regsvr32.exe / s rsaenh.dll
regsvr32.exe / s gpkcsp.dll
regsvr32.exe / s sccbase.dll
regsvr32.exe / s slbcsp.dll
regsvr32.exe / s cryptdlg.dll
regsvr32.exe / s oleaut32.dll
regsvr32.exe / s ole32.dll
regsvr32.exe / s shell32.dll
regsvr32.exe / s initpki.dll
regsvr32.exe / s wuapi.dll
regsvr32.exe / s wuaueng.dll
regsvr32.exe / s wuaueng1.dll
regsvr32.exe / s wucltui.dll
regsvr32.exe / s wups.dll
regsvr32.exe / s wups2.dll
regsvr32.exe / s wuweb.dll
regsvr32.exe / s qmgr.dll
regsvr32.exe / s qmgrprxy.dll
regsvr32.exe / s wucltux.dll
regsvr32.exe / s muweb.dll
regsvr32.exe / s wuwebv.dll
regsvr32 / s wudriver.dll
netsh winsock reset
netsh winsock reset proxy

: Start
net start bits
net start wuauserv
net start appidsvc
net start cryptsvc
echo Task completed sucessfully! Please restart your computer and check for the updates again.

Save the changes in the text editor, then close it and rename it to “Reset WU.bat” (or any other name, for example, WUpdateRes.bat). Confirm your intentions when the system asks you if you really want to change the file extension. Double click on the created file and watch the magic.

Once the update process is complete, restart your computer and try updating your Windows OS again. This time the error 0x8024a11a should have receded.

Earn points and exchange them for valuable prizes – details

Leave a Comment