Appears to be an Update Problem

glennc · 23 Jun 2015

Hello,
Began a thread in Backup and Restore, in reference to the fact that after the last Windows 7 update I could not backup to an external SATA Hardrive. I found the drive in disk manager and set it to active and gave it a drive letter. It has worked perfectly in the past on this computer. Prior to reactivating it I checked it on my other computers with the USB ports as they don't have the external SATA connector. They saw the drive fine and a chkdsk on the drive was also successful. I ran a System Image with Paragon.
I ran an sfc /scannow for the first time in I don't recall how many months. It failed and indicated corrupted files. I did a system image restore to a point pre-latest updates as I assumed that this might have been the cause. Same sfc failure. Found the forum's SURT and sfc instructions and performed them.
At this time a kind member replied with information about checking the CBS.log for certain updates ( KB3022345 and KB3068708 ). I found similar errors in the log as Dennis indicated and after attempting confirmation from Microsoft, the Tech identified the first as an optional update and the second as Important.
The Tech wanted the updates uninstalled and then reinstalled as part of his troubleshooting. I do not allow remote access.
I did a system restore to the newest version (post latest updates) and uninstalled the KB3022345. sfc still produced the same errors. Rebooted and then I uninstalled the KB3068708 update. I ran the sfc /scannow and it came back clean with no integrity errors! Yay!
Dennis also suggested that I stop and disable the Diagnostic Service Host and the Diagnostic System host with which these updates dealt with.
I am awaiting his reply about the disabling requirement and the Importance of the KB3068708 update in the original thread.
But since it truly appears to be an update problem I wanted to present it in the appropriate area and allow others to see it as an update problem, along with any other suggestions or information that you all might feel are applicable!
Thanks
glennc

NoelDP · 23 Jun 2015

It's very likely that the SFC 'corruptions are in fact a problem with a recent update, where MS mis-coded a pair of files as static when they should have been coded as variable.

Pleasefollow the WindowsUpdate Posting Instructions and postthe requested data

If thefile is too large (8MB compressed), remove the older CBSPersist cab files untilthe final file is below the limit - you can always post them separately afterzipping them. (the forum doesn't allow the upload of bare CAB files, for anumber of reasons)

Pleasealso post the C:\Windows\windowsudpate.log file

glennc · 23 Jun 2015

Howdy NoelDP,
Not really understanding how the CBS.log works, does it matter that I have uninstalled some of the updates? I have one from before I got my system to give me a clean sfc. Which would be better?
glennc

NoelDP · 23 Jun 2015

That doesn't matter - I only need the requested data.

glennc · 23 Jun 2015

Okay, here you go and thanks!

Attachment 363714

WindowsUpdate.zip

glennc

glennc · 23 Jun 2015

Will this possibly address the original issue, not recognizing the external SATA hardrive? Should I reinstall the KB3022345 and KB3068708 Updates?
glennc

NoelDP · 23 Jun 2015

I don't know - until you post ALL the requested data.
we need the latest CBSPersist cab file and the CheckSUR and Filters logs as well.

glennc · 23 Jun 2015

Ahaa Sir,
Misread instructions! Ran the SURT without incidence, ran sfc /scannow, no Windows Error Codes on last update. Okay, the latest CBSperistXXX.cab file is 18,903 KB, zipped. The oldest is 9MB. Unless I am missing something. The rest of the files are here -

Attachment 363724

Don't recognize Filter logs....................
Thank you and let me know what else you might need!
glennc

NoelDP · 24 Jun 2015

Here's the error list from CheckSUR...

Code:

Checking Component Store
(f) CSI Missing Deployment Key 0x00000000 b238d78ab96..82cf8316b9e_31bf3856ad364e35_6.1.7601.18804_5385b5271435d4db HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 f90a84c118a..f442269f912_31bf3856ad364e35_6.1.7601.18804_b965690873110d6b HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 85ac31a8dd9..c93b7d3c6ce_31bf3856ad364e35_6.1.7601.18804_4e0050898b85214c HKLM\Components\CanonicalData\Deployments 
(f) CSI Missing Deployment Key 0x00000000 66b5879f4aa..95d056a9958_31bf3856ad364e35_6.1.7601.18804_a6f2c2c883114848 HKLM\Components\CanonicalData\Deployments 
Summary:
Seconds executed: 1405
 Found 4 errors
  CSI Missing Deployment Key Total count: 4

(I hate missing Component/Deployment Keys!)

I need to have a look at your COMPONENTS registry hive

Please copy the C:\Windows\System32\config\COMPONENTS file (no extension) to your desktop and then compress it - upload the compressed file to your favoured fileshare site (preferably Dropbox or OneDrive) and post a link.

glennc · 24 Jun 2015

Good Day NoelDP,
I do not have an online dropbox or anycloud. The closest thing to what you requested was a "components"
file and it was date coded, today, is that it? Any other way to get at the CBSpersistXXX.cabs ? Arrgh.
How about a system restore to an earlier time and subsequent update to all required and my important data... Since the change? Would you consider your assistance, assuming I can find a way to provide you with the information or the above restore, or a clean Windows 7 Ultimate 64 bit install to be the most completely successful way to clear all and any issues?
Thank you good Sir!
glennc