Windows update error 800B0100 (Win7 Pro)

moz · Feb 13, 2015

Hi,

I'm having trouble with Windows Update failing at installing updates such as KB2985461.

The issue persists, despite completing the following a few times:

-SURT
-manual install of KB2985461 (a different failing update for .NET worked this way)
-Windows Update Troubleshooter (normal mode and safe mode; see screenshot)
-sfc /scannow (elevated cmd.exe via safe mode; "Windows Resource Protection found corrupt files but was unable to fix some of them.")

Attached CBS.log suggests corrupt packages, catalog verification, TRUST_E_NOSIGNATURE problems etc. There's also a line with a failure with KB976932, seems to be SP1 for Win7 but this is already installed as per System Properties.

What makes this difficult is I only have remote access to the machine and it has a BIOS password, so reboots can only be done when the user is available... which isn't often.

Thanks in advance!

tom982 · Feb 13, 2015

Hello moz, welcome to Sysnative!

You have a few issues here:

Code:

2015-02-13 10:45:48, Info                  CBS    Missing Current State value for package: Package_for_KB2898785~31bf3856ad364e35~amd64~~11.2.1.0, force absent so at least it can be re-installed
2015-02-13 10:45:48, Info                  CBS    Missing Current State value for package: Package_for_KB2898785~31bf3856ad364e35~amd64~~11.2.1.0, force absent so at least it can be re-installed
2015-02-13 10:45:50, Info                  CBS    WinVerifyTrust failed [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2015-02-13 10:45:50, Error                 CBS    Failed to verify if catalog file \\?\C:\Windows\Servicing\Packages\Package_for_KB2985461~31bf3856ad364e35~amd64~~6.1.1.0.cat is valid. [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2015-02-13 10:45:50, Info                  CBS    Mark store corruption flag because of package: Package_for_KB2985461~31bf3856ad364e35~amd64~~6.1.1.0. [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2015-02-13 10:45:50, Info                  CBS    Failed to initialize package: Package_for_KB2985461~31bf3856ad364e35~amd64~~6.1.1.0, from path: \\?\C:\Windows\Servicing\Packages\Package_for_KB2985461~31bf3856ad364e35~amd64~~6.1.1.0.mum, existing package: 1 [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2015-02-13 10:45:50, Info                  CBS    Failed to resolve package [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2015-02-13 10:45:50, Info                  CBS    Failed to populate children. [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2015-02-13 10:45:50, Info                  CBS    Failed to initialize package: Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514, from path: \\?\C:\Windows\Servicing\Packages\Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514.mum, existing package: 1 [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2015-02-13 10:45:50, Info                  CBS    Failed to resolve package [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2015-02-13 10:45:50, Info                  CBS    Failed to populate children. [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2015-02-13 10:45:50, Info                  CBS    Failed to initialize internal package for package: Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514 [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2015-02-13 10:45:50, Info                  CBS    Delay load failed for package: Package_for_KB976932~31bf3856ad364e35~amd64~~6.1.1.17514 [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2015-02-13 10:45:50, Error                 CBS    Delay Initialization Failed [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]

And:

Code:

2015-02-13 15:37:18, Info                  CSI    0000035b Manifest hash for component [ml:280{140},l:156{78}]"msil_mscorlib.resources_b77a5c561934e089_6.1.7601.18529_en-us_6685ac8c75cac403" does not match expected value. 
 Expected:{l:32 b:f4a80e2827414ff077dbb5336baf5a2128abe5484a0e54056001c5d936bb90c7}
 Found:{l:32 b:a0567813dfb85d8da78f389e9916a919db3afe3d273bafb8c138e08d01a69bbb}.
2015-02-13 15:37:18, Info                  CSI    0000035c Looking for manifest in Backup Dir...
2015-02-13 15:37:18, Error                 CSI    0000035d (F) Unable to load manifest for component [ml:280{140},l:156{78}]"msil_mscorlib.resources_b77a5c561934e089_6.1.7601.18529_en-us_6685ac8c75cac403"[gle=0x80004005]
2015-02-13 15:37:18, Error                 CSI    0000035e@2015/2/13:20:37:18.741 (F) d:\win7sp1_gdr\base\wcp\componentstore\storelayout.cpp(2714): Store corruption detected in function ComponentStore::CRawStoreLayout::FetchManifestContent expression: 0
  FileHashMismatch on resource [105]"\winsxs\manifests\msil_mscorlib.resources_b77a5c561934e089_6.1.7601.18529_en-us_6685ac8c75cac403.manifest"[gle=0x80004005]

Can you upload the log from the SURT please:

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

It's a lot better for diagnosing this kind of problem :)

Tom

moz · Feb 13, 2015

Hi Tom,

Thanks for the quick reply!

Indeed, CheckSUR is a friendlier looking log. Sorry I missed that the first time.

tom982 · Feb 13, 2015

Hi moz,

No worries, we don't ask for it in every case so you weren't to know :) This should fix the lot:

SFCFix Script

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.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the file below, SFCFixScript.zip, and save this to your Desktop.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.zip.
Drag the file SFCFixScript.zip onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

https://dl.dropboxusercontent.com/u/16537616/Fixes/SFCFix/Scripts/moz/SFCFixScript.zip

When that's finished, run the SURT and post the log again please.

Tom

moz · Feb 14, 2015

That's great, thanks again. I assume this can't be done in safe mode?

I ask as it's how I'm currently booted, and connected remotely. The machine has a boot password (Self-Encrypting Drive) which I'll need the user to type in when they return Monday as I can't do it remotely. :s6:

I wonder if vPro/KVM would have got me around that.

moz · Feb 14, 2015

I gave it a go in safe mode, let me know this looks. I figured it had something to do with permissions.

Will just need to wait for that reboot to run Windows Update.

Code:

SFCFix version 2.4.2.1 by niemiro.
Start time: 2015-02-14 01:44:52.282
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Support and Settings\SFCfix\SFCFixScript.zip [0]
 
 
 
 
PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\Manifests\amd64_microsoft-windows-t..lservices-workspace_31bf3856ad364e35_6.1.7601.18546_none_2ef67fe170d4f4b5.manifest
Successfully took permissions for file or folder C:\Windows\winsxs\Manifests\amd64_microsoft-windows-t..lservices-workspace_31bf3856ad364e35_6.1.7601.22757_none_2f764ef089f9c6ee.manifest
Successfully took permissions for file or folder C:\Windows\winsxs\Manifests\amd64_microsoft-windows-t..workspace.resources_31bf3856ad364e35_6.1.7601.22757_en-us_6f72e28ec11a8983.manifest
Successfully took permissions for file or folder C:\Windows\winsxs\Manifests\msil_mscorlib.resources_b77a5c561934e089_6.1.7601.18529_en-us_6685ac8c75cac403.manifest
Successfully took permissions for file or folder C:\Windows\winsxs\Manifests\msil_mscorlib.resources_b77a5c561934e089_6.1.7601.22740_en-us_4fbad3448f6f705f.manifest
Successfully took permissions for file or folder C:\Windows\winsxs\Manifests\wow64_microsoft-windows-t..lservices-workspace_31bf3856ad364e35_6.1.7601.18546_none_394b2a33a535b6b0.manifest
Successfully took permissions for file or folder C:\Windows\winsxs\Manifests\wow64_microsoft-windows-t..lservices-workspace_31bf3856ad364e35_6.1.7601.22757_none_39caf942be5a88e9.manifest
Successfully took permissions for file or folder C:\Windows\winsxs\Manifests\x86_microsoft-windows-t..workspace.resources_31bf3856ad364e35_6.1.7601.22757_en-us_1354470b08bd184d.manifest
Successfully took permissions for file or folder C:\Windows\servicing\Packages\package_1_for_kb2985461~31bf3856ad364e35~amd64~~6.1.1.0.cat
Successfully took permissions for file or folder C:\Windows\servicing\Packages\package_1_for_kb2985461~31bf3856ad364e35~amd64~~6.1.1.0.mum
Successfully took permissions for file or folder C:\Windows\servicing\Packages\package_8_for_kb2985461~31bf3856ad364e35~amd64~~6.1.1.0.cat
Successfully took permissions for file or folder C:\Windows\servicing\Packages\package_8_for_kb2985461~31bf3856ad364e35~amd64~~6.1.1.0.mum
Successfully took permissions for file or folder C:\Windows\servicing\Packages\package_for_kb2985461_sp1~31bf3856ad364e35~amd64~~6.1.1.0.cat
Successfully took permissions for file or folder C:\Windows\servicing\Packages\package_for_kb2985461_sp1~31bf3856ad364e35~amd64~~6.1.1.0.mum
Successfully took permissions for file or folder C:\Windows\servicing\Packages\Package_for_KB2985461~31bf3856ad364e35~amd64~~6.1.1.0.cat
Successfully took permissions for file or folder C:\Windows\servicing\Packages\Package_for_KB2985461~31bf3856ad364e35~amd64~~6.1.1.0.mum
 
Successfully copied file C:\Users\JTK\AppData\Local\niemiro\Archive\winsxs\Manifests\amd64_microsoft-windows-t..lservices-workspace_31bf3856ad364e35_6.1.7601.18546_none_2ef67fe170d4f4b5.manifest to C:\Windows\winsxs\Manifests\amd64_microsoft-windows-t..lservices-workspace_31bf3856ad364e35_6.1.7601.18546_none_2ef67fe170d4f4b5.manifest.
Successfully copied file C:\Users\JTK\AppData\Local\niemiro\Archive\winsxs\Manifests\amd64_microsoft-windows-t..lservices-workspace_31bf3856ad364e35_6.1.7601.22757_none_2f764ef089f9c6ee.manifest to C:\Windows\winsxs\Manifests\amd64_microsoft-windows-t..lservices-workspace_31bf3856ad364e35_6.1.7601.22757_none_2f764ef089f9c6ee.manifest.
Successfully copied file C:\Users\JTK\AppData\Local\niemiro\Archive\winsxs\Manifests\amd64_microsoft-windows-t..workspace.resources_31bf3856ad364e35_6.1.7601.22757_en-us_6f72e28ec11a8983.manifest to C:\Windows\winsxs\Manifests\amd64_microsoft-windows-t..workspace.resources_31bf3856ad364e35_6.1.7601.22757_en-us_6f72e28ec11a8983.manifest.
Successfully copied file C:\Users\JTK\AppData\Local\niemiro\Archive\winsxs\Manifests\msil_mscorlib.resources_b77a5c561934e089_6.1.7601.18529_en-us_6685ac8c75cac403.manifest to C:\Windows\winsxs\Manifests\msil_mscorlib.resources_b77a5c561934e089_6.1.7601.18529_en-us_6685ac8c75cac403.manifest.
Successfully copied file C:\Users\JTK\AppData\Local\niemiro\Archive\winsxs\Manifests\msil_mscorlib.resources_b77a5c561934e089_6.1.7601.22740_en-us_4fbad3448f6f705f.manifest to C:\Windows\winsxs\Manifests\msil_mscorlib.resources_b77a5c561934e089_6.1.7601.22740_en-us_4fbad3448f6f705f.manifest.
Successfully copied file C:\Users\JTK\AppData\Local\niemiro\Archive\winsxs\Manifests\wow64_microsoft-windows-t..lservices-workspace_31bf3856ad364e35_6.1.7601.18546_none_394b2a33a535b6b0.manifest to C:\Windows\winsxs\Manifests\wow64_microsoft-windows-t..lservices-workspace_31bf3856ad364e35_6.1.7601.18546_none_394b2a33a535b6b0.manifest.
Successfully copied file C:\Users\JTK\AppData\Local\niemiro\Archive\winsxs\Manifests\wow64_microsoft-windows-t..lservices-workspace_31bf3856ad364e35_6.1.7601.22757_none_39caf942be5a88e9.manifest to C:\Windows\winsxs\Manifests\wow64_microsoft-windows-t..lservices-workspace_31bf3856ad364e35_6.1.7601.22757_none_39caf942be5a88e9.manifest.
Successfully copied file C:\Users\JTK\AppData\Local\niemiro\Archive\winsxs\Manifests\x86_microsoft-windows-t..workspace.resources_31bf3856ad364e35_6.1.7601.22757_en-us_1354470b08bd184d.manifest to C:\Windows\winsxs\Manifests\x86_microsoft-windows-t..workspace.resources_31bf3856ad364e35_6.1.7601.22757_en-us_1354470b08bd184d.manifest.
Successfully copied file C:\Users\JTK\AppData\Local\niemiro\Archive\servicing\Packages\package_1_for_kb2985461~31bf3856ad364e35~amd64~~6.1.1.0.cat to C:\Windows\servicing\Packages\package_1_for_kb2985461~31bf3856ad364e35~amd64~~6.1.1.0.cat.
Successfully copied file C:\Users\JTK\AppData\Local\niemiro\Archive\servicing\Packages\package_1_for_kb2985461~31bf3856ad364e35~amd64~~6.1.1.0.mum to C:\Windows\servicing\Packages\package_1_for_kb2985461~31bf3856ad364e35~amd64~~6.1.1.0.mum.
Successfully copied file C:\Users\JTK\AppData\Local\niemiro\Archive\servicing\Packages\package_8_for_kb2985461~31bf3856ad364e35~amd64~~6.1.1.0.cat to C:\Windows\servicing\Packages\package_8_for_kb2985461~31bf3856ad364e35~amd64~~6.1.1.0.cat.
Successfully copied file C:\Users\JTK\AppData\Local\niemiro\Archive\servicing\Packages\package_8_for_kb2985461~31bf3856ad364e35~amd64~~6.1.1.0.mum to C:\Windows\servicing\Packages\package_8_for_kb2985461~31bf3856ad364e35~amd64~~6.1.1.0.mum.
Successfully copied file C:\Users\JTK\AppData\Local\niemiro\Archive\servicing\Packages\package_for_kb2985461_sp1~31bf3856ad364e35~amd64~~6.1.1.0.cat to C:\Windows\servicing\Packages\package_for_kb2985461_sp1~31bf3856ad364e35~amd64~~6.1.1.0.cat.
Successfully copied file C:\Users\JTK\AppData\Local\niemiro\Archive\servicing\Packages\package_for_kb2985461_sp1~31bf3856ad364e35~amd64~~6.1.1.0.mum to C:\Windows\servicing\Packages\package_for_kb2985461_sp1~31bf3856ad364e35~amd64~~6.1.1.0.mum.
Successfully copied file C:\Users\JTK\AppData\Local\niemiro\Archive\servicing\Packages\Package_for_KB2985461~31bf3856ad364e35~amd64~~6.1.1.0.cat to C:\Windows\servicing\Packages\Package_for_KB2985461~31bf3856ad364e35~amd64~~6.1.1.0.cat.
Successfully copied file C:\Users\JTK\AppData\Local\niemiro\Archive\servicing\Packages\Package_for_KB2985461~31bf3856ad364e35~amd64~~6.1.1.0.mum to C:\Windows\servicing\Packages\Package_for_KB2985461~31bf3856ad364e35~amd64~~6.1.1.0.mum.
 
Successfully restored ownership for C:\Windows\winsxs\Manifests\amd64_microsoft-windows-t..lservices-workspace_31bf3856ad364e35_6.1.7601.18546_none_2ef67fe170d4f4b5.manifest
Successfully restored permissions on C:\Windows\winsxs\Manifests\amd64_microsoft-windows-t..lservices-workspace_31bf3856ad364e35_6.1.7601.18546_none_2ef67fe170d4f4b5.manifest
Successfully restored ownership for C:\Windows\winsxs\Manifests\amd64_microsoft-windows-t..lservices-workspace_31bf3856ad364e35_6.1.7601.22757_none_2f764ef089f9c6ee.manifest
Successfully restored permissions on C:\Windows\winsxs\Manifests\amd64_microsoft-windows-t..lservices-workspace_31bf3856ad364e35_6.1.7601.22757_none_2f764ef089f9c6ee.manifest
Successfully restored ownership for C:\Windows\winsxs\Manifests\amd64_microsoft-windows-t..workspace.resources_31bf3856ad364e35_6.1.7601.22757_en-us_6f72e28ec11a8983.manifest
Successfully restored permissions on C:\Windows\winsxs\Manifests\amd64_microsoft-windows-t..workspace.resources_31bf3856ad364e35_6.1.7601.22757_en-us_6f72e28ec11a8983.manifest
Successfully restored ownership for C:\Windows\winsxs\Manifests\msil_mscorlib.resources_b77a5c561934e089_6.1.7601.18529_en-us_6685ac8c75cac403.manifest
Successfully restored permissions on C:\Windows\winsxs\Manifests\msil_mscorlib.resources_b77a5c561934e089_6.1.7601.18529_en-us_6685ac8c75cac403.manifest
Successfully restored ownership for C:\Windows\winsxs\Manifests\msil_mscorlib.resources_b77a5c561934e089_6.1.7601.22740_en-us_4fbad3448f6f705f.manifest
Successfully restored permissions on C:\Windows\winsxs\Manifests\msil_mscorlib.resources_b77a5c561934e089_6.1.7601.22740_en-us_4fbad3448f6f705f.manifest
Successfully restored ownership for C:\Windows\winsxs\Manifests\wow64_microsoft-windows-t..lservices-workspace_31bf3856ad364e35_6.1.7601.18546_none_394b2a33a535b6b0.manifest
Successfully restored permissions on C:\Windows\winsxs\Manifests\wow64_microsoft-windows-t..lservices-workspace_31bf3856ad364e35_6.1.7601.18546_none_394b2a33a535b6b0.manifest
Successfully restored ownership for C:\Windows\winsxs\Manifests\wow64_microsoft-windows-t..lservices-workspace_31bf3856ad364e35_6.1.7601.22757_none_39caf942be5a88e9.manifest
Successfully restored permissions on C:\Windows\winsxs\Manifests\wow64_microsoft-windows-t..lservices-workspace_31bf3856ad364e35_6.1.7601.22757_none_39caf942be5a88e9.manifest
Successfully restored ownership for C:\Windows\winsxs\Manifests\x86_microsoft-windows-t..workspace.resources_31bf3856ad364e35_6.1.7601.22757_en-us_1354470b08bd184d.manifest
Successfully restored permissions on C:\Windows\winsxs\Manifests\x86_microsoft-windows-t..workspace.resources_31bf3856ad364e35_6.1.7601.22757_en-us_1354470b08bd184d.manifest
Successfully restored ownership for C:\Windows\servicing\Packages\package_1_for_kb2985461~31bf3856ad364e35~amd64~~6.1.1.0.cat
Successfully restored permissions on C:\Windows\servicing\Packages\package_1_for_kb2985461~31bf3856ad364e35~amd64~~6.1.1.0.cat
Successfully restored ownership for C:\Windows\servicing\Packages\package_1_for_kb2985461~31bf3856ad364e35~amd64~~6.1.1.0.mum
Successfully restored permissions on C:\Windows\servicing\Packages\package_1_for_kb2985461~31bf3856ad364e35~amd64~~6.1.1.0.mum
Successfully restored ownership for C:\Windows\servicing\Packages\package_8_for_kb2985461~31bf3856ad364e35~amd64~~6.1.1.0.cat
Successfully restored permissions on C:\Windows\servicing\Packages\package_8_for_kb2985461~31bf3856ad364e35~amd64~~6.1.1.0.cat
Successfully restored ownership for C:\Windows\servicing\Packages\package_8_for_kb2985461~31bf3856ad364e35~amd64~~6.1.1.0.mum
Successfully restored permissions on C:\Windows\servicing\Packages\package_8_for_kb2985461~31bf3856ad364e35~amd64~~6.1.1.0.mum
Successfully restored ownership for C:\Windows\servicing\Packages\package_for_kb2985461_sp1~31bf3856ad364e35~amd64~~6.1.1.0.cat
Successfully restored permissions on C:\Windows\servicing\Packages\package_for_kb2985461_sp1~31bf3856ad364e35~amd64~~6.1.1.0.cat
Successfully restored ownership for C:\Windows\servicing\Packages\package_for_kb2985461_sp1~31bf3856ad364e35~amd64~~6.1.1.0.mum
Successfully restored permissions on C:\Windows\servicing\Packages\package_for_kb2985461_sp1~31bf3856ad364e35~amd64~~6.1.1.0.mum
Successfully restored ownership for C:\Windows\servicing\Packages\Package_for_KB2985461~31bf3856ad364e35~amd64~~6.1.1.0.cat
Successfully restored permissions on C:\Windows\servicing\Packages\Package_for_KB2985461~31bf3856ad364e35~amd64~~6.1.1.0.cat
Successfully restored ownership for C:\Windows\servicing\Packages\Package_for_KB2985461~31bf3856ad364e35~amd64~~6.1.1.0.mum
Successfully restored permissions on C:\Windows\servicing\Packages\Package_for_KB2985461~31bf3856ad364e35~amd64~~6.1.1.0.mum
PowerCopy:: directive completed successfully.
 
 
 
 
RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB2898785~31bf3856ad364e35~amd64~~11.2.1.0.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB2898785~31bf3856ad364e35~amd64~~11.2.1.0.
 
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB2898785~31bf3856ad364e35~amd64~~11.2.1.0.
 
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB2898785~31bf3856ad364e35~amd64~~11.2.1.0.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB2898785~31bf3856ad364e35~amd64~~11.2.1.0.
 
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB2898785~31bf3856ad364e35~amd64~~11.2.1.0.
 
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB2898785~31bf3856ad364e35~amd64~~11.2.1.0.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB2898785~31bf3856ad364e35~amd64~~11.2.1.0.
RegistryScript:: directive completed successfully.
 
 
 
 
Successfully processed all directives.
SFCFix version 2.4.2.1 by niemiro has completed.
Currently storing 17 datablocks.
Finish time: 2015-02-14 01:44:53.268
Script hash: dgbJbik3Jlq6mZ2FIdPu8RSl3Fb7Q6VhdtiuF3z6pFc=
----------------------EOF-----------------------

tom982 · Feb 14, 2015

Looks good! Good question, but I think SFCFix should work perfectly in safe mode.

This wasn't actually a permissions problem, it was a few corrupt files which we just replaced. The permissions lines you see in the SFCFix output were just SFCFix unlocking the file then tidying up after itself.

You should be able to run the SURT and SFC /scannow without rebooting so if you could get that done then that'd be great - it will confirm we've fixed the problem at which point we can run Windows Update to confirm it. There's a good chance you'll hit a 0x8024200D error as a result of the fix we did, but that's fixed by installing the update manually from the Microsoft site.

moz · Feb 14, 2015

Okay thanks, I reviewed closer and see what you mean.

There seem to be similar errors in the original logs for two other KB's not addressed here.

Should I be concerned with this?

Code:

(f)    CBS Registry Error    0x80070002    Package_38_for_KB2929437~31bf3856ad364e35~amd64~~11.2.1.0        failed to get CurrentState
(f)    CBS Registry Error    0x80070002    Package_38_for_KB2929437~31bf3856ad364e35~amd64~~11.2.1.0        failed to get Visibility
(f)    CBS Registry Error    0x80070002    Package_39_for_KB2929437~31bf3856ad364e35~amd64~~11.2.1.0        failed to get CurrentState
(f)    CBS Registry Error    0x80070002    Package_39_for_KB2929437~31bf3856ad364e35~amd64~~11.2.1.0        failed to get Visibility

And this (from the end of the first chunk of code you pasted)?

Code:

2015-02-13 10:45:50, Info                  CBS    Delay load failed for package: Package_for_KB976932~31bf3856ad364e35~amd64~~6.1.1.17514 [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]
2015-02-13 10:45:50, Error                 CBS    Delay Initialization Failed [HRESULT = 0x800b0100 - TRUST_E_NOSIGNATURE]

I re-ran SURT but that won't work in safe mode:

Windows Update Standalone Installer: 0x8007043c
This service cannot be started in Safe Mode

SFC however did work: "Windows Resource Protection did not find any integrity violations."

tom982 · Feb 14, 2015

The first errors you listed were from previous runs of the SURT and they're no longer an issue. While the SURT hasn't actually fixed them, they're no longer a problem - perhaps the update was removed or another update fixed it. The SURT is usually very reliable at picking up those errors (unlike some others) so if it says they're not an issue then I'm confident that it won't be a problem, but I'll double check the CBS log at the end to make sure.

Good spot on the 0x800b0100 on Package_for_KB976932~31bf3856ad364e35~amd64~~6.1.1.17514.mum, I'd missed that one. We would've picked it up later but you've saved me some time so thanks!

Oh sorry, I completely misunderstood what you said about rebooting. Yeah looks like we're going to have to wait until you can reboot the PC but I'll still be around on Monday so when you've rebooted if you could run the SURT, try to update and post your CheckSUR.persist.log and CBS.log files then that'd be great :)

Tom

moz · Feb 14, 2015

Ok, sounds good.

So I shouldn't do anything about KB976932 now while it's still in safe mode?

If not, I assume once out of safe mode, I'll need to address that, or will SURT give that answer?

The user is actually coming in Sunday, so I'll shut down now if we're done.

tom982 · Feb 15, 2015

Nope, there's nothing left to do for now. When you're out of safe mode, run the SURT and post the logs then we'll be able to assess the problem.

Oh that's great, shut it down and we can continue tomorrow.

moz · Feb 15, 2015

Ok Tom, thanks again for your help. You've been great!

tom982 · Feb 15, 2015

No problem! Happy to help :)

moz · Feb 16, 2015

Okay, here's where we're at:

User logged in today without any messages about "Preparing to configure Windows". After logging in, the icon of the exclamation shield appeared on the Start/Shut down button; "Installs updates and then shuts down your computer".

We did not shut down, instead ran SURT as instructed. SURT found "Hotfix for Windows KB947821". hm.. that KB is SURT, in the flesh. Upon proceeding, it copied packages to the Windows update cache, then sat at "Installing..." for 20mins with 0% on the progress bar. Then it jumped to 100% and disappeared without any message.

Re-ran SURT, progress bar again sat at 0% but moved to 100% quickly (after about a minute), followed by "Installation Complete". Great! Clicked OK and re-ran SURT just to be sure. But again, "Hotfix for Windows KB947821" is available. Not sure if because it can't overwrite itself but I tried again and it sat at "Installing..." for about 5mins, then another "Installation complete".

Decided at this point to run SFC /scannow; right-clicked "Command prompt" from Start menu search, "ran as administrator", but it wouldn't open. Tried again, same thing. Tried non-elevated, worked fine. Tried running elevated directly from windows\system32\cmd.exe, and it opened fine. SFC /scannow completed and found no integrity violations.

Opened Windows Update to see what was waiting:

Logs are attached. Whenever you can, just let me know what's next -- wasn't sure if I should proceed with those updates, or if we're better to wait for the user to reboot given the indication in the beginning by the Start/Shut down button (that updates were already installed before running SURT, and it was waiting for a reboot).

tom982 · Feb 17, 2015

Hi moz,

The SURT isn't a conventional update in the sense that you install it once then you're good to go, think of it more as a tool where you run it every time you need to scan your computer. I know it has a KB number and says it's installing, but IMO this is a poor explanation from Microsoft. It can be 'installed' as many times as you want, so don't be alarmed by what you experienced :)

The logs are all clear now indicating everything should be fixed, so feel free to reboot and see if the updates work. Fingers crossed!

Tom

moz · Feb 17, 2015

Still having a problem with KB2985461 but was able to get through the initial install stage of a handful of others (seen as "Pending"). Based on the list of failed updates just below that, it appears the user may have already attempted this. :banghead:

But unless you have a different plan, I'll wait for them to reboot again and see if the pending updates complete this time. Fingers crossed they do, and will allow me to finally get KB2985461 installed:

tom982 · Feb 17, 2015

I think it's best to try once more, and failing that we can investigate this a little more. Should it fail, can you upload these logs please:

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

Tom

moz · Feb 17, 2015

Okay sir, will do.

And thanks again.

moz · Feb 18, 2015

Hey Tom,

The user got stuck in that "Failure configuring Windows updates" reboot loop again, so these updates are not completing. They said it does the revert/reboot thing 3-4 times before they can login to Windows.

One or several of these KB's have been causing this since late last year, so it's been sitting like this for a while. I'll get those two logs for you once they leave in a couple hours but tell me: do we need safe mode for what's next? I'll need to know that before they leave.

To resolve this, I was going to suggest we select one update at a time and narrow down the culprit(s) -- I don't imagine every one of them requires a reboot. But since this has to be done remotely, I can't throw the user into another reboot loop, especially if it becomes perpetual.

If there's a way to know, can we install any KB's not requiring a reboot? Seems all of these are considered "Important" or "Recommended". If the culprit to this problem is only a "Recommended" update, how bad is it to hide it?

Thanks for all your help with this, hopefully we can conclude things soon!

moz · Feb 18, 2015

Aaand here's round three of the logs. The user has left, and I'm sitting in "normal" (not safe) mode.

If you're around again, let me know what you suggest. For now I've hidden all updates in order to avoid the dreaded loop when they return.

Windows update error 800B0100 (Win7 Pro)

Active member

Attachments

Emeritus

Active member

Attachments

Emeritus

Active member

Active member

Emeritus

Active member

Emeritus

Active member

Emeritus

Active member

Emeritus

Active member

Attachments

Emeritus

Active member

Emeritus

Active member

Active member

Active member

Attachments