Windows Server 2019 gets Source Error when running DISM

[KRAER]

Hello Community!

I am having a problem with Server 2019 regarding Updates and DISM Runs.

Here is the CBS portion that tells me how many problems I have ... and what should I tell you? It's 232 problems but ...

CBS.Log:

[...]
2024-02-02 19:39:42, Info                  CBS    Summary:
2024-02-02 19:39:42, Info                  CBS    Operation: Detect and Repair
2024-02-02 19:39:42, Info                  CBS    Operation result: 0x800f081f
2024-02-02 19:39:42, Info                  CBS    Last Successful Step: Entire operation completes.
2024-02-02 19:39:42, Info                  CBS    Total Detected Corruption:    232
2024-02-02 19:39:42, Info                  CBS        CBS Manifest Corruption:    0
2024-02-02 19:39:42, Info                  CBS        CBS Metadata Corruption:    231
2024-02-02 19:39:42, Info                  CBS        CSI Manifest Corruption:    0
2024-02-02 19:39:42, Info                  CBS        CSI Metadata Corruption:    0
2024-02-02 19:39:42, Info                  CBS        CSI Payload Corruption:    1
2024-02-02 19:39:42, Info                  CBS    Total Repaired Corruption:    0
2024-02-02 19:39:42, Info                  CBS        CBS Manifest Repaired:    0
2024-02-02 19:39:42, Info                  CBS        CSI Manifest Repaired:    0
2024-02-02 19:39:42, Info                  CBS        CSI Payload Repaired:    0
2024-02-02 19:39:42, Info                  CBS        CSI Store Metadata refreshed:    True
[...]

I could fix one Manifest Corruption already. But the rest is a problem for me.

And I let the Components Scanner run and got this:

ComponentsScanner Version 1.5.1.0 by sysnative.com
Windows Version: Windows Server 2019 Standard x64 (10.0.17763.5329)
Start time: 2024-02-02T20:05:11
Hive scanned: %windir%\System32\config\COMPONENTS
Number of keys: 178650
Number of values: 500121


==== Critical Errors ====
None


==== Corrupt Key Names ====
None


==== Corrupt Value Names ====
None


==== Corrupt Value Data Type ====
None


==== Corrupt Value Data ====
None


==== Repair Log ====
No possible repairs


==== Warnings ====


== Corrupt Files ==
C:\Windows\winsxs\Catalogs\5c8ec6e59fd3687f2edf5425ceee5595bb35509833778d6a8b9bb46b453a1ea4.cat (Expected SHA256: 5c8ec6e59fd3687f2edf5425ceee5595bb35509833778d6a8b9bb46b453a1ea4. Actual SHA256: 6f2bd6039516811fba9af3d7ab3d7ef87081f10a5c6c285580ffc2a63fe09600
C:\Windows\winsxs\Catalogs\adbd74e0f5278da72740546e61d4133c2e44c9a22549f8b406e5e3c048dfac14.cat (Expected SHA256: adbd74e0f5278da72740546e61d4133c2e44c9a22549f8b406e5e3c048dfac14. Actual SHA256: cf2a6452266f0bfa675e046a0b2b8a8839f282610cb4800c19dce55f7c3631d1






Storing 2,89KB in C:\Users\Administrator\AppData\Local\Sysnative\ComponentsScanner
Archived report directory contains 2 files


Finish Time: 2024-02-02T20:20:55. Corruption scan time: 930,3774131s
===========================EOF===========================

Maybe you have a hint on what to do ..

Thanks

KRAER

 

[Maxstar]

Hi and welcome to Sysnative,

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.