Users typically encounter this issue after attempting to update Windows 10 via Windows Update (WU). The error 0x8024a105 signals a problem with the Automatic Updates components. Typically, after a failed update users will see the following message:
“There were problems downloading some updates, but we’ll try again later. If you keep seeing this, try searching the web or contacting support for help. This error code might help: (0x8024a105).”
If you’re currently struggling with this issue, we have managed to identify a few viable fixes that have successfully helped users in a similar situation as you. Please follow each of the methods below in order until you encounter a solution that manages to resolve your problem.
Method 1: Running the Windows Update troubleshooter
Let’s start simple, by running the Windows Update troubleshooter. Some users have managed to allow the updates to get through by allowing the built-in troubleshooter to automatically fix the broken components. Here’s a quick guide on how to run the Windows Update Troubleshooter:
- Press Windows key + R to open up a Run window. Type or paste the following.
control.exe /name Microsoft. Troubleshooting
Hit Enter to open the built-in troubleshooter.
- In the Troubleshoot window, click on Windows Update, then click on Run the troubleshooter.
- Wait until the troubleshooter detects problems with your updating client. If it manages to identify any issues with it, follow the on-screen prompts to trigger the automatic repair. Typically, you’ll just need to choose to Apply this fix.
- If the Update Troubleshooter reports that it managed to repair anything, restart your computer and see if the issue is resolved at the next startup.
If the updates are still failing with the 0x8024a105 error, move down to Method 2.
Method 2: Change User Account Control (UAC) Settings
If the troubleshooter didn’t manage to fix the issue automatically, let’s see if the issue is not created by a User Account Control setting. As it turns out, some updates were failing with the 0x8024a105 error because the logged-in account doesn’t have the necessary permissions. You can remedy this issue easily by changing the User Accounts permissions related to your account to the Administrator. Here’s a quick guide to doing this:
- Press Windows key + R to open up a Run window. Type or paste “netplwiz” and hit Enter to open the built-in troubleshooter.
- In the Users tab, select the user that you’re using and click on Properties.
- In the Properties window, go to Group Membership and set the level of access to the Administrator. Hit Apply to save your changes.
Note: If the level of access is already set to Administrator, move directly to Method 3.
- Reboot your computer and make sure you log in with the same user account. Once the startup is complete attempt to perform the updates again. If you see them fail with the 0x8024a105 error, move down to the third method.
Method 3: Resetting the Windows Updates components manually
If the above methods have proved to be unsuccessful, we have little choice but to manually reset the Windows Updates Components and then restart the Windows Update process. Out of the four featured methods, this one has a higher probability of success but requires more tweaking.
Here’s a quick guide to resetting the Windows Updates components:
- Click the Windows Start bar (bottom-left corner) and search for “cmd“. Then, right-click on Command prompt and choose Run as Administrator.
- In the elevated Command Prompt, we are going to stop the services of MSI Installer, Windows Update, BITS, and Cryptographic. To do this, insert the following commands and press Enter after each one:
net stop wuauserv net stop cryptSvc net stop bits net stop msiserver
- Once all the services have been stopped, let’s rename the SoftwareDistribution folder and the Catroot2 folder in order to force Windows Update to reinitiate its components. Paste or type the two commands into the elevated Command prompt and press Enter after each one:
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 Catroot2.old
- Once the two folders have been renamed, it’s time to restart the services of MSI Installer, BITS, Cryptographic and Windows Update. To do this, type the following command in Command Prompt and hit Enter after each command:
net start wuauserv net start cryptSvc net start bits net start msiserver
- Once the services have been restarted, close the elevated Command Prompt and reboot your computer.
Method 4: Delete Software Distribution Folder
In some cases, the issue can be fixed simply by deleting a folder using Powershell. Therefore, in this step, first, we will be running PowerShell as an admin and then we will delete the Software distribution folder to kickstart the update process. For that:
- Press “Windows” + “X” buttons simultaneously and select the “Power Shell(Admin)” option.
- Type in the following command and press “Enter” to execute it.
net stop wuauserv
- Again, type in the following command and press “Enter”.
net stop bits
- Lastly, navigate to the following folder.
- Press “Ctrl” + “A” to select all the contents of the folder and press “Shift” + “Del” button to delete them permanently.
- Confirm any prompts that warn you about deleting these files and then reboot your computer to complete the process.
- Now, try to update and check to see if the issue persists.
Once your computer boots back up, see whether you are able to install the updates without the 0x8024a105 error. If you do, try to perform an SFC scan to fix any issues with missing files or drivers.