Hi Jills,
That's great news! Thanks for posting back the results. I'll explain all of the errors for you:
Code:
(f) CSI Payload File Missing 0x00000000 msado25.tlb amd64_microsoft-windows-m..do-backcompat-tlb25_31bf3856ad364e35_6.1.7601.17514_none_490721c608dddcf4 (f) CSI Payload File Missing 0x00000000 msado15.dll x86_microsoft-windows-m..ents-mdac-ado15-dll_31bf3856ad364e35_6.1.7601.17514_none_0e384c71cee8c9e1
The first two mean that files are missing from your system - solution: replace these files. I performed this fix with SFCFix and these files now exist on your computer.
C:\Windows\winsxs\amd64_microsoft-windows-m..do-backcompat-tlb25_31bf3856ad364e35_6.1.7601.17514_none_490721c608dddcf4\msado25.tlb
C:\Windows\winsxs\x86_microsoft-windows-m..ents-mdac-ado15-dll_31bf3856ad364e35_6.1.7601.17514_none_0e384c71cee8c9e1\msado15.dll
The remaining errors are all due to registry corruption. The file that you uploaded for me is known as your COMPONENTS registry hive and it is where most of the information about Windows Update is stored. If something goes wrong here then Windows Update will probably fail, like it did here.
Code:
(f) CSI Corrupt Identity 0xC0150017 Microsoft-Windows-Microsoft-Data-Access-Components-(MDAC)-SQL-NetLibs-NP, ulture=neutral, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS amd64_microsoft-windows-m..mdac-sql-netlibs-np_31bf3856ad364e35_6.1.7600.16385_none_4aF0e0ac9428f959 Bad identity
In your COMPONENTS hive there is a subkey called \DerivedData\Components and details the information about the core Windows files on your computer - versions, languages etc. In each subkey of this, a component will have a value called Identity which is a little information about the component. The identity is actually printed in the error above:
Code:
Microsoft-Windows-Microsoft-Data-Access-Components-(MDAC)-SQL-NetLibs-NP, ulture=neutral, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS
It takes the form: {Parent Package (ie where the file came from)}, {locale (the language of the component, if necessary. In this case it isn't language specific}, {Version}, {Public Key of component}, {Architecture of component: 32 bit or 64 bit}, {I have no idea what this means}
The CheckSUR log said this key has a CSI Corrupt Identity and also says Bad identity at the end of the log line. So we know this is corrupt, but where? Well you might have spotted the ulture=neutral in the middle of the identity - this should in fact read, Culture=neutral. What has happened here is known as a bitflip - where one binary bit has flipped from a 0 to a 1 or vice versa. There is actually a character before that u but you can't see it, it is 05 in hex which has no character equivalent. If we look at the binary for each character they should be fairly similar:
The hidden character: 00000101
c: 01000011
Bitflips are usually one or two bits flipping but here we actually have 3 that have flipped. It is rare, but not impossible. To fix this I loaded your COMPONENTS hive in regedit, then just renamed the identity to correct this.
Code:
(f) CSI Manifest Missing 0x00000002 amd64_microsoft-windows-m..mdac-sql-netlibs-np_31bf3856ad364e35_6.1.7600.16385_none_4aF0e0ac9428f959.manifest amd64_microsoft-windows-m..mdac-sql-netlibs-np_31bf3856ad364e35_6.1.7600.16385_none_4aF0e0ac9428f959
This error is somewhat related to the error before as it is about the same component. When missing manifest errors occur in logs it means one of two things: the manifest is missing or the SURT can't find it. As the component name above has a capital letter in it: 4aF0e0ac9428f959 when it should all be lower case, I suspected the latter. When I looked at the registry I found there was another very similar key named:
amd64_microsoft-windows-m..mdac-sql-netlibs-np_31bf3856ad364e35_6.1.7600.16385_none_4ad0e0ac9428f959
I have been dealing with corruption like this for a while now and recognised this instantly. When a key gets corrupt and changes name, like it did here, Windows will attempt to rebuild the key but it will always miss out one crucial bit of data, the S256H value. So all I had to do to fix this was copy the S256H value from the corrupt key name into the correct key, then delete the corrupt key.
Code:
(f) CSI Corrupt Identity 0xC0150017 Microsoft-Windows-Microsoft-Data-ACcess-Components-(MDAC)-RDS-Handler, Culture=neutral, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitec2ure=x86, versionScope=NonSxS x86_microsoft-windows-m..ts-mdac-rds-handler_3ubf3856ad364e35_6.1.7600.16385_none_4fa991419452cee2 Bad identity
Another bitflip: ProcessorArchitec2ure
This should be: ProcessorArchitecture
2: 00110010
t: 01110100
Strangely, another 3 bits have flipped here. To fix this I just renamed it, like the one before :)
Code:
(f) CSI Manifest Missing 0x00000002 x86_microsoft-windows-m..ts-mdac-rds-handler_3ubf3856ad364e35_6.1.7600.16385_none_4fa991419452cee2.manifest x86_microsoft-windows-m..ts-mdac-rds-handler_3ubf3856ad364e35_6.1.7600.16385_none_4fa991419452cee2
Exactly the same as the last missing manifest.
The key name is: x86_microsoft-windows-m..ts-mdac-rds-handler_3ubf3856ad364e35_6.1.7600.16385_none_4fa991419452cee2
When it should be: x86_microsoft-windows-m..ts-mdac-rds-handler_31bf3856ad364e35_6.1.7600.16385_none_4fa991419452cee2
So I copied over the S256H value and deleted the corrupt key.
Code:
(f) CSI Corrupt Component Keyform 0x00000000 identity x86_miCrosoft-windows-n..ssprotection-client_31bf3856ad364e35_6.1.7600.16385_none_f7338b129465ce6c identity and keyform do not match; keyform is wrong.
The Corrupt Component Keyform error means that the identity and the key name don't match. At the end of the line it says keyform is wrong so we know the key is named wrongly. This is another bitflip.
What it is: x86_miCrosoft-windows-n..ssprotection-client_31bf3856ad364e35_6.1.7600.16385_none_f7338b129465ce6c
What it should be: x86_microsoft-windows-n..ssprotection-client_31bf3856ad364e35_6.1.7600.16385_none_f7338b129465ce6c
This is a very common, and very sneaky bitflip as the letter has bitflipped to the capital of that letter.
C: 01000011
c: 01100011
Solution, rename the key to the correct name :)
Your CheckSUR log is reporting a few missing packages which I've never seen before in my life!
Code:
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 18.0
2013-05-18 02:36
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x80070026 servicing\Packages\PA7C9F~1.MUM Line 1: X¡
(f) CBS Catalog Missing 0x00000002 servicing\Packages\PA7C9F~1.cat
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
Summary:
Seconds executed: 3159
Found 2 errors
CBS MUM Corrupt Total count: 1
CBS Catalog Missing Total count: 1
Unavailable repair files:
servicing\packages\PA7C9F~1.mum
servicing\packages\PA7C9F~1.mum
servicing\packages\PA7C9F~1.cat
servicing\packages\PA7C9F~1.cat
System Look
Please download SystemLook from one of the links below and save it to your Desktop.
- Double-click SystemLook.exe to run it.
- Copy the content of the following codebox into the main textfield:
- Click the Look button to start the scan.
- When finished, a notepad window will open with the results of the scan. Please post this log in your next reply.
Note: The log can also be found on your Desktop entitled SystemLook.txt
Tom
Quote
found in your system tray (next to the time). If you are still having issues locating this folder, unless otherwise specified, it can be found under this location: C:\Users\{Your username}\Dropbox
file in your Public folder.
button and in the search box, type Command Prompt