[SOLVED] Windows Server 2019 fail to install KB5040430 with error 0x800f0986

Verricom

Member
Joined
Jun 16, 2024
Posts
7
Basic issue : Server 2019 is consistently failing to apply latest cumulative update packages

This has been a problem since the March cumulative update KB5035849 which caused server crashes due to errors introducted into LSSAS.EXE
The patch KB5037425 was applied to resolve this issue and the server appears to function normally again but is falling behind with updates

The Windows update process for collecting logs as detailed in the forum has been completed as follows

UNDERLINE are timestamps
BOLD items are commands executed
ITALIC items are the resulting responses

2024-07-19 10:58
Open command prompt as administrator

2024-07-19 10:59
SFC /scannow
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.


2024-07-19 11:16
DISM /Online /Cleanup-Image /RestoreHealth
Version: 10.0.17763.3406
Image Version: 10.0.17763.5579
[==========================100.0%==========================]
Error: 0xd0000034
DISM failed. No operation was performed.
For more information, review the log file.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log


2024-07-19 11:25
ComponentsScanner.exe executed as administrator
Note : Various errors were shown whilst executing, the window closed but log file was created

Also attached is the zipped DISM log file as this also contains potentially useful error info

Any help in getting this resolved would be much appreciated.
 

Attachments

Found help on other forums, seems that some files were missing in various WinSXS folders. These were copied in from another known good server using a tool called PowerRun that can copy things as the TrustedInstaller account.
 
Rich (BB code):
2024-07-19 11:24:42, Info                  CBS    (p)    CSI Payload Corrupt    (n)            amd64_microsoft-windows-gdi_31bf3856ad364e35_10.0.17763.1_none_9a99025db2afc948\dciman32.dll
2024-07-19 11:24:42, Info                  CBS    Repair failed: Missing replacement payload.
2024-07-19 11:24:42, Info                  CBS    (p)    CSI Payload Corrupt    (n)            amd64_microsoft-windows-gdi_31bf3856ad364e35_10.0.17763.1_none_9a99025db2afc948\atmlib.dll
2024-07-19 11:24:42, Info                  CBS    Repair failed: Missing replacement payload.
2024-07-19 11:24:42, Info                  CBS    (p)    CSI Payload Corrupt    (n)            amd64_microsoft-windows-f..temutilitylibraries_31bf3856ad364e35_10.0.17763.1_none_da5c41bd47d6c594\ifsutil.dll
2024-07-19 11:24:42, Info                  CBS    Repair failed: Missing replacement payload.
2024-07-19 11:24:42, Info                  CBS    (p)    CSI Payload Corrupt    (n)            amd64_microsoft-windows-f..temutilitylibraries_31bf3856ad364e35_10.0.17763.1_none_da5c41bd47d6c594\ulib.dll
2024-07-19 11:24:42, Info                  CBS    Repair failed: Missing replacement payload.
2024-07-19 11:24:42, Info                  CBS    (p)    CSI Payload Corrupt    (n)            amd64_microsoft-windows-geolocation-framework_31bf3856ad364e35_10.0.17763.1_none_01cebefea44fc567\LocationFrameworkPS.dll
2024-07-19 11:24:42, Info                  CBS    Repair failed: Missing replacement payload.
2024-07-19 11:24:42, Info                  CBS    (p)    CSI Payload Corrupt    (n)            amd64_microsoft-windows-g..rveradmintools-gpmc_31bf3856ad364e35_10.0.17763.1_none_a6f8d4d208e895af\gpmc.msc
2024-07-19 11:24:42, Info                  CBS    Repair failed: Missing replacement payload.
2024-07-19 11:24:42, Info                  CBS    (p)    CSI Payload Corrupt    (n)            amd64_microsoft-windows-globalization_31bf3856ad364e35_10.0.17763.1_none_03d99488371ae4e9\GlobCollationHost.dll
2024-07-19 11:24:42, Info                  CBS    Repair failed: Missing replacement payload.
2024-07-19 11:24:42, Info                  CBS    (p)    CSI Payload Corrupt    (n)            amd64_microsoft-windows-fsrm-common_31bf3856ad364e35_10.0.17763.1_none_ba74958cb8f956e4\srm.dll
2024-07-19 11:24:42, Info                  CBS    Repair failed: Missing replacement payload.
2024-07-19 11:24:42, Info                  CBS    (p)    CSI Payload Corrupt    (n)            amd64_microsoft-windows-fsrm-common_31bf3856ad364e35_10.0.17763.1_none_ba74958cb8f956e4\srmtrace.dll
2024-07-19 11:24:42, Info                  CBS    Repair failed: Missing replacement payload.
2024-07-19 11:24:42, Info                  CBS    (p)    CSI Payload Corrupt    (n)            amd64_microsoft-windows-fsrm-common_31bf3856ad364e35_10.0.17763.1_none_ba74958cb8f956e4\srm_ps.dll
2024-07-19 11:24:42, Info                  CBS    Repair failed: Missing replacement payload.
2024-07-19 11:24:42, Info                  CBS    (p)    CSI Payload Corrupt    (n)            amd64_microsoft-windows-heatcore_31bf3856ad364e35_10.0.17763.1_none_d82da509eac058f1\WindowsDefaultHeatProcessor.dll
2024-07-19 11:24:42, Info                  CBS    Repair failed: Missing replacement payload.
2024-07-19 11:24:42, Info                  CBS    (p)    CSI Payload Corrupt    (n)            amd64_microsoft-windows-i..ectionsharingconfig_31bf3856ad364e35_10.0.17763.1_none_a0fc2f99ecc2f28d\hnetcfg.mof
2024-07-19 11:24:42, Info                  CBS    Repair failed: Missing replacement payload.
2024-07-19 11:24:42, Info                  CBS    (p)    CSI Payload Corrupt    (n)            amd64_microsoft-windows-appmanagement-appvwow_31bf3856ad364e35_10.0.17763.5576_none_00b7b0eac4411c6f\r\AppVEntSubsystems64.dll
2024-07-19 11:24:42, Info                  CBS    Repair failed: Missing replacement payload.

Hi,

I don't know on which other forum you also asked for help, but glad you've managed to resolve this issue. And yes some payload files in the WinSxS were missing as we can see in the excerpt above.

What I'd like to add is that there are other ways than using PowerRun to resolve such issues, especially if you can use another server as source. Then the following command is the easiest way to restore the missing or corrupted files from a known and good working server.

Rich (BB code):
DISM /Online /Cleanup-Image /RestoreHealth /Source:\\ServerName\C$\Windows\WinSxS\ /LimitAccess

Another option is to follow this guide, and with the usage of SFCFix it will automate those things with permissions etc, and this tool is developed by Sysnative to perform such tasks.
 
I did try the SFCfix stuff based on the help guide but didnt fully understand a few of the points.
The other server was on a different site and uncontactable but the guide and notes I found on a reply from a similar issue on answers.microsoft.com made sense and fixed it first time in about 20 mins.
Thank you for the reply though, been struggling with this for ages and had I not succeeded I would likely have asked for a bit more in depth guidance.
 
I did try the SFCfix stuff based on the help guide but didnt fully understand a few of the points.
Can you please let us know the issues you encountered following that guide? Then I can pass them to the administrators for improvement etc...
 
Back
Top