[SOLVED] Server 2016 (1607) RestoreHealth missing components

cavaliersa

cavaliersa

Windows Update Trainee
Joined
Jul 24, 2023
Posts
35
Location
Johannesburg, South Africa
I have Windows Server 2016 (1607) VM with some component store issues. I've managed to trace some 90 other missing files from other VMs, but despite provisioning a new VM with the RTM 2016 ISO and installing the same features I am still unable to find the below files.
(p) CSI Payload Corrupt amd64_microsoft-windows-printing3d-winrt-core_31bf3856ad364e35_10.0.14393.0_none_c3a3413c8c9e2d6e\Windows.Graphics.Printing.3D.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_microsoft-windows-printing-winrt-core_31bf3856ad364e35_10.0.14393.0_none_21e57b3122388569\Windows.Graphics.Printing.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_microsoft-windows-profsvc_31bf3856ad364e35_10.0.14393.0_none_2925c2e8495fb010\profsvc.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_microsoft-windows-r..ral-language-client_31bf3856ad364e35_10.0.14393.0_none_e9f98a40bc58c4f0\RemoteNaturalLanguage.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_microsoft-windows-rasmprddm_31bf3856ad364e35_10.0.14393.0_none_c68abc9fe44aeffd\mprddm.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_microsoft-windows-rasserver_31bf3856ad364e35_10.0.14393.0_none_d91da4d27e7f8576\iprtrmgr.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_microsoft-windows-rasmanservice_31bf3856ad364e35_10.0.14393.0_none_cc3201bcb75b27c0\rasmans.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_microsoft-windows-printing-dialogs_31bf3856ad364e35_10.0.14393.0_none_367e1fbf666b0c64\PrintDialogs.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_microsoft-windows-printing-dialogs3d_31bf3856ad364e35_10.0.14393.0_none_1ea89b5dd9315f93\PrintDialogs3D.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_microsoft-windows-printing-wsdahost_31bf3856ad364e35_10.0.14393.0_none_2a6969d5aaa7f490\PrintWSDAHost.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_microsoft-windows-printing-localprinting_31bf3856ad364e35_10.0.14393.0_none_f9b838674202b991\localui.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_microsoft-windows-qedit_31bf3856ad364e35_10.0.14393.0_none_881048285e19fc2e\qedit.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_microsoft-windows-rasbase-rascustom_31bf3856ad364e35_10.0.14393.0_none_2691f0d4d3695a72\rascustom.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_microsoft-windows-rmapi_31bf3856ad364e35_10.0.14393.0_none_86ed5bf17856a4e4\RMapi.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_microsoft-windows-r..s-regkeys-component_31bf3856ad364e35_10.0.14393.0_none_5d02961f1e81d0f8\rdpudd.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_microsoft-windows-printing-spooler-core_31bf3856ad364e35_10.0.14393.0_none_03c00e9cd83b697d\spoolsv.exe
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_microsoft-windows-r..ckgroundmediapolicy_31bf3856ad364e35_10.0.14393.0_none_70789e6f1b60c075\BackgroundMediaPolicy.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_microsoft-windows-r..ckgroundmediaplayer_31bf3856ad364e35_10.0.14393.0_none_e95a6db4c0d1e852\Windows.Media.BackgroundMediaPlayback.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_microsoft-windows-resourcemanager-server_31bf3856ad364e35_10.0.14393.0_none_4d5e1ef7bed192d0\PsmServiceExtHost.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_microsoft-windows-r..ndows-media-editing_31bf3856ad364e35_10.0.14393.0_none_adebb9fcafa36dc1\Windows.Media.Editing.dll
Repair failed: Missing replacement payload.
Click to expand...

Does anyone have these files for an SFCFix?
 
Hi,

Here are the requested files.

Step 1. Download
6530fbb0f4101-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.
650c22f99662d-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.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Thanks, the SFCFix applied as it should but the subsequent RestoreHealth still failed on these 20 files, but I think it is complaining about the file hashes being different (expected vs what is) - the CBS log is attached.
PS 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

[===========================80.0%============== ]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source.

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

Attachments

Hi,

Upload your COMPONENTS hive.
  • Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
  • Please copy this file to your desktop.
  • Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
  • Right-click on this file on your desktop and select Send To > Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
 
Here's the next fix.

Step 1.
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.
650c22f99662d-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.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Thanks. RestoreHealth went through, then AnalyzeComponentStore showed a number of packages that could be claimed so ran StartComponentCleanup; this gave an error.
PS 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

[============= 23.8% ]

Error: 14098

The component store has been corrupted.

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

Ran through sfc /verifyonly (clean) followed by dism /online /cleanup-image /scanhealth (The component store is repairable). So followed up with a RestoreHealth which gave the below (CBS log file attached).
PS 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

[===========================80.0%============== ]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source.

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

Attachments

Here's the next fix.

Step 1.
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.
650c22f99662d-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.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Thanks. It seems to still be moaning about the same two files.
(p) CSI Payload Corrupt amd64_microsoft-windows-rpc-local_31bf3856ad364e35_10.0.14393.0_none_e16f0a925bc6f3c6\rpcrt4.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_microsoft-windows-rpc-kernel_31bf3856ad364e35_10.0.14393.0_none_ec80ef5098993856\msrpc.sys
Repair failed: Missing replacement payload.
Click to expand...
Here is the current CBS log file and components hive.
20240419_1445.zip
 
Here's the next fix with the uncompressed files.

Step 1.
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.
650c22f99662d-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.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Please post the CBS logs, then I can check the expected hash values if it's logged..

Step 1.
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.
650c22f99662d-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.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Next fix.

Step 1.
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.
650c22f99662d-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.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Here are the next missing files.
(p) CSI Payload Corrupt amd64_microsoft-windows-s..-credentialprovider_31bf3856ad364e35_10.0.14393.0_none_108b6895d1e59826\BioCredProv.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_microsoft-windows-runtime-windows-media_31bf3856ad364e35_10.0.14393.0_none_74ddd78ce52ff282\Windows.Media.dll
Repair failed: Missing replacement payload.
Click to expand...

I really wish it would just give all of them at once 😅
 

Attachments

I really wonder what happend with this server and/or which previous fixes where applied?

Step 1.
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.
650c22f99662d-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.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

This explains a lot why such issues arise after the lack of maintaince...
 
Yup, all of the various stores are left to just grow and grow, temp file locations are never attended to, logs trimmed, the machine gets slower and slower, Windows Updates take forever, the WinSxS folder grows to 50GB+ in size, etc.
I'm fixing these servers as and when I find them. The one I fixed earlier this week went from 63GB WinSxS down to 8GB. It took a few iterations of RestoreHealth and StartComponentCleanup but it got there.

Here is the latest missing file.
(p) CSI Payload Corrupt amd64_microsoft-windows-s..-csvlk-pack-license_31bf3856ad364e35_10.0.14393.0_none_96990dda3b46b6b9\csvlk-pack-Volume-CSVLK-6-ul-phn-rtm.xrm-ms
Repair failed: Missing replacement payload.
Click to expand...
 

Attachments

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