[SOLVED] 2022-08 Windows Update(KB5016616) failed - 0x80073701

Hi,

The update KB5017308 fail again but the error code change : 0x80073712

There is the CBS log and SFCFix.txt
 

Attachments

Rich (BB code):
2022-09-15 07:49:39, Error                 CSI    0000023f@2022/9/15:05:49:39.077 (F) onecore\base\wcp\componentstore\csd_core.cpp(659): Error STATUS_SXS_COMPONENT_STORE_CORRUPT originated in function CCSDirect::GetComponentManifest expression: (null)
[gle=0x80004005]
2022-09-15 07:49:39, Error                 CSI    00000240 (F) HRESULT_FROM_WIN32(14098) #2934606# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = Microsoft-Windows-PowerShell-V2-Deployment-LanguagePack, version 10.0.19041.1645, arch amd64, culture [l:5]'fr-FR', nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'Microsoft-Windows-PowerShell-V2-Client-Package~31bf3856ad364e35~amd64~fr-FR~10.0.19041.1645.MicrosoftWindowsPowerShellV2', rah = (null), manpath = (null), catpath = (null), ed = 0, disp [gle=0x80073712]
2022-09-15 07:49:39, Error                 CSI    = 0)[gle=0x80073712]
2022-09-15 07:49:39, Info                  CBS    Failed to pin deployment while resolving Update: Microsoft-Windows-PowerShell-V2-Client-Package~31bf3856ad364e35~amd64~fr-FR~10.0.19041.1645.MicrosoftWindowsPowerShellV2 from file: (null) [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-09-15 07:49:39, Info                  CBS    Failed to bulk stage deployment manifest and pin deployment for package:Microsoft-Windows-MSMQ-MMC-OptGroup-WOW64-Package~31bf3856ad364e35~amd64~~10.0.19041.1586 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]

Rich (BB code):
2022-09-15 07:49:25, Info                  CBS    Exec: Resolving Package: Microsoft-Windows-PowerShell-V2-Client-Package~31bf3856ad364e35~amd64~fr-FR~10.0.19041.1645, Update: MicrosoftWindowsPowerShellV2, PinDeployment: amd64_microsoft-windows-p..oyment-languagepack_31bf3856ad364e35_10.0.19041.1_fr-fr_8d37e6d7c9e1b92e

Rich (BB code):
2022-09-15 07:49:46, Error                 CBS    Failed to perform operation.  [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-09-15 07:49:46, Info                  CBS    Session: 30984389_2170788732 finalized. Reboot required: no [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-09-15 07:49:46, Info                  CBS    Failed finalizing session [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-09-15 07:49:46, Info                  CBS    Failed to call Process on TiWorker session [HRESULT = 0x80073712]
2022-09-15 07:50:14, Info                  CSI    00000244 Warning: Unable to repair manifest for component ([l:101 ml:140]'amd64_microsoft-windows-s..ubsystem-deployment_31bf3856ad364e35_10.0.19041.1620_none_43329109f88974ff') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-09-15 07:50:14, Info                  CSI    00000245 Warning: Unable to repair manifest for component ([l:101 ml:140]'amd64_microsoft-windows-s..hellhost-deployment_31bf3856ad364e35_10.0.19041.1620_none_bc8153b8f8a2e7b7') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-09-15 07:50:16, Info                  CSI    00000246 Warning: Unable to repair manifest for component ([l:101 ml:140]'amd64_microsoft-windows-u..ntos-ekb-deployment_31bf3856ad364e35_10.0.19041.1645_none_2f8069b4cff884b7') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-09-15 07:50:16, Info                  CSI    00000247 Warning: Unable to repair manifest for component ([l:101 ml:140]'amd64_microsoft-windows-p..data-ekb-deployment_31bf3856ad364e35_10.0.19041.1645_none_483f872b98892e4f') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-09-15 07:50:16, Info                  CSI    00000248 Warning: Unable to repair manifest for component ([l:101 ml:140]'amd64_microsoft-windows-u..21h1-ekb-deployment_31bf3856ad364e35_10.0.19041.1645_none_4c89ca868d006f82') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-09-15 07:50:16, Info                  CSI    00000249 Warning: Unable to repair manifest for component ([l:101 ml:140]'amd64_microsoft-windows-p..21h2-ekb-deployment_31bf3856ad364e35_10.0.19041.1645_none_735e6014b4c427c1') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-09-15 07:50:16, Info                  CSI    0000024a Warning: Unable to repair manifest for component ([l:101 ml:140]'amd64_microsoft-windows-u..21h2-ekb-deployment_31bf3856ad364e35_10.0.19041.1645_none_9040f7d0b675076b') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-09-15 07:50:30, Info                  CSI    0000024b Warning: Unable to repair manifest for component ([l:102 ml:140]'amd64_microsoft-windows-p..oyment-languagepack_31bf3856ad364e35_10.0.19041.1645_fr-fr_32f349638c2fddd9') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-09-15 07:50:30, Info                  CSI    0000024c Warning: Unable to repair manifest for component ([l:102 ml:140]'amd64_microsoft-windows-e..oyment-languagepack_31bf3856ad364e35_10.0.19041.1645_fr-fr_9bd811dd825c04b6') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-09-15 07:50:33, Info                  CSI    0000024d Warning: Unable to repair manifest for component ([l:102 ml:140]'amd64_microsoft-windows-c..equired-deployment0_31bf3856ad364e35_10.0.19041.1620_fr-fr_036f589107afeece') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-09-15 07:50:48, Info                  CSI    0000024e Warning: Unable to repair manifest for component ([l:102 ml:140]'amd64_microsoft-windows-c..red-deployment01100_31bf3856ad364e35_10.0.19041.1620_fr-fr_cd53e3049e9b4664') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-09-15 07:51:12, Info                  CSI    0000024f Warning: Unable to repair manifest for component ([l:102 ml:140]'amd64_microsoft-windows-c..uired-deployment010_31bf3856ad364e35_10.0.19041.1620_fr-fr_5f089043decaa227') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-09-15 07:51:21, Error                 CSI    00000250@2022/9/15:05:51:21.977 (F) Attempting to mark store corrupt with category [l:15 ml:16]'CorruptManifest'[gle=0x80004005]

Hi,

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Last edited:
Hi,

I have a error when i execute the command "DISM /online /cleanup-image /RestoreHealth" --> error 2

In joined the dism log here with CBS and SFCfix.txt

Windows update error 0x80073712
 

Attachments

Hi,

Please upload a new copy of your COMPONENTS hive.

Upload your COMPONENTS hive.
  • Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
  • Please copy this file to your desktop.
  • Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
  • Right-click on this file on your desktop and select Send To > Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
 
Rich (BB code):
2022-09-15 19:39:02, Error                 CSI    0000021f (F) HRESULT_FROM_WIN32(14098) #914640# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = Microsoft-Windows-GroupPolicy-ClientTools-merged-Deployment-LanguagePack, version 10.0.19041.1620, arch amd64, culture [l:5]'fr-FR', nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'Microsoft-Windows-GroupPolicy-ClientTools-merged-Package~31bf3856ad364e35~amd64~fr-FR~10.0.19041.1620.64aeffcf1ed3cb7ca29738c4a2e80bbe', rah = (null), manpath = (null), c[gle=0x80073712]
2022-09-15 19:39:02, Error                 CSI    atpath = (null), ed = 0, disp = 0)[gle=0x80073712]
2022-09-15 19:39:02, Info                  CBS    Failed to pin deployment while resolving Update: Microsoft-Windows-GroupPolicy-ClientTools-merged-Package~31bf3856ad364e35~amd64~fr-FR~10.0.19041.1620.64aeffcf1ed3cb7ca29738c4a2e80bbe from file: (null) [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
2022-09-15 19:39:02, Info                  CBS    Failed to bulk stage deployment manifest and pin deployment for package:Microsoft-Windows-MSMQ-MMC-OptGroup-WOW64-Package~31bf3856ad364e35~amd64~~10.0.19041.1586 [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]

Rich (BB code):
2022-09-15 19:38:28, Info                  CBS    Exec: Resolving Package: Microsoft-Windows-GroupPolicy-ClientTools-merged-Package~31bf3856ad364e35~amd64~fr-FR~10.0.19041.1620, Update: 64aeffcf1ed3cb7ca29738c4a2e80bbe, PinDeployment: amd64_microsoft-windows-g..oyment-languagepack_31bf3856ad364e35_10.0.19041.1620_fr-fr_dcb9ae1363a133c3

Rich (BB code):
2022-09-15 19:02:04, Error                 CSI    00000009 (F) STATUS_OBJECT_NAME_NOT_FOUND #467822# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0x2efd7b218->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[216]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1940 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-s..hellhost-deployment_31bf3856ad364e35_none_23abd42e1d11b5d4\v!10.0.19041.1[gle=0xd0000034]
2022-09-15 19:02:04, Error                 CSI    620'; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 4023889840)[gle=0xd0000034]
2022-09-15 19:02:04, Error                 CSI    0000000a@2022/9/15:17:02:04.301 (F) onecore\base\wcp\sil\ntsystem.cpp(5363): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null)
[gle=0x80004005]

Rich (BB code):
2022-09-15 19:02:03, Info                  CSI    00000007 Warning: Unable to repair manifest for component ([l:101 ml:140]'amd64_microsoft-windows-s..corebase-deployment_31bf3856ad364e35_10.0.19041.1620_none_6575e2a7a7b6e374') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-09-15 19:02:03, Error                 CSI    00000008@2022/9/15:17:02:03.668 (F) onecore\base\wcp\sil\ntsystem.cpp(5363): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null)
[gle=0x80004005]

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Rich (BB code):
2022-09-16 10:15:24, Error                 CSI    00000237 (F) STATUS_SXS_ASSEMBLY_MISSING #1490303# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 2[gle=0xd015000c]
2022-09-16 10:15:24, Error                 CSI    00000238 (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #1490158# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = microsoft-windows-client-desktop-required-deployment01110, version 10.0.19041.1586, arch amd64, culture [l:5]'fr-FR', nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'Microsoft-Windows-Client-Desktop-Required-Package0111~31bf3856ad364e35~amd64~fr-FR~10.0.19041.1586.6d32b8512538c3869c96ab14705c23f3', rah = (null), manpath = (null[gle=0x80073701]
2022-09-16 10:15:24, Error                 CSI    ), catpath = (null), ed = 0, disp = 0)[gle=0x80073701]
2022-09-16 10:15:24, Info                  CBS    Failed to pin deployment while resolving Update: Microsoft-Windows-Client-Desktop-Required-Package0111~31bf3856ad364e35~amd64~fr-FR~10.0.19041.1586.6d32b8512538c3869c96ab14705c23f3 from file: (null) [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2022-09-16 10:15:24, Info                  CBS    Failed to bulk stage deployment manifest and pin deployment for package:Microsoft-Windows-MSMQ-MMC-OptGroup-WOW64-Package~31bf3856ad364e35~amd64~~10.0.19041.1586 [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]

Rich (BB code):
2022-09-16 10:15:11, Info                  CBS    Exec: Resolving Package: Microsoft-Windows-Client-Desktop-Required-Package0111~31bf3856ad364e35~amd64~fr-FR~10.0.19041.1586, Update: 6d32b8512538c3869c96ab14705c23f3, PinDeployment: amd64_microsoft-windows-c..red-deployment01110_31bf3856ad364e35_10.0.19041.1586_fr-fr_cd652c469e8d759a

Rich (BB code):
2022-09-16 10:15:47, Error                 CSI    0000023e (F) STATUS_OBJECT_NAME_NOT_FOUND #2045757# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0xb8ff07d2c8->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[216]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1940 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-u..ntos-ekb-deployment_31bf3856ad364e35_none_2adc867976eb9bcf\v!10.0.19041[gle=0xd0000034]
2022-09-16 10:15:47, Error                 CSI    .1645'; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 4278702176)[gle=0xd0000034]
2022-09-16 10:15:47, Error                 CSI    0000023f@2022/9/16:08:15:47.771 (F) onecore\base\wcp\sil\ntsystem.cpp(5363): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null)
[gle=0x80004005]
2022-09-16 10:15:47, Error                 CSI    00000240 (F) STATUS_OBJECT_NAME_NOT_FOUND #2045756# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0xb8ff07d2c8->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[216]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1940 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-u..ntos-ekb-deployment_31bf3856ad364e35_none_2adc867976eb9bcf\v!10.0.19041.1645'; a:(OBJ_CAS[gle=0xd0000034]

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFixScript.txt and save it to your desktop.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
62151e1bebac4-SFCFix-Txt-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.



Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log. (p.s. I don't need the DISM log for now)
Code:
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Last edited:
Rich (BB code):
2022-09-16 11:10:11, Error                 CSI    00000236 (F) STATUS_SXS_ASSEMBLY_MISSING #2912597# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 2[gle=0xd015000c]
2022-09-16 11:10:11, Error                 CSI    00000237 (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #2912452# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = microsoft-windows-client-desktop-required-deployment01120, version 10.0.19041.1620, arch amd64, culture [l:5]'fr-FR', nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'Microsoft-Windows-Client-Desktop-Required-Package0112~31bf3856ad364e35~amd64~fr-FR~10.0.19041.1620.4DCB7FA34F991DAE5CE511A14DB76894D9B427AC069E171D87D4611A0E16CDCE[gle=0x80073701]
2022-09-16 11:10:11, Error                 CSI    ', rah = (null), manpath = (null), catpath = (null), ed = 0, disp = 0)[gle=0x80073701]
2022-09-16 11:10:11, Info                  CBS    Failed to pin deployment while resolving Update: Microsoft-Windows-Client-Desktop-Required-Package0112~31bf3856ad364e35~amd64~fr-FR~10.0.19041.1620.4DCB7FA34F991DAE5CE511A14DB76894D9B427AC069E171D87D4611A0E16CDCE from file: (null) [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2022-09-16 11:10:11, Info                  CBS    Failed to bulk stage deployment manifest and pin deployment for package:Microsoft-Windows-MSMQ-MMC-OptGroup-WOW64-Package~31bf3856ad364e35~amd64~~10.0.19041.1586 [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]

Rich (BB code):
2022-09-16 11:09:56, Info                  CBS    Exec: Resolving Package: Microsoft-Windows-Client-Desktop-Required-Package0112~31bf3856ad364e35~amd64~fr-FR~10.0.19041.1620, Update: 4DCB7FA34F991DAE5CE511A14DB76894D9B427AC069E171D87D4611A0E16CDCE, PinDeployment: amd64_microsoft-windows-c..red-deployment01120_31bf3856ad364e35_10.0.19041.1620_fr-fr_cd55e3989e997912

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFixScript.txt and save it to your desktop.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
62151e1bebac4-SFCFix-Txt-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Rich (BB code):
2022-09-16 11:46:26, Error                 CSI    00000236 (F) STATUS_SXS_ASSEMBLY_MISSING #2914427# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 2[gle=0xd015000c]
2022-09-16 11:46:26, Error                 CSI    00000237 (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #2914282# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = microsoft-windows-client-desktop-required-deployment01130, version 10.0.19041.1566, arch amd64, culture [l:5]'fr-FR', nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'Microsoft-Windows-Client-Desktop-Required-Package0113~31bf3856ad364e35~amd64~fr-FR~10.0.19041.1566.2d313237b25ffbc04c29c86c30823f31', rah = (null), manpath = (null[gle=0x80073701]
2022-09-16 11:46:26, Error                 CSI    ), catpath = (null), ed = 0, disp = 0)[gle=0x80073701]
2022-09-16 11:46:26, Info                  CBS    Failed to pin deployment while resolving Update: Microsoft-Windows-Client-Desktop-Required-Package0113~31bf3856ad364e35~amd64~fr-FR~10.0.19041.1566.2d313237b25ffbc04c29c86c30823f31 from file: (null) [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2022-09-16 11:46:26, Info                  CBS    Failed to bulk stage deployment manifest and pin deployment for package:Microsoft-Windows-MSMQ-MMC-OptGroup-WOW64-Package~31bf3856ad364e35~amd64~~10.0.19041.1586 [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]

Rich (BB code):
2022-09-16 11:46:12, Info                  CBS    Exec: Resolving Package: Microsoft-Windows-Client-Desktop-Required-Package0113~31bf3856ad364e35~amd64~fr-FR~10.0.19041.1566, Update: 2d313237b25ffbc04c29c86c30823f31, PinDeployment: amd64_microsoft-windows-c..red-deployment01130_31bf3856ad364e35_10.0.19041.1566_fr-fr_cd652c469e8d759a

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Rich (BB code):
2022-09-16 14:32:51, Error                 CSI    00000246 (F) STATUS_SXS_ASSEMBLY_MISSING #3446907# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 2[gle=0xd015000c]
2022-09-16 14:32:51, Error                 CSI    00000247 (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #3446762# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = microsoft-windows-client-desktop-required-wow64-deployment0, version 10.0.19041.1620, arch amd64, culture [l:5]'fr-FR', nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'Microsoft-Windows-Client-Desktop-Required-WOW64-Package~31bf3856ad364e35~amd64~fr-FR~10.0.19041.1620.607BA8A22EDB6B70993764733A22879AB49F22EF34195FE33B5C0F0A3D73[gle=0x80073701]
2022-09-16 14:32:51, Error                 CSI    A618', rah = (null), manpath = (null), catpath = (null), ed = 0, disp = 0)[gle=0x80073701]
2022-09-16 14:32:51, Info                  CBS    Failed to pin deployment while resolving Update: Microsoft-Windows-Client-Desktop-Required-WOW64-Package~31bf3856ad364e35~amd64~fr-FR~10.0.19041.1620.607BA8A22EDB6B70993764733A22879AB49F22EF34195FE33B5C0F0A3D73A618 from file: (null) [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2022-09-16 14:32:51, Info                  CBS    Failed to bulk stage deployment manifest and pin deployment for package:Microsoft-Windows-MSMQ-MMC-OptGroup-WOW64-Package~31bf3856ad364e35~amd64~~10.0.19041.1586 [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]

Rich (BB code):
2022-09-16 14:32:34, Info                  CBS    Exec: Resolving Package: Microsoft-Windows-Client-Desktop-Required-WOW64-Package~31bf3856ad364e35~amd64~fr-FR~10.0.19041.1620, Update: 607BA8A22EDB6B70993764733A22879AB49F22EF34195FE33B5C0F0A3D73A618, PinDeployment: amd64_microsoft-windows-c..d-wow64-deployment0_31bf3856ad364e35_10.0.19041.1620_fr-fr_d15923994fa0acc4

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFixScript.txt and save it to your desktop.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
62151e1bebac4-SFCFix-Txt-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Rich (BB code):
2022-09-16 15:07:19, Error                 CSI    00000246 (F) STATUS_SXS_ASSEMBLY_MISSING #3447779# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 2[gle=0xd015000c]
2022-09-16 15:07:19, Error                 CSI    00000247 (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #3447634# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = Microsoft-Windows-GroupPolicy-Management-Tools-FoD-Deployment, version 10.0.19041.1566, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'Microsoft-Windows-GroupPolicy-Management-Tools-FoD-Package~31bf3856ad364e35~amd64~~10.0.19041.1566.f27544fe6e0607c248490e4f9e04f7b9', rah = (null), manpath = (null), catpath = (null[gle=0x80073701]
2022-09-16 15:07:19, Error                 CSI    ), ed = 0, disp = 0)[gle=0x80073701]
2022-09-16 15:07:19, Info                  CBS    Failed to pin deployment while resolving Update: Microsoft-Windows-GroupPolicy-Management-Tools-FoD-Package~31bf3856ad364e35~amd64~~10.0.19041.1566.f27544fe6e0607c248490e4f9e04f7b9 from file: (null) [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2022-09-16 15:07:19, Info                  CBS    Failed to bulk stage deployment manifest and pin deployment for package:Microsoft-Windows-MSMQ-MMC-OptGroup-WOW64-Package~31bf3856ad364e35~amd64~~10.0.19041.1586 [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]

Rich (BB code):
2022-09-16 15:07:05, Info                  CBS    Exec: Resolving Package: Microsoft-Windows-GroupPolicy-Management-Tools-FoD-Package~31bf3856ad364e35~amd64~~10.0.19041.1566, Update: f27544fe6e0607c248490e4f9e04f7b9, PinDeployment: amd64_microsoft-windows-g..ools-fod-deployment_31bf3856ad364e35_10.0.19041.1566_none_1c3d3fd6fa2f0dd1
2022-09-16 15:07:05, Info                  CBS    Exec: Resolving Package: Microsoft-Windows-DirectoryServices-DomainController-Tools-Client-Package~31bf3856ad364e35~amd64~~10.0.19041.1586, Update: c4531fdd1b0b614d3d0ee80f22d54c67, PinDeployment: amd64_microsoft-windows-d..s-client-deployment_31bf3856ad364e35_10.0.19041.1586_none_c8b8243089802f8c
2022-09-16 15:07:05, Info                  CBS    Exec: Resolving Package: Microsoft-Windows-Embedded-UnifiedWriteFilterCSP-Package~31bf3856ad364e35~amd64~~10.0.19041.1566, Update: bc07459e74891aac47d4de21a6aa5697, PinDeployment: amd64_microsoft-windows-e..iltercsp-deployment_31bf3856ad364e35_10.0.19041.1566_none_05baa9937a87a0f2
2022-09-16 15:07:05, Info                  CBS    Exec: Resolving Package: Microsoft-Windows-GroupPolicy-ClientTools-merged-Package~31bf3856ad364e35~amd64~~10.0.19041.1620, Update: 0ce669e0eba7422a53347cd6fcb4e477, PinDeployment: amd64_microsoft-windows-g..s-merged-deployment_31bf3856ad364e35_10.0.19041.1620_none_86afe401820c917e
2022-09-16 15:07:05, Info                  CBS    Exec: Resolving Package: Microsoft-Windows-OfflineFiles-merged-Package~31bf3856ad364e35~amd64~~10.0.19041.1620, Update: 0e75c6575e2253da1b2bfc45ac2f386a, PinDeployment: amd64_microsoft-windows-o..s-merged-deployment_31bf3856ad364e35_10.0.19041.1620_none_9017c7b237f077fc

Hi,

Here's the next fix to restore several missing component and deployments keys at once.

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFixScript.txt and save it to your desktop.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
62151e1bebac4-SFCFix-Txt-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Hi,

I have a other error : 0x80070002

The command "DISM /online /cleanup-image /RestoreHealth" return also a error 2, but in the log file error 0x80070002.

Here is the log attached.
 

Attachments

Rich (BB code):
2022-09-19 10:22:04, Info                  CSI    00000009 Warning: Unable to repair manifest for component ([l:101 ml:140]'amd64_microsoft-windows-e..iltercsp-deployment_31bf3856ad364e35_10.0.19041.1566_none_05baa9937a87a0f2') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-09-19 10:22:04, Info                  CSI    0000000a Warning: Unable to repair manifest for component ([l:101 ml:140]'amd64_microsoft-windows-g..ools-fod-deployment_31bf3856ad364e35_10.0.19041.1566_none_1c3d3fd6fa2f0dd1') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-09-19 10:22:04, Info                  CSI    0000000b Warning: Unable to repair manifest for component ([l:101 ml:140]'amd64_microsoft-windows-d..s-client-deployment_31bf3856ad364e35_10.0.19041.1586_none_c8b8243089802f8c') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-09-19 10:22:05, Info                  CSI    0000000c Warning: Unable to repair manifest for component ([l:101 ml:140]'amd64_microsoft-windows-g..s-merged-deployment_31bf3856ad364e35_10.0.19041.1620_none_86afe401820c917e') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-09-19 10:22:05, Info                  CSI    0000000d Warning: Unable to repair manifest for component ([l:101 ml:140]'amd64_microsoft-windows-o..s-merged-deployment_31bf3856ad364e35_10.0.19041.1620_none_9017c7b237f077fc') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-09-19 10:22:05, Info                  CSI    0000000e Warning: Unable to repair manifest for component ([l:100 ml:140]'amd64_microsoft-windows-shell-customshellhost_31bf3856ad364e35_10.0.19041.1620_none_fd2e23f85456c531') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-09-19 10:22:05, Info                  CSI    0000000f Warning: Unable to repair manifest for component ([l:90 ml:140]'amd64_microsoft-emergencyupdate_31bf3856ad364e35_10.19042.19041.1645_none_4c454a2635ca12c6') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-09-19 10:22:05, Info                  CSI    00000010 Warning: Unable to repair manifest for component ([l:99 ml:140]'amd64_microsoft-updatetargeting-clientos_31bf3856ad364e35_10.19042.19041.1645_none_00ead4c7646decf4') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-09-19 10:22:05, Info                  CSI    00000011 Warning: Unable to repair manifest for component ([l:87 ml:140]'amd64_microsoft-product-data_31bf3856ad364e35_10.19042.19041.1645_none_f738a4ec0fc03b82') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-09-19 10:22:05, Info                  CSI    00000012 Warning: Unable to repair manifest for component ([l:87 ml:140]'wow64_microsoft-product-data_31bf3856ad364e35_10.19042.19041.1645_none_018d4f3e4420fd7d') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2022-09-19 10:22:05, Error                 CSI    00000013@2022/9/19:08:22:05.895 (F) onecore\base\wcp\sil\ntsystem.cpp(5363): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null)
[gle=0x80004005]

Hi,

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealth
 

Attachments

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

Back
Top