[SOLVED] Server 2022 failing KB5041160 with error 0x800f0982

[narasimha01]

I have a Windows Server 2022 VM is failing to install KB5041160 it's failing with 0x800f0982 error.

Tried multiple attempts and Tried running "DISM /Online /Cleanup-Image /RestoreHealth" and "DISM /Online /Cleanup-Image /RestoreHealth /Source:" with SXS folder from working server did not solve the issue.

Here is the windows log.
2024/08/14 16:20:47.4679409 8516 9884 Handler *FAILED* [800F0982] file = onecore\enduser\windowsupdate\client\engine\handler\osdeployment\helper\osdeploymenthelper.cpp, line = 730
2024/08/14 16:20:47.4679458 8516 9884 Handler *FAILED* [800F0982] file = onecore\enduser\windowsupdate\client\engine\handler\osdeployment\installer\osinstaller.cpp, line = 1103
2024/08/14 16:20:47.4699358 8516 9884 Handler Install complete for update ID: B78E6476-C096-40F6-967C-743397BB5FDC.1 Return code is 0x800F0982. Requires Reboot:No
2024/08/14 16:20:47.4699380 8516 9884 Handler Enter deployment handler NotifyResult
2024/08/14 16:20:47.4700217 5292 4948 Deployment Deployment job Id 884CB336-B6C4-4D22-B870-815ED6BBE0C1 : Update b78e6476-c096-40f6-967c-743397bb5fdc.1 failure delegate invoked.
2024/08/14 16:20:47.4700552 8516 9884 Handler Leave deployment handler NotifyResult
2024/08/14 16:20:47.4701282 8516 9884 Handler *FAILED* [800F0982] file = onecore\enduser\windowsupdate\client\engine\handler\osdeployment\installer\osinstaller.cpp, line = 339
2024/08/14 16:20:47.4701293 8516 9884 Handler *FAILED* [800F0982] Leave deployment handler Install
2024/08/14 16:20:47.4701765 5292 7648 Deployment Deployment job Id 884CB336-B6C4-4D22-B870-815ED6BBE0C1 : NotifyClient (7648)(0) called for update id b78e6476-c096-40f6-967c-743397bb5fdc.1, code = Update failed, percent complete = 100
2024/08/14 16:20:47.4701971 5292 7648 ComApi Deployment job proxy : deployment callback for top-level update B78E6476-C096-40F6-967C-743397BB5FDC.1, reboot required = unspecified, commit required = No, mapped result = 0x800f0982, unmapped result = 0x00000000
2024/08/14 16:20:47.4702471 5292 7648 ComApi Deployment callback complete for UpdateID = b78e6476-c096-40f6-967c-743397bb5fdc, callback code = 8, CallbackInfo cookie length = 0
2024/08/14 16:20:47.4730531 5292 4660 ComApi Deployment Job Proxy : Callback for inner update : B78E6476-C096-40F6-967C-743397BB5FDC.1, top-level update B78E6476-C096-40F6-967C-743397BB5FDC.1, reboot required = unspecified, commit required = No, callback info length = 0
2024/08/14 16:20:47.7077009 6596 10476 DownloadManager CloseUpdateInstallDirectory invoked for Update ID = B78E6476-C096-40F6-967C-743397BB5FDC.1, serverID = 8B24B027-1DEE-BABB-9A95-3517DFB9C552, Update installation result = 0x800f0982.
2024/08/14 16:20:47.9759271 6596 10476 DownloadManager CloseUpdateInstallDirectory successful for Update ID = B78E6476-C096-40F6-967C-743397BB5FDC.1.
2024/08/14 16:20:47.9807606 6596 10476 DownloadManager Unlock the sandbox of update B78E6476-C096-40F6-967C-743397BB5FDC.1 (session data: (null))
2024/08/14 16:20:48.0318596 5292 4660 Deployment Mutex will be closed. index = 0, HANDLE = 00000000000007E8
2024/08/14 16:20:48.0318721 5292 4660 Deployment *FAILED* [800F0982] Deployment job Id 884CB336-B6C4-4D22-B870-815ED6BBE0C1 : Top level update id b78e6476-c096-40f6-967c-743397bb5fdc.1, bundled update id b78e6476-c096-40f6-967c-743397bb5fdc.1
2024/08/14 16:20:48.0318744 5292 4660 Deployment *FAILED* [800F0982] Deployment job Id 884CB336-B6C4-4D22-B870-815ED6BBE0C1 : Top level update id b78e6476-c096-40f6-967c-743397bb5fdc.1
2024/08/14 16:20:48.0318767 5292 4660 Deployment Deployment job Id 884CB336-B6C4-4D22-B870-815ED6BBE0C1 : Update b78e6476-c096-40f6-967c-743397bb5fdc.1 failure delegate invoked.
2024/08/14 16:20:48.2449992 6596 10476 Agent AddEventGroup: Adding non-pending event for update id B78E6476-C096-40F6-967C-743397BB5FDC.1
2024/08/14 16:20:48.2463716 5292 4660 Deployment Deployment job Id 884CB336-B6C4-4D22-B870-815ED6BBE0C1 : Job complete delegate invoked.
2024/08/14 16:20:48.2463797 5292 4660 Deployment Deployment job Id 884CB336-B6C4-4D22-B870-815ED6BBE0C1 : Ending deployment for updates, CallerId = MoUpdateOrchestrator, Exit code = 0x00000000
2024/08/14 16:20:48.2464943 5292 7700 Deployment Deployment job Id 884CB336-B6C4-4D22-B870-815ED6BBE0C1 : WaitForEnd invoked for deployment job. Beginning the wait now!
2024/08/14 16:20:48.2465152 5292 7692 Deployment Deployment job Id 884CB336-B6C4-4D22-B870-815ED6BBE0C1 : NotifyClient (7692)(0) called with Deployment callback code = Job complete, reboot status = no reboot
2024/08/14 16:20:48.2465260 5292 7692 ComApi Install ClientId = MoUpdateOrchestrator
2024/08/14 16:20:48.2465287 5292 7692 ComApi Install call complete (succeeded = 0, succeeded with errors = 0, failed = 1, cancelled = 0, unaccounted = 0
2024/08/14 16:20:48.2465859 5292 7692 ComApi Reboot required = False
2024/08/14 16:20:48.2465876 5292 7692 ComApi Call error code = 0x80240022

 

[Maxstar]

Hi and welcome to Synative,

Please follow the Windows Update Forum Posting Instructions and provide the requested files in your next post

 

[narasimha01]

Thank you. Please find the attached reports and help me to resolve this issue. we are having same issue with multiple servers.

 

[Maxstar]

Hi,

Upload your COMPONENTS hive.

• Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
• Please copy this file to your desktop.
• Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
• Right-click on this file on your desktop and select Send To > Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
• If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.

 

[narasimha01]

Here is the file

 

[Maxstar]

Download

SFCFix and save it to your desktop.

Warning: This fix was written specifically for this system. Do not run this fix on another system.

• Save any work you have open, and close all programs.
• Download the attachment SFCFix.zip and save it to your desktop.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.

• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Post the logfile (SFCFix.txt) as attachment in your next reply.

Afterwards attempt to update. If it fails attach a new copy of the CBS logs.

 

[narasimha01]

Thank YOU soo much. the patch is installed successfully.

Could you please tell me what's the issue on the server?
Do I need to follow the same for all the remaining servers? Would you please let me know the fix so that I can proceed with installing the same on remaining servers.

 

[Maxstar]

You're welcome. Glad to hear the update installed successfully this time.

The issue is more a bug and quite difficult to explain in a few words! But, are the remaining servers installed with the same (image / template), and are they on the same patch level. This because the issue may differ even when the error code is the same. So I would suggest to start a new thread for each server!

 

[narasimha01]

Wonderful. Thanks again. yes, all the servers are with same image and same patch level. Anyways, will try install the patch and post in a new thread if they fails .

 

[Maxstar]

Please don't use the same fix without looking at the CBS logs first, it make things more difficult to resolve when i'ts a slightly different issue. So please start a new thread and I will look at them as well.

 

[narasimha01]

I have created a new thread.

windows patch installation failed for windows 2022 server

Please check and let me know if that is the same issue.

 

[Maxstar]

I've spotted the new thread and it seems to be a different issue! That's the reason why we always warn not to use fixes from threads with similar issues!