Share via

How do I fix my Terminal server corruption that affects file serving functionality

Anonymous
2024-03-07T15:44:34+00:00

I cannot get my file server to work as a result of my LServer_PKConfig.xml being improperly hashed, and sfc /scannow is unable to repair the file system as a result of this error.

This is for a Windows Server 2019, Version 1809, with an OS Build of 17763.5458.

The file server is correctly serving files with the group policy to other computers once they have a reestablished connection to the domain and initiate group policy requests.

However, when initiating group policy requests on the terminal server, there are issues with the shared folders and printers appearing based on the domain name (AESDC02), and instead they only appear when inputting the file server IP (10.1.200.241).

Below are the results from running an sfc /scannow for my CBS.log. Let me know how I can send the whole file over.

CSI 0000b674 [SR] Beginning Verify and Repair transaction

2024-03-07 10:05:56, Info CSI 0000b675 Hashes for file member [l:20]'LServer_PKConfig.xml' do not match.

Expected: {l:32 ml:4096 b:a68ced28a12c6d3a25c153e76217f1830e2d94b9c71e4f9b2ebb2b01335af2b6}.

Actual: {l:32 b:b45d90e43527e118b400d87486820dd8460912fabd1ef147e654b1afc0d4378c}.

CSI 0000b6a7 Warning: Overlap: Duplicate ownership for directory ??\C:\Windows\Tasks in component Microsoft-Windows-TaskScheduler-Compatibility, version 10.0.17763.2931, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

2024-03-07 10:05:57, Info CSI 0000b6a8 Warning: Overlap: 1 directory duplicate ownerships detected.

CSI 0000b6ac Hashes for file member [l:20]'LServer_PKConfig.xml' do not match.

Expected: {l:32 ml:4096 b:a68ced28a12c6d3a25c153e76217f1830e2d94b9c71e4f9b2ebb2b01335af2b6}.

Actual: {l:32 b:b45d90e43527e118b400d87486820dd8460912fabd1ef147e654b1afc0d4378c}.

2024-03-07 10:05:57, Info CSI 0000b6ad [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

2024-03-07 10:05:57, Info CSI 0000b6ae [SR] This component was referenced by [l:99]'Microsoft-Windows-TerminalServices-Licensing-Package~31bf3856ad364e35~amd64~~10.0.17763.1.Licensing'

2024-03-07 10:05:57, Info CSI 0000b6af [SR] This component was referenced by [l:105]'Microsoft-Windows-TerminalServices-Licensing-UI-Package~31bf3856ad364e35~amd64~~10.0.17763.1.Licensing-UI'

2024-03-07 10:05:57, Info CSI 0000b6b0 Hashes for file member [l:20]'LServer_PKConfig.xml' do not match.

Expected: {l:32 ml:4096 b:a68ced28a12c6d3a25c153e76217f1830e2d94b9c71e4f9b2ebb2b01335af2b6}.

Actual: {l:32 b:b45d90e43527e118b400d87486820dd8460912fabd1ef147e654b1afc0d4378c}.

2024-03-07 10:05:57, Info CSI 0000b6b1 Hashes for file member [l:20]'LServer_PKConfig.xml' do not match.

Expected: {l:32 ml:4096 b:a68ced28a12c6d3a25c153e76217f1830e2d94b9c71e4f9b2ebb2b01335af2b6}.

Actual: {l:32 b:b45d90e43527e118b400d87486820dd8460912fabd1ef147e654b1afc0d4378c}.

2024-03-07 10:05:57, Info CSI 0000b6b2 [SR] Could not reproject corrupted file ??\C:\Windows\System32\LServer_PKConfig.xml; source file in store is also corrupted

Windows for business | Windows Server | Networking | Network connectivity and file sharing

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-03-11T06:43:05+00:00

    Hello,

    Based on the information you provided, it seems that the LServer_PKConfig.xml file on your Windows Server 2019 is corrupt and cannot be repaired by running the sfc /scannow command. This file is related to the Terminal Services Licensing component of Windows Server.

    To resolve this issue, you may need to replace the corrupt LServer_PKConfig.xml file with a known good copy. You can try to locate a backup copy of the file, or you can try to extract a new copy of the file from the Windows Server installation media.

    To extract a new copy of the LServer_PKConfig.xml file from the installation media, you can follow these steps:

    1. Insert the Windows Server installation media into the server.
    2. Open a command prompt with administrative privileges.
    3. Type the following command and press Enter: dism /online /cleanup-image /restorehealth /source:WIM:X:\Sources\Install.wim:1 /limitaccess Replace "X:" with the drive letter of your Windows Server installation media.
    4. Wait for the command to complete. This may take some time.
    5. After the command completes, type the following command and press Enter: sfc /scannow This will run the System File Checker tool again to verify and repair any remaining corrupted files.

    I hope this helps!

    Best regards

    Zunhui

    0 comments