Windows Server 2016

R

rwt

Contributor
Joined
Aug 9, 2019
Posts
13
The server itself has several odd things happening. The Start menu won't show, and the Settings area of Windows won't load. Control Panel is ok, so i think there's some corruption there and have run dism and sfc /scannow with no immediate fix.

Looking at the dism.log (re: the guide on this site), shows this KB4512495 but I can't find this KB as a download from windows catalog. Tried unpackaging all the .cab files from the most recent cumulative update but that didn't help.

Checking System Update Readiness.

(p) CBS Catalog Missing Package_1996_for_KB4512495~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_2006_for_KB4512495~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_2007_for_KB4512495~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_2008_for_KB4512495~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_2009_for_KB4512495~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_2010_for_KB4512495~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_2012_for_KB4512495~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_2013_for_KB4512495~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_2014_for_KB4512495~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_2015_for_KB4512495~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_2016_for_KB4512495~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_2017_for_KB4512495~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_2019_for_KB4512495~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_2020_for_KB4512495~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_2021_for_KB4512495~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_2022_for_KB4512495~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_2023_for_KB4512495~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_2024_for_KB4512495~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_2025_for_KB4512495~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_2026_for_KB4512495~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_2027_for_KB4512495~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_2028_for_KB4512495~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_2029_for_KB4512495~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_2030_for_KB4512495~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_2031_for_KB4512495~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_2032_for_KB4512495~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_2033_for_KB4512495~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_2034_for_KB4512495~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_2035_for_KB4512495~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_2036_for_KB4512495~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_2037_for_KB4512495~31bf3856ad364e35~amd64~~10.0.1.8
(p) CBS Catalog Missing Package_2038_for_KB4512495~31bf3856ad364e35~amd64~~10.0.1.8
(p) CSI Payload Corrupt amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreatCatalog.cdxml
(p) CSI Payload Corrupt amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\Defender.psd1
(p) CSI Payload Corrupt amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpWDOScan.cdxml
(p) CSI Payload Corrupt amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpSignature.cdxml
(p) CSI Payload Corrupt amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreat.cdxml
(p) CSI Payload Corrupt amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpComputerStatus.cdxml
(p) CSI Payload Corrupt amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpScan.cdxml
(p) CSI Payload Corrupt amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreatDetection.cdxml
(p) CSI Payload Corrupt amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpPreference.cdxml

Summary:
Operation: Detect only
Operation result: 0x0
Last Successful Step: CSI store detection completes.
Total Detected Corruption: 41
CBS Manifest Corruption: 32
CBS Metadata Corruption: 0
CSI Manifest Corruption: 0
CSI Metadata Corruption: 0
CSI Payload Corruption: 9
Total Repaired Corruption: 0
CBS Manifest Repaired: 0
CSI Manifest Repaired: 0
CSI Payload Repaired: 0
CSI Store Metadata refreshed: False

Total Operation Time: 430 seconds.

SFCFix crashed (maybe doesn't support server?)

Link to CBS logs
CBS-7-21-2021.zip
 
I've looked on like 5 other Server 2016 computers we have and none of them have these packages in the package folder. Is there a way to tell Microsoft to ignore this package maybe? I guess the other corruptions are still a problem.
 
I'm giving up on this and just suggesting they wipe and install Server 2019. Upgrade install might still have problems.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top