[SOLVED] CU Install Error on Server 2019 - 0x800f0983

nongilg · Jul 18, 2024

Hello,

The cumulative update for Server 2019 no longer installs since the April 2024 update.

I have a servicing stack wcp.dll error in the logs.
I noticed that the version indicated by winver is 17763.5820 but that the dll version is 17763.6040.

CSI 00000001 Shim considered [l:126]'\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17763.6040_none_5710df3f98fe5d57\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND
CSI 00000002 Shim considered [l:123]'\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17763.6040_none_5710df3f98fe5d57\wcp.dll' : got STATUS_SUCCESS

As if the maintenance stack update hadn't installed correctly.

After browsing sites and forums, and trying several workarounds :
- Dsim restaure
- Copy localy from other computer the package
- Replace manually the dll

I managed to install the April and May updates by switching the language to English instead of French.
However, the June and July updates are still blocking.

Here attached the log files.

Thank you for your help.

nongilg · Jul 23, 2024

Hello,

I've just seen that when installing the update, I have another error in the CBS.log.
That I don't have on a manual dsim scan.

Do you have any idea?

2024-07-22 22:06:43, Error CBS Failed to perform operation. [HRESULT = 0x800f0983 - PSFX_E_MATCHING_COMPONENT_DIRECTORY_MISSING]
2024-07-22 22:06:43, Info CBS Session: 31120498_1332458327 finalized. Reboot required: no [HRESULT = 0x800f0983 - PSFX_E_MATCHING_COMPONENT_DIRECTORY_MISSING]
2024-07-22 22:06:43, Info CBS Failed finalizing session [HRESULT = 0x800f0983 - PSFX_E_MATCHING_COMPONENT_DIRECTORY_MISSING]
2024-07-22 22:06:43, Info CBS Failed to call Process on TiWorker session [HRESULT = 0x800f0983]
2024-07-22 22:06:58, Info CBS Repr: CBS Store check completes
2024-07-22 22:06:58, Info CSI 0000002c StoreCorruptionRepair transaction begun. WcpVersion: [l:38]'10.0.17763.6040 (WinBuild.160101.0800)'.
2024-07-22 22:06:58, Info CSI 0000002d@2024/7/22:20:06:58.974 Starting corruption detection (InnerFlags=10)
2024-07-22 22:07:35, Error CSI 0000002e (F) STATUS_OBJECT_NAME_NOT_FOUND #2909319# from Windows::Rtl::SystemImplementation:

irectFileSystemProvider::SysCreateFile(flags = 0, handle = {provider=NULL, handle=0, name= ("null")}, da = (FILE_GENERIC_READ), oa = @0x4f95a7d538->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[120]'\SystemRoot\WinSxS\wow64_microsoft-windows-wmi-core_31bf3856ad364e35_10.0.17763.5830_none_1102a9ce25ef0deb\r\mofcomp.exe'; a

OBJ_CASE_INSENSITIVE)}, iosb = @0x4f95a7d590, as = (null), fa = 0, sa = (FILE_SHARE_READ|FILE_SHARE_[gle=0xd0000034]
2024-07-22 22:07:35, Error CSI WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_NON_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid)
[gle=0xd0000034]
2024-07-22 22:07:35, Error CSI 0000002f@2024/7/22:20:07:35.850 (F) onecore\base\wcp\sil\ntsystem.cpp(2987): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation:

irectFileSystemProvider::SysCreateFile expression: (null)
[gle=0x80004005]
2024-07-22 22:07:35, Error CSI 00000030 (F) STATUS_OBJECT_NAME_NOT_FOUND #2909318# from Windows::Rtl::SystemImplementation::CDirectory::OpenExistingFile(...)[gle=0xd0000034]
2024-07-22 22:07:35, Error CSI 00000031 (F) STATUS_OBJECT_NAME_NOT_FOUND #2909317# from Windows::Rtl::SystemImplementation::CDirectory_IRtlDirectoryTearoff::OpenExistingFile(flags = 0, da = (FILE_GENERIC_READ), oa = @0x4f95a7db78->SIL_OBJECT_ATTRIBUTES {s:40; on:"mofcomp.exe"; a

OBJ_CASE_INSENSITIVE)}, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), oo = (FILE_SYNCHRONOUS_IO_NONALERT|FILE_NON_DIRECTORY_FILE|FILE_OPEN_FOR_BACKUP_INTENT), file = NULL, disp = Invalid)
[gle=0xd0000034]
2024-07-22 22:08:46, Error CSI 00000032 (F) Failed to clear possible corruptions file with status STATUS_SUCCESS and disposition 3[gle=0x80004005]
2024-07-22 22:08:46, Error CSI 00000033@2024/7/22:20:08:46.726 (F) Attempting to mark store corrupt with category [l:18 ml:19]'CorruptPayloadFile'[gle=0x80004005]
2024-07-22 22:08:46, Info CSI 00000034@2024/7/22:20:08:46.757 Corruption detection complete. numCorruptions = 1, Disp = 1.
2024-07-22 22:08:47, Info CBS Repr: CSI meta data corruption found, will commit repair transaction if repair is asked.
2024-07-22 22:08:47, Info CBS Repr: CSI Store check completes
2024-07-22 22:08:47, Info CBS Exec: Not able to find wow64_microsoft-windows-wmi-core_31bf3856ad364e35_10.0.17763.5830_none_1102a9ce25ef0deb\r\mofcomp.exe from directory local source
2024-07-22 22:08:47, Info CBS Exec: Not able to find WinSxS\wow64_microsoft-windows-wmi-core_31bf3856ad364e35_10.0.17763.5830_none_1102a9ce25ef0deb\r\mofcomp.exe from directory local source
2024-07-22 22:08:47, Info CBS Repr: Not able to find replacement file for component wow64_microsoft-windows-wmi-core_31bf3856ad364e35_10.0.17763.5830_none_1102a9ce25ef0deb, file r\mofcomp.exe from any local source
2024-07-22 22:08:47, Info CBS Repr: Add missing payload:wow64_microsoft-windows-wmi-core_31bf3856ad364e35_10.0.17763.5830_none_1102a9ce25ef0deb\r\mofcomp.exe
2024-07-22 22:08:47, Info CBS FC: Calling Download on WUClient Acquirer
2024-07-22 22:08:47, Info CBS FC: Calling WindowsUpdateDownloadFromUUP
2024-07-22 22:08:47, Info CBS FC: WULib Mode Complete: [0]
2024-07-22 22:08:47, Info CBS WU: Microsoft Update service is the default, URL: https://fe2.update.microsoft.com/v6/, Name: Microsoft Update
2024-07-22 22:08:47, Info CBS Not able to read BranchName [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2024-07-22 22:08:47, Info CBS Not able to read ContentType [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2024-07-22 22:08:47, Info CBS Not able to read Ring [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2024-07-22 22:08:47, Info CBS Not able to read IsBuildFlightingEnabled [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2024-07-22 22:08:47, Info CBS Windows Insider Program: Current settings: Content type: (null), Build branch: (null), Ring: (null), Build Flighting Enabled: No
2024-07-22 22:08:47, Info CBS WU: Windows update server selection group policy not set [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2024-07-22 22:08:47, Info CBS DWLD: Current product search criteria: (Product='Server.OS.amd64' and CurrentVersionOnly=1)
2024-07-22 22:09:08, Info CBS Session: 31120499_49718868 initialized by client WinMgmt, external staging directory: (null), external registry directory: (null

2024-07-22 22:10:49, Info CBS Failed to collect payload and there is nothing to repair. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2024-07-22 22:10:49, Info CBS Failed to repair store. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2024-07-22 22:10:49, Info CBS
2024-07-22 22:10:49, Info CBS =================================
2024-07-22 22:10:49, Info CBS Checking System Update Readiness.
2024-07-22 22:10:49, Info CBS
2024-07-22 22:10:49, Info CBS (p) CSI Payload Corrupt

wow64_microsoft-windows-wmi-core_31bf3856ad364e35_10.0.17763.5830_none_1102a9ce25ef0deb\r\mofcomp.exe
2024-07-22 22:10:49, Info CBS Repair failed: Missing replacement payload.
2024-07-22 22:10:49, Info CBS
2024-07-22 22:10:49, Info CBS Summary:
2024-07-22 22:10:49, Info CBS Operation: Detect and Repair
2024-07-22 22:10:49, Info CBS Operation result: 0x800f081f
2024-07-22 22:10:49, Info CBS Last Successful Step: Entire operation completes.
2024-07-22 22:10:49, Info CBS Total Detected Corruption: 1
2024-07-22 22:10:49, Info CBS CBS Manifest Corruption: 0
2024-07-22 22:10:49, Info CBS CBS Metadata Corruption: 0
2024-07-22 22:10:49, Info CBS CSI Manifest Corruption: 0
2024-07-22 22:10:49, Info CBS CSI Metadata Corruption: 0
2024-07-22 22:10:49, Info CBS CSI Payload Corruption: 1
2024-07-22 22:10:49, Info CBS Total Repaired Corruption: 0
2024-07-22 22:10:49, Info CBS CBS Manifest Repaired: 0
2024-07-22 22:10:49, Info CBS CSI Manifest Repaired: 0
2024-07-22 22:10:49, Info CBS CSI Payload Repaired: 0
2024-07-22 22:10:49, Info CBS CSI Store Metadata refreshed: True
2024-07-22 22:10:49, Info CBS
2024-07-22 22:10:49, Info CBS Total Operation Time: 249 seconds.
2024-07-22 22:10:49, Info CBS Ensure CBS corruption flag is clear
2024-07-22 22:10:49, Info CBS Not all CSI corruption was fixed, create CorruptionDetectedDuringAcr flag for slow mode reset
2024-07-22 22:10:49, Info CBS CheckSur: hrStatus: 0x800f081f [CBS_E_SOURCE_MISSING], download Result: 0x800f081f [CBS_E_SOURCE_MISSING]
2024-07-22 22:10:49, Info CBS Count of times corruption detected: 2
2024-07-22 22:10:49, Info CBS Seconds between initial corruption detections: -1
2024-07-22 22:10:49, Info CBS Seconds between corruption and repair: -1
2024-07-22 22:10:49, Info CBS Failed to run Detect and repair. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2024-07-22 22:10:50, Info CBS Reboot mark cleared

Regards,

Maxstar · Jul 24, 2024

Hi and welcome to Sysnative,

Step 1. 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.

Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.

Code:

DISM /online /cleanup-image /RestoreHealth

nongilg · Jul 24, 2024

Hello,

Thank you for your feedback.

Since yesterday, I managed to make the WMI-Core error disappear by removing the functionality in the manager and launching a dism repair with a winsxs from another 2019 server as source.

Behind, I got an error on: amd64_microsoft-windows-security-spp-clientext_31bf3856ad364e35_10.0.17763.5830_none_1a20f23b8314a13a

================================
2024-07-24 11:22:50, Info CBS Checking System Update Readiness.
2024-07-24 11:22:50, Info CBS
2024-07-24 11:22:50, Info CBS (p) CSI Payload Corrupt (l) (Fixed) amd64_microsoft-windows-security-spp-clientext_31bf3856ad364e35_10.0.17763.5830_none_1a20f23b8314a13a\f\sppcext.dll
2024-07-24 11:22:50, Info CBS (p) CSI Payload Corrupt (l) (Fixed) amd64_microsoft-windows-security-spp-clientext_31bf3856ad364e35_10.0.17763.5830_none_1a20f23b8314a13a\r\sppcext.dll
2024-07-24 11:22:50, Info CBS (p) CSI Payload Corrupt (l) (Fixed) amd64_microsoft-windows-security-spp-clientext_31bf3856ad364e35_10.0.17763.5830_none_1a20f23b8314a13a\f\slcext.dll
2024-07-24 11:22:50, Info CBS (p) CSI Payload Corrupt (l) (Fixed) amd64_microsoft-windows-security-spp-clientext_31bf3856ad364e35_10.0.17763.5830_none_1a20f23b8314a13a\r\slcext.dll
2024-07-24 11:22:50, Info CBS (p) CSI Payload Corrupt

amd64_microsoft-windows-setup-component_31bf3856ad364e35_10.0.17763.5830_none_7f867ab57f37f494\r\Setup.exe
2024-07-24 11:22:50, Info CBS Repair failed: Missing replacement payload.
2024-07-24 11:22:50, Info CBS
2024-07-24 11:22:50, Info CBS Summary:
2024-07-24 11:22:50, Info CBS Operation: Detect and Repair
2024-07-24 11:22:50, Info CBS Operation result: 0x800f081f
2024-07-24 11:22:50, Info CBS Last Successful Step: Entire operation completes.
2024-07-24 11:22:50, Info CBS Total Detected Corruption: 5
2024-07-24 11:22:50, Info CBS CBS Manifest Corruption: 0
2024-07-24 11:22:50, Info CBS CBS Metadata Corruption: 0
2024-07-24 11:22:50, Info CBS CSI Manifest Corruption: 0
2024-07-24 11:22:50, Info CBS CSI Metadata Corruption: 0
2024-07-24 11:22:50, Info CBS CSI Payload Corruption: 5
2024-07-24 11:22:50, Info CBS Total Repaired Corruption: 4
2024-07-24 11:22:50, Info CBS CBS Manifest Repaired: 0
2024-07-24 11:22:50, Info CBS CSI Manifest Repaired: 0
2024-07-24 11:22:50, Info CBS CSI Payload Repaired: 4
2024-07-24 11:22:50, Info CBS CSI Store Metadata refreshed: True
2024-07-24 11:22:50, Info CBS
2024-07-24 11:22:50, Info CBS Total Operation Time: 220 seconds.

Based on another resolved post, I looked in the COMPONENTS registry, in order to compare with my other working server.
I exported the corresponding key and imported it.

I no longer get the SPP error, but the installation doesn't work: 0x8007371b.
I don't get a dism error, but when I run the componentsscanner I get the error:

== f! Mark Count Mismatch ==
amd64_microsoft-windows-security-spp-clientext_31bf3856ad364e35_10.0.17763.5830_none_1a20f23b8314a13a has 3 f! marks, expected 1

Here attached the new log files and reg import.

Thank you for your help.

Maxstar · Jul 24, 2024

nongilg said:
I no longer get the SPP error, but the installation doesn't work: 0x8007371b.

Please attach the latest CBS logs as well as a copy of the SBS hive.

Upload a copy of the CBS folder

Open Windows Explorer and browse to the C:\Windows\Logs folder.
Right-click on the CBS folder and choose Send to > Compressed (zipped) folder.
Now the message will appear, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?"
Click on the Yes button here.

Attach the file CBS.zip to your next reply. If the file is too large to attach, upload the CBS.zip file to www.wetransfer.com and post the link in your next reply.

Export SBS (SideBySide) hive

Click on the Start button and type regedit
When you see regedit on the list, right-click on it and select Run as administrator.
When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.
Code:
```
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide
```
Once selected, click File > Export....
Change the Save as type: to Registry Hive Files (*.*).
Name this file SideBySide (with no file extension) and save it to your Desktop.
Right-click on the saved file and choose Send > Compressed (zipped) Folder.
Attach the .ZIP file to your next post.
If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.

nongilg · Jul 24, 2024

Here are the files.

Maxstar · Jul 24, 2024

Step 1. 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.

Step 2. Run

ComponentsScanner again.

Right-click ComponentsScanner.exe and select "Run as administrator", click Yes on the UAC (User Account Control) prompt which appears.
Follow the on-screen instructions.
Once complete, a report will be saved to your desktop called ComponentsScanner.txt.
Post the logfile ComponentsScanner.txt as attachment into your next reply.

nongilg · Jul 24, 2024

There are no more errors.

Maxstar · Jul 24, 2024

Great, please attempt to update again.If it fails attach the new CBS logs.

nongilg · Jul 24, 2024

It's ok.

Thank you very much for your time and help.

Maxstar · Jul 24, 2024

Oh, ok! You have already attempted to update again. Then let me know the result after the restart....

nongilg · Jul 24, 2024

Restart ok. Problem solved.
It's really weird these corruptions, I have a good ten 2019s, this is the only one that did this to me.

Thank you very much for your time and help.

Maxstar · Jul 25, 2024

Hi,

You're welome. Glad to hear everything is up-to-date now...

I will mark this thread as solved.

Search

Search

[SOLVED] CU Install Error on Server 2019 - 0x800f0983

nongilg

Member

Attachments

nongilg

Member

Maxstar

Windows Update Moderator, Security Analyst

Attachments

nongilg

Member

Attachments

Maxstar

Windows Update Moderator, Security Analyst

nongilg

Member

Attachments

Maxstar

Windows Update Moderator, Security Analyst

Attachments

nongilg

Member

Attachments

Maxstar

Windows Update Moderator, Security Analyst

nongilg

Member

Maxstar

Windows Update Moderator, Security Analyst

nongilg

Member

Maxstar

Windows Update Moderator, Security Analyst