Help creating fixlist.txt

[JvO]

I have a windows server 2016 standard that has problems installing the cumulative updates. In the CBS.log I get the following error: 0x80073701 – STATUS-SXS-ASSEMBLY-MISSING
Searching this forum I was finding similar problems with solutions creating a fixlist.txt from a searchreg.txt created with the Farbar Recovery Scan Tool.

So I have run the FRST searching for "KB4507459" wich I think is the culprit but have no clue on how to create the Fixlist.txt.

Just in case, I have included a portion of my cbs.log from the time I started the installation of the cumulative update up to the point when it fails.


2019-10-11 21:42:39, Error CSI 00006a5e@2019/10/11:19:42:39.406 (F) onecore\base\wcp\componentstore\csd_locking.cpp(200): Error STATUS_SXS_ASSEMBLY_MISSING originated in function CCSDirectTransaction::LockComponent expression: (null)
[gle=0x80004005]
2019-10-11 21:42:39, Info CBS Added C:\Windows\Logs\CBS\CBS.log to WER report.
2019-10-11 21:42:39, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20191011050004.log to WER report.
2019-10-11 21:42:39, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20191010052611.log to WER report.
2019-10-11 21:42:39, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20191009145002.log to WER report.
2019-10-11 21:42:39, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20191009021804.log to WER report.
2019-10-11 21:42:39, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20191008042650.cab to WER report.
2019-10-11 21:42:39, Info CBS Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2019-10-11 21:42:39, Info CBS Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2019-10-11 21:42:39, Info CBS Not able to add poqexec.log to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2019-10-11 21:42:45, Error CSI 00006a5f (F) STATUS_SXS_ASSEMBLY_MISSING #31825286# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 2[gle=0xd015000c]
2019-10-11 21:42:45, Error CSI 00006a60 (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #31825030# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = 3e029d19a0a3584347a724e8fef9a3af, version 10.0.14393.2580, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'Package_1243_for_KB4467691~31bf3856ad364e35~amd64~~10.0.1.3.4467691-3817_neutral', rah = '2', manpath = (null), catpath = (null), ed = 0, disp = 0)[gle=0x80073701]
2019-10-11 21:42:45, Info CBS Failed to pin deployment while resolving Update: Package_1243_for_KB4467691~31bf3856ad364e35~amd64~~10.0.1.3.4467691-3817_neutral from file: (null) [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2019-10-11 21:42:45, Info CBS Failed to bulk stage deployment manifest and pin deployment for packageackage_9848_for_KB4507459~31bf3856ad364e35~amd64~~10.0.1.6 [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2019-10-11 21:42:45, Info CBS CommitPackagesState: Started persisting state of packages
2019-10-11 21:42:45, Info CBS CommitPackagesState: Completed persisting state of packages
2019-10-11 21:42:45, Info CSI 00006a61@2019/10/11:19:42:45.482 CSI Transaction @0x17d4d73c8d0 destroyed
2019-10-11 21:42:45, Info CBS Perf: Resolve chain complete.
2019-10-11 21:42:45, Info CBS Failed to resolve execution chain. [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2019-10-11 21:42:45, Error CBS Failed to process single phase execution. [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2019-10-11 21:42:45, Info CBS WER: Generating failure report for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.3115.1.6, status: 0x80073701, failure source: Resolve, start state: Resolved, target state: Installed, client id: WindowsUpdateAgent
2019-10-11 21:42:45, Info CBS Not able to query DisableWerReporting flag. Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2019-10-11 21:42:45, Info CBS Added C:\Windows\Logs\CBS\CBS.log to WER report.
2019-10-11 21:42:45, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20191011050004.log to WER report.
2019-10-11 21:42:45, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20191010052611.log to WER report.
2019-10-11 21:42:45, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20191009145002.log to WER report.
2019-10-11 21:42:45, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20191009021804.log to WER report.
2019-10-11 21:42:45, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20191008042650.cab to WER report.
2019-10-11 21:42:45, Info CBS Not able to add %windir%\winsxs\poqexec.log to WER report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2019-10-11 21:42:45, Info CBS Not able to add %windir%\winsxs\pending.xml to WER report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2019-10-11 21:42:45, Info CBS Not able to add %windir%\winsxs\pending.xml.bad to WER report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2019-10-11 21:42:53, Info CBS Reboot mark cleared
2019-10-11 21:42:53, Info CBS Winlogon: Simplifying Winlogon CreateSession notifications
2019-10-11 21:42:53, Info CBS Winlogon: Deregistering for CreateSession notifications
2019-10-11 21:42:53, Info CBS FinalCommitPackagesState: Started persisting state of packages
2019-10-11 21:42:53, Info CBS Reporting package change for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.3115.1.6, 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: 720, first merged sequence: 720, 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-10-11 21:42:54, Info CBS SQM: Package change report datapoints not populated because SQM is not initialized or not running online.
2019-10-11 21:42:54, Info CBS Reporting package change completion for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.3115.1.6, current: Resolved, original: Resolved, target: Installed, status: 0x80073701, failure source: Resolve, failure details: "(null)", client id: WindowsUpdateAgent, initiated offline: False, execution sequence: 720, first merged sequence: 720, pending decision: InteractiveInstallFailed, primitive execution context: Interactive Flight: False
2019-10-11 21:42:54, Info CBS Resolve time performance datapoint is invalid. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2019-10-11 21:42:54, Info CBS Stage time performance datapoint is invalid. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2019-10-11 21:42:54, Info CBS Execute time performance datapoint is invalid. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2019-10-11 21:42:54, Info CBS SQM: Package change report datapoints not populated because SQM is not initialized or not running online.
2019-10-11 21:42:54, Info CBS FinalCommitPackagesState: Completed persisting state of packages
2019-10-11 21:42:54, Info CBS Enabling LKG boot option
2019-10-11 21:42:58, Info CBS Exec: Processing complete. Session: 30769258_2591896644, Package: Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.3115.1.6 [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]

 

[Sysnative Windows Update]

Hello and welcome!

Please search for KB4467691

 

[JvO]

Hi, Thanx!

Included is the searchreg.txt for KB4467691

 

[Sysnative Windows Update]

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 the attached fixlist.txt 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. Reboot and retry updates.

 

[JvO]

Thanx, that helped! I was able to install the missing update!

Do you have any information on how to create the fixlist.txt?

 

[x BlueRobot]

Do you have any information on how to create the fixlist.txt

If you want to learn more about fixing Windows Update issues, then I would check out the Windows Update Academy.

 

[Sysnative Windows Update]

If you are interested in the Academy, please read the following article and send me a PM if you are still interested after reading it:

Learn How to Fix Windows Update: The Sysnative Windows Update Academy

Thank you.