Users often encounter this problem after trying to update Windows 10 via Windows Update (WU). The error 0x8024a105 indicates a problem with Automatic Updates components. Normally, after a failed update, users will see the following message:
"There were problems downloading some updates, but we will try again later. If you keep seeing this, try searching the web or contact support for help. This error code can help: (0x8024a105). »
If you are currently struggling with this problem, we have managed to identify some viable solutions that have successfully helped users in a situation similar to yours. Follow each of the methods below in order until you find a solution that solves your problem..
Method 1: Run the Windows Update troubleshooter
Let's get started by simply running the Windows Update troubleshooter. Some users have made the updates by allowing the built-in troubleshooter to automatically repair broken components. Here's a quick guide on how to run the Windows Update troubleshooter:
-
Press the Windows key + R to open a run window. Write or paste the following.
control.exe / Microsoft name. Problem solving
Press Enter to open the built-in troubleshooter.
-
In the Troubleshoot window, click Windows Update, then click Run the troubleshooter.
-
Wait until the troubleshooter detects problems with your update client. If you can identify a problem with it, follow the onscreen instructions to activate automatic repair. Normally, you will only have to choose Apply this repair.
-
If the update troubleshooter reports that it has managed to fix something, restart your computer and see if the problem is resolved on the next startup.
If updates keep failing with the error 0x8024a105 , go to Method 2.
Method 2: change User Account Control settings (UAC)
If the troubleshooter was unable to fix the problem automatically, Let's see if the problem is not created with a User Account Control configuration. Turns out some updates were failing with the error. 0x8024a105 because the account started does not have the necessary permissions. You can easily fix this problem by changing the permissions of the user accounts related to your account to Administrator. Here is a quick guide to do it:
-
Press the Windows key + R to open a run window. Type or paste »netplwiz» and hit Enter to open the built-in troubleshooter.
-
In the Users tab, select the user you are using and click Properties.
-
In the Properties window, go to Group Membership and set the access level to Administrator. Press Apply to save the changes.
Note: If the access level is already configured as Administrator, go directly to Method 3.
-
Restart your computer and make sure you are logged in with the same user account. Once startup is complete, try updates again. If you see they fail with the error 0x8024a105 , go to the third method.
Method 3: manual restart of Windows update components
If the above methods have not been successful, we have no choice but to manually restart the Windows update components and then restart the Windows update. Of the four methods presented, this has a higher probability of success but requires more adjustments.
Here's a quick guide to restarting Windows Updates components:
-
Click on the Windows start bar (lower left corner) and search for »cmd«. Later, right click on the command line and choose Run as administrator.
-
At the elevated command prompt, let's stop the MSI installer, Windows Update, BITS and cryptographic services. For it, we will insert the following commands and press Enter after each one:
net stop wuauserv net stop cryptSvc bits de parada de red net stop msiserver
-
After all services have stopped, we will rename the SoftwareDistribution folder and the Catroot2 folder to force Windows Update to restart its components. Paste or type the two commands in the elevated command prompt and press Enter after each one:
ren C:WindowsSoftwareDistribution SoftwareDistribution.old
ren C:N-System32Ncatroot2 Catroot2.old
-
Once the two folders have been renamed, it's time to restart the MSI Installer services, BITS, Cryptographic y Windows Update. To do this, type the following command at the command prompt and press Enter after each command:
net start wuauserv net start cryptSvc bits de inicio de la red net start msiserver
-
After services have been restarted, close command prompt high and restart the computer.
Method 4: delete software distribution folder
In some cases, the problem can be fixed simply by deleting a folder with Powershell. Therefore, in this step, we will first run PowerShell as administrator and then delete the software distribution folder to start the update process. For that:
-
Press “Windows” + “X” simultaneously and select the option “Power Shell (Admin)”.
-
Type the following command and press “Enter” to run it.
net stop wuauserv
-
Again, type the following command and press “Enter”.
net stop bits
-
By last, navigate to the following folder.
C:WindowsSoftwareDistribution
-
Press “Ctrl” + “A” to select all the contents of the folder and press “Shift” + “Supr” to permanently remove them.
Select the contents of the software distribution folder
-
Confirm any messages telling you to delete these files and then restart your computer to complete the process.
-
Now, try to update and check if the problem persists.
Once your computer starts up again, check if you can install the updates without the error 0x8024a105 . If so, try running an SFC scan to fix any issues with missing files or drivers.




Note: If the access level is already configured as Administrator, go directly to Method 3.



Select the contents of the software distribution folder



