Can't do Windows updates on Server 2016

D

Dave B B

I've had a problem for months with a server updates.

I've recently had time to do more research on the errors, and found references on other forums that pointed to missing language packs shown in the CBS.log file. Others complained of not being able to add Roles or Features to their server, and I verified that I had this problem too. So the suggested fixes - either installing the missing language pack/s, or deleting the registry values that pointed to those language packs - seemed relevant to my issue.

For some reason the server fails to install additional language packs, so I was left with the other 'fix' - delete registry values relating to the problem language pack (in my case Italian, with 'it-IT' in the name) - located in:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect

Now I've done this and it resolved the problem adding Roles and Features to the server, but Windows updates still don't run - this time I get different errors. The CBS.log file shows:

2018-02-22 20:15:48, Error CSI 0000001f@2018/2/22:07:15:48.803 (F) onecore\base\wcp\componentstore\csd_locking.cpp(200): Error STATUS_SXS_ASSEMBLY_MISSING originated in function CCSDirectTransaction::LockComponent expression: (null)

[gle=0x80004005]

2018-02-22 20:15:48, Info CBS Added C:\Windows\Logs\CBS\CBS.log to WER report.

2018-02-22 20:15:48, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20180221193539.log to WER report.

2018-02-22 20:15:48, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20180221185220.log to WER report.

2018-02-22 20:15:48, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20180221121503.log to WER report.

2018-02-22 20:15:48, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20180221110151.log to WER report.

2018-02-22 20:15:48, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20180221093736.cab to WER report.

2018-02-22 20:15:48, Info CBS Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2018-02-22 20:15:48, Info CBS Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2018-02-22 20:15:48, Info CBS Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2018-02-22 20:15:48, Error CSI 00000020 (F) STATUS_SXS_ASSEMBLY_MISSING #1671150# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 2[gle=0xd015000c]

2018-02-22 20:15:48, Error CSI 00000021 (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #1670998# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = d986ebc677a9486301cc4dd42969d26c, version 10.0.14393.1066, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'Package_957_for_KB4019472~31bf3856ad364e35~amd64~~10.0.1.6.4019472-2597_neutral', rah = '2', manpath = (null), catpath = (null), ed = 0, disp = 0)[gle=0x80073701]

2018-02-22 20:15:48, Info CBS Failed to pin deployment while resolving Update: Package_957_for_KB4019472~31bf3856ad364e35~amd64~~10.0.1.6.4019472-2597_neutral from file: (null) [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]

2018-02-22 20:15:48, Info CBS Failed to bulk stage deployment manifest and pin deployment for package:package_7777_for_KB4053579~31bf3856ad364e35~amd64~~10.0.1.3 [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]

2018-02-22 20:15:48, Info CBS CommitPackagesState: Started persisting state of packages

2018-02-22 20:15:49, Info CBS CommitPackagesState: Completed persisting state of packages

2018-02-22 20:15:49, Info CSI 00000022@2018/2/22:07:15:49.077 CSI Transaction @0x20246d2eab0 destroyed

2018-02-22 20:15:49, Info CBS Perf: Resolve chain complete.

2018-02-22 20:15:49, Info CBS Failed to resolve execution chain. [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]

2018-02-22 20:15:49, Error CBS Failed to process single phase execution. [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]

2018-02-22 20:15:49, Info CBS WER: Generating failure report for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.1944.1.3, status: 0x80073701, failure source: Resolve, start state: Absent, target state: Installed, client id: WindowsUpdateAgent

2018-02-22 20:15:49, Info CBS Not able to query DisableWerReporting flag. Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2018-02-22 20:15:49, Info CBS Added C:\Windows\Logs\CBS\CBS.log to WER report.

2018-02-22 20:15:49, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20180221193539.log to WER report.

2018-02-22 20:15:49, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20180221185220.log to WER report.

2018-02-22 20:15:49, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20180221121503.log to WER report.

2018-02-22 20:15:49, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20180221110151.log to WER report.

2018-02-22 20:15:49, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20180221093736.cab to WER report.

2018-02-22 20:15:49, Info CBS Not able to add %windir%\winsxs\pending.xml to WER report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2018-02-22 20:15:49, Info CBS Not able to add %windir%\winsxs\pending.xml.bad to WER report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2018-02-22 20:15:49, Info CBS Reboot mark cleared

2018-02-22 20:15:49, Info CBS Winlogon: Simplifying Winlogon CreateSession notifications

2018-02-22 20:15:49, Info CBS Winlogon: Deregistering for CreateSession notifications

2018-02-22 20:15:49, Info CBS FinalCommitPackagesState: Started persisting state of packages

2018-02-22 20:15:50, Info CBS Reporting package change for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.1944.1.3, current: Absent, pending: Default, start: Absent, 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: 275, first merged sequence: 275, reboot reason: REBOOT_NOT_REQUIRED, RM App session: -1, RM App name: N/A, FileName in use: N/A, release type: Security 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

2018-02-22 20:15:50, Info CBS SQM: Package change report datapoints not populated because SQM is not initialized or not running online.

2018-02-22 20:15:50, Info CBS Reporting package change completion for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.1944.1.3, current: Absent, original: Absent, target: Installed, status: 0x80073701, failure source: Resolve, failure details: "(null)", client id: WindowsUpdateAgent, initiated offline: False, execution sequence: 275, first merged sequence: 275, pending decision: InteractiveInstallFailed, primitive execution context: Interactive Flight: False

2018-02-22 20:15:50, Info CBS The store corruption status report is incomplete. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2018-02-22 20:15:50, Info CBS Resolve time performance datapoint is invalid. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

2018-02-22 20:15:50, Info CBS Stage time performance datapoint is invalid. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

2018-02-22 20:15:50, Info CBS Execute time performance datapoint is invalid. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

2018-02-22 20:15:50, Info CBS SQM: Package change report datapoints not populated because SQM is not initialized or not running online.

2018-02-22 20:15:50, Info CBS FinalCommitPackagesState: Completed persisting state of packages

2018-02-22 20:15:50, Info CBS Enabling LKG boot option

2018-02-22 20:15:51, Info CBS Exec: Processing complete. Session: 30649257_3355789102, Package: Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.1944.1.3 [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]

2018-02-22 20:19:31, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP

In accordance with advice on other forums, I've run the following with no errors:

DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Other advice I've seen is to run an upgrade install within Windows using the installation media, but this sounds a rather reckless and dangerous thing to do on a production server.

I've been looking at another Technet thread on a similar issue and noticed a comment in the post that "I'm pretty sure that it's only happening when we use the default ISO image provided from Lenovo (multilingual version)"

Now this is exactly what has happened in my case - a Server 2016 installation from the Lenovo multilingual version. So I'm not the only one with the problem.

I'd really appreciate any advice, because at the moment I don't really see any solution outside a complete server rebuild.

Continue reading...
 
Back
Top Bottom