Jul 15 2024 10:09 AM
The below patch fails
DISM fails at 97.2%
Windows Version: Windows Server 2019 Standard x64 (10.0.17763.4737)
Tried DISM with NW and Restore.
Tried to install manually : Failed
CBS logs error:
2024-07-11 11:02:47, Info CSI 00005d75 [SR] Cannot repair member file [l:12]'services.lnk' of Microsoft-Windows-ServicesSnapIn, version 10.0.17763.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch 2024-07-11 11:02:47, Info CSI 00005d78 [SR] Cannot repair member file [l:12]'services.lnk' of Microsoft-Windows-ServicesSnapIn, version 10.0.17763.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch 2024-07-11 11:02:47, Info CSI 00005d79 [SR] This component was referenced by [l:132]'Microsoft-Windows-Server-Gui-Mgmt-Package-admin~31bf3856ad364e35~amd64~~10.0.17763.1.Microsoft-Windows-Server-Gui-Mgmt-Package-admin' 2024-07-11 11:02:47, Info CSI 00005d7a [SR] This component was referenced by [l:116]'Microsoft-Windows-Server-Features-Package01613~31bf3856ad364e35~amd64~~10.0.17763.1.3a3f5d9a1e7ba91a7cc08e1f5d07f00a' 2024-07-11 11:02:47, Info CSI 00005d7d [SR] Could not reproject corrupted file \??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools\\services.lnk; source file in store is also corrupted 2024-07-11 11:02:47, Info CSI 00005d7f [SR] Repair complete
Any help would be highly appreciated!
Jul 16 2024 01:36 AM
HI Aditya,
This issue could be due SxS component corruption. To fix this you should have similar server (2019 with same versoin)and it should be health like patched recently. Both should be accessable over the same network C$.
Please run the following commands.
dism.exe /online /cleanup-image /startcomponentcleanup
dism.exe /online /cleanup-image /restorehelath /source:\\goodserver\c$\windows /limitaccess
Hope this will help