[SOLVED] LServer_PKConfig.xml Hash Mismatch - sfc/scannow

rnotek

Member
Joined
Aug 6, 2023
Posts
5
When we run sfc/scannow on our Windows Server Datacenter 2019 EC2 instance, we are getting the following error in the CBS.log file:

2023-08-06 11:15:32, Info CSI 000044a9 Hashes for file member [l:20]'LServer_PKConfig.xml' do not match.
Expected: {l:32 ml:4096 b:a68ced28a12c6d3a25c153e76217f1830e2d94b9c71e4f9b2ebb2b01335af2b6}.
Actual: {l:32 b:b45d90e43527e118b400d87486820dd8460912fabd1ef147e654b1afc0d4378c}.
2023-08-06 11:15:32, Info CSI 000044aa [SR] Cannot repair member file [l:20]'LServer_PKConfig.xml' of Microsoft-Windows-TerminalServices-LicenseServer-LRWIZDLL, version 10.0.17763.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2023-08-06 11:15:32, Info CSI 000044ab [SR] This component was referenced by [l:99]'Microsoft-Windows-TerminalServices-Licensing-Package~31bf3856ad364e35~amd64~~10.0.17763.1.Licensing'
2023-08-06 11:15:32, Info CSI 000044ac [SR] This component was referenced by [l:105]'Microsoft-Windows-TerminalServices-Licensing-UI-Package~31bf3856ad364e35~amd64~~10.0.17763.1.Licensing-UI'
2023-08-06 11:15:32, Info CSI 000044ad Hashes for file member [l:20]'LServer_PKConfig.xml' do not match.
Expected: {l:32 ml:4096 b:a68ced28a12c6d3a25c153e76217f1830e2d94b9c71e4f9b2ebb2b01335af2b6}.
Actual: {l:32 b:b45d90e43527e118b400d87486820dd8460912fabd1ef147e654b1afc0d4378c}.
2023-08-06 11:15:33, Info CSI 000044ae Hashes for file member [l:20]'LServer_PKConfig.xml' do not match.
Expected: {l:32 ml:4096 b:a68ced28a12c6d3a25c153e76217f1830e2d94b9c71e4f9b2ebb2b01335af2b6}.
Actual: {l:32 b:b45d90e43527e118b400d87486820dd8460912fabd1ef147e654b1afc0d4378c}.
2023-08-06 11:15:33, Info CSI 000044af [SR] Could not reproject corrupted file \??\C:\Windows\System32\\LServer_PKConfig.xml; source file in store is also corrupted

I've tried running dism /online /cleanup-image /restorehealth but it fails with Error 0x800f081f "The source files could not be found".

Has anyone successfully fixed this error? Thanks!


MOD note: Windows Server Datacenter 2016 EC2 changed to Windows Server Datacenter 2019 EC2
 
Last edited by a moderator:
Hi and welcome to Sysnative,

This corrupt file is a component of Server 2019, not of Windows Server 2016 as indicated in the post above? This must be a typo I guess?
 
No problem, here's the fix to replace the corrupt file.

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

Looks like that fixed it. Thank you. I've seen in other threads where this issue has come back...hopefully not the case here.
 

Attachments

Hi,

You're welcome. This is a common issue on servers, but most of the times the issue does not returns after it has been fixed.
 
Back
Top