Clients regularly experience this issue in the wake of endeavoring to refresh Windows 10 by means of Windows Update (WU). The error code 0x8024a105 signs an issue with the Automatic Updates segments. Ordinarily, after a bombed update clients will see the accompanying message:
There were issues downloading a few updates, yet we’ll attempt again later. On the off chance that you continue seeing this, take a stab at looking through the web or reaching support for help. This error code may support: (0x8024a105).
f you’re at present battling with this issue, we have figured out how to recognize a couple of reasonable fixes that have effectively helped clients in a comparative circumstance as you. If it’s not too much trouble follow every one of the techniques underneath all together until you experience an answer that figures out how to determine your concern.
We should begin basic, by running the Windows Update troubleshooter. A few clients have figured out how to permit the updates to overcome by permitting the implicit troubleshooter to naturally fix the wrecked parts. Here’s a speedy guide on the best way to run the Windows Update Troubleshooter:
Press Windows key + R to open up a Run window. Type or glue “control.exe/name Microsoft. Troubleshooting” and hit Enter to open the inherent troubleshooter.
In the Troubleshoot window, click on Windows Update, at that point click on Run the troubleshooter.
Hold up until the troubleshooter recognizes issues with your refreshing customer. On the off chance that it figures out how to distinguish any issues with it, follow the on-screen prompts to trigger the programmed fix. Ordinarily, you’ll simply need to pick Apply this fix.
In the event that the Update Troubleshooter reports that it figured out how to fix anything, restart your PC and check whether the issue is settled at the following startup.
In the event that the updates are as yet falling flat with the 0x8024a105 error, descend to Method 2.
In the event that the troubleshooter didn’t figure out how to fix the issue consequently, we should check whether the issue isn’t made by a User Account Control setting. Notably, a few updates were coming up short with the 0x8024a105 error on the grounds that the signed-in account doesn’t have the important authorizations. You can cure this issue effectively by changing the User Accounts consents identified with your record to the Administrator. Here’s a speedy manual for doing this:
Press Windows key + R to open up a Run window. Type or glue “netplwiz” and hit Enter to open the implicit troubleshooter.
In the Users tab, select the client that you’re utilizing and click on Properties.
In the Properties window, go to Group Membership and set the degree of access to the Administrator. Hit Apply to spare your changes.
Note: If the degree of access is as of now set to Administrator, move legitimately to Method 3.
Reboot your PC and ensure you sign in with a similar client account. When the startup is finished endeavor to play out the updates once more. On the off chance that you see them fall flat with the 0x8024a105 error, descend to the last technique.
In the event that the above techniques have ended up being ineffective, we have a minimal decision yet to physically reset the Windows Updates Components and afterward restart the Windows Update process. Out of the three included strategies, this one has a higher likelihood of progress yet requires all the more tweaking.
Here’s a snappy manual for resetting the Windows Updates parts:
Snap the Windows Start bar (base left corner) and quest for “cmd”. At that point, right-click on Command provoke and pick Run as Administrator.
In the raised Command Prompt, we are going to stop the administrations of MSI Installer, Windows Update, BITS and Cryptographic. To do this, embed the accompanying directions and press Enter after every one:
net stop wuauserv net stop cryptSvc net stop bits net stop msiserver
When every one of the administrations have been halted, how about we rename the SoftwareDistribution organizer and the Catroot2 envelope so as to compel Windows Update to reinitiate its segments. Glue or type the two directions into the raised Command brief and press Enter after each one:ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 Catroot2.old
When the two envelopes have been renamed, it’s a great opportunity to restart the administrations of MSI Installer, BITS, Cryptographic and Windows Update. To do this, type the accompanying order in Command Prompt and hit Enter after each direction:
net start wuauserv net start cryptSvc net start bits net start msiserver
When the administrations have been restarted, close the raised Command Prompt and reboot your PC. When your PC boots back up, see whether you can introduce the updates without the 0x8024a105 error.