[SOLVED] Windows Server 2012 Standard, Won't Update, Missing Payloads

soj4trade

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

I have two servers running Windows Server 2012 Standard (that's not 2012 R2, it's just normal 2012). DISM /Online /Cleanup-Image /RestoreHealth fails with the error:
Code:
C:\Windows\system32>DISM /Online /Cleanup-Image /restoreHealth

Deployment Image Servicing and Management tool
Version: 6.2.9200.22807

Image Version: 6.2.9200.22807

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

Error: 0x80240440

DISM failed. No operation was performed.
For more information, review the log file.

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

CBS.log is attached. Unfortunately all of the missing payloads are associated with Windows Updates that are expired/no longer available on the update catalog. Here they are:
Code:
=================================
Checking System Update Readiness.

(p)    CSI Payload Corrupt            x86_prnms003.inf_31bf3856ad364e35_6.2.9200.17285_none_4f7b6c1ba546002e\I386\unishare-pipelineconfig.xml
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_prnms003.inf_31bf3856ad364e35_6.2.9200.17285_none_4f7b6c1ba546002e\I386\unishare.gpd
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_prnms003.inf_31bf3856ad364e35_6.2.9200.17285_none_4f7b6c1ba546002e\I386\PrintConfig.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_prnms003.inf_31bf3856ad364e35_6.2.9200.17285_none_4f7b6c1ba546002e\prnms003.cat
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_prnms003.inf_31bf3856ad364e35_6.2.9200.17285_none_4f7b6c1ba546002e\prnms003.inf
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_prnms003.inf_31bf3856ad364e35_6.2.9200.17285_none_ab9a079f5da37164\Amd64\PrintConfig.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_prnms003.inf_31bf3856ad364e35_6.2.9200.17285_none_ab9a079f5da37164\Amd64\unishare.gpd
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_prnms003.inf_31bf3856ad364e35_6.2.9200.17285_none_ab9a079f5da37164\Amd64\unishare-pipelineconfig.xml
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_prnms003.inf_31bf3856ad364e35_6.2.9200.17285_none_ab9a079f5da37164\prnms003.cat
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_prnms003.inf_31bf3856ad364e35_6.2.9200.17285_none_ab9a079f5da37164\prnms003.inf
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_prnms003.inf_31bf3856ad364e35_6.2.9200.21401_none_50578904be26583b\I386\unishare-pipelineconfig.xml
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_prnms003.inf_31bf3856ad364e35_6.2.9200.21401_none_50578904be26583b\I386\unishare.gpd
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_prnms003.inf_31bf3856ad364e35_6.2.9200.21401_none_50578904be26583b\I386\PrintConfig.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_prnms003.inf_31bf3856ad364e35_6.2.9200.21401_none_50578904be26583b\prnms003.cat
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            x86_prnms003.inf_31bf3856ad364e35_6.2.9200.21401_none_50578904be26583b\prnms003.inf
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_prnms003.inf_31bf3856ad364e35_6.2.9200.21401_none_ac7624887683c971\Amd64\PrintConfig.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_prnms003.inf_31bf3856ad364e35_6.2.9200.21401_none_ac7624887683c971\Amd64\unishare.gpd
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_prnms003.inf_31bf3856ad364e35_6.2.9200.21401_none_ac7624887683c971\Amd64\unishare-pipelineconfig.xml
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_prnms003.inf_31bf3856ad364e35_6.2.9200.21401_none_ac7624887683c971\prnms003.cat
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_prnms003.inf_31bf3856ad364e35_6.2.9200.21401_none_ac7624887683c971\prnms003.inf
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_prnms004.inf_31bf3856ad364e35_6.2.9200.17285_none_ac2319d476c1adcd\Amd64\unishare-manifest.ini
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_prnms004.inf_31bf3856ad364e35_6.2.9200.17285_none_ac2319d476c1adcd\Amd64\unishare.gpd
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_prnms004.inf_31bf3856ad364e35_6.2.9200.17285_none_ac2319d476c1adcd\Amd64\unishare-pipelineconfig.xml
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_prnms004.inf_31bf3856ad364e35_6.2.9200.17285_none_ac2319d476c1adcd\prnms004.cat
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_prnms004.inf_31bf3856ad364e35_6.2.9200.17285_none_ac2319d476c1adcd\prnms004.inf
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_prnms004.inf_31bf3856ad364e35_6.2.9200.21401_none_acff36bd8fa205da\Amd64\unishare-manifest.ini
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_prnms004.inf_31bf3856ad364e35_6.2.9200.21401_none_acff36bd8fa205da\Amd64\unishare.gpd
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_prnms004.inf_31bf3856ad364e35_6.2.9200.21401_none_acff36bd8fa205da\Amd64\unishare-pipelineconfig.xml
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_prnms004.inf_31bf3856ad364e35_6.2.9200.21401_none_acff36bd8fa205da\prnms004.cat
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_prnms004.inf_31bf3856ad364e35_6.2.9200.21401_none_acff36bd8fa205da\prnms004.inf
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_wnetvsc_vfpp.inf_31bf3856ad364e35_6.3.9600.18692_none_8de8e6efb8dfd888\wnetvsc_vfpp.inf
Repair failed: Missing replacement payload.

Summary:
Operation: Detect and Repair
Operation result: 0x80240440
Last Successful Step: Entire operation completes.
Total Detected Corruption:    31
    CBS Manifest Corruption:    0
    CBS Metadata Corruption:    0
    CSI Manifest Corruption:    0
    CSI Metadata Corruption:    0
    CSI Payload Corruption:    31
Total Repaired Corruption:    0
    CBS Manifest Repaired:    0
    CSI Manifest Repaired:    0
    CSI Payload Repaired:    0
    CSI Store Metadata refreshed:    True

Total Operation Time: 14107 seconds.

Many thanks, as always!! And here's CBS.log: Cbs2.log
 
Hello,

Follow the instructions below please.

Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
  • Download
    myjIXnC.png
    SFCFix and move the executable to your desktop.
  • Download the attachment SFCFix.zip and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
    1p8eDnI.gif
  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Open the file, then copy and paste its content in your next reply.

Step 2:
Provide the Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. 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. Note: If you find that you need to reboot and are unable to because this is a server then try Option#2 below.
3. 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.
4. The file will likely be too large to upload here so please upload to Gofile or WeTransfer and just provide the link here.


Option#2 (only if you are unable to follow the previous instructions)

  • Please download the Freeware RegBak from here: Acelogix Software - Download products
    You will find it at the bottom of the page that the link brings you to.
  • Go ahead and install this program and accept all the defaults. After the last install screen the program should open.
  • Click the New Backup button. Accept the defaults and simply click Start.
  • When it says Finished successfully, click the Close button.
  • This will bring you back to the main screen of the program. You will see one entry in this list with the date that you did it. Right-click on this line-item and select Explore Backup...
  • This will bring you into the folder where the backup was made. You should see a Users folder and a Windows folder along with a couple other files. Double-click on the Windows folder to open it. Then open the System32 folder and then config folder. You should see around 6 files in here, one of which is named COMPONENTS.
  • Copy the COMPONENTS file to your Desktop. If the COMPONENTS file does not exist, please fetch it instead from C:\Windows\System32\config\COMPONENTS.
  • Now right-click on the COMPONENTS file that is on your desktop and select Send to > Compressed (zipped) folder.
  • Then please upload the zip file (COMPONENTS.zip) to your favourite file sharing website (it will be too big to upload here). Examples of services to upload to are Gofile or WeTransfer and then just provide the link in your reply.
  • You can close any open windows you have as well as the RegBak program now.
 

Attachments

Do you have access to another Windows Server 2012 Standard having the bolded folder C:\Windows\winsxs\amd64_wnetvsc_vfpp.inf_31bf3856ad364e35_6.3.9600.18692_none_8de8e6efb8dfd888 ?
 
Hey PeterJ,

Unfortunately, I do not... I don't have many Server 202 (non-R2) servers in my fleet [fortunately], so that leaves me with a very small pool of potential candidates. In this case, none of them have the missing components. Bummer!

You folks don't happen to have that one, do you?
 
You folks don't happen to have that one, do you?
Yep. Here you go. Thanks to @Maxstar.

Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
  • Download
    myjIXnC.png
    SFCFix and move the executable to your desktop.
  • Download the attachment SFCFix.zip and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
    1p8eDnI.gif
  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Open the file, then copy and paste its content in your next reply.

Step 2:
Restart the machine.
Check Windows Update again and report the result.
 

Attachments

Strangely, the server is not finding any updates other than a SQL 2008 Service Pack (which fails to install). I am certain it's missing other updates, but I can't think of why it wouldn't be finding them. I manually attempted to install KB4580353 from the Update Catalog, as it looks like it was the latest Cumulative Update for Server 2012. The install didn't outright "fail", but it also didn't install. I ran DISM /Online /Cleanup-Image /RestoreHealth and it outputted the following error:

Code:
c:\Users\TechOrange\Desktop>DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 6.2.9200.22807

Image Version: 6.2.9200.22807

[==========================100.0%==========================]
The restore operation failed. Either the repair source was not found or the comp
onent store cannot be repaired.

Error: 0x800f081f

DISM failed. No operation was performed.
For more information, review the log file.

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

Attachments

Attach the file C:\Windows\Logs\DISM\dism.log to your next reply.
 
Run the command Dism /Online /Cleanup-Image /ScanHealth in a elevated commandprompt.
When completed, provide a screenshot of the result and the file C:\Windows\Logs\DISM\dism.log.
 
Ok.
Run the command Dism /Online /Cleanup-Image /CheckHealth in a elevated commandprompt.
When completed, provide a screenshot of the result and the file C:\Windows\Logs\DISM\dism.log.
 
Run the command Dism /Online /Cleanup-Image /RestoreHealth in a elevated commandprompt.
When completed, provide a screenshot of the result and the file C:\Windows\Logs\DISM\dism.log.
 
I deeply apologize for the delay... Things got busy here and I had to shift gears. I'm running those commands right now. More to come soon!
 
Attach the file C:\Windows\Logs\DISM\dism.log.
 
Hey PeterJ,

Thanks again for your help so far!!

I've actually placed my two weeks' notice at my employer, so this will very shortly no longer be my problem. However, in good faith, I was looking to maybe get this resolved before I leave. Is there any chance you and I can work together on this, or are you stumped? No worries either way!! I deeply appreciate the help I've been given so far!
 

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

Back
Top