[WinServer2008R2] CSI Missing Identity in CheckSUR log

J

JPilot

New member
Joined
May 8, 2017
Posts
1
Can't install windows updates. Ran SFC /scannow and it didn't find any errors. Ran the system update readiness tool and get the following the CheckSUR log

Checking Windows Servicing Packages


Checking Package Manifests and Catalogs


Checking Package Watchlist


Checking Component Watchlist


Checking Packages


Checking Component Store
(f) CSI Missing Identity 0x00000000 appid c0b6066ffcd..8575a272b2f_b03f5f7f11d50a3a_6.1.7601.18529_b79c96324a24f83e
(f) CSI Missing Identity 0x00000000 appid 8c67a8b2cce..1153de5e1a6_b03f5f7f11d50a3a_6.1.7601.18523_f19a46f6cc658f11
(f) CSI Missing Identity 0x00000000 appid winusb.inf_31bf3856ad364e35_6.1.7601.17514_561ae9f52c40e492
(f) CSI Missing Identity 0x00000000 appid mchgr.inf_31bf3856ad364e35_6.1.7601.17514_7320af8f6febd179
(f) CSI Missing Identity 0x00000000 appid d69cba77ffe..982478bba7f_31bf3856ad364e35_6.1.7601.23002_5f74cdd44d0e50d1
(f) CSI Missing Identity 0x00000000 appid f81e4802240..be4ee21dba2_31bf3856ad364e35_6.1.7601.18615_4d918e1ebccf5d77
(f) CSI Missing Identity 0x00000000 identity x86_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.23037_none_a8cf913913d821da
(f) CSI Missing Identity 0x00000000 identity amd64_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.23037_none_04ee2cbccc359310
(f) CSI Missing Identity 0x00000000 appid b05bb26db5e..d2f7cb4272a_31bf3856ad364e35_7.2.7601.22787_fde0795a8c68fec5
(f) CSI Missing Identity 0x00000000 identity amd64_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.18833_none_0460b6a7b31b5aa8
(f) CSI Missing Identity 0x00000000 identity x86_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.18833_none_a8421b23fabde972
(f) CSI Missing Identity 0x00000000 appid f937d241483..1e67792f7e3_b03f5f7f11d50a3a_6.1.7601.22740_f3a58660beadb629
(f) CSI Missing Identity 0x00000000 appid e4683fbbeb0..6c51aa01337_b03f5f7f11d50a3a_6.1.7601.18529_b567988c168fd5f6


Summary:
Seconds executed: 107408
Found 13 errors
CSI Missing Identity Total count: 13

Is there a way to manually repair the CSI Missing Identity errors or is a in-place upgrade or reinstall the only options left?
 
Hello and welcome

Due to the precise nature of your corruption, you will receive help from a user named PeterJ. He's one of our senior trainees here who's in his final phrase of his studies and needs to gain some real world experience in specific areas of Windows Update. This means that he'll be assisting you, but that I will first need to double check and approve his fixes before he posts them to you. If anything this is a good thing for you because it means that you've got at least two of us watching over your thread, but it will unfortunately add a slight delay between each reply. I hope that you understand and can accept the need for us to train up new members in this way in order to carry on doing what we do here, however, if for any reason you object to this setup, I will happily take on your thread myself.

Thank you very much for your understanding. We'll be with you very shortly.
 
Hello and welcome.

Please post the complete CheckSur logfile as attachment.
 
This thread was originally started by someone that was helping me sort out these issues. If it's not a problem I would like to take over from this end to avoid a second middle man. Latest CheckSUR log is attached to this post.
 

Attachments

I should probably also mention that for this latest CheckSUR logfile I ran CheckSUR by using the command "DISM /Online /Cleanup-Image /Scanhealth" as recommended at The New and Improved CheckSUR | Ask the Core Team
I did this due to the fact that "Windows6.1-KB947821-v34-x64" took 107408 seconds (almost 30 hours) to run.
 
Follow the instructions below please.

WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system. If you need assistance with an issue, please start a new thread and someone will assist you shortly.


  • Download
    myjIXnC.png
    SFCFix and move the executable to your desktop.
  • Download the attachment SFCFixScript.txt and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
    1p8eDnI.gif
  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Open the file, then copy and paste its content in your next reply.
 

Attachments

SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-05-15 07:28:15.504
Microsoft Windows Server 2008 R2 Service Pack 1 - amd64
Using .txt script file at C:\Users\it\Desktop\SFCFixScript.txt [0]


RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\c0b6066ffcd..8575a272b2f_b03f5f7f11d50a3a_6.1.7601.18529_b79c96324a24f83e.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\8c67a8b2cce..1153de5e1a6_b03f5f7f11d50a3a_6.1.7601.18523_f19a46f6cc658f11.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\winusb.inf_31bf3856ad364e35_6.1.7601.17514_561ae9f52c40e492.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\mchgr.inf_31bf3856ad364e35_6.1.7601.17514_7320af8f6febd179.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\d69cba77ffe..982478bba7f_31bf3856ad364e35_6.1.7601.23002_5f74cdd44d0e50d1.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\f81e4802240..be4ee21dba2_31bf3856ad364e35_6.1.7601.18615_4d918e1ebccf5d77.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.23037_none_a8cf913913d821da.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.23037_none_04ee2cbccc359310.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.18833_none_0460b6a7b31b5aa8.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.18833_none_a8421b23fabde972.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\f937d241483..1e67792f7e3_b03f5f7f11d50a3a_6.1.7601.22740_f3a58660beadb629.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\e4683fbbeb0..6c51aa01337_b03f5f7f11d50a3a_6.1.7601.18529_b567988c168fd5f6.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\c0b6066ffcd..8575a272b2f_b03f5f7f11d50a3a_6.1.7601.18529_b79c96324a24f83e.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\8c67a8b2cce..1153de5e1a6_b03f5f7f11d50a3a_6.1.7601.18523_f19a46f6cc658f11.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\winusb.inf_31bf3856ad364e35_6.1.7601.17514_561ae9f52c40e492.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\mchgr.inf_31bf3856ad364e35_6.1.7601.17514_7320af8f6febd179.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\d69cba77ffe..982478bba7f_31bf3856ad364e35_6.1.7601.23002_5f74cdd44d0e50d1.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\f81e4802240..be4ee21dba2_31bf3856ad364e35_6.1.7601.18615_4d918e1ebccf5d77.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.23037_none_a8cf913913d821da.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.23037_none_04ee2cbccc359310.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.18833_none_0460b6a7b31b5aa8.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.18833_none_a8421b23fabde972.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\f937d241483..1e67792f7e3_b03f5f7f11d50a3a_6.1.7601.22740_f3a58660beadb629.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\e4683fbbeb0..6c51aa01337_b03f5f7f11d50a3a_6.1.7601.18529_b567988c168fd5f6.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\c0b6066ffcd..8575a272b2f_b03f5f7f11d50a3a_6.1.7601.18529_b79c96324a24f83e.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\8c67a8b2cce..1153de5e1a6_b03f5f7f11d50a3a_6.1.7601.18523_f19a46f6cc658f11.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\winusb.inf_31bf3856ad364e35_6.1.7601.17514_561ae9f52c40e492.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\mchgr.inf_31bf3856ad364e35_6.1.7601.17514_7320af8f6febd179.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\d69cba77ffe..982478bba7f_31bf3856ad364e35_6.1.7601.23002_5f74cdd44d0e50d1.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\f81e4802240..be4ee21dba2_31bf3856ad364e35_6.1.7601.18615_4d918e1ebccf5d77.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.23037_none_a8cf913913d821da.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.23037_none_04ee2cbccc359310.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.18833_none_0460b6a7b31b5aa8.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.18833_none_a8421b23fabde972.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\f937d241483..1e67792f7e3_b03f5f7f11d50a3a_6.1.7601.22740_f3a58660beadb629.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\e4683fbbeb0..6c51aa01337_b03f5f7f11d50a3a_6.1.7601.18529_b567988c168fd5f6.
RegistryScript:: directive completed successfully.


RegistryExport::
Successfully exported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\b05bb26db5e..d2f7cb4272a_31bf3856ad364e35_7.2.7601.22787_fde0795a8c68fec5.
[HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\b05bb26db5e..d2f7cb4272a_31bf3856ad364e35_7.2.7601.22787_fde0795a8c68fec5]
"p!CBS_package_1_for_kb2984981~31bf3856ad364e35~amd64~~6.1.1.1.2984_a88501b1d7280a3d"=hex:4d,\
00,00,00,01,00,00,00,50,61,63,6b,61,67,65,5f,31,5f,66,6f,72,5f,4b,42,32,39,\
38,34,39,38,31,7e,33,31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,7e,61,6d,\
64,36,34,7e,7e,36,2e,31,2e,31,2e,31,2e,32,39,38,34,39,38,31,2d,31,5f,6e,65,\
75,74,72,61,6c,5f,4c,44,52,33
"p!CBS_package_2_for_kb2984981~31bf3856ad364e35~amd64~~6.1.1.1.2984_2c50a58611769308"=hex:4d,\
00,00,00,01,00,00,00,50,61,63,6b,61,67,65,5f,32,5f,66,6f,72,5f,4b,42,32,39,\
38,34,39,38,31,7e,33,31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,7e,61,6d,\
64,36,34,7e,7e,36,2e,31,2e,31,2e,31,2e,32,39,38,34,39,38,31,2d,33,5f,6e,65,\
75,74,72,61,6c,5f,4c,44,52,33
Datablocks: O:SYD:AI(A;ID;KR;;;BU)(A;CIIOID;GR;;;BU)(A;ID;KA;;;BA)(A;CIIOID;GA;;;BA)(A;ID;KA;;;SY)(A;CIIOID;GA;;;SY)(A;CIIOID;GA;;;CO)
RegistryExport:: directive completed successfully.


Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 13 datablocks.
Finish time: 2017-05-15 07:28:18.316
Script hash: YQI83GMXz/pNUE+Bmg4BYc4nP2uksh98Z3arVvnWsJY=
----------------------EOF-----------------------
 
Step 1:
Re-install Windows Update (KB2984981):


Step 2:
Please run a new scan with the System Update Readiness Tool (SURT).
Provide the log as attachment in your next reply.
 
I am unable to uninstall KB2984981. I get the error, "An error has occurred. Not all of the updates were successfully uninstalled". I have restarted the computer to see if that helped and it appeared to install some updates when I did, but I am still unable to uninstall this one.

The following are the two updates that installed when I restarted, just in case you need to know:
Windows Malicious Software Removal Tool x64 - May 2017 (KB890830)
Cumulative Security Update for Internet Explorer 11 for Windows Server 2008 R2 for x64-based Systems (KB2987107)
 
I just attempted to do the uninstall using "wusa /uninstall /kb:2984981" via command prompt and received a more specific error.

Installer encountered an error: 0x800736b3


The referenced assembly is not installed on your system.
 
It gives me the message: Security Update for Windows (KB2984981) is already installed on this computer.
 
Follow the instructions below please.

Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system. If you need assistance with an issue, please start a new thread and someone will assist you shortly.


  • Download
    myjIXnC.png
    SFCFix and move the executable to your desktop.
  • Download the attachment SFCFixScript.txt and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
    1p8eDnI.gif
  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Open the file, then copy and paste its content in your next reply.


Step 2:
Please run a new scan with the System Update Readiness Tool (SURT).
Provide the log as attachment in your next reply.
 

Attachments

SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-05-17 15:40:53.846
Microsoft Windows Server 2008 R2 Service Pack 1 - amd64
Using .txt script file at C:\Users\it\Desktop\SFCFixScript.txt [0]


RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\b05bb26db5e..d2f7cb4272a_31bf3856ad364e35_7.2.7601.22787_fde0795a8c68fec5.
Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\b05bb26db5e..d2f7cb4272a_31bf3856ad364e35_7.2.7601.22787_fde0795a8c68fec5.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\CanonicalData\Deployments\b05bb26db5e..d2f7cb4272a_31bf3856ad364e35_7.2.7601.22787_fde0795a8c68fec5.
RegistryScript:: directive completed successfully.


Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 13 datablocks.
Finish time: 2017-05-17 15:40:54.078
Script hash: RlgZTmfrgmEXTsI3IFc2KKB41kUS3iPTphlpSQV5yDw=
----------------------EOF-----------------------
 

Attachments

CheckSUR found new problems and could fix them all.
Run Windows Updates again and report the result.
 
KB3092601 failed with error code: 8007371B


KB3122648 failed with error code: 80073712


KB3179573 failed with error code: 80073712


KB3172605 succeeded


KB4019112 failed with error code: 80073712


KB4019264 failed with error code: 80073712
 
Perform a SFC scan and post a logfile.

SFC Scan

  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

    Code: 
    sfc /scannow
    Wait for this to finish before you continue

    Code: 
    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
    Note: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the download link.
 
Try to install one of the updates that failed and if it fails again, post the CBS.log. (You don't have to run SFC first, just post the CBS.log.)
 
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