Updating your Windows 10 computer does not always go smoothly as there are some errors you can encounter along the way. One of these Windows Update errors is the error code of 0x80246008. This kind of error can occur during different phases of an update that’s being downloaded or installed and even when an update is being initialized.
If you narrow down the cause of this Windows Update error, you’ll most likely see that it is related to the deliverability of a file to a computer from the servers of Microsoft. In other words, the error might be due to conflicts from programs like Firewall as well as third party programs like Antivirus or it could also be due to corrupted disk image or system files or it could be that any of the supporting Windows Update components and services are not working properly. Whatever the cause may be, the potential fixes provided in this post can be applicable to Windows Updates as well as the Microsoft Store.
Refer to the suggestions provided below to resolve the Windows Update Error 0x80246008 but before you proceed, make sure that you create a System Restore point first.
reg add HKLMSYSTEMCurrentControlSetControlBackupRestoreFilesNotToBackup
If the registry tweak didn’t work, you can run a System File Checker scan instead. It is a built-in command-line utility that replaces bad and corrupted system files to good system files that might be the cause why you’re getting the error when you try updating your computer. To run the SFC command, follow the steps given below.
The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:
If the System File Checker wasn’t able to resolve the Windows Update error, you could also try running the Windows Update Troubleshooter as it could also help in fixing any issues related to Windows Update including this one. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.
Disabling the antivirus program or any security software installed in your computer is always a good idea you can try when the Windows Update process does not go smoothly. So before you try updating your computer again, make sure to disable the antivirus or security program and once the Windows Update is done, don’t forget to enable the antivirus program back again.
The downloaded Windows Updates are placed in a folder called “SoftwareDistribution”. The files downloaded in this folder are automatically deleted once the installation is completed. However, if the files are not clean up or if the installation is still pending, you can delete all the files in this folder after you pause the Windows Update service. For complete instructions, refer to the steps below.
net stop wuauserv
net start cryptSvc
net start bits
net start msiserver
After resetting the SoftwareDistribution folder, you need to reset the Catroot2 folder to restart the services you just stopped. To do that, follow these steps:
net start wuauserv
net start cryptSvc
net start bits
net start msiserver

AtoZManuals is a Browser Extension developed by MindSpark Inc. This extension offers users an easy way to search Customer Manuals for Products. This extension may seem handy at first, however, this extension hijacks your browser home page, and changes your default search engine to MyWay.
While browsing the internet with this extension you will see additional ads, sponsored links, and pop-up ads in your browser. Additionally, this extension monitors your browser activity, including search words, visited links, shopping information, and sometimes even personal information, which is later used to display better-targeted ads.
Multiple anti-virus scanners have marked this extension as a Browser Hijacker, and due to its rogue behavior, it is not recommended to keep it on your computer.
Error Causes‘Update server not available (error: 3)’
Error Causes
A few days ago we celebrated fixing of months-long PrintNightmare vulnerability by Microsoft, sadly a new bug and issue have been found.
Firstly discovered Microsoft stated:
A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged file operations. An attacker who successfully exploited this vulnerability could run arbitrary code with SYSTEM privileges. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.A few days ago, Microsoft officially released a patch that was supposed to finally fix it. As you might recall this vulnerability was present for quite some time, Microsoft's solution after a long struggle was to elevate certain privileges to administrator account only and remove user accounts from managing printers. It complicated things a little bit but it was stated payoff was worth it. The new issue now is that on a system that already had accounts created and set, old accounts still can hijack the system, patch issues address only accounts that are created after the fix is administrated, old ones can still do whatever they want. Once again of course Microsoft has stated that until it is again resolved you should again disable the Print Spooler service as a temporary workaround.