[SOLVED] LServer_PKConfig.xml Hash mismatch with Server 2025

[Channing]

There is a mismatch of hashes for file LServer_PKConfig.xml the hash count of for the file in System32 folder is different than the SFC expects per CBS log. This appears to be a similar/same problem that Server 2019 and Server 2022 have a LServer_PKConfig.xml for ‘LServer_PKConfig.xml ’ and DISM & SFC report the same errors reported for the Server 2019 & Server 2022 mismatch of hash count.

There are no solution for mismatch of hashes for file LServer_PKConfig.xml that I can find for Server 2025.

DISM gives Error: 0x800f081f The source files could not be found.

Same Error: 0x800f081f in the OS & in the PE running: ‘DISM /Image:\ /Cleanup-Image /RestoreHealth /scratchdir:\windows\temp /Source:WIM:\Dell\install.WIM:2 /limitaccess’

SFC completes normally, but gives error “Windows Resource Protection found corrupt files but was unable to fix some of them.”

Same error running SFC in PE ‘sfc /SCANNOW /OFFBOOTDIR=D:\ /OFFWINDIR=D:\windows’

Mismatch of hashes for file LServer_PKConfig.xml from CBS.log

Expected: {l:32 ml:33 b:13bf8ca71a639aa2fd30e16a97c603eac597bc79706c0bc21403d1fa5444b8bb}.

Actual: {l:32 b:cfa5c1d46b882f7980fbacca01c6cfe80aad5ec96392d3f839dbd7ef27f40321}.

 

[Windows Update Bot]

Hi @Channing,

Welcome to Sysnative Forums!

If you haven't already, please review the posting instructions here, and attach the requested log files. Without log files, our helpers will not be able to assist, and this will slow down fixing your machine.

If logs have been already been provided, our team of volunteers will analyse the provided log files to build a fix for your system. Please be aware that this may take several days from your initial post, due to the high volume of threads that we receive.


- Sysnative Windows Update Team

 

[Channing]

Microsoft pushed some updates. I installed them in hopes it would help. Looks like updates didn't help, but I ran new logs (attached).

 

[Channing]

SOLVED

Windows update installed the correct version or LServer_PKConfig.xml file with a Hashes count that matched the SFC to one of the shadow folders. The system tried to run a repair on itself at midnight, but was only partially successful.

I checked the Hashes count on the LServer_PKConfig.xml that the update made in a shadow directory and it matched the hashes count that SFC was looking to match.

I then installed this correct LServer_PKConfig.xml file in the system32 folder and the other shadow folder in WinSxS that still had a corrupt copy. This completely cleared out all corruption.

SFC and DISM found no corruption after I put the correct LServer_PKConfig.xml file in the 3 places that the OS stores it.

2025-04 Cumulative Update for Microsoft server operating system version 24H2 for x64-based Systems (KB5055523) said that is successfully installed last night in the update log, but it came up again in the Windows Updated after the LServer_PKConfig.xml corruption was cleared after reboot. I installed it a second time and it completed successfully.

I speculate that 2025-04 Cumulative Update (KB5055523) attempted to clear the LServer_PKConfig.xml, but was only partially successful. There was a partial WS2025 OS that it tried to created on its own that I had to deleted out of the System Configuration Boot menu. Maybe this will help someone else with this problem.

The other update that was installed last night was 2025-04 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Microsoft server operating system version 24H2 for x64 (KB5054979), but I don’t think this had anything to do with clearing the corruption.

I'm attaching the logs post repair for anyone that is interested.