[SOLVED] CSI Missing Winning Component Key

A

ajp

Member
Joined
May 22, 2019
Posts
8
Hi - Having run SFC and System Update Readiness I have the following errors in the Component Store:

(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-directwrite_31bf3856ad364e35_6.1.7601.18946_none_30a4f63116252eb3
(f) CSI Missing Winning Component Key 0x00000000 wow64_microsoft-windows-i..rnational-timezones_31bf3856ad364e35_6.1.7601.24350_none_7e1c18206dd45cbf
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.24350_en-us_85d6cddef94a9e4b
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-directx-warp10_31bf3856ad364e35_7.1.7601.18946_none_39dba738f849264f
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-directx-warp10_31bf3856ad364e35_6.1.7601.18946_none_ec4c8f6fb5050c4a
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.24178_en-us_85c92c8af953a697
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-directwrite_31bf3856ad364e35_7.1.7601.18946_none_c5f6d6f2e8ae664c
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.24178_fr-fr_284bff6dec4cae9e
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.18946_none_16fb00c9b13ce8bf
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.24290_en-us_85ab8c48f96b10e8
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.24350_de-de_dce5f7e60a6c9286
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-directx-warp10_31bf3856ad364e35_6.1.7601.18946_none_486b2af36d627d80
(f) CSI Missing Winning Component Key 0x00000000 wow64_microsoft-windows-scripting_31bf3856ad364e35_6.1.7601.18283_none_b096369f4b940a23
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.24350_es-es_e1c0c646b1cf0126
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.24290_fr-fr_282e5f2bec6418ef
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-i..rnational-timezones_31bf3856ad364e35_6.1.7601.24290_none_739c2c3839940d61
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.24178_de-de_38f6f215c2d30c08
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.24178_es-es_8594896ef97a983c
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-directwrite_31bf3856ad364e35_6.1.7601.18946_none_d4865aad5dc7bd7d
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.24290_de-de_dcbab6500a8d0523
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.24350_de-de_39049369c2ca03bc
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.24290_en-us_e1ca27ccb1c8821e
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-directwrite-fontcache_31bf3856ad364e35_7.1.7601.18946_none_542211a0b2ebfcea
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-scripting_31bf3856ad364e35_6.1.7601.18283_none_a6418c4d17334828
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.24178_es-es_e1b324f2b1d80972
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.24178_de-de_dcd856920a759ad2
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.24290_de-de_38d951d3c2ea7659
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.7601.18946_none_8382f002ed61108b
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-directwrite_31bf3856ad364e35_7.1.7601.18946_none_22157276a10bd782
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-i..rnational-timezones_31bf3856ad364e35_6.1.7601.24178_none_73b9cc7a397ca310
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18946_none_2b27281071eac12c
(f) CSI Missing Winning Component Key 0x00000000 wow64_microsoft-windows-i..rnational-timezones_31bf3856ad364e35_6.1.7601.24290_none_7df0d68a6df4cf5c
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18946_none_72d45ee78666ea32
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.24350_en-us_e1f56962b1a80f81
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.24290_es-es_8576e92cf992028d
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.24290_fr-fr_844cfaafa4c18a25
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.24350_fr-fr_2859a0c1ec43a652
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.0.7601.18946_none_3bd5b92bd8e4e785
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-directwrite-fontcache_31bf3856ad364e35_6.1.7601.18946_none_62b1955b2805541b
(f) CSI Missing Winning Component Key 0x00000000 wow64_microsoft-windows-i..rnational-timezones_31bf3856ad364e35_6.1.7601.24178_none_7e0e76cc6ddd650b
(f) CSI Missing Winning Component Key 0x00000000 wow64_microsoft-windows-gdi_31bf3856ad364e35_6.1.7601.18946_none_122f49d9a59d3e46
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-gdi_31bf3856ad364e35_6.1.7601.18946_none_07da9f87713c7c4b
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.23149_none_17877694ca5807d0
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-i..rnational-timezones_31bf3856ad364e35_6.1.7601.24350_none_73c76dce39739ac4
(f) CSI Missing Winning Component Key 0x00000000 wow64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.18946_none_214fab1be59daaba
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.24178_fr-fr_846a9af1a4aa1fd4
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.24178_en-us_e1e7c80eb1b117cd
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.24290_es-es_e19584b0b1ef73c3
(f) CSI Missing Winning Component Key 0x00000000 wow64_microsoft-windows-win32k_31bf3856ad364e35_6.1.7601.23149_none_21dc20e6feb8c9cb
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.24350_fr-fr_84783c45a4a11788
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-directx-warp10_31bf3856ad364e35_7.1.7601.18946_none_ddbd0bb53febb519
(f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-i..timezones.resources_31bf3856ad364e35_6.1.7601.24350_es-es_85a22ac2f9718ff0

The components ZIP file can be found at COMPONENTS.zip (26.37MB) - SendSpace.com.

Any help that can be provided will be greatly appreciated.
 

Attachments

Hello and welcome,

Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the Farbar Recovery Scan Tool and save it to your Desktop:
    64-bit: Downloading Farbar Recovery Scan Tool
  2. Download the attachment fixlist.txt and save it to your desktop.
  3. Right-click on FRST64.exe and select "Run as administrator".
  4. Press the Fix button.
  5. The tool will now process fixlist.txt.
  6. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  7. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  8. Post the logfile Fixlog.txt as attachment in your next reply.

Step 2:
Start the System Update Readiness Tool (SURT) again.
On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log in your next reply.
 

Attachments

Thank you very much for your response. It is most appreciated.

Attached are copies of the fixlog.txt and CheckSUR.log files as requested. There are now just 26 CSI Missing Winning Component Key outstanding.
 

Attachments

Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Post the logfile Fixlog.txt as attachment in your next reply.

Step 2:
Start the System Update Readiness Tool (SURT) again.
On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log in your next reply.
 

Attachments

Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Post the logfile Fixlog.txt as attachment in your next reply.

Step 2:
Start the System Update Readiness Tool (SURT) again.
On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log in your next reply.
 

Attachments

Attached are the outputs from running the latest fix file. Six errors remain that appear to relate to es-es timezones resources files. Thank you once again for your help so far.
 

Attachments

Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Post the logfile Fixlog.txt as attachment in your next reply.

Step 2:
Start the System Update Readiness Tool (SURT) again.
On completion, attach the logfile C:\Windows\Logs\CBS\CheckSUR.log in your next reply.
 

Attachments

Positive news that there are no outstanding errors in the CheckSUR.log however the "2019-05 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4499164)" security update still fails to install. Other security updates that are not the "monthly quality rollups" install correctly.

An extract from the CBS.LOG where the installation of KB4499164 falls over shows:

2019-05-29 17:11:40, Info CBS Appl: Evaluating package applicability for package Package_381_for_KB4486563~31bf3856ad364e35~amd64~~6.1.1.4, applicable state: Installed
2019-05-29 17:11:40, Info CBS Plan: Package: Package_381_for_KB4486563~31bf3856ad364e35~amd64~~6.1.1.4, current: Superseded, pending: Default, start: Superseded, applicable: Installed, targeted: Superseded, limit: Superseded
2019-05-29 17:11:40, Error CSI 0000000d@2019/5/29:16:11:40.259 (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]
2019-05-29 17:11:41, Error CSI 0000000e (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_NOT_FOUND) #390814# from Windows::ServicingAPI::CCSITransactionAnalysis_ICSIInventory::GetDeploymentInformation(flags = 0, class = ICSIINVENTORY_GET_DEPLOYMENT_INFORMATION_CLASS_CLOSURE (1), information = {dwFlags=00000000})
[gle=0x800736b3]
2019-05-29 17:11:41, Info CBS Failed to call GetDeploymentInformation on deployment: amd64_6a1cf3679e57ccd084da3ac0d8fce882_31bf3856ad364e35_6.1.7601.24290_none_af9efa39b3b432fe [HRESULT = 0x800736b3 - ERROR_SXS_ASSEMBLY_NOT_FOUND]
2019-05-29 17:11:41, Info CBS Failed to get component state. [HRESULT = 0x800736b3 - ERROR_SXS_ASSEMBLY_NOT_FOUND]
2019-05-29 17:11:41, Info CBS Failed to get current state of the deployment [HRESULT = 0x800736b3 - ERROR_SXS_ASSEMBLY_NOT_FOUND]
2019-05-29 17:11:41, Info CBS Failed to get Transaction State for package: Package_381_for_KB4486563~31bf3856ad364e35~amd64~~6.1.1.4, update: 4486563-1319_neutral_LDR [HRESULT = 0x800736b3 - ERROR_SXS_ASSEMBLY_NOT_FOUND]
2019-05-29 17:11:41, Info CBS Failed to get current state. [HRESULT = 0x800736b3 - ERROR_SXS_ASSEMBLY_NOT_FOUND]
2019-05-29 17:11:41, Info CBS Failed to populate updates for package: Package_381_for_KB4486563~31bf3856ad364e35~amd64~~6.1.1.4 [HRESULT = 0x800736b3 - ERROR_SXS_ASSEMBLY_NOT_FOUND]
2019-05-29 17:11:41, Info CBS Failed to add child package to the strategy [HRESULT = 0x800736b3 - ERROR_SXS_ASSEMBLY_NOT_FOUND]
2019-05-29 17:11:41, Info CBS Failed to add child package to the strategy [HRESULT = 0x800736b3 - ERROR_SXS_ASSEMBLY_NOT_FOUND]
2019-05-29 17:11:41, Info CBS Failed to add package: Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24356.1.4 [HRESULT = 0x800736b3 - ERROR_SXS_ASSEMBLY_NOT_FOUND]
2019-05-29 17:11:41, Info CBS Failed to re-install supersed versions for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24411.1.8 [HRESULT = 0x800736b3 - ERROR_SXS_ASSEMBLY_NOT_FOUND]
2019-05-29 17:11:41, Info CBS Failed to process mum servicing on package:Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24411.1.8 [HRESULT = 0x800736b3 - ERROR_SXS_ASSEMBLY_NOT_FOUND]
2019-05-29 17:11:41, Info CBS Failed to add package: Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24411.1.8 [HRESULT = 0x800736b3 - ERROR_SXS_ASSEMBLY_NOT_FOUND]
2019-05-29 17:11:41, Info CBS Failed to recall or supersed lower version on package: Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24443.1.8 [HRESULT = 0x800736b3 - ERROR_SXS_ASSEMBLY_NOT_FOUND]
2019-05-29 17:11:41, Info CBS Failed to process mum servicing on package:Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24443.1.8 [HRESULT = 0x800736b3 - ERROR_SXS_ASSEMBLY_NOT_FOUND]
2019-05-29 17:11:41, Info CBS Failed to add package: Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24443.1.8 [HRESULT = 0x800736b3 - ERROR_SXS_ASSEMBLY_NOT_FOUND]
2019-05-29 17:11:41, Info CBS Failed to prepare starting packages [HRESULT = 0x800736b3 - ERROR_SXS_ASSEMBLY_NOT_FOUND]
2019-05-29 17:11:41, Error CBS Failed to process single phase execution. [HRESULT = 0x800736b3 - ERROR_SXS_ASSEMBLY_NOT_FOUND]
2019-05-29 17:11:41, Info CBS WER: Generating failure report for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24443.1.8, status: 0x800736b3, failure source: CBS Other, start state: Absent, target state: Installed, client id: WindowsUpdateAgent
2019-05-29 17:11:41, Info CBS Failed to query DisableWerReporting flag. Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2019-05-29 17:11:41, Info CBS Failed to add %windir%\winsxs\pending.xml to WER report because it is missing. Continuing without it...

Any advice or suggestions as to the next steps to resolve this issue would be greatly appreciated.
 

Attachments

Remove Update Manually
  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 command into it, then press enter.
    wusa /uninstall /KB:4486563
  4. Let me know if it says it was successful or if there are any errors.
 
It states that "The update KB4486563 is not installed on this computer". If you try to install the update it states "The update is not applicable to your computer".
 
Do not try to install KB4486563. Please follow the instructions only.

FRST Registry Search
  1. Click your Start button and choose Control Panel.
  2. In the upper right corner ensure the View by: is set to Category.
  3. Select the Programs group.
  4. Click the Turn Windows features on or off link. This will bring up the Server Manager dialog.
    Note: This loads your components hive which is what we want. Please keep this dialog open while you perform the remaining steps. You can minimize it if you wish but keep it open.
  5. Right-click on the file FRST64.exe and choose Run as administrator.
  6. Copy and paste KB4486563 into the Search box and click the Search Registry button.
  7. When the scan is complete, a message will display that 'SearchReg.txt' is saved in the same folder FRST was started from. Notepad will open this file also. Close Notepad and attach the file 'SearchReg.txt' to your next reply.
  8. You may close any remaining open windows now.
 
Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Post the logfile Fixlog.txt as attachment in your next reply.

Step 2:
Check Windows Update again and report the result.
 

Attachments

Great news - you have resolved my issue as after running the latest fix, the "2019-05 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4499164)" security update has now successfully been installed. Thank you for your all assistance in resolving this issue. It is very much appreciated. :-)
 

Attachments

Great.
You may remove all the tools and log files used in this thread to clean up.

Take care.
 
You must log in or register to reply here.

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

Back
Top