[SOLVED] SFC and DISM can't repair system

Joined
May 4, 2023
Posts
6
Hi.

Here there is another one that SFC get errors but can't repair, DISM checkhealt says that there is reparable, but DISM restorehealth don't find sources again with or without source specification.

There is a recently installation of windows server, but it have a couple of weeks of data production, so I want try to repain against reinstall it.
 

Attachments

I see that error on several windows servers that i usually install for our clients, and i decide to investigate what really causes this fail.

I just install a new windows 2022 server with desktop experience, evaluation.

I make an sfc /scannow every important step i do.

2023.05.04 13:30 - OK - Just installed (dism image 10.0.20348.587)
2023.05.04 14:35 - OK - Windows update (dism image 10.0.20348.1668)
2023.05.04 15:15 - OK - Install AD and RDP
2023.05.04 16:00 - FAIL - Added remote desktop licence server.

CBS.log fragment:
Code:
2023-05-04 15:59:20, Info                  CSI    00000328 Hashes for file member [l:20]'LServer_PKConfig.xml' do not match.
 Expected: {l:32 ml:33 b:d89ab0d7cf6262145ab3517febd26dbb95297bdf0adb72d551746f4e409eb089}.
 Actual: {l:32 b:b45d90e43527e118b400d87486820dd8460912fabd1ef147e654b1afc0d4378c}.
2023-05-04 15:59:20, Info                  CSI    00000329 Hashes for file member [l:20]'LServer_PKConfig.xml' do not match.
 Expected: {l:32 ml:33 b:d89ab0d7cf6262145ab3517febd26dbb95297bdf0adb72d551746f4e409eb089}.
 Actual: {l:32 b:b45d90e43527e118b400d87486820dd8460912fabd1ef147e654b1afc0d4378c}.
2023-05-04 15:59:20, Info                  CSI    0000032a [SR] Could not reproject corrupted file \??\C:\Windows\System32\\LServer_PKConfig.xml; source file in store is also corrupted
2023-05-04 15:59:20, Info                  CSI    0000032b [SR] Repair complete


I atach whole log of this clean system in order to find what cause that problem.
 

Attachments

Hi and welcome to Sysnative,

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

Attachments

Awesome

I had checked the content of the files before applying the SFCfix and it was exactly the same as my WinSxS files, but after applying them the DISM and SFC errors have stopped.

What was the difference between them, the permissions?
 
Hi,

This was not a permissions issue, it has to due with file compression.
 
So, I have other windows server with same problem, I can use same fix.zip for this concrete issue? Or i need custom fix for each one?
 
Could you please upload the CBS log from that server, then I can take a look if you can apply the same fix.
 
Really first post and second are diferent servers with same issue (I think), you can check if the first one are same issue.
 
Yes it is the same issue in the second post, so you can use the same fix for that server. I thought this log file was only from a test environment...
 

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

Back
Top