New
#11
CBS logs
CBS logs
Hmmm - both SFC and CheckSUR appear clear.
in the background of the CBS.log, though are errors such as this...
The only times I've actually seen this error before, it was connected with KB3004394 being installed.Code:2015-01-12 08:31:57, Info CBS Plan: Package: Package_1_for_KB3025390~31bf3856ad364e35~amd64~~11.2.1.0, Update: 3025390-1_neutral_GDR, current: Resolved, pending: Default, start: Resolved, applicable: Installed, targeted: Staged, limit: Staged, selected: Default 2015-01-12 08:31:57, Info CBS Perf: Resolve chain started. 2015-01-12 08:31:57, Info CSI 0000000b@2015/1/12:13:31:57.980 CSI Transaction @0xe20d80 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000002 and client id [79]"TI1.30420588_588261301:2/Package_for_KB3025390~31bf3856ad364e35~amd64~~11.2.1.0" 2015-01-12 08:31:57, Info CBS Failed call to CryptCATAdminAddCatalog. [HRESULT = 0x800706f7 - RPC_X_BAD_STUB_DATA] 2015-01-12 08:31:57, Info CBS Failed to install catalog file \\?\C:\Windows\SoftwareDistribution\Download\c0a10c451f03ed1382d49cca6b8029be\update.cat for package [HRESULT = 0x800706f7 - RPC_X_BAD_STUB_DATA] 2015-01-12 08:31:57, Info CBS Failed to install catalog for package: Package_for_KB3025390~31bf3856ad364e35~amd64~~11.2.1.0 [HRESULT = 0x800706f7 - RPC_X_BAD_STUB_DATA] 2015-01-12 08:31:57, Info CBS Failed to stage package manifest. [HRESULT = 0x800706f7 - RPC_X_BAD_STUB_DATA] 2015-01-12 08:31:57, Info CBS Failed to add package. [HRESULT = 0x800706f7 - RPC_X_BAD_STUB_DATA] ... etc.
Please download the KB3024777 'patch' from Download Update for Windows 7 and Windows Server 2008 R2 for x64-based Systems (KB3024777) from Official Microsoft Download Center and run it - what happens?
Nothing happens when I run that patch even as Administrator.
In that case, I have no idea where to start
probably a full reset of WIndows Update is the first thing to try - Windows Update - Reset
Ran BAT for option 1. Now running Windows Updates. I will let you know what happens.
same failure
Unfortunately, that also didn't allow the update to run. Any other ideas? I'm at a total loss and am not frequently stumped.
Please post the new windowsupdate.log file and I'll see if anything springs out at me - otherwise we may be looking at a repair install
log