New
#11
Yes please! this is definitely intriguing.
The oldest CBSPersist file there is 89MB (1.6GB uncompressed)- which is what's causing the bloat.
The CBS.log has the following error in it...
Please find the fileCode:2015-04-24 07:47:57, Info CSI 00000081 Component change list: 2015-04-24 07:47:57, Info CSI 00000082 Couldn't find the hash of component: Microsoft-Windows-IE-InternetExplorer-Optional, Version = 11.2.9600.17728, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the catalog [l:192{96}]"\SystemRoot\WinSxS\Catalogs\8279850e727389f06786a2e520a840ebb7f2a24f18cf3c65c99d80b0a44ede35.cat". 2015-04-24 07:47:57, Error CSI 00000083@2015/4/24:04:47:57.355 (F) d:\win7sp1_gdr\base\wcp\componentstore\csd_winners.cpp(1302): Error 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] originated in function CCSDirectTransaction::AddImplicationsToCatalogsAndVerifyComponentHashes expression: (null) [gle=0x80004005] 2015-04-24 07:47:57, Error CSI 00000084 (F) 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] #89032# from CCSDirectTransaction::PrepareForCommit(...)[gle=0x90092004] 2015-04-24 07:47:57, Error CSI 00000085 (F) 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] #89031# from CCSDirectTransaction::ExamineTransaction(...)[gle=0x90092004] 2015-04-24 07:47:57, Error CSI 00000086 (F) 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] #89030# from CCSDirectTransaction_IRtlTransaction::ExamineTransaction(...)[gle=0x90092004] 2015-04-24 07:47:57, Error CSI 00000087 (F) CRYPT_E_NOT_FOUND #88145# from Windows::COM::CPendingTransaction::IStorePendingTransaction_Analyze(...)[gle=0x80092004] 2015-04-24 07:47:57, Error CSI 00000088 (F) CRYPT_E_NOT_FOUND #85770# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_Commit(Flags = 38 (0x00000026), pSink = NULL, disp = 0, coldpatching = FALSE)[gle=0x80092004] 2015-04-24 07:47:57, Error CSI 00000089 (F) CRYPT_E_NOT_FOUND #85769# 729212 us from Windows::ServicingAPI::CCSITransaction_ICSITransaction::Commit(flags = 0x00000026, pSink = NULL, disp = 0) [gle=0x80092004] 2015-04-24 07:47:57, Error CBS Exec: Failed to commit CSI transaction to resolve execution chain. [HRESULT = 0x80092004 - CRYPT_E_NOT_FOUND] 2015-04-24 07:47:57, Info CSI 0000008a@2015/4/24:04:47:57.395 CSI Transaction @0x28a1a0 destroyed 2015-04-24 07:47:57, Info CBS Perf: Resolve chain complete. 2015-04-24 07:47:57, Info CBS Failed to resolve execution chain. [HRESULT = 0x80092004 - CRYPT_E_NOT_FOUND] 2015-04-24 07:47:57, Error CBS Failed to process single phase execution. [HRESULT = 0x80092004 - CRYPT_E_NOT_FOUND] 2015-04-24 07:47:57, Info CBS WER: Generating failure report for package: Package_for_KB3038314~31bf3856ad364e35~amd64~~11.2.1.0, status: 0x80092004, failure source: Resolve, start state: Absent, target state: Staged, client id: WindowsUpdateAgent
C:\Windows\WinSxS\Catalogs\8279850e727389f06786a2e520a840ebb7f2a24f18cf3c65c99d80b0a44ede35.cat
double-click on it and it should open the Catalog. If not, then we know where the problem is
Both CheckSUR and SFC scans are clear of errors.
Last edited by NoelDP; 24 Apr 2015 at 03:37. Reason: typo
Try copying this into the Address bar in Windows Explorer....
C:\Windows\WinSxS\Catalogs\8279850e727389f06786a2e520a840ebb7f2a24f18cf3c65c99d80b0a44ede35.cat
if you then hit the Enter key, it should just open the file - or say 'Not found'
Not sure - yet!
It's the 'master' catalog file for all the files involved in the update, I think, which tells Windows the file sizes to expect from an update.
It seems that for whatever reason this file isn't where it's expected to be, either because the file itself hasn't been put there, or it's been misnamed. The question then becomes how to fix it.
I think the first thing to do is to delete the source files and re-download them...
This could be due to corruption in the SoftwareDistribution folder - the problem with that the conventional cure can lead to problems later on, if not handled properly, and you will lose your Update history (but the updates will still be installed, and viewable in the Installed Updates listing).
Open an Elevated Command Prompt
Run the following commands
NET STOP WUAUSERV
REN C:\WINDOWS\SoftwareDistribution SDOLD
NET START WUAUSERV
reboot
then wait 10 minutes, and open Windows Updates, and run a Check for Updates.
Install only the oldest update found - and reboot once installed
then go back to Windows updates and install the others.
Maybe I don't need to do anything after all:
IE11 patch KB 3038314 blocks search engines and may fail with error 80092004 | InfoWorld
It appears like it's a corrupt update , which has already caused problems for a lot more users.
Interesting article - I hadn't seen that (or heard of the problems) before.
I'll do some research over the weekend.