Wings Mob Blogs

0x8024a105 is one of the most common errors for Windows 8 and Windows 10 that occurs during the process of updating the operating system. Along with the error code in Windows Update, you can see the following text:

There were problems installing some updates, but another attempt will be made later. If you continue to see this message and want to search the Internet for more information or contact support, the following information may help you: (0x8024a105).

The most common reasons behind the appearance of this error are damage to one or more components of the Update Center and problems with the network connection. Windows update problems are a common occurrence for many Microsoft users. Fortunately, error 0x8024a105 – and other similar errors – can be resolved using a number of generic methods.

Resolving update error 0x8024a105

Method # 1 Automated Troubleshooter

The troubleshooter is your first step. This tool will scan your system to find problematic elements in it that cause incidents during the update, and will try to fix them. It is worth noting that the tool does not always cope with its task, but it is worth using it, especially since it is impossible for them to harm their OS, unlike other methods in the article.

So, to get the troubleshooter to work, do the following:

• press the Win + I combination to open the System Settings in front of you;
• find and click LMB on the “Update and Security” section;
• go to the “Troubleshooting” tab using the panel on the left;
• find in the provided list “Windows Update” and click on it with LMB;
• click on the “Run the troubleshooter” button;
• follow the instructions on your screen to fix the OS update issues found.

When you are finished using the tool, restart your PC and try updating your PC again. Error 0x8024a105 disappeared? If nothing has changed, then let’s move on …

Method # 2 Deployment Image Servicing and Management (DISM)

There is a possibility that some of your Windows system files have been damaged, as a result of which it can no longer update correctly. In this case, the best solution is to use the so-called Deployment Image Servicing and Management (DISM) system.

In simple terms, DISM is an incredibly useful utility that can fix a wide variety of Windows problems, including update issues. Here’s what you need to do to get DISM to work:

• press Win + R to bring up the Run window in front of you;
• enter cmd in an empty line, then press the combination Ctrl + Shift + Enter;
• Once in the command line, write the DISM / Online / Cleanup-Image / RestoreHealth command and press Enter;
• wait until DISM finishes working (a successful completion message appears) and restart your computer.

Be sure to make sure you have stable internet access while running DISM. The fact is that the utility downloads new files from Microsoft servers and replaces the old, damaged files on your system with them.

Method # 3 Search for problematic elements

You may not be able to update your system because some services or programs running in the background are interfering with this process. To test this possibility, you need to perform a clean boot on your PC. Simply put, boot the system with the minimum set of necessary system services, which will allow you to determine whether the problems with the update were caused by third-party services and programs or not.

A download of this type is done as follows:

• press Win + R;
• type msconfig and press Enter;
• in the window that opens, go to the “Services” tab;
• check the box next to the option “Do not display Microsoft services”;
• click on the “Disable all” button in the same tab;
• go to the “Startup” tab and click on the “Open Task Manager” hyperlink;
• in the startup tab, disable all applications by using the corresponding button in the lower right corner of the window;
• close all windows and restart your computer.

Run Windows Update and check if error 0x8024a105 is gone.

Method # 4 Restoring Windows Update Components

Still having trouble updating your Windows OS? Well, obviously something went wrong – some components of the Update Center were damaged. No, you don’t have to completely reinstall Windows. Instead, we recommend that you start restoring the Update Center components to their original state.

It sounds scary, but in fact the process is extremely simple, especially if you use a homemade batch file. So, create a very basic text file on your Desktop and paste the following code into it:

:: Run the reset Windows Update components.
:: void components ();
:: / ********************************************** ************************************* /
: components
:: —— Stopping the Windows Update services ——
call: print Stopping the Windows Update services.
net stop bitscall: print Stopping the Windows Update services.
net stop wuauservcall: print Stopping the Windows Update services.
net stop appidsvccall: print Stopping the Windows Update services.
net stop cryptsvccall: print Canceling the Windows Update process.
taskkill / im wuauclt.exe / f
:: —— Checking the services status ——
call: print Checking the services status.

sc query bits | findstr / I / C: “STOPPED”
if% errorlevel% NEQ 0 (
echo. Failed to stop the BITS service.
echo.
echo.Press any key to continue. … …
pause> nul
goto: eof
)

call: print Checking the services status.

sc query wuauserv | findstr / I / C: “STOPPED”
if% errorlevel% NEQ 0 (
echo. Failed to stop the Windows Update service.
echo.
echo.Press any key to continue. … …
pause> nul
goto: eof
)

call: print Checking the services status.

sc query appidsvc | findstr / I / C: “STOPPED”
if% errorlevel% NEQ 0 (
sc query appidsvc | findstr / I / C: “OpenService FAILED 1060”
if% errorlevel% NEQ 0 (
echo. Failed to stop the Application Identity service.
echo.
echo.Press any key to continue. … …
pause> nul
if% family% NEQ 6 goto: eof
)
)

call: print Checking the services status.

sc query cryptsvc | findstr / I / C: “STOPPED”
if% errorlevel% NEQ 0 (
echo. Failed to stop the Cryptographic Services service.
echo.
echo.Press any key to continue. … …
pause> nul
goto: eof
)

:: —— Delete the qmgr * .dat files ——
call: print Deleting the qmgr * .dat files.

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

:: —— Renaming the softare distribution folders backup copies ——
call: print Deleting the old software distribution backup copies.

cd / d% SYSTEMROOT%

if exist “% SYSTEMROOT% winsxs pending.xml.bak” (
del / s / q / f “% SYSTEMROOT% winsxs pending.xml.bak”
)
if exist “% SYSTEMROOT% SoftwareDistribution.bak” (
rmdir / s / q “% SYSTEMROOT% SoftwareDistribution.bak”
)
if exist “% SYSTEMROOT% system32 Catroot2.bak” (
rmdir / s / q “% SYSTEMROOT% system32 Catroot2.bak”
)
if exist “% SYSTEMROOT% WindowsUpdate.log.bak” (
del / s / q / f “% SYSTEMROOT% WindowsUpdate.log.bak”
)

call: print Renaming the software distribution folders.

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” (
attrib -r -s -h / s / d “% SYSTEMROOT% SoftwareDistribution”
ren “% SYSTEMROOT% SoftwareDistribution” SoftwareDistribution.bak
if exist “% SYSTEMROOT% SoftwareDistribution” (
echo.
echo. Failed to rename the SoftwareDistribution folder.
echo.
echo.Press any key to continue. … …
pause> nul
goto: eof
)
)
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” (
attrib -r -s -h / s / d “% SYSTEMROOT% WindowsUpdate.log”
ren “% SYSTEMROOT% WindowsUpdate.log” WindowsUpdate.log.bak
)

:: —— Reregister the BITS files and the Windows Update files ——
call: print Reregister the BITS files and the Windows Update files.

cd / d% SYSTEMROOT% system32
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

:: —— Resetting Winsock ——
call: print Resetting Winsock.
netsh winsock reset

:: —— Resetting WinHTTP Proxy ——
call: print Resetting WinHTTP Proxy.

if% family% EQU 5 (
proxycfg.exe -d
) else (
netsh winhttp reset proxy
)

:: —— Set the startup type as automatic ——
call: print Resetting the services as automatics.
sc.exe config wuauserv start = auto
sc.exe config bits start = delayed-auto
sc.exe config cryptsvc start = auto
sc.exe config TrustedInstaller start = demand
sc.exe config DcomLaunch start = auto

:: —— Starting the Windows Update services ——
call: print Starting the Windows Update services.
net start bits

call: print Starting the Windows Update services.
net start wuauserv

call: print Starting the Windows Update services.
net start appidsvc

call: print Starting the Windows Update services.
net start cryptsvc

call: print Starting the Windows Update services.
net start DcomLaunch

:: —— End process ——
call: print The operation completed successfully.

echo.Press any key to continue. … …
pause> nul
goto: eof
:: / ********************************************** ************************************* /

Save the changes you made to the text editor and change its extension from .txt to .bat. You can name the file whatever you want – it doesn’t matter. Right click on the created file and select “Run as administrator”. Wait a few seconds for the script to finish restoring Windows Update components. Finally, restart your computer one last time.

Error 0x8024a105 should have gone away. But if it has not disappeared, even after following all the above methods, we advise you not to bother anymore and download the problematic update from Microsoft Update Catalog…