FransJvr
New member
- Jan 15, 2024
- 2
Hey Guys,
We have been having some issues with one of our 2022 servers failing to install the new CU's.
Troubleshooting this issue I have found there is quite a bit of errors being thrown up when running DISM.
with a few examples being:
I have tried doing a DISM repair pointing at a new ISO, and running the below pointing to a up to date similar 2022 server:
Dism /Online /Cleanup-Image /RestoreHealth /Source:f:\sources\sxs /LimitAccess
Where f is mapped to \\othermachine\c:\windows\servicing\packages
We also tried mapping it to Manifests and Winsxs but we could not get this repaired this way.
Lastly, we were advised to wait for the latest CU(now for Jan 24) but this is still failing on our end.
I have attached CBS/DISM logs and the Componentscanner logs, not sure if anything else is needed in this instance?
We have been having some issues with one of our 2022 servers failing to install the new CU's.
Troubleshooting this issue I have found there is quite a bit of errors being thrown up when running DISM.
Code:
2023-12-01 09:29:18, Info CBS Total Detected Corruption: 396
2023-12-01 09:29:18, Info CBS CBS Manifest Corruption: 396
2023-12-01 09:29:18, Info CBS CBS Metadata Corruption: 0
2023-12-01 09:29:18, Info CBS CSI Manifest Corruption: 0
2023-12-01 09:29:18, Info CBS CSI Metadata Corruption: 0
2023-12-01 09:29:18, Info CBS CSI Payload Corruption: 0
2023-12-01 09:29:18, Info CBS Total Repaired Corruption: 0
2023-12-01 09:29:18, Info CBS CBS Manifest Repaired: 0
2023-12-01 09:29:18, Info CBS CSI Manifest Repaired: 0
2023-12-01 09:29:18, Info CBS CSI Payload Repaired: 0
2023-12-01 09:29:18, Info CBS CSI Store Metadata refreshed: True
2023-12-01 09:29:18, Info CBS Staged Packages:
2023-12-01 09:29:18, Info CBS CBS Staged packages: 0
2023-12-01 09:29:18, Info CBS CBS Staged packages removed: 0
with a few examples being:
Code:
2023-12-05 08:52:17, Info CBS Checking System Update Readiness.
2023-12-05 08:52:17, Info CBS
2023-12-05 08:52:17, Info CBS (p) CBS Catalog Missing (n) Containers-Dynamic-Image-Package~31bf3856ad364e35~amd64~~10.0.20348.1906
2023-12-05 08:52:17, Info CBS Repair failed: Missing replacement mum/cat pair.
2023-12-05 08:52:17, Info CBS (p) CBS Catalog Missing (n) Containers-Server-HNS-Package~31bf3856ad364e35~amd64~~10.0.20348.1906
2023-12-05 08:52:17, Info CBS Repair failed: Missing replacement mum/cat pair.
2023-12-05 08:52:17, Info CBS (p) CBS Catalog Missing (n) Containers-Server-merged-Package~31bf3856ad364e35~amd64~~10.0.20348.1850
2023-12-05 08:52:17, Info CBS Repair failed: Missing replacement mum/cat pair.
2023-12-05 08:52:17, Info CBS (p) CBS Catalog Missing (n) Containers-Server-Package~31bf3856ad364e35~amd64~~10.0.20348.1906
2023-12-05 08:52:17, Info CBS Repair failed: Missing replacement mum/cat pair.
2023-12-05 08:52:17, Info CBS (p) CBS Catalog Missing (n) Containers-Server-SDN-Package~31bf3856ad364e35~amd64~~10.0.20348.1850
2023-12-05 08:52:17, Info CBS Repair failed: Missing replacement mum/cat pair.
2023-12-05 08:52:17, Info CBS (p) CBS Catalog Missing (n) HyperV-Chipset-Package~31bf3856ad364e35~amd64~~10.0.20348.1726
I have tried doing a DISM repair pointing at a new ISO, and running the below pointing to a up to date similar 2022 server:
Dism /Online /Cleanup-Image /RestoreHealth /Source:f:\sources\sxs /LimitAccess
Where f is mapped to \\othermachine\c:\windows\servicing\packages
We also tried mapping it to Manifests and Winsxs but we could not get this repaired this way.
Lastly, we were advised to wait for the latest CU(now for Jan 24) but this is still failing on our end.
I have attached CBS/DISM logs and the Componentscanner logs, not sure if anything else is needed in this instance?