[SOLVED] Windows update fails to install KB2809289 with error 80073712

[fralken]

Hello,
I have Windows 7 Ultimate x64 and I'm not able to install recent updates for IE9, KB2792100.
Since this one was superceded by KB2809289 I tried installing it but failed with error 80073712.
Then I tried installing IE10, both via Windows Update and Standalone installer but failed as well (I can't remember error code).
All other updates appear to install correctly.
For now I had to hide these updates otherwise the system tries updating them at every shutdown.
Is there a solution other than recovering the system?
Thank you very much for your help.
fralken

 

[tom982]

Hello fralken, welcome to Sysnative!

Could you post your CBS log for me please:

Export CBS.log

1. Click on the Start
   
   button and then click Computer
2. Double click on the C: drive, under the Hard Disk Drives category, and then scroll down to, and double click on the Windows folder
3. Find and double click on the Logs folder, and then inside that folder, the CBS folder
4. Right-click on the CBS.log file, and select Copy. It may show as just CBS (without the .log extension). Do not be concerned, and proceed to copy the file.
5. Go back to your Desktop, right-click on it, and select Paste. You should now see a file on your Desktop called CBS(.log)
6. Right-click on this file again, and navigate through Send to, and select Compressed (zipped) folder
7. Another new file, also called CBS, but this time with a different icon, will be created. Please upload this new file to the forum, here

Tom

 

[fralken]

Here it is the CBS.log
Thank you

 

[tom982]

Hi fralken,

Your CBS log is showing some registry corruption so I would like to take a further look into that.

2013-03-25 22:38:36, Info                  CSI    00000012@2013/3/25:21:38:36.989 CSI Transaction @0x32aaa0 destroyed
2013-03-25 22:38:36, Error                 CSI    00000013@2013/3/25:21:38:36.989 (F) d:\win7sp1_gdr\base\wcp\componentstore\installmap.cpp(620): Error STATUS_SXS_COMPONENT_STORE_CORRUPT originated in function InstallMap::CRawInstallMap::GetComponentWinningVersion expression: (null)
[gle=0x80004005]
2013-03-25 22:38:37, Error                 CSI    00000014 (F) HRESULT_FROM_WIN32(14098) #9410# from Windows::ServicingAPI::CCSITransactionAnalysis_ICSIInventory::GetComponentInstalledVersions(flags = 0, cAssemblies = 1)
[gle=0x80073712]
2013-03-25 22:38:37, Info                  CBS    Failed to get the current component winner [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2013-03-25 22:38:37, Info                  CBS    Failed to get component installed versions, component: x86_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_8.0.7601.17608_none_64742e7661bc885d [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2013-03-25 22:38:37, Info                  CBS    Failed to determine whether the udpate will be superseded: 2530548-13_neutral_GDR [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2013-03-25 22:38:37, Error                 CBS    Failed to call external evaluate applicability on package: Package_3_for_KB2530548~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2530548-13_neutral_GDR [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2013-03-25 22:38:37, Info                  CBS    Failed to evaluate external applicability for package update: 2530548-143_neutral_PACKAGE [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2013-03-25 22:38:37, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2530548_SP1~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2530548-143_neutral_PACKAGE [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2013-03-25 22:38:37, Info                  CBS    Failed to evaluate external applicability for package update: 2530548-150_neutral_PACKAGE [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2013-03-25 22:38:37, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2530548~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2530548-150_neutral_PACKAGE [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]

Export registry as hive

1. Click on the Start
   
   button and in the search box, type regedit.
2. When you see regedit on the list, right-click on it and select Run as administrator.
3. When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.
   
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide
   
   
4. Once selected, click File > Export....
5. Change the Save as type: to Registry Hive Files (*.*).
6. Name this file SideBySide (with no file extension) and save it to your Desktop.

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:\Users\{Your Username}\Desktop\SideBySide (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

 

[fralken]

Here it is:
https://dl.dropbox.com/u/5187827/SideBySide.zip

 

[tom982]

Hi fralken,

That's perfect, thank you. It's getting late here and I have an early start tomorrow so I'm going to have to call it a day now but I'll get back to you tomorrow :)

Tom

 

[fralken]

Hello Tom,
have you found anything for this problem?
Thanks
fralken

 

[tom982]

Hi Fralken,

Sorry for the delay! It's been a very busy weekend. I need a little bit more information before I can go ahead with a fix:

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 C:\tom982.reg "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing"
   
   
4. This will create a text file called tom982.reg in the root folder of your main drive (e.g. C:\tom982.reg). Please copy and paste the contents of this into your next post.

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)
   • C:\tom982.reg
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

 

[fralken]

Hello Tom,
thank you for your answer.
Here it is the zip with the two files: https://dl.dropbox.com/u/5187827/tom982.zip
Thanks,
fralken

 

[tom982]

Hi fralken,

Thanks for the files. I'm going cross eyed with all of this data, you should see the number of windows I have open trying to sift through it all!

Right, now for your problem, I think I have found the problem in your registry but I'm not 100% sure on this. I have devised a fix for this but it might be wrong, there's only one way to find out. Due to the risk I would like to make backups for us to fall back on if it is wrong prior to running this fix but I can assure you that if my fix is wrong, it will do nothing more than give you a different error in your CBS log, I don't think you will notice any difference :) If you are happy to go ahead with this, I don't mind either way, then can you do the following please:

RegBak

Please download RegBak (by AceLogix Software) from the link below and save it to your Desktop.

RegBak.zip​

• Right-click on regbak.zip then select Extract all... and extract the files to your Desktop
  
  
  For 32-bit (x86) editions of Windows, double-click on regbak.exe
  For 64-bit (x64) editions of Windows, double-click on regbak64.exe​
  
  If you are unsure whether you have x86 or x64 Windows, see here
  
  
• Without changing any options, click Next. RegBak will now backup all of your registry hives.

Modify Registry Permissions

1. Click on the Start
   
   button and in the search box, type regedit
2. When you see regedit on the list, right-click on it and select Run as administrator.
3. In the left hand panel of regedit, you will see a list of registry keys. Navigate to the following key, right-click on it and select Permissions...:
   
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
   
   
4. Click Advanced.
5. Under the Owner tab, click Edit.
6. Click "Other Users and Groups".
7. Click Advanced.
8. Click "Find Now".
9. Scroll down and double click on Everyone.
10. Click OK.
11. Put the check in "Replace owner on subcontainers and objects", click Apply then change to the Permissions tab.
12. Under type Deny, single click on any entries and click Remove. (N.B.: There may not be any Deny entries, in which case just ignore this step. Just remove any that do exist)
13. Click Edit (now on the standard file Property window under the Security tab).
14. Click Add.
15. Click Advanced.
16. Click "Find Now".
17. Scroll down and double click on Everyone.
18. Click OK.
19. Single click on Everyone and then tick the "Full Control" box under Allow.
20. Click OK TWO times.
    
    Download the below file, fralken_Fix.reg, and save this to your Desktop. Double-click on fralken_Fix.reg and accept any warning about merging the file with your registry.
    
    https://dl.dropbox.com/u/16537616/fralken_Fix.reg
    
    Finally:
    
21. Navigate to the following key, right-click on it and select Permissions...:
    
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
    
    
22. Click Advanced.
23. Click on the Permissions tab (should be the default tab).
24. Select and click Remove on the ALLOW: Everyone entry you just added.
25. Click OK.
26. Go to Owner tab.
27. Click Edit.
28. Click "Other Users and Groups".
29. Paste in "NT Service\TrustedInstaller"
30. Click OK.
31. Put the check in "Replace owner on subcontainers and objects".
32. Click Yes on any message boxes which pop-up.
33. Click Continue on any Access is Denied messages.
34. Click OK out of the final message box.
35. Click OK out of everything.

Tom

 

[fralken]

Hello Tom,
I followed your instructions but I get the same error when trying installing this update.
To be sure I did it right, below is the new content of this registry key.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_0.0.0.0_none_6b7da006d4ae6c79]
"Package_12_for_KB2699988~31bf3856ad364e35~amd64~~6.1.1.1.2699988-77_neutral_LDR"="8.0.7600.21198@2"
"Package_12_for_KB2699988~31bf3856ad364e35~amd64~~6.1.1.1.2699988-78_neutral_LDR"="8.0.7600.21198@4"
"Package_12_for_KB2699988~31bf3856ad364e35~amd64~~6.1.1.1.2699988-79_neutral_GDR"="8.0.7600.17006@2"
"Package_13_for_KB2699988~31bf3856ad364e35~amd64~~6.1.1.1.Trigger_1"="8.0.7600.21198@@2"
"Package_3_for_KB2699988~31bf3856ad364e35~amd64~~6.1.1.1.2699988-13_neutral_LDR"="8.0.7601.21976@2"
"Package_3_for_KB2699988~31bf3856ad364e35~amd64~~6.1.1.1.2699988-14_neutral_LDR"="8.0.7601.21976@4"
"Package_3_for_KB2699988~31bf3856ad364e35~amd64~~6.1.1.1.2699988-15_neutral_GDR"="8.0.7601.17824@2"
"Package_4_for_KB2699988~31bf3856ad364e35~amd64~~6.1.1.1.Trigger_1"="8.0.7601.21976@@2"
"Package_2_for_KB2722913~31bf3856ad364e35~amd64~~9.4.1.0.2722913-7_neutral_LDR"="9.4.8112.20554@2"
"Package_2_for_KB2722913~31bf3856ad364e35~amd64~~9.4.1.0.2722913-8_neutral_GDR"="9.4.8112.16448@2"
"Package_2_for_KB2744842~31bf3856ad364e35~amd64~~9.4.1.0.2744842-7_neutral_LDR"="9.4.8112.20557@2"
"Package_2_for_KB2744842~31bf3856ad364e35~amd64~~9.4.1.0.2744842-8_neutral_GDR"="9.4.8112.16450@2"
"Package_2_for_KB2761451~31bf3856ad364e35~amd64~~9.4.1.0.2761451-7_neutral_LDR"="9.4.8112.20562@2"
"Package_2_for_KB2761451~31bf3856ad364e35~amd64~~9.4.1.0.2761451-8_neutral_GDR"="9.4.8112.16455@2"
"Package_2_for_KB2761465~31bf3856ad364e35~amd64~~9.4.1.0.2761465-7_neutral_LDR"="9.4.8112.20565@2"
"Package_2_for_KB2761465~31bf3856ad364e35~amd64~~9.4.1.0.2761465-8_neutral_GDR"="9.4.8112.16457@2"
"Package_3_for_KB2530548~31bf3856ad364e35~amd64~~6.1.1.2.2530548-13_neutral_GDR"="8.0.7601.17608@2"
"Package_3_for_KB2530548~31bf3856ad364e35~amd64~~6.1.1.2.2530548-143_neutral_PACKAGE"="8.0.7601.17608@2"
"Package_for_KB2530548_SP1~31bf3856ad364e35~amd64~~6.1.1.2.2530548-143_neutral_PACKAGE"="8.0.7601.17608@2"
"Package_for_KB2530548_SP1~31bf3856ad364e35~amd64~~6.1.1.2.2530548-150_neutral_PACKAGE"="8.0.7601.17608@2"
"Package_for_KB2530548~31bf3856ad364e35~amd64~~6.1.1.2.2530548-150_neutral_PACKAGE"="8.0.7601.17608@2"

Thanks,
fralken

 

[tom982]

Hi fralken,

It looks like you did everything perfectly :) Can you upload your CBS log please?

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

Tom

 

[fralken]

Hello Tom,
sorry for the late anser but I faced an hard disk failure and I took some time to recover. Seems I'm a bit unlucky recently with my pc...

Btw, it seems fails in CBS.log are the same as before:

2013-04-04 01:24:28, Error                 CSI    0000000b@2013/4/3:23:24:28.415 (F) d:\win7sp1_gdr\base\wcp\componentstore\installmap.cpp(620): Error STATUS_SXS_COMPONENT_STORE_CORRUPT originated in function InstallMap::CRawInstallMap::GetComponentWinningVersion expression: (null) 
[gle=0x80004005] 
2013-04-04 01:24:28, Error                 CSI    0000000c (F) HRESULT_FROM_WIN32(14098) #6201# from Windows::ServicingAPI::CCSITransactionAnalysis_ICSIInventory::GetComponentInstalledVersions(flags = 0, cAssemblies = 1) 
[gle=0x80073712] 
2013-04-04 01:24:28, Info                  CBS    Failed to get the current component winner [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT] 
2013-04-04 01:24:28, Info                  CBS    Failed to get component installed versions, component: x86_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_8.0.7601.17608_none_64742e7661bc885d [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT] 
2013-04-04 01:24:28, Info                  CBS    Failed to determine whether the udpate will be superseded: 2530548-13_neutral_GDR [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT] 
2013-04-04 01:24:28, Error                 CBS    Failed to call external evaluate applicability on package: Package_3_for_KB2530548~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2530548-13_neutral_GDR [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT] 
2013-04-04 01:24:28, Info                  CBS    Failed to evaluate external applicability for package update: 2530548-143_neutral_PACKAGE [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT] 
2013-04-04 01:24:28, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2530548_SP1~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2530548-143_neutral_PACKAGE [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT] 
2013-04-04 01:24:28, Info                  CBS    Failed to evaluate external applicability for package update: 2530548-150_neutral_PACKAGE [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT] 
2013-04-04 01:24:28, Error                 CBS    Failed to call external evaluate applicability on package: Package_for_KB2530548~31bf3856ad364e35~amd64~~6.1.1.2, Update: 2530548-150_neutral_PACKAGE [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]

Thanks,
fralken

 

[tom982]

Hi fralken,

That's a shame. This registry problem keeps cropping up and every time I try something new, it seems to fail. Right now, I'm all out of potential fixes and anything I try from this point is nothing more than guessing. I would hate to waste your time so I think the best way forward is for you to do a repair install:

https://www.sysnative.com/forums/wi...-install-windows-windows-7-windows-vista.html

Sorry I couldn't have been of more help but this is very difficult problem to diagnose! I will find a solution eventually though.

Tom

 

[fralken]

Hi Tom,
sorry I replied so late but last week I had a problem with my HD, I had to send it back to the vendor to get it repaired. Now it's ok again.

Before trying the last resort you suggested, I advice you that I ran the System Update Readiness Tool and got this CheckSUR.log:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 18.0
2013-04-16 00:23

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist
(f)    CBS Watchlist Component Missing    0x80070002    x86_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_0.0.0.0_none_6b7da006d4ae6c79    Package_3_for_KB2530548~31bf3856ad364e35~amd64~~6.1.1.2    Package registry presence failed, possibly an orphaned package on package watchlist
(f)    CBS Watchlist Component Missing    0x80070002    x86_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_0.0.0.0_none_6b7da006d4ae6c79    Package_3_for_KB2530548~31bf3856ad364e35~amd64~~6.1.1.2    Package registry presence failed, possibly an orphaned package on package watchlist
(f)    CBS Watchlist Component Missing    0x80070002    x86_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_0.0.0.0_none_6b7da006d4ae6c79    Package_for_KB2530548_SP1~31bf3856ad364e35~amd64~~6.1.1.2    Package registry presence failed, possibly an orphaned package on package watchlist
(f)    CBS Watchlist Component Missing    0x80070002    x86_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_0.0.0.0_none_6b7da006d4ae6c79    Package_for_KB2530548_SP1~31bf3856ad364e35~amd64~~6.1.1.2    Package registry presence failed, possibly an orphaned package on package watchlist
(f)    CBS Watchlist Component Missing    0x80070002    x86_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_0.0.0.0_none_6b7da006d4ae6c79    Package_for_KB2530548~31bf3856ad364e35~amd64~~6.1.1.2    Package registry presence failed, possibly an orphaned package on package watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 128
 Found 5 errors
  CBS Watchlist Component Missing Total count: 5

These missing components are those you told me to add in the registry. Is it possible to add them in some way? I tried installing KB2530548 update but it's impossible.

Thanks,
fralken

 

[tom982]

Hi fralken,

That's very promising! As you can see, those errors are for the registry key x86_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_0.0.0.0_none_6b7da006d4ae6c79 which is the same as what we faced in the CBS log:

2013-04-04  01:24:28, Error                 CSI    0000000b@2013/4/3:23:24:28.415  (F) d:\win7sp1_gdr\base\wcp\componentstore\installmap.cpp(620): Error  STATUS_SXS_COMPONENT_STORE_CORRUPT originated in function  InstallMap::CRawInstallMap::GetComponentWinningVersion expression:  (null) 
[gle=0x80004005] 
2013-04-04 01:24:28,  Error                 CSI    0000000c (F) HRESULT_FROM_WIN32(14098)  #6201# from  Windows::ServicingAPI::CCSITransactionAnalysis_ICSIInventory::GetComponentInstalledVersions(flags  = 0, cAssemblies = 1) 
[gle=0x80073712] 
2013-04-04 01:24:28,  Info                  CBS    Failed to get the current component winner  [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT] 
2013-04-04  01:24:28, Info                  CBS    Failed to get component  installed versions, component:  x86_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_8.0.7601.17608_none_64742e7661bc885d  [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT] 
2013-04-04  01:24:28, Info                  CBS    Failed to determine whether the  udpate will be superseded: 2530548-13_neutral_GDR [HRESULT = 0x80073712 -  ERROR_SXS_COMPONENT_STORE_CORRUPT] 
2013-04-04 01:24:28,  Error                 CBS    Failed to call external evaluate  applicability on package:  Package_3_for_KB2530548~31bf3856ad364e35~amd64~~6.1.1.2, Update:  2530548-13_neutral_GDR [HRESULT = 0x80073712 -  ERROR_SXS_COMPONENT_STORE_CORRUPT] 
2013-04-04 01:24:28,  Info                  CBS    Failed to evaluate external applicability  for package update: 2530548-143_neutral_PACKAGE [HRESULT = 0x80073712 -  ERROR_SXS_COMPONENT_STORE_CORRUPT] 
2013-04-04 01:24:28,  Error                 CBS    Failed to call external evaluate  applicability on package:  Package_for_KB2530548_SP1~31bf3856ad364e35~amd64~~6.1.1.2, Update:  2530548-143_neutral_PACKAGE [HRESULT = 0x80073712 -  ERROR_SXS_COMPONENT_STORE_CORRUPT] 
2013-04-04 01:24:28,  Info                  CBS    Failed to evaluate external applicability  for package update: 2530548-150_neutral_PACKAGE [HRESULT = 0x80073712 -  ERROR_SXS_COMPONENT_STORE_CORRUPT] 
2013-04-04 01:24:28,  Error                 CBS    Failed to call external evaluate  applicability on package:  Package_for_KB2530548~31bf3856ad364e35~amd64~~6.1.1.2, Update:  2530548-150_neutral_PACKAGE [HRESULT = 0x80073712 -  ERROR_SXS_COMPONENT_STORE_CORRUPT]

I'm hoping this is the same problem, though it may well just be a symptom of a deeper problem. To fix those SURT errors, I need a little more information:

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\ComponentDetect\x86_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_0.0.0.0_none_6b7da006d4ae6c79
   
   
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.

Tom

 

[fralken]

Hello Tom,
I think we are looping ... :smile9:

The registry extraction you are asking is the one I posted on #11.

As you can see, there are 5 entries you told me to add in post #10, in an attempt to fix problems logged on CBS.log.
Nevertheless, these problems are still present in CBS.log, but as a side effect I have now errors in CheckSUR.log (shown in #15).

Maybe there is something more I should add/change somewhere.
For example, is the content of c:\windows\winsxs relevant for this kind of problem?

Thank you, fralken

 

[tom982]

Hi Fralken,

Sorry about that, when you deal with lots of threads at once it's surprisingly easy to confuse two of them!

Just when I was about to give up and accept defeat, I've found your problem:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_none_e88a3e957903983f\9.4]
"9.4.8112.16447"=hex:01
@=";.4.:112.16477"
"9.4.8112.16448"=hex:01
"9.4.8112.16450"=hex:01
"9.4.8112.16455"=hex:01
"9.4.8112.16457"=hex:01

Notice that @=";.4.:112.16477" should be @="9.4.8112.16477", so let's fix this corruption:


Modify Registry Permissions

1. Click on the Start
   
   button and in the search box, type regedit
2. When you see regedit on the list, right-click on it and select Run as administrator.
3. In the left hand panel of regedit, you will see a list of registry keys. Navigate to the following key, right-click on it and select Permissions...:
   
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_none_e88a3e957903983f
   
   
4. Click Advanced.
5. Under the Owner tab, click Edit.
6. Click "Other Users and Groups".
7. Click Advanced.
8. Click "Find Now".
9. Scroll down and double click on Everyone.
10. Click OK.
11. Put the check in "Replace owner on subcontainers and objects", click Apply then change to the Permissions tab.
12. Under type Deny, single click on any entries and click Remove. (N.B.: There may not be any Deny entries, in which case just ignore this step. Just remove any that do exist)
13. Click Edit (now on the standard file Property window under the Security tab).
14. Click Add.
15. Click Advanced.
16. Click "Find Now".
17. Scroll down and double click on Everyone.
18. Click OK.
19. Single click on Everyone and then tick the "Full Control" box under Allow.
20. Click OK TWO times.
    
    In the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_none_e88a3e957903983f
    
    You will see a few values with the following names:
    
    (Default)
    9.4.8112.16447
    9.4.8112.16448
    9.4.8112.16450
    9.4.8112.16455
    9.4.8112.16457
    
    Double click on (Default) and a window labelled Edit String should appear, change the Value Data to: 9.4.8112.16477 and press OK.
    
    Finally:
    
21. Navigate to the following key, right-click on it and select Permissions...:
    
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_none_e88a3e957903983f
    
    
22. Click Advanced.
23. Click on the Permissions tab (should be the default tab).
24. Select and click Remove on the ALLOW: Everyone entry you just added.
25. Click OK.
26. Go to Owner tab.
27. Click Edit.
28. Click "Other Users and Groups".
29. Paste in "NT Service\TrustedInstaller"
30. Click OK.
31. Put the check in "Replace owner on subcontainers and objects".
32. Click Yes on any message boxes which pop-up.
33. Click Continue on any Access is Denied messages.
34. Click OK out of the final message box.
35. Click OK out of everything.

Reboot and try updating. If it fails, upload your CBS log please :)

Tom

 

[fralken]

Tom,
you are a genius!! :grin1:

This was the right direction!

This registry section was very corrupted, and your suggestion was just the first bit of a long and tedious work of fixing a lot of registry keys. But anyway, the place to look into was exactly HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners

FYI, please note that the owner of this registry section is Administrator, so you don't need to change and then restore TrustedInstaller. Hence, the 35 steps can be reduced to just 1, the #20. Much easier indeed! This can be useful for you when you'll give advice to other users...

Anyway, I summarize what I did:

1) I rollbacked the fix you suggest in post #10, that was wrong. After that, my CheckSUR.log was clean again

2) I found all the corrupted keys in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners
This is the list:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_03938a0592aea3ecc60744746897769a_31bf3856ad364e35_none_46b25d937f1789ef\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_2912dc5ebedafb00cff4f71735750d34_31bf3856ad364e35_none_07d660f76819d127\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_3b8c55a92fabe853b5ad96e14984ae91_31bf3856ad364e35_none_2b9984cf5ca535bd\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_4fca8a041b08cbdaac464dd25a48280b_31bf3856ad364e35_none_3e0b8b5a638cd753\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_54f746e54de731c9d061f85ae648ed96_31bf3856ad364e35_none_eee12ea7cad2e593\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_656bf750abd164d523c4c290a613c930_31bf3856ad364e35_none_04f77002edc215d3\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_6b417b119e3562a0e6f8dd46d400911b_31bf3856ad364e35_none_5e3295a99cb053fe\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_6e2206f50b40aa71dd6d492ba737a646_31bf3856ad364e35_none_53668b8456dea95d\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_7d84efac137af2c9eeb4b1dcda3ba6b4_31bf3856ad364e35_none_8a6b2694afb5a396\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_8edc29bd3daa7bc5d34b31de0e2ea360_31bf3856ad364e35_none_eb5e52af055bb396\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_c72e4f56eed6a2368a01c03c2bc73ee3_31bf3856ad364e35_none_e771edffc24fda78\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_e0f529148f74f0d68d09ad5ec08044fa_31bf3856ad364e35_none_d2d9a063dcfd0990\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-i..ersandsecurityzones_31bf3856ad364e35_none_de3177239ae782e5\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-i..etexplorer-optional_31bf3856ad364e35_none_5d98835e4a20dc2c\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-i..nternetcontrolpanel_31bf3856ad364e35_none_ebfb3d55c61ec5e1\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_none_5baf0220f61f622a\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-ie-devtools_31bf3856ad364e35_none_251ec48b1d7459b1\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-ieframe_31bf3856ad364e35_none_8f9ed8701133631f\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_none_36fb5ae359a40124\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-ie-ieproxy_31bf3856ad364e35_none_73f4badbaa7c19e3\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-ie-jscriptdebugui_31bf3856ad364e35_none_6c06ae399beb9649\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_none_44a8da1931610975\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-ie-versioninfo_31bf3856ad364e35_none_f338a86a1ea94449\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-ie-winsockautodialstub_31bf3856ad364e35_none_5f55bb4bfdae9250\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-scripting-jscript_31bf3856ad364e35_none_dfca736909165a7b\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-scripting-vbscript_31bf3856ad364e35_none_1dd485790300b91f\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\wow64_microsoft-windows-ie-feeds-platform_31bf3856ad364e35_none_a6d0805dfd18a92d\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\wow64_microsoft-windows-ieframe_31bf3856ad364e35_none_99f382c24594251a\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\wow64_microsoft-windows-ie-internetexplorer_31bf3856ad364e35_none_154da5285609899a\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-i..ersandsecurityzones_31bf3856ad364e35_none_8212db9fe28a11af\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_none_ff90669d3dc1f0f4\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-ie-devtools_31bf3856ad364e35_none_c90029076516e87b\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-ie-ieproxy_31bf3856ad364e35_none_17d61f57f21ea8ad\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-ie-ieshims_31bf3856ad364e35_none_1df092d5e944d62f\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_none_e88a3e957903983f\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-ie-versioninfo_31bf3856ad364e35_none_971a0ce6664bd313\9.4

A long list indeed.
These keys had wrong values similar (but not necessarly equal) to the one you noticed ";.4.:112.16477". So I had to carefully check one by one.

But there was another trick: 9.4.8112.16477 was still wrong!
This is because the default value must match one of the values listed below (usually the biggest one).
As you can see, in this list
(Default)
9.4.8112.16447
9.4.8112.16448
9.4.8112.16450
9.4.8112.16455
9.4.8112.16457
that value is not present. Instead, I should change the default to 9.4.8112.16457

In short, 16477 was a corrupted value, and should be changed to 16457 (or 16476 in other cases). This is the list of keys containing the 16477 corruption:

keys with default value containing 16477
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_03938a0592aea3ecc60744746897769a_31bf3856ad364e35_none_46b25d937f1789ef\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_6e2206f50b40aa71dd6d492ba737a646_31bf3856ad364e35_none_53668b8456dea95d\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_7d84efac137af2c9eeb4b1dcda3ba6b4_31bf3856ad364e35_none_8a6b2694afb5a396\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_c72e4f56eed6a2368a01c03c2bc73ee3_31bf3856ad364e35_none_e771edffc24fda78\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_none_5baf0220f61f622a\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-ie-feeds-platform_31bf3856ad364e35_none_9c7bd60bc8b7e732\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-ieframe_31bf3856ad364e35_none_8f9ed8701133631f\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_none_44a8da1931610975\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-ie-versioninfo_31bf3856ad364e35_none_f338a86a1ea94449\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\wow64_microsoft-windows-ie-internetexplorer_31bf3856ad364e35_none_154da5285609899a\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-ie-ieproxy_31bf3856ad364e35_none_17d61f57f21ea8ad\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-ie-ieshims_31bf3856ad364e35_none_1df092d5e944d62f\9.4
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\x86_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_none_e88a3e957903983f\9.4

this key had a wrong value containing 16477 instead of 16457, and data 03 instead of 01
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\wow64_microsoft-windows-ie-feeds-platform_31bf3856ad364e35_none_a6d0805dfd18a92d\9.4

After this other fix, I was finally able to install both IE9 update and then IE10! Amazing.
No need to do a repair install of Windows...

I can happily mark this thread as solved. I hope it can be useful for other users, too.

Thank you again,
fralken

P.S. I suppose the cause of this corruption could be a RAM stick failure I suffered a few month ago. I had to replace the RAM, and at that time Windows Update stopped working. Luckily, this forum again gave me the solution for that problem, too.

 

[tom982]

Hi fralken,

That's great news! Thanks for posting back the results, and even more for investigating this so much yourself. It's a good job that you know your way around a computer because it's very likely that the registry corruption would be shown one key at a time in the CBS log, as soon as we fixed this one it would have detected the next, and so on, and made this a very, very long process!

Though Windows Update is working once again, I would highly recommend you run the System Update Readiness Tool just to make sure it doesn't detect any problems from what we've changed here. If the CheckSUR log has any errors, post it here and we can fix those as well.

Tom