[SOLVED] Windows Server 2016 Standard - Can't Update, Manifest & Payload Corruption

soj4trade

soj4trade

Well-known member
Joined
Jul 14, 2022
Posts
133
Location
US East
Hey folks,

I've got a server running Windows Server 2016 Standard (domain controller) that won't update. Attached is my CBS.log. DISM /Online /Cleanup-Image /RestoreHealth fails saying the source files couldn't be found (classic).

I know how to resolve payload corruptions, but I have no clue how to resolve manifest corruptions. Actually, I think I do, but none of the other servers in our fleet contain the missing .CAT/MUM files in C:\Windows\Servicing\Packages\, and thus I have nothing to import.

What's more, KB4493473 (the update that's throwing all these corruption errors) isn't even installed. Unfortunately it's not present in the Windows Update Catalog, so I can't download it (classic). Bummer that Microsoft does that.
  • DISM /ONLINE /GET-PACKAGES /FORMAT:TABLE - KB4493473 is not there.
  • systeminfo - KB4493473 is not there.
  • wusa /uninstall /KB:4493473 - KB4493473 is not installed.

I ran the FRST64.exe application and got thousands of hits for KB4493473. See attached. But alas, I don't really know what to do with that info. Hoping you can assist! :)
 

Attachments

Hi again, ;)

Step 1. Download
56f31e53c97da-SFCFix.PNG
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.
6190d993a26f3-SFCFix-Zip-Eng.gif

  • 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. If Windows Update failes upload a copy of the COMPONENTS hive as well.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Code: 
C:\Windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.14393.4169

Image Version: 10.0.14393.4169

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

I'll run updates tonight and keep you posted!!
 
Perfect, when the installation of updates fails, we should probably also repair the registry keys regarding the following files.

Rich (BB code): 
(p)    CSI Payload Corrupt            amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreatCatalog.cdxml
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\Defender.psd1
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpWDOScan.cdxml
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpSignature.cdxml
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreat.cdxml
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpComputerStatus.cdxml
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpScan.cdxml
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpThreatDetection.cdxml
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.14393.0_none_1137c685b804c9a3\MSFT_MpPreference.cdxml
Repair failed: Missing replacement payload.
 
Dang, I might have spoken too soon.. Windows does update, but now I'm getting this when making an attempt to clean the component store:

Code: 
C:\Windows\system32>dism /online /cleanup-image /startcomponentcleanup

Deployment Image Servicing and Management tool
Version: 10.0.14393.4169

Image Version: 10.0.14393.4169

[==========================100.0%==========================]

Error: 2

The system cannot find the file specified.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
 

Attachments

Hi,

Could you please run dism /online /cleanup-image /startcomponentcleanup while ProcMon is running?

Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Run the DISM command just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square (CTRL +E) on the toolbar as shown below.



4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up the LogFile.PML and upload it to WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free and provide the link.
 
Hey Maxstar, sorry for the bad info... I saw one package listed as "Staged". I removed it, rebooted, and now DISM /Online /Cleanup-Image /AnalyzeComponentStore and DISM /Online /Cleanup-Image /StartComponentCleanup both succeed @ 100%. Thanks a million for your help!!
 
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