Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Win7 home premium 64bit update fails, error 8007370B


16 May 2013   #1

Windows 7 Home Premium 64bit SP1
 
 
Win7 home premium 64bit update fails, error 8007370B

Hi Folks,

My Windows 7 home premium 64bit SP1 has failed to update since 2012. Every time I tried, the system update ended up with error code 8007370B: Windows Update encountered an unknown error.

I have followed the steps at

Windows Update Posting Instructions

and installed the SURT.

It installed correctly but did not solve the problem, still the same error code: 8007370B.

I have also tried running sfc /scannow in an elevated cmd, but it failed with the following output:
C:\windows\system32>sfc /scannow

Beginning system scan. This process will take some time.


Windows Resource Protection could not perform the requested operation.

Attached is my CBS.zip and windows update error screenshot. I want to point out that I have installed several versions of SURT from 2012 till now, none of which fixed the problem, but may have generated some logs to CBS.


Thanks for any possible solutions.




Attached Thumbnails
Win7 home premium 64bit update fails, error 8007370B-update_error.png  
Attached Files
File Type: zip CBS.zip (2.75 MB, 4 views)
My System SpecsSystem Spec
.

16 May 2013   #2

Windows 7 Ultimate 32-Bit & Windows 7 Ultimate 64-Bit
 
 

See if you could use SFC /scannow during boot

SFC /SCANNOW : Run in Command Prompt at Boot
My System SpecsSystem Spec
16 May 2013   #3

Microsoft Community Contributor Award Recipient

Windows 8.1 Pro x64
 
 

Hello Jills, welcome to the forums

Your CheckSUR log has shown a bit of registry corruption:


Code:
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 18.0
2013-05-16 00:13


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs
(f)    CBS MUM Corrupt    0x80070026    servicing\Packages\PA7C9F~1.MUM        Line 1: X9
(f)    CBS Catalog Missing    0x00000002    servicing\Packages\PA7C9F~1.cat        


Checking Package Watchlist


Checking Component Watchlist


Checking Packages


Checking Component Store
(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    
(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
(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    
(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
(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    
(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.


Summary:
Seconds executed: 758
 Found 9 errors
  CSI Manifest Missing Total count: 2
  CSI Corrupt Component Keyform Total count: 1
  CSI Corrupt Identity Total count: 2
  CSI Payload File Missing Total count: 2
  CBS MUM Corrupt Total count: 1
  CBS Catalog Missing Total count: 1


Unavailable repair files:
    winsxs\manifests\amd64_microsoft-windows-m..mdac-sql-netlibs-np_31bf3856ad364e35_6.1.7600.16385_none_4aF0e0ac9428f959.manifest
    winsxs\manifests\x86_microsoft-windows-m..ts-mdac-rds-handler_3ubf3856ad364e35_6.1.7600.16385_none_4fa991419452cee2.manifest
    servicing\packages\PA7C9F~1.mum
    servicing\packages\PA7C9F~1.mum
    servicing\packages\PA7C9F~1.cat
    servicing\packages\PA7C9F~1.cat
In order to fix this, I will have to manually edit one of your registry hives so it would be great if you could upload this for me please:


Upload a file to Dropbox


Note: If you prefer, the same techniques can be applied to your Skydrive however these instructions may not necessarily work for Skydrive.
  1. If you haven't already created a Dropbox account, please do so Here
  2. Although this procedure can be done directly through the website, it is much easier to do so via the Windows client which can be downloaded from the Dropbox website:


    https://www.dropbox.com/install
  3. After you have downloaded and installed that, you should now see Dropbox in your Favourites box in Windows Explorer. This is the folder that will be synchronised with the Dropbox servers, anything that you wish to back up online can be put in here, but today we will be using it to transfer files.





  4. To access your Dropbox folder, just click on the link in the top left hand corner of Windows Explorer (accessible from any location - Documents etc.). Alternatively, you can double click on the icon 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
  5. Copy all of the following files to the Public folder in your Dropbox:
    • C:\Windows\system32\config\components (it has no file extension)
  6. Select all files by pressing Ctrl+A then right-click and select Send to > Compressed (zipped) folder
  7. This will create a .zip file in your Public folder.
  8. Right-click on this file and select Dropbox > Copy Public Link then Paste (Ctrl + V) this link into your next post for me please


Tom
My System SpecsSystem Spec
.


16 May 2013   #4

Microsoft Community Contributor Award Recipient

Windows 8.1 Pro x64
 
 

Quote   Quote: Originally Posted by VistaKing View Post
See if you could use SFC /scannow during boot

SFC /SCANNOW : Run in Command Prompt at Boot
It will definitely fail again The CBS log shows the same problems as the CheckSUR:


Code:
2013-05-13 00:08:50, Error                 CSI    00000005 (F) Invalid attribute name found: [l:14{7}]"ulture"[gle=0x80004005]
2013-05-13 00:08:50, Error                 CSI    00000006@2013/5/13:07:08:50.769 (F) d:\win7sp1_gdr\base\wcp\identity\id_baseidentity.cpp(1263): Error STATUS_SXS_INVALID_IDENTITY_ATTRIBUTE_NAME originated in function Windows::Identity::Rtl::Implementation::CRtlIdentityBase::CRtlIdentityBase_Initialize expression: pBAI != 0
[gle=0x80004005]
2013-05-13 00:08:51, Error                 CSI    00000007 (F) STATUS_SXS_INVALID_IDENTITY_ATTRIBUTE_NAME #408036# from Windows::Identity::Rtl::Implementation::CRtlIdentityAuthority::IRtlIdentityAuthority_Parse(flags = 0, string = [l:392{196}]"Microsoft-Windows-Microsoft-Data-Access-Components-(MDAC)-SQL-NetLibs-NP, ulture=neutral, Version=6.1.7600.16385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS")
[gle=0xd0150017]
2013-05-13 00:08:51, Info                  CBS    NonStart: Failed to get store. [HRESULT = 0x8007370b - ERROR_SXS_INVALID_IDENTITY_ATTRIBUTE_NAME]
2013-05-13 00:08:51, Info                  CBS    Failed to ensure no startup processing was required. [HRESULT = 0x8007370b - ERROR_SXS_INVALID_IDENTITY_ATTRIBUTE_NAME]
2013-05-13 00:08:51, Info                  CBS    Failed during startup processing, continuing with Trusted Installer execution [HRESULT = 0x8007370b - ERROR_SXS_INVALID_IDENTITY_ATTRIBUTE_NAME]

The registry corruption has invalidated a registry value and now SFC can't find it. Until we fix the registry, SFC won't be able to do a thing


Tom
My System SpecsSystem Spec
16 May 2013   #5

Windows 7 Ultimate 32-Bit & Windows 7 Ultimate 64-Bit
 
 

Thanks Tom for the heads up .
My System SpecsSystem Spec
17 May 2013   #6

Windows 7 Home Premium 64bit SP1
 
 

Quote   Quote: Originally Posted by tom982 View Post
Hello Jills, welcome to the forums

Your CheckSUR log has shown a bit of registry corruption:


Code:
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 18.0
2013-05-16 00:13


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs
(f)    CBS MUM Corrupt    0x80070026    servicing\Packages\PA7C9F~1.MUM        Line 1: X9
(f)    CBS Catalog Missing    0x00000002    servicing\Packages\PA7C9F~1.cat        


Checking Package Watchlist


Checking Component Watchlist


Checking Packages


Checking Component Store
(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    
(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
(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    
(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
(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    
(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.


Summary:
Seconds executed: 758
 Found 9 errors
  CSI Manifest Missing Total count: 2
  CSI Corrupt Component Keyform Total count: 1
  CSI Corrupt Identity Total count: 2
  CSI Payload File Missing Total count: 2
  CBS MUM Corrupt Total count: 1
  CBS Catalog Missing Total count: 1


Unavailable repair files:
    winsxs\manifests\amd64_microsoft-windows-m..mdac-sql-netlibs-np_31bf3856ad364e35_6.1.7600.16385_none_4aF0e0ac9428f959.manifest
    winsxs\manifests\x86_microsoft-windows-m..ts-mdac-rds-handler_3ubf3856ad364e35_6.1.7600.16385_none_4fa991419452cee2.manifest
    servicing\packages\PA7C9F~1.mum
    servicing\packages\PA7C9F~1.mum
    servicing\packages\PA7C9F~1.cat
    servicing\packages\PA7C9F~1.cat
In order to fix this, I will have to manually edit one of your registry hives so it would be great if you could upload this for me please:


Upload a file to Dropbox


Note: If you prefer, the same techniques can be applied to your Skydrive however these instructions may not necessarily work for Skydrive.
  1. If you haven't already created a Dropbox account, please do so Here
  2. Although this procedure can be done directly through the website, it is much easier to do so via the Windows client which can be downloaded from the Dropbox website:


    https://www.dropbox.com/install
  3. After you have downloaded and installed that, you should now see Dropbox in your Favourites box in Windows Explorer. This is the folder that will be synchronised with the Dropbox servers, anything that you wish to back up online can be put in here, but today we will be using it to transfer files.





  4. To access your Dropbox folder, just click on the link in the top left hand corner of Windows Explorer (accessible from any location - Documents etc.). Alternatively, you can double click on the icon 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
  5. Copy all of the following files to the Public folder in your Dropbox:
    • C:\Windows\system32\config\components (it has no file extension)
  6. Select all files by pressing Ctrl+A then right-click and select Send to > Compressed (zipped) folder
  7. This will create a .zip file in your Public folder.
  8. Right-click on this file and select Dropbox > Copy Public Link then Paste (Ctrl + V) this link into your next post for me please


Tom
Hi Tom,

Thanks and the dropbox link to my components.zip file is:
https://www.dropbox.com/s/gms1bamk6b...COMPONENTS.zip
My System SpecsSystem Spec
17 May 2013   #7

Microsoft Community Contributor Award Recipient

Windows 8.1 Pro x64
 
 

Hi Jills,

Thanks for uploading your COMPONENTS hive, I've managed to fix all of the corruption manually so all that's left to do now is to replace your current hive with this one.

Download this file please: https://dl.dropboxusercontent.com/u/...COMPONENTS.zip

Extract the contents to your Desktop, there should be one file named components.

Then navigate to C:\Windows\system32\config

And rename the file components to components.bak.

Then copy and paste the components file on your Desktop to this folder. Reboot and try updating again.

If, at any point, you are displayed an error saying the file is in use, or access denied, reboot and try again.

SFCFix Script


Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a files should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl + C) and Paste (Ctrl + V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.
https://dl.dropboxusercontent.com/u/...lls/SFCFix.zip

Command Prompt


Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each


    regedit /e %SYSTEMDRIVE%\tom982.txt "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages"


  4. This will create a text file called tom982.txt in the root folder of your main drive (e.g. C:\tom982.txt). Please copy and paste the contents of this into your next post.


Then re-run the System Update Readiness Tool (SURT) and post the log please:

C:\Windows\Logs\CBS\CheckSUR.persist.log


Tom
My System SpecsSystem Spec
18 May 2013   #8

Windows 7 Home Premium 64bit SP1
 
 

Quote   Quote: Originally Posted by tom982 View Post
Hi Jills,

Thanks for uploading your COMPONENTS hive, I've managed to fix all of the corruption manually so all that's left to do now is to replace your current hive with this one.

Download this file please: https://dl.dropboxusercontent.com/u/...COMPONENTS.zip

Extract the contents to your Desktop, there should be one file named components.

Then navigate to C:\Windows\system32\config

And rename the file components to components.bak.

Then copy and paste the components file on your Desktop to this folder. Reboot and try updating again.

If, at any point, you are displayed an error saying the file is in use, or access denied, reboot and try again.

SFCFix Script




Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a files should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl + C) and Paste (Ctrl + V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.
https://dl.dropboxusercontent.com/u/...lls/SFCFix.zip

Command Prompt


Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each


    regedit /e %SYSTEMDRIVE%\tom982.txt "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages"


  4. This will create a text file called tom982.txt in the root folder of your main drive (e.g. C:\tom982.txt). Please copy and paste the contents of this into your next post.
Then re-run the System Update Readiness Tool (SURT) and post the log please:

C:\Windows\Logs\CBS\CheckSUR.persist.log


Tom

Hi Tom,

Your COMPONENTS.zip fixed the update problem: after replacing the old COMPONENTS and rebooting, windows update found 100+ updates and installed them correctly. Thank you very much! Btw, really curious how you did it.

I also ran the SFCFix, executed the cmd commands, and reinstalled the SURT.

The content of the SFCFix.txt is as follows:
Code:
 
SFCFix version 1.5.2.0 by niemiro.
Start time: 2013-05-18 09:26:36.660
Using .zip script file at C:\Users\Jills\Desktop\Windows 7 update fix\SFCFix.zip
 
 
PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-m..do-backcompat-tlb25_31bf3856ad364e35_6.1.7601.17514_none_490721c608dddcf4
Successfully took permissions for file or folder C:\Windows\winsxs\x86_microsoft-windows-m..ents-mdac-ado15-dll_31bf3856ad364e35_6.1.7601.17514_none_0e384c71cee8c9e1
Successfully copied file \\?\C:\Users\Jills\AppData\Local\niemiro\Archive\msado25.tlb to \\?\C:\Windows\winsxs\amd64_microsoft-windows-m..do-backcompat-tlb25_31bf3856ad364e35_6.1.7601.17514_none_490721c608dddcf4\msado25.tlb.
Successfully copied file \\?\C:\Users\Jills\AppData\Local\niemiro\Archive\msado15.dll to \\?\C:\Windows\winsxs\x86_microsoft-windows-m..ents-mdac-ado15-dll_31bf3856ad364e35_6.1.7601.17514_none_0e384c71cee8c9e1\msado15.dll.
Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-m..do-backcompat-tlb25_31bf3856ad364e35_6.1.7601.17514_none_490721c608dddcf4
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-m..do-backcompat-tlb25_31bf3856ad364e35_6.1.7601.17514_none_490721c608dddcf4
Successfully restored ownership for C:\Windows\winsxs\x86_microsoft-windows-m..ents-mdac-ado15-dll_31bf3856ad364e35_6.1.7601.17514_none_0e384c71cee8c9e1
Successfully restored permissions on C:\Windows\winsxs\x86_microsoft-windows-m..ents-mdac-ado15-dll_31bf3856ad364e35_6.1.7601.17514_none_0e384c71cee8c9e1
PowerCopy:: directive completed successfully.
 
 
Successfully processed all directives.
SFCFix version 1.5.2.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2013-05-18 09:26:37.883
----------------------EOF-----------------------

tom982.txt and CheckSUR.persist are both attached.

Thank you!


Attached Files
File Type: zip tom982.zip (105.2 KB, 1 views)
File Type: zip CheckSUR.persist.log.zip (2.4 KB, 1 views)
My System SpecsSystem Spec
18 May 2013   #9

Microsoft Community Contributor Award Recipient

Windows 8.1 Pro x64
 
 

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.
Download Mirror #1
  • Double-click SystemLook.exe to run it.
  • Copy the content of the following codebox into the main textfield:
    Code:
    :regfind
    PA7C9F
  • 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
My System SpecsSystem Spec
18 May 2013   #10

Windows 7 Home Premium 64bit SP1
 
 

Hi Tom,

Thank you for the detailed explanations, really appreicate it.

Do you know why/how those bit flips happened?

I have run the SystemLook and the results are:

Code:
 
SystemLook 30.07.11 by jpshortstuff
Log created at 13:48 on 18/05/2013 by Jills
Administrator - Elevation successful
========== regfind ==========
Searching for "PA7C9F"
No data found.
-= EOF =-
My System SpecsSystem Spec
Reply

 Win7 home premium 64bit update fails, error 8007370B




Thread Tools



Similar help and support threads for2: Win7 home premium 64bit update fails, error 8007370B
Thread Forum
Windows 7 Professional 64bit Update Error Code 8007370B Windows Updates & Activation
Solved Windows Update Error Code 8007370B (Win 7 Professional 64bit) Windows Updates & Activation
Solved Windows 7 Home Premium 64bit Update Error Windows Updates & Activation
Win7 home update fails, error 8007370B - cannot update, install SP1. Windows Updates & Activation
win7 home premium 64bit sp1 OEM to home prem. retail fam pack ugrade Installation & Setup
Win7 32bit Home Premium to Win7 64bit Ultimate: Possible without Clean Installation & Setup
Upgrade from Win7 Home Premium 64bit to Win7 Ultimate General Discussion

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 01:42 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33