V ViKi67 New member Joined Nov 8, 2019 Posts 2 Nov 8, 2019 #1 Have got problems Update Win 2008R2 server - Get error 80073712. Have run System Readiness tool but not able to fix problem. CheckSUR.log Checking System Update Readiness. Binary Version 6.1.7601.22471 Package Version 26.0 2019-11-08 12:47 Checking Windows Servicing Packages Checking Package Manifests and Catalogs Checking Package Watchlist Checking Component Watchlist Checking Packages Checking Component Store (f) CSI Missing Deployment Key 0x00000000 47f06f7463d..9f2da657e19_31bf3856ad364e35_6.1.7601.23017_745e4849833a661d HKLM\Components\CanonicalData\Deployments (f) CSI Missing Deployment Key 0x00000000 46bea376c29..a09d67c6375_31bf3856ad364e35_6.1.7601.18812_264e0aab5acf74c5 HKLM\Components\CanonicalData\Deployments (f) CSI Missing Identity 0x00000000 identity x86_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.18833_none_a8421b23fabde972 (f) CSI Manifest Bad XML 0xC0150006 winsxs\Manifests\x86_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.18833_none_a8421b23fabde972.manifest x86_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.18833_none_a8421b23fabde972 (f) CSI Missing Deployment Key 0x00000000 251bc41103f..1cc74c71ce4_31bf3856ad364e35_6.1.7601.23017_9068ef3be6bb1cdb HKLM\Components\CanonicalData\Deployments (f) CSI Missing Identity 0x00000000 identity amd64_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.18833_none_0460b6a7b31b5aa8 (f) CSI Manifest Bad XML 0xC0150006 winsxs\Manifests\amd64_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.18833_none_0460b6a7b31b5aa8.manifest amd64_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.18833_none_0460b6a7b31b5aa8 (f) CSI Missing Deployment Key 0x00000000 d2a4b1fcace..9700ff63c81_31bf3856ad364e35_6.1.7601.23017_54195836b1774756 HKLM\Components\CanonicalData\Deployments (f) CSI C Mark Deployment Missing 0x00000000 c!b6e1254e594..152f1d8ea3a_31bf3856ad364e35_6.1.7601.18833_023df6b8c462dad5 amd64_microsoft-windows-c..order-adm.resources_31bf3856ad364e35_6.1.7601.18833_en-us_46cdefe8499ddf37 (f) CSI C Mark Deployment Missing 0x00000000 c!0e349f35c12..516851d6a8b_31bf3856ad364e35_6.1.7601.18812_c7a321654a95b65c wow64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.18812_none_e52b8aeaad8cedbc (f) CSI C Mark Deployment Missing 0x00000000 c!e09d7624f45..f2f7a602604_31bf3856ad364e35_6.1.7601.18833_529078f82c407f61 x86_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.18833_none_a8421b23fabde972 (f) CSI C Mark Deployment Missing 0x00000000 c!0e349f35c12..516851d6a8b_31bf3856ad364e35_6.1.7601.18812_c7a321654a95b65c x86_microsoft-windows-ncrypt-dll_31bf3856ad364e35_6.1.7601.18812_none_5fe3add34fe00616 (f) CSI C Mark Deployment Missing 0x00000000 c!0e349f35c12..516851d6a8b_31bf3856ad364e35_6.1.7601.18812_c7a321654a95b65c wow64_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.18812_none_a345e92ec7b73e6d (f) CSI C Mark Deployment Missing 0x00000000 c!e09d7624f45..f2f7a602604_31bf3856ad364e35_6.1.7601.18833_529078f82c407f61 amd64_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.18833_none_0460b6a7b31b5aa8 (f) CSI C Mark Deployment Missing 0x00000000 c!90ddcb4a5e7..28bb0f9fac5_31bf3856ad364e35_6.1.7601.23037_79439fb72a0aef66 amd64_microsoft-windows-c..order-adm.resources_31bf3856ad364e35_6.1.7601.23037_en-us_475b65fd62b8179f Summary: Seconds executed: 825 Found 15 errors CSI Manifest Bad XML Total count: 2 CSI Missing Deployment Key Total count: 4 CSI Missing Identity Total count: 2 CSI C Mark Deployment Missing Total count: 7 Unavailable repair files: winsxs\manifests\x86_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.18833_none_a8421b23fabde972.manifest winsxs\manifests\amd64_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.18833_none_0460b6a7b31b5aa8.manifest Have also tried SFCFix but looks like not able to fix. SFCfix.txt SFCFix version 3.0.2.1 by niemiro. Start time: 2019-11-08 12:30:15.436 Microsoft Windows Server 2008 R2 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: 15 SURT total unimportant corruption count: 0 SURT total fixed corruption count: 0 AutoAnalysis:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.2.1 by niemiro has completed. Currently storing 0 datablocks. Finish time: 2019-11-08 12:43:20.793 ----------------------EOF----------------------- Will appreciate any suggestions what to do to fix. Thanks in advance.
Have got problems Update Win 2008R2 server - Get error 80073712. Have run System Readiness tool but not able to fix problem. CheckSUR.log Checking System Update Readiness. Binary Version 6.1.7601.22471 Package Version 26.0 2019-11-08 12:47 Checking Windows Servicing Packages Checking Package Manifests and Catalogs Checking Package Watchlist Checking Component Watchlist Checking Packages Checking Component Store (f) CSI Missing Deployment Key 0x00000000 47f06f7463d..9f2da657e19_31bf3856ad364e35_6.1.7601.23017_745e4849833a661d HKLM\Components\CanonicalData\Deployments (f) CSI Missing Deployment Key 0x00000000 46bea376c29..a09d67c6375_31bf3856ad364e35_6.1.7601.18812_264e0aab5acf74c5 HKLM\Components\CanonicalData\Deployments (f) CSI Missing Identity 0x00000000 identity x86_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.18833_none_a8421b23fabde972 (f) CSI Manifest Bad XML 0xC0150006 winsxs\Manifests\x86_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.18833_none_a8421b23fabde972.manifest x86_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.18833_none_a8421b23fabde972 (f) CSI Missing Deployment Key 0x00000000 251bc41103f..1cc74c71ce4_31bf3856ad364e35_6.1.7601.23017_9068ef3be6bb1cdb HKLM\Components\CanonicalData\Deployments (f) CSI Missing Identity 0x00000000 identity amd64_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.18833_none_0460b6a7b31b5aa8 (f) CSI Manifest Bad XML 0xC0150006 winsxs\Manifests\amd64_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.18833_none_0460b6a7b31b5aa8.manifest amd64_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.18833_none_0460b6a7b31b5aa8 (f) CSI Missing Deployment Key 0x00000000 d2a4b1fcace..9700ff63c81_31bf3856ad364e35_6.1.7601.23017_54195836b1774756 HKLM\Components\CanonicalData\Deployments (f) CSI C Mark Deployment Missing 0x00000000 c!b6e1254e594..152f1d8ea3a_31bf3856ad364e35_6.1.7601.18833_023df6b8c462dad5 amd64_microsoft-windows-c..order-adm.resources_31bf3856ad364e35_6.1.7601.18833_en-us_46cdefe8499ddf37 (f) CSI C Mark Deployment Missing 0x00000000 c!0e349f35c12..516851d6a8b_31bf3856ad364e35_6.1.7601.18812_c7a321654a95b65c wow64_microsoft-windows-security-ntlm_31bf3856ad364e35_6.1.7601.18812_none_e52b8aeaad8cedbc (f) CSI C Mark Deployment Missing 0x00000000 c!e09d7624f45..f2f7a602604_31bf3856ad364e35_6.1.7601.18833_529078f82c407f61 x86_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.18833_none_a8421b23fabde972 (f) CSI C Mark Deployment Missing 0x00000000 c!0e349f35c12..516851d6a8b_31bf3856ad364e35_6.1.7601.18812_c7a321654a95b65c x86_microsoft-windows-ncrypt-dll_31bf3856ad364e35_6.1.7601.18812_none_5fe3add34fe00616 (f) CSI C Mark Deployment Missing 0x00000000 c!0e349f35c12..516851d6a8b_31bf3856ad364e35_6.1.7601.18812_c7a321654a95b65c wow64_microsoft-windows-security-digest_31bf3856ad364e35_6.1.7601.18812_none_a345e92ec7b73e6d (f) CSI C Mark Deployment Missing 0x00000000 c!e09d7624f45..f2f7a602604_31bf3856ad364e35_6.1.7601.18833_529078f82c407f61 amd64_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.18833_none_0460b6a7b31b5aa8 (f) CSI C Mark Deployment Missing 0x00000000 c!90ddcb4a5e7..28bb0f9fac5_31bf3856ad364e35_6.1.7601.23037_79439fb72a0aef66 amd64_microsoft-windows-c..order-adm.resources_31bf3856ad364e35_6.1.7601.23037_en-us_475b65fd62b8179f Summary: Seconds executed: 825 Found 15 errors CSI Manifest Bad XML Total count: 2 CSI Missing Deployment Key Total count: 4 CSI Missing Identity Total count: 2 CSI C Mark Deployment Missing Total count: 7 Unavailable repair files: winsxs\manifests\x86_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.18833_none_a8421b23fabde972.manifest winsxs\manifests\amd64_microsoft-windows-c..graphy-cryptoconfig_31bf3856ad364e35_6.1.7601.18833_none_0460b6a7b31b5aa8.manifest Have also tried SFCFix but looks like not able to fix. SFCfix.txt SFCFix version 3.0.2.1 by niemiro. Start time: 2019-11-08 12:30:15.436 Microsoft Windows Server 2008 R2 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: 15 SURT total unimportant corruption count: 0 SURT total fixed corruption count: 0 AutoAnalysis:: directive completed successfully. Successfully processed all directives. SFCFix version 3.0.2.1 by niemiro has completed. Currently storing 0 datablocks. Finish time: 2019-11-08 12:43:20.793 ----------------------EOF----------------------- Will appreciate any suggestions what to do to fix. Thanks in advance.
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Nov 8, 2019 #2 Hello and welcome! Has the RAM been tested/replaced recently?
V ViKi67 New member Joined Nov 8, 2019 Posts 2 Nov 8, 2019 #3 ViKi67 said: CheckSUR.log Checking System Update Readiness. Binary Version 6.1.7601.22471 Package Version 26.0 2019-11-08 12:47 Click to expand... Not experienced any other problems or instability with the server, but is not exactly in heavy use, so I'll try run a memory test on it this weekend. Thanks.
ViKi67 said: CheckSUR.log Checking System Update Readiness. Binary Version 6.1.7601.22471 Package Version 26.0 2019-11-08 12:47 Click to expand... Not experienced any other problems or instability with the server, but is not exactly in heavy use, so I'll try run a memory test on it this weekend. Thanks.
