[SOLVED] Error 800B0100

C

conker

Member
Joined
Mar 9, 2016
Posts
10
SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-03-10 09:33:46.509
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.




AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2016-03-10 09:38:13.991
----------------------EOF-----------------------


The CBS log is very large. Uploading shortly.



Everything was fine until this recent Patch Tuesday. 2 identical machines patched just fine. This one errored out with 800B0100. The error happens every time, and I've tried clearing out the Windows Update download cache, resetting its history, running WindowsUpdateDiagnostic.diagcab and Windows6.1-KB947821-v34-x64.msu . The WindowsUpdateDiagnostic reports some issues and fixes them, but never fixes the 800B0100 issue. Windows6.1-KB947821-v34-x64.msu fails to install, so it never does its thing.

Windows Update fails regardless of whether I try to install directly from Microsoft or via our System Center / WSUS site.

Any ideas?
Thanks
 
Hello and Welcome!

Please try to install the update again using the downloaded MSU.
When the update fails to install, zip and attach C:\Windows\Logs\CBS\CBS.log with your reply.
If CBS.zip is larger than 8MB, please use a file sharing service such as OneDrive, DropBox, SendSpace, etc. to upload the file and include the link with your reply.
 
zcomputerwiz said:
Hello and Welcome!

Please try to install the update again using the downloaded MSU.
When the update fails to install, zip and attach C:\Windows\Logs\CBS\CBS.log with your reply.
If CBS.zip is larger than 8MB, please use a file sharing service such as OneDrive, DropBox, SendSpace, etc. to upload the file and include the link with your reply.
Click to expand...

Which update should I try to install manually? Any update?

The definition updates for System Center Endpoint Protection are able to install successfully via Windows Update.
But everything else is not.

I just tried manually downloading and installing Windows6.1-KB3000483-x64.msu and it failed.
CBS.log has 0x800b0100 / TRUST_E_NOSIGNATURE errors.

Attached. View attachment CBS.zip
 
zcomputerwiz said:
System Update Readiness Tool (SURT)

Download and run the System Update Readiness Tool for your version of Windows here: System Update Readiness Tool

NOTE: If you aren't sure if your Windows installation is 32-bit or 64-bit, check here: How to determine whether a computer is running a 32-bit version or 64-bit version of the Windows operating system

This tool will take some time to complete - when it has finished, attach C:\Windows\Logs\CBS\CheckSUR.log with your reply.
Click to expand...

Attached. View attachment CheckSUR.log
It lists 75 zeroed manifests, 27 corrupt mums and 27 corrupt cats.

It lists 129 different unavailable repair files. (I checked, and I have these files on an identical system.)
 
Windows Update Package Replacement

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Please download the attached file, Packs.zip and save this to your Desktop.
  2. Right-click on the file and select Extract All...
  3. Tick the box labelled Show extracted files when complete then click Extract
  4. A window will open showing two folders, Manifests and Packages
  5. Open the Manifests folder and copy the files into the following folder

    C:\Windows\Temp\CheckSur\Winsxs\Manifests

  6. Open the Packages folder and copy the files into the following folder

    C:\Windows\Temp\CheckSur\Servicing\Packages

  7. Run the System Update Readiness Tool (SURT) again.
  8. When the SURT finishes installing, copy (Ctrl + C) and paste (Ctrl + V) the contents of the SURT log into your next post please:

    C:\Windows\Logs\CBS\CheckSUR.log

View attachment Packs.zip
 
zcomputerwiz said:
Windows Update Package Replacement

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Please download the attached file, Packs.zip and save this to your Desktop.
  2. Right-click on the file and select Extract All...
  3. Tick the box labelled Show extracted files when complete then click Extract
  4. A window will open showing two folders, Manifests and Packages
  5. Open the Manifests folder and copy the files into the following folder

    C:\Windows\Temp\CheckSur\Winsxs\Manifests
  6. Open the Packages folder and copy the files into the following folder

    C:\Windows\Temp\CheckSur\Servicing\Packages
  7. Run the System Update Readiness Tool (SURT) again.
  8. When the SURT finishes installing, copy (Ctrl + C) and paste (Ctrl + V) the contents of the SURT log into your next post please:

    C:\Windows\Logs\CBS\CheckSUR.log

View attachment 19633
Click to expand...

Looks like that worked perfectly.

Attached. View attachment CheckSUR.log
 
Very good.

Please check for Windows Updates and install any that are offered.

If an update fails to install, zip and attach CBS.log with your reply.
 
I tested one of the updates that failed and it worked.
I'll restart and test the others later, but I believe everything is working correctly now.

Thanks for the help.
 
zcomputerwiz said:
Is everything working as expected?
Click to expand...

Unfortunately no.

After restarting, I could no longer remote into the box.
I've pulled it over to my desk and hooked up a monitor, mouse, and keyboard.

The event viewer adds several audit failure entries whenever I try to remote in. The error is "Code integrity determined that the image hash of a file is not valid. The file could be corrupt due to unauthorized modification or the invalid hash could indicate a potential disk device error."

The file in question is "\Device\Harddisk\Volume4\Windows\System32\drivers\tssecsrv.sys". I was able to successfully remote into the box before issuing the last restart after the 1 successful update.

sfc /scannow reports no issues.
chkdsk c: reports no issues. (I haven't done an offline chkdsk /r yet since the box is being used.)
 
Additionally, the System log shows Event ID 26, Application Popup, :\SystemRoot\System32\DRIVERS\tssecsrv.sys failed to load

I've run a chkdsk /B/ V and no problems were reported.
I've also explicitly run a sfc /verifyfile=c:windows\system32\drivers\tssecsrv.sys and no issues are found.

I'm able to run Windows update, though, and have installed all the updates that were causing problems before.
 
I inspected the file details of tssecsrv.sys and looked up the file version string and saw that that version came from KB3080079.
I uninstalled KB3080079, rebooted, and was able to remote into the box again.

I'm going to try reinstalling the update (via Windows Update if possible), rebooting, and remoting in again.

Edit: Actually, I'm not. This box doesn't need anything this update does, and it's not one we push out (I must have grabbed it when manually using Windows Update) so I shouldn't need to mess with it. I'm leaving it as is.

Thanks
 
Very interesting. I'm surprised that SFC didn't take issue with the file.

So you are able to remote into the machine and no further Windows Updates are being offered?
 
Glad to hear it :)

I'll mark the thread solved. If you encounter problems, please post back and I will continue to assist you.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top