[SOLVED] Windows Server 2012 R2, unable to install KB3191564 (WMF 5.1)

alexsaesee

alexsaesee

Member
Joined
Dec 22, 2021
Posts
17
Location
France
Hello,

Summary: Prior to install Veeam B&R 11.x, the server needs WMF 5.1 (4.0 installed). The Veeam installer failed to install the KB3191564 from it prerequisites.
I downloaded the KB on Microsoft's website making sure to get the 2K12R2 version (Win8.1AndW2K12R2-KB3191564-x64.msu).
The installation failed without error, the installer just telling that it was not installed.

I searched for updates, rebooted the server several times and followed the guide here before posting.
  • sfc /scannow result is "Windows Resource Protection did not find any integrity violations".
  • Dism /Online /Cleanup-Image /RestoreHealth failed because of unreachable Source.
  • SFCFix didn't found anything, the log is attached here. SFCFix managed with success to do the Dism command.
  • CBS link to download it: CBS.zip.
I also tried to install the KB in command lines with logs activated with .\Win8.1AndW2K12R2-KB3191564-x64.msu /quiet /log /norestart. ETL files attached too if that can help.

Sidenote: I will be off office from 25 dec. to 03 jan., if you answer this post in this period, sorry I will probably won't be able to answer it until I come back at the office.

Thank you.
 

Attachments

Hello @alexsaesee :-)

I was looking back through old threads and see that you are still waiting. The CBS logs are no longer available so if you would like help please resubmit the latest CBS logs from your system.
 
Looking back through your logs I see there are some corrupted files which were not replaced by DISM

Code: 
Checking System Update Readiness.

(p)    CSI Payload Corrupt            amd64_prnms003.inf_31bf3856ad364e35_6.3.9600.18050_none_43aa1403a7c28eae\Amd64\PrintConfig.dll
Repair failed: Missing replacement payload.
(p)    CSI Payload Corrupt            amd64_prnms003.inf_31bf3856ad364e35_6.3.9600.18050_none_43aa1403a7c28eae\prnms003.cat
Repair failed: Missing replacement payload.

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

Total Operation Time: 1529 seconds.

To repair these, please do the following:

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Attach this SFCFix.txt file into your next post for me to check please.

Afterwards, please run SFC /scannow in a command prompt and then try the update again.
 

Attachments

Thanks for the answer.
I executed the SFCFix you provided, the SFCFix.txt looks like it worked.
Executed SFC /scannow, finished without any violation found.

Tried to install the KB. Failed, the window as usual showed no error code or anything, juste Windows didn't installed it.
 

Attachments

Please upload the latest CBS.log for me.
 
Attach the file C:\Windows\inf\setupapi.dev.log to your next reply.
Note: if the file is too big to upload to your next post please upload via a service such as One Drive or SendSpace and just provide the download link.
 
I need to find where the versions of prnms003.inf are on your system. Please do the following:

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Attach this file into your next post for me to check please.
 

Attachments

It appears that a file is missing from the DriverStore as reported in the setupapi.dev.log. Let's try and put it there manually with a new SFCFixScript.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Attach this file into your next post for me to check please.
 

Attachments

There may be other files missing from the DriverStore prnms003.inf_amd64_637000eba4a1238b folder. The following script will extract a copy of the folder and place it on your desktop as a .zip file. Please upload it to your next post.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a zip file should be created on your Desktop: extract.zip.
  8. Attach this file into your next post for me to check please.
 

Attachments

There are a number of files missing from that directory. Before doing any manual fix please try a DISM Restore Health to see if this will identify and fix the problems.
Type Dism /Online /Cleanup-Image /RestoreHealth into an elevated command prompt. Post the CBS.log after doing this.
 
Thanks, it doesn't look as if it actually fixed anything though so I think you will still be unable to update?

It appears that another file is missing from the DriverStore as reported earlier in the setupapi.dev.log. Let's try and put it there manually with a new SFCFixScript.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the attached file, SFCFixScript.txt, and save this to your Desktop. Ensure that this file is named SFCFixScript.txt - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFixScript.txt.
  5. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a log should be created on your Desktop: SFCFix.txt.
  8. Attach this file into your next post for me to check please.
 

Attachments

Last edited:
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