Update failure: 0x80073701(ERROR_SXS_ASSEMBLY_MISSING)

[Shawesome]

Hello,

I'm having an error installing any recent cumulative update, having tried KB4519979, KB4519998, and KB4525236 on a Windows Server 2016 Standard.

I've seen another person with nearly the exact same issue, and they have linked another person too:
[SOLVED] - Update failure: 0x80073701

I have done the exact same things they did or that you (sysnative) suggested in the "Please follow instructions here..." thread.

All dism, sfc, and chkdsk scan/fix commands have been unable to fix any of the issues they found.

I believe my issue is related to KB4507460, if it's the same issue. I've attached a CBS log after a failed installation of KB4519979. No matter which KB I try to install, they all end up with very similar logs, and each of them have KB4507460 in the location that the other two mentioned forums had their problem KB located.

Here's a portion of the CBS log that resembles the other SOLVED forums:

2019-11-13 10:27:33, Info CSI 083706281ff, version 10.0.14393.2879, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}]) comp: (null) man: @0x1e649092d00
(24) Stage: flags: 8 app: [f11dc7ba5a91d7d815be95890bfad042, version 10.0.14393.2879, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}]) comp: (null) man: @0x1e649092c90
(25) Stage: flags: 8 app: [b1d510b3b52171772db88e5c66e13e13, version 4.0.15552.17515, arch amd64, nonSxS, pkt {l:8 b:b03f5f7f11d50a3a}]) comp: (null) man: @0x1e6490915d0
(26) Stage: flags: 8 app: [e9bad9a09249d918e5c3e4cc4e629922, version 10.0.14393.953, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}]) comp: (null) man: @0x1e6490929f0
(27) Stage: flags: 8 app: [8e042aa5ee2cbf0b9a1b5bce5a695701, version 10.0.14393.2999, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}]) comp: (null) man: @0x1e649091c60
(28) Stage: flags: 8 app: [a75723911176dc0c288ba6f4e48f3f24, version 10.0.14393.2791, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}]) comp: (null) man: @0x1e649091fe0
(29) Stage: flags: 8 app: [d31c8634a17f290b7d95c7c3a0d2c9ae, version 10.0.14393.2791, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}]) comp: (null) man: @0x1e6490916b0
(30) Stage: flags: 8 app: [2051e450726c9f70595cb3617b038ac1, version 10.0.14393.206, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}]) comp: (null) man: @0x1e649091870
(31) Stage: flags: 8 app: [19ec5ac5b6f3a5a5a71cc4416674fca4, version 10.0.14393.206, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}]) comp: (null) man: @0x1e649092130
2019-11-13 10:27:33, Info CSI 0000001e Performing 1 operations as follows:
(0) AddCat: flags: 1 catfile: @0x1e649092fa0
2019-11-13 10:27:33, Error CSI 0000001f@2019/11/13:16:27:33.690 (F) onecore\base\wcp\componentstore\csd_locking.cpp(200): Error STATUS_SXS_ASSEMBLY_MISSING originated in function CCSDirectTransaction::LockComponent expression: (null)
[gle=0x80004005]
2019-11-13 10:27:33, Info CBS Added C:\Windows\Logs\CBS\CBS.log to WER report.
2019-11-13 10:27:33, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20191113154437.log to WER report.
2019-11-13 10:27:33, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20191113043057.log to WER report.
2019-11-13 10:27:33, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20191112213336.log to WER report.
2019-11-13 10:27:33, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20191112200232.log to WER report.
2019-11-13 10:27:33, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20191112194010.log to WER report.
2019-11-13 10:27:33, Info CBS Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2019-11-13 10:27:33, Info CBS Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2019-11-13 10:27:33, Info CBS Not able to add poqexec.log to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2019-11-13 10:27:33, Error CSI 00000020 (F) STATUS_SXS_ASSEMBLY_MISSING #4326300# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 2[gle=0xd015000c]
2019-11-13 10:27:33, Error CSI 00000021 (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #4326148# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = 1bb84d3ea297e94486704ab8bc560cc7, version 10.0.14393.3053, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'Package_1932_for_KB4507460~31bf3856ad364e35~amd64~~10.0.1.6.4507460-4976_neutral', rah = '2', manpath = (null), catpath = (null), ed = 0, disp = 0)[gle=0x80073701]
2019-11-13 10:27:33, Info CBS Failed to pin deployment while resolving Update: Package_1932_for_KB4507460~31bf3856ad364e35~amd64~~10.0.1.6.4507460-4976_neutral from file: (null) [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2019-11-13 10:27:33, Info CBS Failed to bulk stage deployment manifest and pin deployment for packageackage_10001_for_KB4519979~31bf3856ad364e35~amd64~~10.0.1.7 [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2019-11-13 10:27:33, Info CBS CommitPackagesState: Started persisting state of packages
2019-11-13 10:27:33, Info CBS CommitPackagesState: Completed persisting state of packages

 

[Sysnative Windows Update]

Hello and welcome!

FRST Registry Search
1. Click your Start button and type in cmd.
2.After you find the Command Prompt, right click on it and select Run as Administrator.
3. Copy and paste the following into the Command Prompt:

reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS

4. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
5. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
6. Copy and paste KB4507460 into the Search box and click the Search Registry button.
7. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt.

 

[Shawesome]

I appreciate your very quick response. However, I wasn't expecting you to respond until tomorrow. I sent in a ticket to Microsoft this morning (also expecting a slower response), but I'm on the phone with them right now. I'm guessing they're probably not going to fix it anytime soon, so I'll try to suggestion tonight. I'll keep you updated.

 

[Sysnative Windows Update]

Okay, attach the log when the steps are complete.