SFC reporting hash mismatch for files LServer_PKConfig.xml & tls_branding_config.xml

G

GMele

Member
Joined
Feb 6, 2022
Posts
9
Hi,

for several weeks now on our Windows 2019 Terminal Server SFC /VERIFYONLY is reporting a hash mismatch for files LServer_PKConfig.xml & tls_branding_config.xml.

I am able to fix this issue by using the following command sequence:
  • sfc /scannow
  • Dism /Online /Cleanup-Image /CheckHealth
  • Dism /Online /Cleanup-Image /ScanHealth
  • Dism /Online /Cleanup-Image /restoreHealth /Source:\\HBMCSRV09\Windows /LimitAccess
  • sfc /scannow
  • sfc /scannow
However, after a few days the problem reappears. Here is an extract of the CBS.LOG file relating to this error:

2022-02-06 08:05:06, Info CSI 000084b1 [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​
2022-02-06 08:05:06, Info CSI 000084b3 [SR] Cannot repair member file [l:23]'tls_branding_config.xml' of Microsoft-Windows-TerminalServices-LicenseServer-TlsBrand, version 10.0.17763.1075, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch​
2022-02-06 08:05:07, Info CSI 000084e2 [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​
2022-02-06 08:05:07, Info CSI 000084ed [SR] Cannot repair member file [l:23]'tls_branding_config.xml' of Microsoft-Windows-TerminalServices-LicenseServer-TlsBrand, version 10.0.17763.1075, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch​
2022-02-06 08:05:07, Info CSI 000084e7 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\\LServer_PKConfig.xml; source file in store is also corrupted​
2022-02-06 08:05:07, Info CSI 000084f3 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\\tls_branding_config.xml; source file in store is also corrupted​
​
I have tried running the SFCFix.exe tool but am getting a fatal error:

SFCFix version 3.0.2.1 by niemiro.​
Start time: 2022-02-06 08:29:24.928​
Microsoft Windows Server 10 Build 17763 - amd64​
Not using a script file.​
​
SFCFix version 3.0.2.1 by niemiro has encountered an unhandled exception.​
Currently storing 0 datablocks.​
Finish time: 2022-02-06 08:37:51.943​
----------------------EOF-----------------------​

When asked by SFCFix if I wanted to upload the .dmp file to Sysnative.com I replied yes.

I have tried uninstalling and reinstalling the Remote Desktop Licensing Manager role but this action hasn't fixed the issue.

Any help would be greatly appreciated.

Thank you.
 

Attachments

Hello @GMele :-)

Are you still needing help with this?

If so, please run Dism /Online /Cleanup-Image /RestoreHealth but do not specify the source.

Then post the CBS logs for me to check.
 
Hi Phil,

yes any help would be appreciated.

Ran the DISM as requested:

C:\Users\gmele>Dism /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool​
Version: 10.0.17763.1697​
​
Image Version: 10.0.17763.2565​
​
[==========================100.0%==========================]​
Error: 0x800f081f​
​
The source files could not be found.​
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source.​
​
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log​

Find the dism.log attached.
 

Attachments

Please can you provide the CBS logs as requested. The DISM log never tells you very much of interest.
 
This is what I was looking for and indicates there was one corrupted file which was not fixed.
Code: 
2022-02-18 10:01:32, Info                  CBS    =================================
2022-02-18 10:01:32, Info                  CBS    Checking System Update Readiness.
2022-02-18 10:01:32, Info                  CBS  
2022-02-18 10:01:32, Info                  CBS    (p)    CSI Payload Corrupt    (w)    (Fixed)    amd64_microsoft-windows-t..enseserver-tlsbrand_31bf3856ad364e35_10.0.17763.1075_none_9c481b71554a77d4\tls_branding_config.xml
2022-02-18 10:01:32, Info                  CBS    (p)    CSI Payload Corrupt    (n)            amd64_microsoft-windows-t..enseserver-lrwizdll_31bf3856ad364e35_10.0.17763.1_none_f5101f628983b202\LServer_PKConfig.xml
2022-02-18 10:01:32, Info                  CBS    Repair failed: Missing replacement payload.

Please follow the instructions below to manually repair this.

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 you can check to see if DISM completes without any errors.
 

Attachments

Here are the SFCFix results:

SFCFix version 3.0.2.1 by niemiro.​
Start time: 2022-02-18 16:06:35.125​
Microsoft Windows Server 10 Build 17763 - amd64​
Using .zip script file at C:\Users\gmele\Downloads\SFCFix.zip [0]​
​
PowerCopy::​
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\amd64_microsoft-windows-t..enseserver-lrwizdll_31bf3856ad364e35_10.0.17763.1_none_f5101f628983b202\LServer_PKConfig.xml​
​
Successfully copied file C:\Users\gmele\AppData\Local\niemiro\Archive\amd64_microsoft-windows-t..enseserver-lrwizdll_31bf3856ad364e35_10.0.17763.1_none_f5101f628983b202\LServer_PKConfig.xml to C:\WINDOWS\WinSxS\amd64_microsoft-windows-t..enseserver-lrwizdll_31bf3856ad364e35_10.0.17763.1_none_f5101f628983b202\LServer_PKConfig.xml.​
​
Successfully restored ownership for C:\WINDOWS\WinSxS\amd64_microsoft-windows-t..enseserver-lrwizdll_31bf3856ad364e35_10.0.17763.1_none_f5101f628983b202\LServer_PKConfig.xml​
Successfully restored permissions on C:\WINDOWS\WinSxS\amd64_microsoft-windows-t..enseserver-lrwizdll_31bf3856ad364e35_10.0.17763.1_none_f5101f628983b202\LServer_PKConfig.xml​
PowerCopy:: directive completed successfully.​
​
Successfully processed all directives.​
SFCFix version 3.0.2.1 by niemiro has completed.​
Currently storing 1 datablocks.​
Finish time: 2022-02-18 16:06:36.420​
Script hash: ZnbUaIPjT/a3gz05apbQSClVpK4dUA5vAZ2W0jueDtM=​
----------------------EOF-----------------------​

Here is the DISM results:

C:\Users\gmele>Dism /Online /Cleanup-Image /RestoreHealth​
​
Deployment Image Servicing and Management tool​
Version: 10.0.17763.1697​
​
Image Version: 10.0.17763.2565​
​
[==========================100.0%==========================] The restore operation completed successfully.​
The operation completed successfully.​

It looks like it's been fixed!

This problem tends to reappear after a few days so I will redo an SFC /VERIFYONLY next week to see if it reappears.

Thank you Phil and have a good weekend!
 
Hi Phil,

unfortunately last night at 9:38 PM a scheduled SFC /VERIFYONLY is reporting errors again:

2022-02-18 21:38:54, Info CSI 000084b7 [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​
2022-02-18 21:38:54, Info CSI 000084b9 [SR] Cannot repair member file [l:23]'tls_branding_config.xml' of Microsoft-Windows-TerminalServices-LicenseServer-TlsBrand, version 10.0.17763.1075, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch​
2022-02-18 21:38:54, Info CSI 000084e8 [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​
2022-02-18 21:38:54, Info CSI 000084f3 [SR] Cannot repair member file [l:23]'tls_branding_config.xml' of Microsoft-Windows-TerminalServices-LicenseServer-TlsBrand, version 10.0.17763.1075, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch​
2022-02-18 21:38:54, Info CSI 000084ed [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\\LServer_PKConfig.xml; source file in store is also corrupted​
2022-02-18 21:38:54, Info CSI 000084f9 [SR] Could not reproject corrupted file \??\C:\WINDOWS\System32\\tls_branding_config.xml; source file in store is also corrupted​

I think this is a Windows bug that Microsoft needs to address. I have previously tried to uninstall the Terminal Services Licensing role and then reinstalled it but the problem keeps coming back after a day or two.
 
Have you reported this potential bug to Microsoft via the Feedback Hub? The other thread you pointed to seems to have a similar problem.

Does anything not work as it should - in other words is this error just incorrectly reported by SFC?
 
Hi Phil,

inspite of the SFC problem everything is working normally on the Terminal Server virtual machine. Do you have an URL that I can use to report this to Microsoft (Feedback hub)?

Thanks.
 
I forgot that there is no Feedback hub for the server versions. You may have to contact Microsoft Support. Sorry I can't be of more help.
 
You must log in or register to reply here.
Back
Top