Code:: 0x800B0100
Hex:: -2146762496
Error Lookup:: TRUST_E_NOSIGNATURE
Possible Cause:: This is almost always a corruption found within a WU file.
The above error message is almost always an indication that there is a corrupt WU file (.cat/.mum/.manifest or Payload system file) on your system.
Check for corrupt files using SURT.
If there is a corrupt WU file on your machine chances are SURT will detect the corruption. For instructions on how to use SURT please refer to the article System Update Readiness Tool (SURT).
After running SURT you will be able to identify if there are any corrupt files on your system by the CheckSur.log.
If the SURT has identified errors but was unable to repair them please create a new thread in the Windows Update forum here. When creating a new thread please include the contents of CheckSUR.log and one of the Windows Update staff will get you going again. This is Free online help.
No corrupts detected by SURT?
If you ran SURT and your log has returned not corruptions. Then it is likely an issue with a temporary downloaded WU file. To fix this please do the following:
- Click Start -> Type in CMD in the search -> Right click on cmd.exe and choose Run as Administrator
- Entre in the following commands:
net stop wuauserv
ren %SystemRoot%\SoftwareDistribution\Download DL.bak
ren %SystemRoot%\SoftwareDistribution\DataStore DS.bak
net start wuauserv
Just in case you are interested as to what is going on with the above commands and how it helped..
Just a little background first…When you open up Windows Update and there is a message that new updates are available the first thing that needs to be done is for Windows to download the files, once the files have been downloaded WU needs to extract the updates in order to install them. Now when WU is performing these tasks the download and the extracts of the downloads get stored inside %SystemRoot%\SoftwareDistribution\ (C:\Windows\SoftwareDistribution). The error message that was being detected was 0x800B0100 means a corrupt file is present and that is stopping WU from installing any updates. What we did before was repair all the corrupt Windows update files inside the location of where the Windows Update packages are stored (C:\Windows\Servicing\Packages) once installed successfully, we did this when running SURT. Now that we know all packages are fixed that live inside C:\Windows\Servicing\Packages we know that the corruption is not with these files.
When SURT does a scan for corrupt WU files it doesn’t look inside C:\Windows\SoftwareDistribution as the directory is pretty much a Temporary file location before the WU is installed. This means that the error detected by WU must be inside the temporary location (C:\Windows\SoftwareDistribution) as the Windows update store (C:\Windows\Servicing\Packages) is no longer showing any corrupt files.
What the first command did net stop wuauserv was stop the Windows Update service from running, if the service is still in use it will block the other commands from being executed.
The following commands,
ren %SystemRoot%\SoftwareDistribution\Download DL.bak
ren %SystemRoot%\SoftwareDistribution\DataStore DS.bak
Renamed two of the temporary locations WU uses to install its updates, what this does is it will force WU to download and installed the files again, hopefully they won’t get corrupt again. Remember how I said before that the wuauserv had to be stopped otherwise the further commands will not work? If wuauserv was not stopped this service would of stopped the rename of both these files, because the service would of ‘locked’ both of the folders from being renamed as it was currently using these folders. Here is what the command line was doing in a bit more detail:
ren %SystemRoot%\SoftwareDistribution\Download DL.bak
ren {Location of original file/folder} {What you want to call the file/folder}
ren is the command to rename a file or folder.
%SystemRoot%\SoftwareDistribution\Download is the path of where the folder is located originally.
DL.bak is what I want to call the folder once the rename has been done.
The Last command net start wuauserv was just starting the service again.
Hope this helps.
Alex