[SOLVED] [WIN7SP1 x64] Monthly rollup Update fails, SURT: CSI Missing Winning Component Key

RitaK

Member
Joined
Jun 18, 2017
Posts
16
Hello,

Windows 7 (SP1 64bits) Monthly Rollup Updates fail since March, other updates work fine. CheckSUR log shows one error:

(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-c..tionauthorityclient_31bf3856ad364e35_6.1.7601.23642_none_360ab9ce6c7f0698
-------------------------------------

I have tried most tips and tricks, including resetting Windows Update Components.

I have just run SFCfix, here is the log :

--------------------------------------
SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-06-18 11:38:37.595
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.


AutoAnalysis::
SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 0
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 1
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.

Failed to generate a complete zip file. Upload aborted.

SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2017-06-18 11:56:35.698
----------------------EOF-----------------------

I will upload the CBS folder later (too large now).

Many thanks in advance for any help or advice.
 
Follow up of my first post. Here is the complete CheckSUR.persist.log :

===================================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2017-01-12 09:32

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-c..tionauthorityclient_31bf3856ad364e35_6.1.7601.23642_none_360ab9ce6c7f0698
(f) CSI Missing Winning Component Key 0x00000000 amd64_a387b952b68c79de2becc717ec33a0e8_31bf3856ad364e35_6.1.7601.23642_none_fad5f70901375f94
(fix) CSI Missing Winning Component Key CSI Registry Item Repaired Deleted winners map value 6.1.7601.23642

Summary:
Seconds executed: 6632
Found 2 errors
Fixed 1 errors
CSI Missing Winning Component Key Total count: 2
Fixed: CSI Missing Winning Component Key. Total count: 1

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2017-06-16 14:19

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-c..tionauthorityclient_31bf3856ad364e35_6.1.7601.23642_none_360ab9ce6c7f0698

Summary:
Seconds executed: 3339
Found 1 errors
CSI Missing Winning Component Key Total count: 1
===========================================
 
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 file 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.
View attachment SFCFix.zip

System Update Readiness Tool (SURT)

Please run the System Update Readiness Tool again and, when it has finished, attach C:\Windows\Logs\CBS\CheckSUR.log with your reply.
 
Here is the result of the SFCFix script, and the CheckSUR.log in the attachment : View attachment CheckSUR.log:

Code:
SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-07-17 22:27:04.031
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\Rob\Desktop\SFCFix.zip [0]


RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..tionauthorityclient_31bf3856ad364e35_6.1.7601.23642_none_360ab9ce6c7f0698.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..tionauthorityclient_31bf3856ad364e35_6.1.7601.23642_none_360ab9ce6c7f0698.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\a387b952b68..717ec33a0e8_31bf3856ad364e35_6.1.7601.23642_fad5f70901375f94.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..tionauthorityclient_31bf3856ad364e35_6.1.7601.23642_none_360ab9ce6c7f0698.
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\a387b952b68..717ec33a0e8_31bf3856ad364e35_6.1.7601.23642_fad5f70901375f94 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments.
RegistryScript:: directive failed to complete successfully.


Failed to process all directives successfully.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2017-07-17 22:27:06.621
Script hash: Rbx54plMAkeak7r7NYCMFUA+QP3H5GxdDM4QPWOvz00=
----------------------EOF-----------------------
 
Code:
Failed to open registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\a387b952b68..717ec33a0e8_31bf3856ad364e35_6.1.7601.23642_fad5f70901375f94 with error code ERROR_FILE_NOT_FOUND.

Please manually upload the components hive by following these instructions:

Upload Components Hive
  1. Navigate to C:\Windows\System32\config
  2. Right-click on the current COMPONENTS file and select copy
    Note: If you get an error that the file is in use, reboot your computer and then try again.
  3. Right-click on your Desktop and select paste
  4. Right-click on the COMPONENTS file on your Desktop and select Send To -> Compressed (zipped) Folder
  5. Upload the zip from your Desktop to a file sharing service such as DropBox, OneDrive, SendSpace, etc. and include the link with your reply.
 
If you run registry editor and browse to HKLM\Components\CanonicalData\Deployments are you able to create a new key with the name a387b952b68..717ec33a0e8_31bf3856ad364e35_6.1.7601.23642_fad5f70901375f94 or does this produce an error message?
 
I have created this new key without any error message. Should I reboot now ? Many Thanks
 
Try running the SFCFix script from my earlier reply again and attach the log once it completes :)
 
Here it is :

Code:
SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-07-18 22:03:49.793
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\Rob\Desktop\SFCFix.zip [1]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..tionauthorityclient_31bf3856ad364e35_6.1.7601.23642_none_360ab9ce6c7f0698.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\a387b952b68..717ec33a0e8_31bf3856ad364e35_6.1.7601.23642_fad5f70901375f94.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..tionauthorityclient_31bf3856ad364e35_6.1.7601.23642_none_360ab9ce6c7f0698.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\a387b952b68..717ec33a0e8_31bf3856ad364e35_6.1.7601.23642_fad5f70901375f94.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..tionauthorityclient_31bf3856ad364e35_6.1.7601.23642_none_360ab9ce6c7f0698.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\a387b952b68..717ec33a0e8_31bf3856ad364e35_6.1.7601.23642_fad5f70901375f94.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2017-07-18 22:03:51.572
Script hash: Rbx54plMAkeak7r7NYCMFUA+QP3H5GxdDM4QPWOvz00=
----------------------EOF-----------------------
 
Great! Go ahead and run the System Update Readiness Tool again and when it has completed, attach C:\Windows\Logs\CBS\CheckSUR.log with your reply.
 
The log is clean now, see below. But the monthly update still fails. Is there a next step? Thanks !

=================================
Code:
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2017-07-18 22:52

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f)    CSI Catalog Missing    0x00000002    b89fa5f4e95793f8b73105f9dea6824bdbaf78d8b8eda58b6db34bf247e4b792.cat    a387b952b68..717ec33a0e8_31bf3856ad364e35_6.1.7601.23642_fad5f70901375f94    Missing catalog or invalid CatalogThumprint
(fix)    CSI Catalog Missing    CSI File Replaced    Deleted CatalogThumbprint

Summary:
Seconds executed: 1923
 Found 1 errors
 Fixed 1 errors
  CSI Catalog Missing Total count: 1
  Fixed: CSI Catalog Missing.  Total count: 1
 
Please try installing the update again, then when it fails zip and attach C:\Windows\Logs\CBS\CBS.log with your reply.
 
Code:
2017-07-19 21:20:35, Info                  CBS    Plan: Package: Package_360_for_KB3212646~31bf3856ad364e35~amd64~~6.1.1.0, current: Installed, pending: Default, start: Installed, applicable: Installed, targeted: Superseded, limit: Superseded
2017-07-19 21:20:35, Error                 CSI    0000000b@2017/7/19:19:20:35.226 (F) d:\w7rtm\base\wcp\componentstore\csd_core.cpp(616): Error STATUS_SXS_ASSEMBLY_NOT_FOUND originated in function CCSDirect::GetDeploymentClosureStatus expression: (null)
[gle=0x80004005]
2017-07-19 21:20:41, Error                 CSI    0000000c (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_NOT_FOUND) #295885# from Windows::ServicingAPI::CCSITransactionAnalysis_ICSIInventory::GetDeploymentInformation(flags = 0, class = ICSIINVENTORY_GET_DEPLOYMENT_INFORMATION_CLASS_CLOSURE (1), information = {dwFlags=00000000})
[gle=0x800736b3]
2017-07-19 21:20:41, Info                  CBS    Failed to call GetDeploymentInformation on deployment: amd64_a387b952b68c79de2becc717ec33a0e8_31bf3856ad364e35_6.1.7601.23642_none_fad5f70901375f94 [HRESULT = 0x800736b3 - ERROR_SXS_ASSEMBLY_NOT_FOUND]
2017-07-19 21:20:41, Info                  CBS    Failed to get component state. [HRESULT = 0x800736b3 - ERROR_SXS_ASSEMBLY_NOT_FOUND]

Install Update with DISM

  1. Download the update MSU here: http://download.windowsupdate.com/c..._a94cf69326099fb121cdd7daf9dfc558f740afb8.msu
  2. Copy the MSU file to a convenient location (such as C:\temp).
  3. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  4. When you see Command Prompt on the list, right-click on it and select Run as administrator
  5. When command prompt opens, copy and paste the following commands into it, press enter after each

    cd C:\temp

    replace C:\temp with your path if different

    expand windows6.1-kb3212646-x64_a94cf69326099fb121cdd7daf9dfc558f740afb8.msu -f:* C:\temp

    DISM.exe /Online /Add-Package /PackagePath:C:\temp\windows6.1-kb3212646-x64.cab

  6. You should receive the message:
    The operation completed successfully.
    Restart Windows to complete this operation.
    Do you want to restart the computer now (Y/N)?

  7. Make sure to allow the computer to restart if prompted.

    If you receive any other message:
  8. Right-click on the Command Prompt window and click Select All, this will invert all of the colours by selecting the text, now press enter. All of this text is now copied.
  9. Paste (Ctrl+V) it into your next post please.
 
It did not work out :

Code:
Microsoft Windows [versie 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle rechten voorbehouden.

C:\Users\Rob>cd C:\Intel

C:\Intel>expand windows6.1-kb3212646-x64_a94cf69326099fb121cdd7daf9dfc558f740afb
8.msu -f:* C:\Intel
Microsoft (R) Hulpprogramma voor uitpakken van bestanden Versie 6.1.7600.16385
Copyright (c) Microsoft Corporation.  Alle rechten voorbehouden.

C:\Intel\WSUSSCAN.cab aan wachtij voor uitpakken toevoegen
C:\Intel\Windows6.1-KB3212646-x64.cab aan wachtij voor uitpakken toevoegen
C:\Intel\Windows6.1-KB3212646-x64-pkgProperties.txt aan wachtij voor uitpakken t
oevoegen
C:\Intel\Windows6.1-KB3212646-x64.xml aan wachtij voor uitpakken toevoegen

Bestanden uitpakken...

Bestanden zijn uitgepakt...
In totaal 4 bestanden.

C:\Intel>DISM.exe /Online /Add-Package /PackagePath:C:\temp\windows6.1-kb3212646
-x64.cab

Hulpprogramma DISM (Deployment Image Servicing and Management)
Versie: 6.1.7600.16385

Versie van installatiekopie: 6.1.7601.18489

Er is een fout opgetreden bij het openen van C:\temp\windows6.1-kb3212646-x64.ca
b Fout: 0x80070003

Fout: 3

Het systeem kan het opgegeven pad niet vinden.

Het DISM-logboekbestand is te vinden op C:\Windows\Logs\DISM\dism.log

C:\Intel>DISM.exe /Online /Add-Package /PackagePath:C:\Intel\windows6.1-kb321264
6-x64.cab

Hulpprogramma DISM (Deployment Image Servicing and Management)
Versie: 6.1.7600.16385

Versie van installatiekopie: 6.1.7601.18489

1 van 1 wordt verwerkt -
Er is een fout opgetreden - Package_for_RollupFix Fout: 0x800736b3

Fout: 14003

Het onderdeel waarnaar wordt verwezen is niet op dit systeem geïnstalleerd.

Het DISM-logboekbestand is te vinden op C:\Windows\Logs\DISM\dism.log

C:\Intel>
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top