[German]Does Windows throws an update error 0x800b0100 and aborts the download and installation of updates? Here are some information about this bug I encountered from Windows 7 to Windows 10.
Recently I stumbled upon a German message reporting update error 0x800b0100 for Windows 10. Windows 10 displayed a clear text error message, saying, that some update files are not signed properly.
But I’ve seen tis error also in Windows 7, and within my German blog post Windows 7 Service Pack 1 Troubleshooting-Tipps I’ve posted some details. The error code 0x800B0100 stands for TRUST_E_NOSIGNATURE and means that the update package`s digital signature is missing or wrong.
The first The first thing I’m suggesting in Windows 10 is to restart the operating system. If necessary, this restart can be carried out with the Shift key pressed.
If the restart does not help, it is recommended that you check the system for corrupted files. The steps are described in more detail in the article Check and repair Windows system files and component store. Dism is also used to inspect and repair the component door, if necessary.
For Windows 7, 8, 8.1 and older versions, Microsoft has described in this KB article that DLL files are no longer properly registered. Microsoft describes in principle the approach to repair, that I discussed in the article the article Check and repair Windows system files and component store. Because Windows 7 doesn’t support dism, the tool checksur is needed to repair the system. And this Microsoft blog post discusses a similar case.
If third-party Internet security tools (virus scanners, etc.) are installed, they should be uninstalled and a clean tool from the manufacturer should be used. This is to ensure that these programs do not damage the downloads.
If these measures do not work, you can still try to reset the Update Store manually. How this works is described in the blog entry Windows 10: Update error 0x80240437.
Microsoft offers broken updates
At the end of the day, however, it can also be, that Microsoft has provided the update packages with incorrect signatures on the update servers. The case quoted above, in which two machines are affected at the same time, indicates this (I know the person affected, and he is able to carry out the above methods).
Cookies helps to fund this blog: Cookie settings