[SOLVED] Update failure: 0x80073701 – STATUS-SXS-ASSEMBLY-MISSING

R

Ritchy059

Contributor
Joined
Nov 5, 2018
Posts
39
Hello,

I Have an Error Installing Cumulative Update 01-2019, 02-2019 on an Windows 2016 Server Standard.

The Error in the CBS.LOG is: 0x80073701 – STATUS-SXS-ASSEMBLY-MISSING

SFC /SCANNOW ist fine (No Errors)
DISM /Online /cleanup-image /ScanHealth is fine (no Errors)
ChkDsk C: /f (no Errors)
Tried: DISM /Online /cleanup-image /RestoreHealth

did not help.

Rebooted several times (20x)

Even a Reset of the Windows Update Folder did'nt help. Normal Updates as Windows Defender and so on is working...

Every Try to Update any Cumulative Updates failed with Error: 0x80073701

Can anybody help me, to find out whats the Problem is with Installed Packages?

See Detect packages...
2019-03-09 02:02:48, Info CSI 4393.206, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}]) comp: (null) man: @0x17edcfa1890
(130) Stage: flags: 8 app: [f4d7ad8e88ec32275b247dace11f2fc3, version 10.0.14393.1358, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}]) comp: (null) man: @0x17edcfa05c0
(131) Stage: flags: 8 app: [344fe820047d743ae0454d292d7b4e61, version 10.0.14393.206, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}]) comp: (null) man: @0x17edcfa04e0
(132) Stage: flags: 8 app: [5d9402385a5b114d7a8a2a84b3a648f1, version 10.0.14393.206, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}]) comp: (null) man: @0x17edcfa1ac0
(133) Stage: flags: 8 app: [2fcafd2dfad7ff2e3fc52187d79c324f, version 10.0.14393.206, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}]) comp: (null) man: @0x17edcfa19e0
(134) Stage: flags: 8 app: [81803a3759e8d03a17c37835d4cc9356, version 10.0.14393.187, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}]) comp: (null) man: @0x17edcfa1a50
(135) Stage: flags: 8 app: [238a3b0018d89f1fb34eccdfbe1d2cb7, version 10.0.14393.1613, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}]) comp: (null) man: @0x17edcfa0630
(136) Stage: flags: 8 app: [890467c7a001008b1cd39541c22f961c, version 11.0.14393.447, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}]) comp: (null) man: @0x17edcfa06a0
(137) Stage: flags: 8 app: [34500c69d48cee515de305ec711d4199, version 10.0.14393.1480, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}]) comp: (null) man: @0x17edcfa0a20
(138) Stage: flags: 8 app: [045be2c3fe8fd168ebeed368941ee424, version 10.0.14393.1480, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}]) comp: (null) man: @0x17edcfa0a90
2019-03-09 02:02:50, Error CSI 00000017@2019/3/9:01:02:50.894 (F) onecore\base\wcp\componentstore\csd_locking.cpp(200): Error STATUS_SXS_ASSEMBLY_MISSING originated in function CCSDirectTransaction::LockComponent expression: (null)
[gle=0x80004005]
2019-03-09 02:02:50, Info CBS Added C:\Windows\Logs\CBS\CBS.log to WER report.
2019-03-09 02:02:51, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20190309002849.log to WER report.
2019-03-09 02:02:51, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20190308233705.log to WER report.
2019-03-09 02:02:51, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20190308214541.log to WER report.
2019-03-09 02:02:51, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20190302231829.cab to WER report.
2019-03-09 02:02:51, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20190302104729.cab to WER report.
2019-03-09 02:02:51, Info CBS Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2019-03-09 02:02:51, Info CBS Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2019-03-09 02:02:51, Info CBS Not able to add poqexec.log to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2019-03-09 02:02:51, Info CBS Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2019-03-09 02:02:51, Error CSI 00000018 (F) STATUS_SXS_ASSEMBLY_MISSING #5960021# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 2[gle=0xd015000c]
2019-03-09 02:02:51, Error CSI 00000019 (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #5959869# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = 8c090c0f1e8cc37e1b82eb1d265d636d, version 10.0.14393.1914, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'Package_167_for_KB4074590~31bf3856ad364e35~amd64~~10.0.1.5.4074590-286_neutral', rah = '2', manpath = (null), catpath = (null), ed = 0, disp = 0)[gle=0x80073701]
2019-03-09 02:02:51, Info CBS Failed to pin deployment while resolving Update: Package_167_for_KB4074590~31bf3856ad364e35~amd64~~10.0.1.5.4074590-286_neutral from file: (null) [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2019-03-09 02:02:51, Info CBS Failed to bulk stage deployment manifest and pin deployment for package:Package_9114_for_KB4487006~31bf3856ad364e35~amd64~~10.0.1.11 [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2019-03-09 02:02:51, Info CBS CommitPackagesState: Started persisting state of packages
2019-03-09 02:02:51, Info CBS CommitPackagesState: Completed persisting state of packages
2019-03-09 02:02:51, Info CSI 0000001a@2019/3/9:01:02:51.197 CSI Transaction @0x17ebcaa5100 destroyed
2019-03-09 02:02:51, Info CBS Perf: Resolve chain complete.
2019-03-09 02:02:51, Info CBS Failed to resolve execution chain. [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2019-03-09 02:02:51, Error CBS Failed to process single phase execution. [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2019-03-09 02:02:51, Info CBS WER: Generating failure report for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.2828.1.11, status: 0x80073701, failure source: Resolve, start state: Resolved, target state: Installed, client id: WindowsUpdateAgent
2019-03-09 02:02:51, Info CBS Not able to query DisableWerReporting flag. Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2019-03-09 02:02:51, Info CBS Added C:\Windows\Logs\CBS\CBS.log to WER report.
2019-03-09 02:02:51, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20190309002849.log to WER report.
2019-03-09 02:02:51, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20190308233705.log to WER report.
2019-03-09 02:02:51, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20190308214541.log to WER report.
2019-03-09 02:02:51, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20190302231829.cab to WER report.
2019-03-09 02:02:51, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20190302104729.cab to WER report.
2019-03-09 02:02:51, Info CBS Not able to add %windir%\winsxs\poqexec.log to WER report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2019-03-09 02:02:51, Info CBS Not able to add %windir%\winsxs\pending.xml to WER report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2019-03-09 02:02:51, Info CBS Not able to add %windir%\winsxs\pending.xml.bad to WER report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2019-03-09 02:02:51, Info CBS Reboot mark cleared
2019-03-09 02:02:51, Info CBS Winlogon: Simplifying Winlogon CreateSession notifications
2019-03-09 02:02:51, Info CBS Winlogon: Deregistering for CreateSession notifications
2019-03-09 02:02:51, Info CBS FinalCommitPackagesState: Started persisting state of packages
2019-03-09 02:02:51, Info CBS Reporting package change for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.2828.1.11, current: Resolved, pending: Default, start: Resolved, applicable: Installed, target: Installed, limit: Installed, hotpatch status: StillGoing, status: 0x0, failure source: Resolve, reboot required: False, client id: WindowsUpdateAgent, initiated offline: False, execution sequence: 227, first merged sequence: 227, reboot reason: REBOOT_NOT_REQUIRED, RM App session: -1, RM App name: N/A, FileName in use: N/A, release type: Update, release quality: final, OC operation: False, download source: 0, download time (secs): 4294967295, download status: 0x0 (S_OK), Express download: False, Download Size: 0
2019-03-09 02:02:51, Info CBS SQM: Package change report datapoints not populated because SQM is not initialized or not running online.
2019-03-09 02:02:51, Info CBS Reporting package change completion for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.2828.1.11, current: Resolved, original: Resolved, target: Installed, status: 0x80073701, failure source: Resolve, failure details: "(null)", client id: WindowsUpdateAgent, initiated offline: False, execution sequence: 227, first merged sequence: 227, pending decision: InteractiveInstallFailed, primitive execution context: Interactive Flight: False
2019-03-09 02:02:51, Info CBS The store corruption status report is incomplete. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2019-03-09 02:02:51, Info CBS Resolve time performance datapoint is invalid. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2019-03-09 02:02:51, Info CBS Stage time performance datapoint is invalid. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2019-03-09 02:02:51, Info CBS Execute time performance datapoint is invalid. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2019-03-09 02:02:51, Info CBS SQM: Package change report datapoints not populated because SQM is not initialized or not running online.
2019-03-09 02:02:52, Info CBS FinalCommitPackagesState: Completed persisting state of packages
2019-03-09 02:02:52, Info CBS Enabling LKG boot option
2019-03-09 02:02:54, Info CBS Exec: Processing complete. Session: 30725648_3071693499, Package: Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.2828.1.11 [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2019-03-09 02:05:41, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2019-03-09 02:05:41, Info CBS TiWorker signaled for shutdown, going to exit.
2019-03-09 02:05:41, Info CBS CbsCoreFinalize: ExecutionEngineFinalize
2019-03-09 02:05:41, Info CBS Ending the TiWorker main loop.

From the CBS.LOG


Thanks
Ritchy059
 
Hi!

FRST Registry Search
1. Click your Start button and choose Control Panel.
2. In the upper right corner ensure the View by: is set to Category.
3. Select the Programs group.
4. Click the Turn Windows features on or off link. This will bring up the Windows Features dialog. Wait until this dialog populates with information. If this does not happen for some reason, please continue with the steps anyway.
Note: This loads your components hive which is what we want. Please keep this dialog open while you perform the remaining steps.
5. 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.
6. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
7. Copy and paste KB4074590 into the Search box and click the Search Registry button.
8. 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.
9. You may close any remaining open windows now.
 
Step#1 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. 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.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
6. Try updates and if any fail, attach CBS.log.
 

Attachments

You must log in or register to reply here.

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

Back
Top