W2022 21h2 cannot install KB5048654 with error 0x8007371b or 0x800f0983.

Question

Few W2022 21h2 servers cannot install KB5048654 (also KB5046616 kept failing) showing 0x8007371b.

Other few W2022 21h2 servers also failed installing the same CUs, ending with error 0x800f0983

We reset win update service, and run 'sfc /scannow' and dism commands, and restated, but update still failing. These are the latest updates released.

It is frustrating, as there is no pattern just seems random.

All above servers successfully installed all the October (including CU/.Net) updates.

This seems to be a Ms issue, so please address urgently. I am sure other users experiencing similar. Because systems are running production and critical apps, it is not possible to re-install or attempt lengthy downtime/offline repairs.

Here are some errors from cbs.log:

2024-12-10 03:45:22, Error CSI 0000084a@2024/12/10:08:45:22.559 (F) onecore\base\wcp\componentstore\csd_winners.cpp(1342): Error STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE originated in function OriginateFilesMissingError expression: (null)

[gle=0x80004005]

2024-12-10 03:45:22, Info CBS Added C:\Windows\Logs\CBS\CBS.log to WER report.

2024-12-10 03:45:22, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20241206231014.log to WER report.

2024-12-10 03:45:22, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20241203085003.cab to WER report.

2024-12-10 03:45:22, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20241129231500.cab to WER report.

2024-12-10 03:45:22, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20241126084855.cab to WER report.

2024-12-10 03:45:22, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20241122230348.cab to WER report.

2024-12-10 03:45:22, Info CBS Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2024-12-10 03:45:22, Info CBS Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2024-12-10 03:45:22, Info CBS Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2024-12-10 03:45:23, Error CSI 0000084b (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #3693407# from CCSDirectTransaction::PerformChangeAnalysis(...)[gle=0xd0150024]

2024-12-10 03:45:23, Error CSI 0000084c (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #3693406# from CCSDirectTransaction::PrepareForCommit(...)[gle=0xd0150024]

2024-12-10 03:45:23, Error CSI 0000084d (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #3693405# from CCSDirectTransaction::ExamineTransaction(...)[gle=0xd0150024]

2024-12-10 03:45:23, Error CSI 0000084e (F) STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE #3693404# from CCSDirectTransaction_IRtlTransaction::ExamineTransaction(...)[gle=0xd0150024]

2024-12-10 03:45:23, Error CSI 0000084f (F) HRESULT_FROM_WIN32(ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE) #3248568# from Windows::COM::CPendingTransaction::IStorePendingTransaction_Analyze(...)[gle=0x8007371b]

2024-12-10 03:45:23, Error CSI 00000850 (F) HRESULT_FROM_WIN32(ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE) #3071748# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_Commit(Flags = 47, pSink = NULL, disp = 0)[gle=0x8007371b]

2024-12-10 03:45:23, Error CSI 00000851 (F) HRESULT_FROM_WIN32(ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE) #3071747# 59959967 us from Windows::ServicingAPI::CCSITransaction_ICSITransaction::Commit(flags = 0x0000002f, pSink = NULL, disp = 0)

[gle=0x8007371b]

2024-12-10 03:45:23, Info CBS Setting ExecuteState key to: ExecuteStateNone

2024-12-10 03:45:23, Info CBS Clearing HangDetect value

2024-12-10 03:45:23, Info CBS Saved last global progress. Current: 0, Limit: 1, ExecuteState: ExecuteStateNone

2024-12-10 03:45:23, Info CBS Configured poqexec to pend to SetupExecute.

2024-12-10 03:45:23, Info CBS Exec: Restoring driver operations because of a CSI commit failure.

2024-12-10 03:45:23, Error CBS Exec: Failed to pend CSI transaction because transactions cannot be merged: 0. [HRESULT = 0x8007371b - ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE]

2024-12-10 03:45:23, Info CBS Perf: InstallUninstallChain complete.

2024-12-10 03:45:23, Info CSI 00000852@2024/12/10:08:45:23.497 CSI Transaction @0x256282b3690 destroyed

2024-12-10 03:45:23, Info CBS Failed to execute execution chain. [HRESULT = 0x8007371b - ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE]

2024-12-10 03:45:23, Error CBS Failed to process single phase execution. [HRESULT = 0x8007371b - ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE]

2024-12-10 03:45:23, Info CBS WER: Generating failure report for package: Package_for_ServicingStack_2750~31bf3856ad364e35~amd64~~20348.2750.1.0, status: 0x8007371b, failure source: Execute, start state: Installed, target state: Installed, client id: WindowsUpdateAgent

2024-12-10 03:45:23, Info CBS Not able to query DisableWerReporting flag. Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2024-12-10 03:45:23, Info CBS Added C:\Windows\Logs\CBS\CBS.log to WER report.

2024-12-10 03:45:23, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20241206231014.log to WER report.

2024-12-10 03:45:23, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20241203085003.cab to WER report.

2024-12-10 03:45:23, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20241129231500.cab to WER report.

2024-12-10 03:45:23, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20241126084855.cab to WER report.

2024-12-10 03:45:23, Info CBS Added C:\Windows\Logs\CBS\CbsPersist_20241122230348.cab to WER report.

2024-12-10 03:45:23, Info CBS Not able to add %windir%\winsxs\pending.xml to WER report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2024-12-10 03:45:23, Info CBS Not able to add %windir%\winsxs\pending.xml.bad to WER report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2024-12-10 03:45:24, Info CBS Reboot mark cleared

2024-12-10 03:45:24, Info CBS Winlogon: Simplifying Winlogon CreateSession notifications

2024-12-10 03:45:24, Info CBS Winlogon: Deregistering for CreateSession notifications

2024-12-10 03:45:24, Info CBS FinalCommitPackagesState: Started persisting state of packages

2024-12-10 03:45:24, Info CBS Reporting package change for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~20348.2849.1.11, current: Staged, pending: Default, start: Staged, applicable: Installed, target: Installed, limit: Installed, status: 0x0, failure source: Execute, reboot required: False, client id: WindowsUpdateAgent, initiated offline: False, execution sequence: 231, first merged sequence: 231, reboot reason: DRIVERSPRESENT, RM App session: -1, RM App name: N/A, FileName in use: N/A, release type: Security Update, OC operation: False, download source: 0, download time (secs): 4294967295, download status: 0x0 (S_OK), Express download: False, Download Size: 0 Used lower priority: False Priority changes: 0

2024-12-10 03:45:24, Info CBS Reporting package change completion for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~20348.2849.1.11, current: Staged, original: Staged, target: Installed, status: 0x8007371b, failure source: Execute, failure details: "(null)", client id: WindowsUpdateAgent, initiated offline: False, execution sequence: 231, first merged sequence: 231, pending decision: PackagePended_NoSmartPendingFlagSet, primitive execution context: Interactive

2024-12-10 03:45:24, Info CBS The store corruption status report is incomplete. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2024-12-10 03:45:24, Info CBS Execute time performance datapoint is invalid. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

2024-12-10 03:45:25, Info CBS FinalCommitPackagesState: Completed persisting state of packages

2024-12-10 03:45:25, Info CBS Enabling LKG boot option

2024-12-10 03:45:26, Info CBS Exec: Will not run corruption repair because no store corruption found.

2024-12-10 03:45:26, Info CBS Exec: Processing complete. Session: 31148766_4125283074, Package: Package_for_ServicingStack_2750~31bf3856ad364e35~amd64~~20348.2750.1.0, Identifier: KB5044414 [HRESULT = 0x8007371b - ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE]

2024-12-10 03:45:33, Info CBS WU creates the package, AppID:<>: SWJobEngineWorker2.exe, UpdateID:{389D3C80-758E-4FC0-BCD9-5D733758013E}, revision: 200

2024-12-10 03:45:33, Info CBS Session: 31148767_3757665956 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null)

Answer 1

Hello,

Thank you for posting in Microsoft Community forum.

Based on the description, I understand your question is related to update failure.

Error 0x8007371b: This error is often related to missing or corrupted system files. It can occur due to multiple reasons, such as corrupted or missing system files, antivirus interference, and so on.

Try running the Windows Update Troubleshooter: Select Start  > Settings  > Update & Security   > Troubleshoot > Additional troubleshooters. Next, under Get up and running, select Windows Update > Run the troubleshooter.

When the troubleshooter is finished running, it's a good idea to restart your device.

Also, try run below commands to check your system files:

sfc /scannow

DISM /Online /Cleanup-Image /RestoreHealth

Error 0x800f0983: This error can be caused by missing update files or conflicts in the update process. It is recommended to retry the update after above steps, restart the device, and retry the update again. If that fails, you might need to consider doing an in place upgrade.

Have a nice day. 

Best Regards,

Molly

Answer 2

I'm having the same problem.

Domain Controller - Windows Server 2022 Datacenter, 21H2, Build 20348.2762

I was unable to install:

November 12, 2024—KB5046616 (OS Build 20348.2849)

or

December 10, 2024—KB5048654 (OS Build 20348.2966)

Update ends with error 0x80073701

I already tried a lot of procedures, for example:

dism.exe /online /cleanup-image /scanhealth
dism.exe /online /cleanup-image /restorehealth
dism.exe /online /cleanup-image /startcomponentcleanup
sfc /scannow

ren %systemroot%\softwaredistribution softwaredistribution.bak
ren %systemroot%\system32\catroot2 catroot2.bak

No effect.

Any suggestions?

Answer 3

Thank you for the reply Molly.

However I already stated I cannot use the in-place upgrade for the systems with error 0x800f0983.

These are production systems, and using enterprise O/S, A downtime is not easily obtained, especially in this case there is no fault from our side to trigger this issue. I am not sure if this is so easily suggested.

These systems just started getting the update errors (after successfully processing the October security updates), with no other change from our side, except that we use the Windows auto update feature to apply the O/S security patches.

As I stated before, I strongly believe this is something Microsoft should take responsibility and address.

Is it possible to have this issue reported and seen by Microsoft support/development team? I already send feedback form (via Feedback Hub), however did not receive any response.

Please advise. Thank you.

Answer 4

Hello

Yesterday, i finally solved the problem running this script: https://www.reddit.com/r/sysadmin/comments/1fda3gu/comment/lmzzbe2/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

Tested on Windows Server 2022.

i hope it helps

Answer 5

Hello

Yesterday, i finally solved the problem running this script: https://www.reddit.com/r/sysadmin/comments/1fda3gu/comment/lmzzbe2/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

Tested on Windows Server 2022.

i hope it helps

Thank you for your suggestion.

I followed the steps provided.

However the update still fails to install with same error: 0x800f0983.