New
#11
I think I see at least some of the problem - back in a bit...
I've uploaded a file - bbsac.zip - to my OneDrive at Noel's OneDrive
Please download and save it to your desktop.
Right-click on the file and select Extract All, and save to the default destination (which should be a folder on the desktop)
Create a new System Restore point
Open an Elevated Command Prompt, and run the following commands.
REN C:\Windows\System32\config\COMPONENTS COMPONENTS.OLD3
COPY %userprofile%\desktop\bbsac\COMPONENTS C:\Windows\System32\config
If you get an error with either command, STOP THERE - do not reboot! - post for instructions.
Assuming both commands go OK, reboot, and run another CheckSUR scan - post the new CheckSUR.log file.
Hi Noel.
I followed your latest instructions and have uploaded the most recent log files here: https://app.box.com/shared/static/xo...lpm0bqzduq.zip
Thank you!
WOW!...
That's gotta be a record.Code:Summary: Seconds executed: 502 Found 41891 errors Fixed 41381 errors CSI Catalog Missing Total count: 7 Fixed: CSI Catalog Missing. Total count: 7 CSI Missing Component Key Total count: 6223 Fixed: CSI Missing Component Key. Total count: 6223 CSI Missing Pinned Component Key Total count: 4681 Fixed: CSI Missing Pinned Component Key. Total count: 4681 CSI Corrupt Deployment Keyform Total count: 1 CSI Missing Identity Total count: 11413 Fixed: CSI Missing Identity. Total count: 10904 CSI Missing C Mark Total count: 12119 Fixed: CSI Missing C Mark. Total count: 12119 CSI F Mark Missing Total count: 12128 Fixed: CSI F Mark Missing. Total count: 12128
With the size of the CheckSUR log, I don't have much chance of isolating the remaining problems - please run it again, this time it'll only find the remaining errors, and I'll see what's what then - post just the CheckSUR.log file
Latest CheckSUR log file has been uploaded here: https://app.box.com/shared/static/2q...cish3tw84h.log
Thank you again Noel for all of your help in dealing with this! I really appreciate it!
Here's the errors from the report...
I need to see the latest version of the COMPONENTS registry hive again - there will have been massive changes since the last upload..Code:Checking Component Store (f) CSI Missing Identity 0x00000000 appid 6a8fcb690db..8d0ba1e04cf_31bf3856ad364e35_6.1.7601.22653_ef68be9025bdf54e (f) CSI Missing Identity 0x00000000 appid 967b65312c0..edc10558113_31bf3856ad364e35_11.2.9600.16521_ffb9abd47b907fbd (f) CSI Corrupt Deployment Keyform 0x00000000 appid 21f12e9d52d..f90f7f0b807_31bf3856ad364es5_6.1.7601.22296_f3e6c00561fc7bbd appid and keyform do not match; keyform is wrong.
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.
Latest version of the COMPONENTS registry hive: https://app.box.com/shared/static/7v...40i98l3f3s.zip
I think I've fixed one of the errors, at least...
I've uploaded a file - bbsad.zip - to my OneDrive at Noel's OneDrive
Please download and save it to your desktop.
Right-click on the file and select Extract All, and save to the default destination (which should be a folder on the desktop)
Create a new System Restore point
Open an Elevated Command Prompt, and run the following commands.
DEL C:\Windows\System32\config\COMPONENTS.OLD*
REN C:\Windows\System32\config\COMPONENTS COMPONENTS.OLD
COPY %userprofile%\desktop\bbsad\COMPONENTS C:\Windows\System32\config
If you get an error with either command, STOP THERE - do not reboot! - post for instructions.
Assuming both commands go OK, reboot, and run another CheckSUR scan - post the new CheckSUR.log file.
(that should clear up the older non-functional hives :))
Hi Noel.
I completed the instructions as requested. I ran CheckSUR a few times and I've uploaded the latest log file here: https://app.box.com/shared/static/0e...95y3ozx1vm.log
Because it updated some registry values, I've also uploaded the most recent COMPONENTS file here: https://app.box.com/shared/static/2d...gpitx4n5b5.zip
There is no point (usually) in running any diagnostic tool more than once - it can in fact be counterproductive.
That said, I'll have a look, and see what I can find.