[SOLVED] W10 2022-09 KB5017308 0x80073701

Asteroza · Sep 16, 2022

Was setting up some new laptops recently, and they had august updates but I wanted to get the September ones in, and 2 got stuck on the September KB5017308 update somehow. It downloads, installs to 20%, gets stuck for a while, then goes to 100% and errors out 0x80073701.

SFC /scannow is clear
dism scan/check/restore clear
SFCfix finds nothing

CBS file here
CBS

trolling the logs does bring up this though

Code:

2022-09-16 15:19:49, Info                  CBS    Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2022-09-16 15:19:49, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2022-09-16 15:19:49, Info                  CBS    Not able to add poqexec.log to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2022-09-16 15:19:49, Info                  CBS    Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2022-09-16 15:19:50, Error                 CSI    0000006f (F) STATUS_SXS_ASSEMBLY_MISSING #2566120# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 2[gle=0xd015000c]
2022-09-16 15:19:50, Error                 CSI    00000070 (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #2565975# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = Microsoft-PPIProjection-Deployment, version 10.0.19041.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'Microsoft-PPIProjection-Package~31bf3856ad364e35~amd64~~10.0.19041.1.fa2fd5786b7a45b84c1df1cc8b01f97d', rah = (null), manpath = (null), catpath = (null), ed = 0, disp = 0)[gle=0x80073701]
2022-09-16 15:19:50, Info                  CBS    Failed to pin deployment while resolving Update: Microsoft-PPIProjection-Package~31bf3856ad364e35~amd64~~10.0.19041.1.fa2fd5786b7a45b84c1df1cc8b01f97d from file: (null) [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2022-09-16 15:19:50, Info                  CBS    Failed to bulk stage deployment manifest and pin deployment for package:Microsoft-Windows-WMPNetworkSharingService-Opt-WOW64-Package~31bf3856ad364e35~amd64~~10.0.19041.746 [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2022-09-16 15:19:50, Info                  CBS    CommitPackagesState: Started persisting state of packages
2022-09-16 15:19:50, Info                  CBS    CommitPackagesState: Completed persisting state of packages
2022-09-16 15:19:50, Info                  CSI    00000071@2022/9/16:06:19:50.173 CSI Transaction @0x10a2b341650 destroyed
2022-09-16 15:19:50, Info                  CBS    Perf: Resolve chain complete.
2022-09-16 15:19:50, Info                  CBS    Failed to resolve execution chain. [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2022-09-16 15:19:50, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2022-09-16 15:19:50, Info                  CBS    WER: Generating failure report for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.2006.1.7, status: 0x80073701, failure source: Resolve, start state: Absent, target state: Installed, client id: UpdateAgentLCU
2022-09-16 15:19:50, Info                  CBS    Not able to query DisableWerReporting flag.  Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

Also, does anybody offhand what URL SFCfix is accessing at Stage 1?

Maxstar · Sep 18, 2022

Hi,

Download

SFCFix and save it to your desktop.

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. If it fails attach a new copy of the CBS logs.

Asteroza · Sep 18, 2022

Update again stops at 20% for a bit, then jumps to 74% for bit, then jumps to 100%, then errors out. New error number 0x80073712.

CBS

Maxstar · Sep 19, 2022

Hi,

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.

Asteroza · Sep 19, 2022

COMPONENTS

Maxstar · Sep 19, 2022

Let's check the following file: C:\Windows\WinSxS\Manifests\amd64_microsoft-ppiprojection-deployment_31bf3856ad364e35_10.0.19041.1503_none_40aa0391982d623d.manifest

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.

Asteroza · Sep 19, 2022

Here you go

Maxstar · Sep 20, 2022

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.

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

Asteroza · Sep 20, 2022

DISM errors out

[=================== 33.9% ]
Error: 2

The system cannot find the file specified.

Maxstar · Sep 20, 2022

Please post the latest CBS log(s) as well.

Asteroza · Sep 20, 2022

Maxstar · Sep 20, 2022

Rich (BB code):

2022-09-20 16:31:10, Error                 CSI    00000008 (F) STATUS_OBJECT_NAME_NOT_FOUND #374275# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0xd48117ae58->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[207]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1940 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-ppiprojection-deployment_31bf3856ad364e35_none_59bdf943d2736f22\v!10.0.19041.1'; a:[gle=0xd0000034]
2022-09-20 16:31:10, Error                 CSI    (OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 2165812208)[gle=0xd0000034]
2022-09-20 16:31:10, Error                 CSI    00000009@2022/9/20:07:31:10.673 (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 16:31:10, Error                 CSI    0000000a (F) STATUS_OBJECT_NAME_NOT_FOUND #374274# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0xd48117ae58->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[207]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1940 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-ppiprojection-deployment_31bf3856ad364e35_none_59bdf943d2736f22\v!10.0.19041.1'; a:(OBJ_CASE_INSENSIT[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

Asteroza · Sep 20, 2022

fix applied
dism returns no errors
ran sfc /scannow twice, no errors
reboot
ran windows update
there was a .net update that ran fine, but KB5017308 errored out 0x800736b3

CBS

Maxstar · Sep 21, 2022

Hi,

Please attempt to update Windows with Process Monitor 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.

Asteroza · Sep 21, 2022

LogFile

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.

Asteroza · Sep 22, 2022

SFCfix runs without error
reboot
Windows update KB5017308 still does the 20-74-100% install chugging then errors out the same 0x800736b3

CBS

Maxstar · Sep 23, 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.

Asteroza · Sep 25, 2022

SFCfix no error

Windows update KB5017308 still does the 20-74-100% install chugging then errors out with new error 0x80070002

CBS

Maxstar · Sep 26, 2022

Rich (BB code):

2022-09-26 09:02:00, Error                 CSI    000002bf (F) STATUS_OBJECT_NAME_NOT_FOUND #2329846# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0xd5a347b3d8->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[205]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1940 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-ppiprojection.appxmain_31bf3856ad364e35_none_6a8dd3c5bb4473fe\v!10.0.19041.1'; a:([gle=0xd0000034]
2022-09-26 09:02:00, Error                 CSI    OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 2739384688)[gle=0xd0000034]
2022-09-26 09:02:00, Error                 CSI    000002c0@2022/9/26:00:02:00.107 (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-26 09:02:00, Error                 CSI    000002c1 (F) STATUS_OBJECT_NAME_NOT_FOUND #2329845# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0xd5a347b3d8->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[205]'\Registry\Machine\COMPONENTS\DerivedData\VersionedIndex\10.0.19041.1940 (WinBuild.160101.0800)\ComponentFamilies\amd64_microsoft-ppiprojection.appxmain_31bf3856ad364e35_none_6a8dd3c5bb4473fe\v!10.0.19041.1'; a:(OBJ_CASE_INSENSITI[gle=0xd0000034]

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.

[SOLVED] W10 2022-09 KB5017308 0x80073701

Well-known member

Moderator, Windows Update Expert, Security Analyst

Attachments

Well-known member

Attachments

Moderator, Windows Update Expert, Security Analyst

Well-known member

Moderator, Windows Update Expert, Security Analyst

Attachments

Well-known member

Attachments

Moderator, Windows Update Expert, Security Analyst

Attachments

Well-known member

Attachments

Moderator, Windows Update Expert, Security Analyst

Well-known member

Moderator, Windows Update Expert, Security Analyst

Attachments

Well-known member

Attachments

Moderator, Windows Update Expert, Security Analyst

Well-known member

Moderator, Windows Update Expert, Security Analyst

Attachments

Well-known member

Attachments

Moderator, Windows Update Expert, Security Analyst

Attachments

Well-known member

Attachments

Moderator, Windows Update Expert, Security Analyst

Attachments