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

Demo2004 · Sep 20, 2022

Hi,

Error 0x80070002

Here is the log attached.

Maxstar · Sep 20, 2022

Rich (BB code):

2022-09-20 15:07:27, Error                 CSI    000003f9 (F) STATUS_OBJECT_NAME_NOT_FOUND #5365778# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0xc5ad0fb698->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[215]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1940 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-shell-customshellhost_31bf3856ad364e35_none_4677bde4d9fdb9aa\v!10.0.19041.[gle=0xd0000034]
2022-09-20 15:07:27, Error                 CSI    1620'; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 2903487536)[gle=0xd0000034]
2022-09-20 15:07:27, Error                 CSI    000003fa@2022/9/20:13:07:27.822 (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 15:07:27, Error                 CSI    000003fb (F) STATUS_OBJECT_NAME_NOT_FOUND #5365777# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0xc5ad0fb698->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[215]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1940 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-windows-shell-customshellhost_31bf3856ad364e35_none_4677bde4d9fdb9aa\v!10.0.19041.1620'; a:(OBJ_CASE[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, please try to update again, if it fails attach a new copy of the CBS log(s).

Demo2004 · Sep 20, 2022

Hi,

Error 0x80070002

Here is the log attached.

Maxstar · Sep 20, 2022

Rich (BB code):

2022-09-20 15:32:20, Error                 CSI    000003f9 (F) STATUS_OBJECT_NAME_NOT_FOUND #5365940# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0xa4e5bfb0b8->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[216]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1940 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-onecore-unifiedwritefilter-csp_31bf3856ad364e35_none_cf8d269ff40a90dc\v!10.0.19041[gle=0xd0000034]
2022-09-20 15:32:20, Error                 CSI    .1566'; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 3854544464)[gle=0xd0000034]
2022-09-20 15:32:20, Error                 CSI    000003fa@2022/9/20:13:32:20.547 (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 15:32:20, Error                 CSI    000003fb (F) STATUS_OBJECT_NAME_NOT_FOUND #5365939# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0xa4e5bfb0b8->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[216]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1940 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-onecore-unifiedwritefilter-csp_31bf3856ad364e35_none_cf8d269ff40a90dc\v!10.0.19041.1566'; 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, please try to update again, if it fails attach a new copy of the CBS log(s).

Demo2004 · Sep 20, 2022

Hi,

Error 0x800736b3

Here is the log attached.

Maxstar · Sep 20, 2022

Hi,

Please run Windows Update again while Process Monitor is running.

Step#1 - 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.

Demo2004 · Sep 21, 2022

Hi,

There is the link for file : GrosFichiers

Thanks

Maxstar · Sep 21, 2022

Hi,

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.

Afterwards, try to update Windows. If it fails attach a new copy of the CBS log.

Demo2004 · Sep 21, 2022

Hi,

Error message 0x80070002

Here is the log attached.

Maxstar · Sep 21, 2022

Rich (BB code):

2022-09-21 14:44:33, Error                 CSI    000003f9 (F) STATUS_OBJECT_NAME_NOT_FOUND #5386701# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0x649b57af88->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[205]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1940 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-emergencyupdate_31bf3856ad364e35_none_8074fbcf5676abe0\v!10.19044.19041.1645'; a:([gle=0xd0000034]
2022-09-21 14:44:33, Error                 CSI    OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 2606214432)[gle=0xd0000034]
2022-09-21 14:44:33, Error                 CSI    000003fa@2022/9/21:12:44:33.396 (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-21 14:44:33, Error                 CSI    000003fb (F) STATUS_OBJECT_NAME_NOT_FOUND #5386700# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0x649b57af88->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[205]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1940 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-emergencyupdate_31bf3856ad364e35_none_8074fbcf5676abe0\v!10.19044.19041.1645'; a:(OBJ_CASE_INSENSITI[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.

Demo2004 · Sep 21, 2022

Hi,

Error 0x80070002

Here is the log attached.

Maxstar · Sep 21, 2022

The CBS log shows the same error as in post #70, did you run DISM first (or something else) after the fix before attempt to update?

Demo2004 · Sep 21, 2022

Hi

I have a error 2 then run the dism command every time .

I retry a update, error 0x80070002

I have attached the log of DISM and CBS

Maxstar · Sep 21, 2022

Hi,

Demo2004 said:
I have a error 2 then run the dism command every time .

Please post a new copy of the 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.

Demo2004 · Sep 22, 2022

Hi,

Here is the components file attached.

Maxstar · Sep 22, 2022

Hi,

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.

Demo2004 · Sep 22, 2022

Hi,

Error 0x80070002

Error 2 again with the dism command also

Maxstar · Sep 22, 2022

Rich (BB code):

2022-09-22 10:12:28, Error                 CSI    00000428 (F) STATUS_OBJECT_NAME_NOT_FOUND #6653801# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0x67f7efcf28->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[214]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1940 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-updatetargeting-clientos_31bf3856ad364e35_none_77e01fe88a2b93a2\v!10.19042.19041.1[gle=0xd0000034]
2022-09-22 10:12:28, Error                 CSI    645'; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 4159687872)[gle=0xd0000034]
2022-09-22 10:12:28, Error                 CSI    00000429@2022/9/22:08:12:28.851 (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-22 10:12:28, Error                 CSI    0000042a (F) STATUS_OBJECT_NAME_NOT_FOUND #6653800# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0x67f7efcf28->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[214]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1940 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-updatetargeting-clientos_31bf3856ad364e35_none_77e01fe88a2b93a2\v!10.19042.19041.1645'; a:(OBJ_CASE_[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.

Demo2004 · Sep 22, 2022

Hi,

error code 0x80070002 again

dism error 2 also

Maxstar · Sep 22, 2022

Rich (BB code):

2022-09-22 10:43:24, Error                 CSI    0000040e (F) STATUS_OBJECT_NAME_NOT_FOUND #6006293# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0x965b9fb4f8->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[205]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1940 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-emergencyupdate_31bf3856ad364e35_none_8074fbcf5676abe0\v!10.19044.19041.1645'; a:([gle=0xd0000034]
2022-09-22 10:43:24, Error                 CSI    OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 1537192592)[gle=0xd0000034]
2022-09-22 10:43:24, Error                 CSI    0000040f@2022/9/22:08:43:24.204 (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-22 10:43:24, Error                 CSI    00000410 (F) STATUS_OBJECT_NAME_NOT_FOUND #6006292# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0x965b9fb4f8->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[205]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1940 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-emergencyupdate_31bf3856ad364e35_none_8074fbcf5676abe0\v!10.19044.19041.1645'; a:(OBJ_CASE_INSENSITI[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.

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

Active member

Attachments

Moderator, Windows Update Expert, Security Analyst

Attachments

Active member

Attachments

Moderator, Windows Update Expert, Security Analyst

Attachments

Active member

Attachments

Moderator, Windows Update Expert, Security Analyst

Active member

Moderator, Windows Update Expert, Security Analyst

Attachments

Active member

Attachments

Moderator, Windows Update Expert, Security Analyst

Attachments

Active member

Attachments

Moderator, Windows Update Expert, Security Analyst

Active member

Attachments

Moderator, Windows Update Expert, Security Analyst

Active member

Attachments

Moderator, Windows Update Expert, Security Analyst

Attachments

Active member

Attachments

Moderator, Windows Update Expert, Security Analyst

Attachments

Active member

Attachments

Moderator, Windows Update Expert, Security Analyst

Attachments