[SOLVED] 2022-08 Windows Update(KB5016616) failed - 0x80073701
- Thread starter Demo2004
- Start date
Rich (BB code):
2022-09-19 13:06:09, Error CSI 000003f8 (F) STATUS_OBJECT_NAME_NOT_FOUND #3514594# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_ALL_ACCESS|KEY_WOW64_64KEY), oa = @0x5a4fffc108->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..21h2-ekb-deployment_31bf3856ad364e35_none_fad0b2aacf16a9bb\v!10.0[gle=0xd0000034]
2022-09-19 13:06:09, Error CSI .19041.1645'; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 1342160544)[gle=0xd0000034]
2022-09-19 13:06:09, Error CSI 000003f9@2022/9/19:11:06:09.426 (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-19 13:06:09, Error CSI 000003fa (F) STATUS_OBJECT_NAME_NOT_FOUND #3514593# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_ALL_ACCESS|KEY_WOW64_64KEY), oa = @0x5a4fffc108->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..21h2-ekb-deployment_31bf3856ad364e35_none_fad0b2aacf16a9bb\v!10.0.19041.1645'; a:(O[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.
- 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
Rich (BB code):
2022-09-19 14:25:07, Error CSI 00000403 (F) STATUS_OBJECT_NAME_NOT_FOUND #4007265# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_ALL_ACCESS|KEY_WOW64_64KEY), oa = @0xb20f17c098->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[216]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1940 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-e..iltercsp-deployment_31bf3856ad364e35_none_3b1938db2b13819a\v!10.0[gle=0xd0000034]
2022-09-19 14:25:07, Error CSI .19041.1566'; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 253214256)[gle=0xd0000034]
2022-09-19 14:25:07, Error CSI 00000404@2022/9/19:12:25:07.341 (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-19 14:25:07, Error CSI 00000405 (F) STATUS_OBJECT_NAME_NOT_FOUND #4007264# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_ALL_ACCESS|KEY_WOW64_64KEY), oa = @0xb20f17c098->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[216]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1940 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-e..iltercsp-deployment_31bf3856ad364e35_none_3b1938db2b13819a\v!10.0.19041.1566'; a:(O[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.
- 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
Rich (BB code):
2022-09-19 15:02:47, Error CSI 00000404 (F) STATUS_OBJECT_NAME_NOT_FOUND #4008152# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_ALL_ACCESS|KEY_WOW64_64KEY), oa = @0x6d1c7fc0a8->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[216]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1940 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-g..s-merged-deployment_31bf3856ad364e35_none_e0ba2b69d4e98685\v!10.0[gle=0xd0000034]
2022-09-19 15:02:47, Error CSI .19041.1620'; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 478133824)[gle=0xd0000034]
2022-09-19 15:02:47, Error CSI 00000405@2022/9/19:13:02:47.467 (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-19 15:02:47, Error CSI 00000406 (F) STATUS_OBJECT_NAME_NOT_FOUND #4008151# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_ALL_ACCESS|KEY_WOW64_64KEY), oa = @0x6d1c7fc0a8->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[216]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1940 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-g..s-merged-deployment_31bf3856ad364e35_none_e0ba2b69d4e98685\v!10.0.19041.1620'; a:(O[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.
- 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
Rich (BB code):
2022-09-19 15:28:25, Error CSI 000003f8 (F) STATUS_OBJECT_NAME_NOT_FOUND #3516592# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_ALL_ACCESS|KEY_WOW64_64KEY), oa = @0x841f3fbc58->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[216]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1940 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-o..s-merged-deployment_31bf3856ad364e35_none_760e228bf9975077\v!10.0[gle=0xd0000034]
2022-09-19 15:28:25, Error CSI .19041.1620'; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 524270064)[gle=0xd0000034]
2022-09-19 15:28:25, Error CSI 000003f9@2022/9/19:13:28:25.867 (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-19 15:28:25, Error CSI 000003fa (F) STATUS_OBJECT_NAME_NOT_FOUND #3516591# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_ALL_ACCESS|KEY_WOW64_64KEY), oa = @0x841f3fbc58->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[216]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1940 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-o..s-merged-deployment_31bf3856ad364e35_none_760e228bf9975077\v!10.0.19041.1620'; a:(O[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.
- 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 /RestoreHealthStep 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
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.
- 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
Rich (BB code):
2022-09-19 17:17:39, Error CSI 0000000f (F) STATUS_OBJECT_NAME_NOT_FOUND #603121# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0xed2f3fb118->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..21h1-ekb-deployment_31bf3856ad364e35_none_ea142d3a61eaba9c\v!10.0.19041.[gle=0xd0000034]
2022-09-19 17:17:39, Error CSI 1645'; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 792702640)[gle=0xd0000034]
2022-09-19 17:17:39, Error CSI 00000010@2022/9/19:15:17:39.154 (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-19 17:17:39, Error CSI 00000011 (F) STATUS_OBJECT_NAME_NOT_FOUND #603120# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0xed2f3fb118->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..21h1-ekb-deployment_31bf3856ad364e35_none_ea142d3a61eaba9c\v!10.0.19041.1645'; a:(OBJ_CASE[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.
- 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 /RestoreHealthHi,
Please run Windows Update again with Process Monitor running.
Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square (CTRL +E) on the toolbar as shown below.
4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up the LogFile.PML and upload it to WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free and provide the link.
Please run Windows Update again with Process Monitor running.
Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square (CTRL +E) on the toolbar as shown below.
4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up the LogFile.PML and upload it to WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free and provide the link.
Last edited:
Hi,
Here the link for the LogFile.PML
I used another transfer service because the Wetransfert limit without an account is 2GB because my zipped file is 3GB :
GrosFichiers
Thanks.
Here the link for the LogFile.PML
I used another transfer service because the Wetransfert limit without an account is 2GB because my zipped file is 3GB :
GrosFichiers
Thanks.
Hi,
Export CBS (Component Based Servicing) hive
Export CBS (Component Based Servicing) hive
- Click on the Start button and type regedit
- When you see regedit on the list, right-click on it and select Run as administrator.
- When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.
Code:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing - Once selected, click File > Export....
- Change the Save as type: to Registry Hive Files (*.*).
- Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
- Right-click on the saved file and choose Send > Compressed (zipped) Folder.
- Attach the .ZIP file to your next post.
- If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
Hi,
Here's the next fix.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
Afterwards, try to update Windows, if it fails attach a new copy of the CBS log.
Here's the next fix.
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.
- 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.
Afterwards, try to update Windows, if it fails attach a new copy of the CBS log.
Rich (BB code):
2022-09-20 14:10:52, Error CSI 000003f9 (F) STATUS_OBJECT_NAME_NOT_FOUND #5363345# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0x139107b4d8->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..corebase-deployment_31bf3856ad364e35_none_7b3158f27b64d2bf\v!10.0.19041[gle=0xd0000034]
2022-09-20 14:10:52, Error CSI .1620'; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 2433200752)[gle=0xd0000034]
2022-09-20 14:10:52, Error CSI 000003fa@2022/9/20:12:10:52.803 (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-20 14:10:52, Error CSI 000003fb (F) STATUS_OBJECT_NAME_NOT_FOUND #5363344# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0x139107b4d8->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..corebase-deployment_31bf3856ad364e35_none_7b3158f27b64d2bf\v!10.0.19041.1620'; a:(OBJ_CAS[gle=0xd0000034]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.
- 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.
Afterwards, try to update Windows, if it fails attach a new copy of the CBS log.
Has Sysnative Forums helped you? Please consider donating to help us support the site!