[SOLVED] SFC not working Windows 2019 Terminals Server

[Bernhard]

we have problems with a small terminal server that is also a domain controller. Every few days the licensing server stops working and the files LServer_PKConfig.xml & tls_branding_config.xml are corrupt. After that we were able to solve the problem for a short time with sfc /scannow, but unfortunately that hasn't worked for a few days now and sfc stops at 23% with the error message "Windows Resource Protection could not perform the requested operation".
Windows updates work and the server is up to date. We had to reinstall the licensing server yesterday, but now it is no longer possible to import the licenses (but I think that is a different problem).
We are at a loss....
Perhaps you have a solution for us.

Thank you very much!

Bernhard

 

[Maxstar]

Hi and welcome to Sysnative,

Step 1. Download

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.

• 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 System File Checker and post the result. If it fails attach a new copy of the CBS log.

SFC /Scannow

 

[Bernhard]

Hello Maxstar,

thanks for the SFCFix!
Unfortunately, the SFC /scannow process stopped again at 23%. I am enclosing the CBS log and the text document from SFCFix.
Thank you very much!

Best Regards

Bernhard

 

[Maxstar]

Please run the System File Checker again with Process Monitor running.

Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Run the System File Checker
3. Stop Process Monitor a minute after it fails. You can simply do this by clicking the capture icon (CTRL +E) on the toolbar as shown below.

4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up the LogFile.PML and upload it to WeTransfer | Send Large Files Fast - Up To 2GB Free and provide the link.
6. Upload also the latest CBS log for the time stamps.

Provide also a copy of the COMPONENTS hive.

Upload your COMPONENTS hive.

• Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
• Please copy this file to your desktop.
• Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
• Right-click on this file on your desktop and select Send To > Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
• If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.

 

[Bernhard]

Hello Maxstar,

Thank you very much for the quick reply. I am sending you the requested files enclosed.

Logfile

Best regards

Bernhard

 

[Maxstar]

Here's the next fix.

Step 1.
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.

• 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 System File Checker again with Process Monitorrunning and post the result. If it fails attach a new copy of the CBS log and the *.PML trace file.

SFC /Scannnow

 

[Bernhard]

Hello Maxstar,

I think the fix worked!!! SFC ran through and found corrupted files, which could be successfully repaired. I have attached the CBS log file. Should this fix also solve the problem of the constantly corrupted files like LServer_PKConfig.xml & tls_branding_config.xml?
Thank you very much!!

Best wishes

Bernhard

 

[Maxstar]

Hi,

Great, the LServer_PKConfig.xml issue should be fixed now, but let me know if this problem recurs.
For now we can mark this thread as solved..