[SOLVED] SFC and DISM both failed

delphin

Member
Joined
Dec 10, 2021
Posts
6
Hello!
I have problems with search in Outlook (something went wrong) at Windows Server 2019 (terminal server role). Tried to fix using:
sfc /scannow
Dism /Online /Cleanup-Image /RestoreHealth
But they failed. Logs are attached. Please help.
 

Attachments

Rich (BB code):
2021-12-10 13:05:46, Info                  CSI    00000007 Hashes for file member [l:23]'tls_branding_config.xml' do not match.
 Expected: {l:32 ml:4096 b:c3b2a8c679b89829b173cd05bdfa46acb1b28a6d4da26fcf0295387a385a9262}.
 Actual: {l:32 b:8e6adaf781147f87780c1dd37e63b529f4a49482d541a7f417fe46458f395047}.
2021-12-10 13:05:46, Info                  CSI    00000008 Warning: Unable to repair payload file ([l:23]'tls_branding_config.xml') for component ([l:101 ml:140]'amd64_microsoft-windows-t..enseserver-tlsbrand_31bf3856ad364e35_10.0.17763.1075_none_9c481b71554a77d4') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2021-12-10 13:08:06, Info                  CBS    Session: 30928301_3554111786 initialized by client LanguageFeaturesOnDemand, external staging directory: (null), external registry directory: (null
2021-12-10 13:09:12, Info                  CSI    00000009 Hashes for file member [l:20]'LServer_PKConfig.xml' do not match.
 Expected: {l:32 ml:4096 b:a68ced28a12c6d3a25c153e76217f1830e2d94b9c71e4f9b2ebb2b01335af2b6}.
 Actual: {l:32 b:b45d90e43527e118b400d87486820dd8460912fabd1ef147e654b1afc0d4378c}.
2021-12-10 13:09:12, Info                  CSI    0000000a Warning: Unable to repair payload file ([l:20]'LServer_PKConfig.xml') for component ([l:98 ml:140]'amd64_microsoft-windows-t..enseserver-lrwizdll_31bf3856ad364e35_10.0.17763.1_none_f5101f628983b202') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2021-12-10 13:09:12, Info                  CSI    0000000b Hashes for file member [l:23]'tls_branding_config.xml' do not match.
 Expected: {l:32 ml:4096 b:c3b2a8c679b89829b173cd05bdfa46acb1b28a6d4da26fcf0295387a385a9262}.
 Actual: {l:32 b:8e6adaf781147f87780c1dd37e63b529f4a49482d541a7f417fe46458f395047}.
2021-12-10 13:09:12, Info                  CSI    0000000c Warning: Unable to repair payload file ([l:23]'tls_branding_config.xml') for component ([l:98 ml:140]'amd64_microsoft-windows-t..enseserver-tlsbrand_31bf3856ad364e35_10.0.17763.1_none_3f5a01e7dbc22676') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2021-12-10 13:12:48, Warning               CBS    Current tick count: 800 lower than last tick count: 1136. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
2021-12-10 13:12:48, Error                 CSI    0000000d@2021/12/10:10:12:48.711 (F) Attempting to mark store corrupt with category [l:18 ml:19]'CorruptPayloadFile'[gle=0x80004005]
2021-12-10 13:12:48, Info                  CSI    0000000e@2021/12/10:10:12:48.786 Corruption detection complete. numCorruptions = 3, Disp = 1.

It appears that one of the files was able to being repaired, however, the system was unable to repair the other following two which are unfortunately belong to an OS version which currently no longer supported.

Rich (BB code):
2021-12-10 13:16:55, Info                  CBS    =================================
2021-12-10 13:16:55, Info                  CBS    Checking System Update Readiness.
2021-12-10 13:16:55, Info                  CBS    
2021-12-10 13:16:55, 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
2021-12-10 13:16:55, Info                  CBS    (p)    CSI Payload Corrupt    (n)            amd64_microsoft-windows-t..enseserver-lrwizdll_31bf3856ad364e35_10.0.17763.1_none_f5101f628983b202\LServer_PKConfig.xml
2021-12-10 13:16:55, Info                  CBS    Repair failed: Missing replacement payload.
2021-12-10 13:16:55, Info                  CBS    (p)    CSI Payload Corrupt    (n)            amd64_microsoft-windows-t..enseserver-tlsbrand_31bf3856ad364e35_10.0.17763.1_none_3f5a01e7dbc22676\tls_branding_config.xml
2021-12-10 13:16:55, Info                  CBS    Repair failed: Missing replacement payload.

I'll try and see find I can find them somewhere, otherwise I'll ask for some advice from a more experienced helper.
 
Update:

I've managed to source this:

Rich (BB code):
amd64_microsoft-windows-t..enseserver-tlsbrand_31bf3856ad364e35_10.0.17763.1_none_3f5a01e7dbc22676\tls_branding_config.xml

However, I'm having some difficulty sourcing this file:

Rich (BB code):
amd64_microsoft-windows-t..enseserver-lrwizdll_31bf3856ad364e35_10.0.17763.1_none_f5101f628983b202\LServer_PKConfig.xml

I'm going to request some additional help in finding it.
 
I believe I've managed to source both of the files correctly, however, I've asked for a more experienced helper to verify these for me.
 
Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
  • Download the attachment SFCFix.zip and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
    1p8eDnI.gif
  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Open the file, then copy and paste its content in your next reply.

Step 2:
Run SFC /SCANNOW in an elevated commandprompt and report the result.
If it fails copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.
 

Attachments

Hello! Thank you!

It failed :(

SFCFix version 3.0.2.1 by niemiro. Start time: 2021-12-15 00:14:56.011 Microsoft Windows Server 10 Build 17763 - amd64 Using .zip script file at C:\Users\delphin\Desktop\SFCFix.zip [0] PowerCopy:: Successfully took permissions for file or folder C:\Windows\WinSxS\amd64_microsoft-windows-t..enseserver-tlsbrand_31bf3856ad364e35_10.0.17763.1_none_3f5a01e7dbc22676\tls_branding_config.xml 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\delphin\AppData\Local\niemiro\Archive\amd64_microsoft-windows-t..enseserver-tlsbrand_31bf3856ad364e35_10.0.17763.1_none_3f5a01e7dbc22676\tls_branding_config.xml to C:\Windows\WinSxS\amd64_microsoft-windows-t..enseserver-tlsbrand_31bf3856ad364e35_10.0.17763.1_none_3f5a01e7dbc22676\tls_branding_config.xml. Successfully copied file C:\Users\delphin\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-tlsbrand_31bf3856ad364e35_10.0.17763.1_none_3f5a01e7dbc22676\tls_branding_config.xml Successfully restored permissions on C:\Windows\WinSxS\amd64_microsoft-windows-t..enseserver-tlsbrand_31bf3856ad364e35_10.0.17763.1_none_3f5a01e7dbc22676\tls_branding_config.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. Failed to generate a complete zip file. Upload aborted. SFCFix version 3.0.2.1 by niemiro has completed. Currently storing 2 datablocks. Finish time: 2021-12-15 00:20:17.809 Script hash: Sve/GuWTZ7gJEWh9AGcPFnnfXLvtsdXR86q21bhFRCE= ----------------------EOF-----------------------
 

Attachments

Rich (BB code):
2021-12-15 00:32:18, Info                  CSI    00005bb7 [SR] Verify complete
2021-12-15 00:32:18, Info                  CSI    00005bb8 [SR] Repairing 2 components
2021-12-15 00:32:18, Info                  CSI    00005bb9 [SR] Beginning Verify and Repair transaction
2021-12-15 00:32:18, Info                  CSI    00005bba Hashes for file member [l:20]'LServer_PKConfig.xml' do not match.
 Expected: {l:32 ml:4096 b:a68ced28a12c6d3a25c153e76217f1830e2d94b9c71e4f9b2ebb2b01335af2b6}.
 Actual: {l:32 b:c5645f3fc7ee69092e01ba0405a9306c43ccadbe42977c7f4fda7b5e7e1ae2f4}.
2021-12-15 00:32:18, Info                  CSI    00005bbb [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
2021-12-15 00:32:18, Info                  CSI    00005bbc@2021/12/14:21:32:18.361 Primitive installers committed for repair
2021-12-15 00:32:18, Info                  CSI    00005bbd Hashes for file member [l:20]'LServer_PKConfig.xml' do not match.
 Expected: {l:32 ml:4096 b:a68ced28a12c6d3a25c153e76217f1830e2d94b9c71e4f9b2ebb2b01335af2b6}.
 Actual: {l:32 b:c5645f3fc7ee69092e01ba0405a9306c43ccadbe42977c7f4fda7b5e7e1ae2f4}.
2021-12-15 00:32:18, Info                  CSI    00005bbe [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
2021-12-15 00:32:18, Info                  CSI    00005bbf [SR] This component was referenced by [l:99]'Microsoft-Windows-TerminalServices-Licensing-Package~31bf3856ad364e35~amd64~~10.0.17763.1.Licensing'
2021-12-15 00:32:18, Info                  CSI    00005bc0 [SR] This component was referenced by [l:105]'Microsoft-Windows-TerminalServices-Licensing-UI-Package~31bf3856ad364e35~amd64~~10.0.17763.1.Licensing-UI'
2021-12-15 00:32:18, Info                  CSI    00005bc1 Hashes for file member [l:20]'LServer_PKConfig.xml' do not match.
 Expected: {l:32 ml:4096 b:a68ced28a12c6d3a25c153e76217f1830e2d94b9c71e4f9b2ebb2b01335af2b6}.
 Actual: {l:32 b:c5645f3fc7ee69092e01ba0405a9306c43ccadbe42977c7f4fda7b5e7e1ae2f4}.
2021-12-15 00:32:18, Info                  CSI    00005bc2 Hashes for file member [l:20]'LServer_PKConfig.xml' do not match.
 Expected: {l:32 ml:4096 b:a68ced28a12c6d3a25c153e76217f1830e2d94b9c71e4f9b2ebb2b01335af2b6}.
 Actual: {l:32 b:c5645f3fc7ee69092e01ba0405a9306c43ccadbe42977c7f4fda7b5e7e1ae2f4}.
2021-12-15 00:32:18, Info                  CSI    00005bc3 [SR] Could not reproject corrupted file \??\C:\Windows\System32\\LServer_PKConfig.xml; source file in store is also corrupted
2021-12-15 00:32:18, Info                  CSI    00005bc4@2021/12/14:21:32:18.376 Primitive installers committed for repair
2021-12-15 00:32:18, Info                  CSI    00005bc5 Hashes for file member [l:23]'tls_branding_config.xml' do not match.
 Expected: {l:32 ml:4096 b:c3b2a8c679b89829b173cd05bdfa46acb1b28a6d4da26fcf0295387a385a9262}.
 Actual: {l:32 b:0a184603cab73a5cca6c945231c3b27940120a9a0e95476b3ffbc9a305347ada}.
2021-12-15 00:32:18, Info                  CSI    00005bc6 [SR] Repairing corrupted file \??\C:\Windows\System32\\tls_branding_config.xml from store
2021-12-15 00:32:18, Info                  CSI    00005bc7@2021/12/14:21:32:18.470 Primitive installers committed for repair
2021-12-15 00:32:18, Info                  CSI    00005bc8 [SR] Repair complete
2021-12-15 00:32:18, Info                  CSI    00005bc9 [SR] Committing transaction
2021-12-15 00:32:18, Info                  CSI    00005bca Creating NT transaction (seq 1)
2021-12-15 00:32:18, Info                  CSI    00005bcb Created NT transaction (seq 1) result 0x00000000, handle @0x69c
2021-12-15 00:32:18, Info                  CSI    00005bcc@2021/12/14:21:32:18.861 Beginning NT transaction commit...
2021-12-15 00:32:18, Info                  CSI    00005bcd@2021/12/14:21:32:18.986 CSI perf trace:
CSIPERF:TXCOMMIT;126031
2021-12-15 00:32:18, Info                  CSI    00005bce [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired

It appears that everything was repaired? Could you please run SFC once more and then upload the CBS log again please?
 
C:\Windows\system32>SFC /SCANNOW The system scan has started. This process may take some time. The beginning of the verification stage when scanning the system. The verification is 100% complete. The Windows Resource Protection Program has detected corrupted files, but cannot restore some of them. For more information, see the CBS.Log file, which is located at the following path: windir\Logs\CBS\CBS.log. For example, C:\Windows\Logs\CBS\CBS.log . The details are included in the log file provided by the /OFFLOGFILE flag.
 

Attachments

It's odd, it's the same file as before yet it claims that it's been repaired in the log? Let's try with DISM and if that doesn't work, then we can investigate further.

Code:
Dism /Online /Cleanup-Image /RestoreHealth

After the command has completed, please upload the CBS log as you've done before.
 
Retrieve Components Hive
1. Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
2. 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.
3. 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.
4. The file will likely be too large to upload here so please upload to a file sharing service. Examples of services to upload to are Dropbox or OneDrive or Google Drive and then just provide the link in your reply.
 
These are the uncompressed versions of the files which I provided earlier.

Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.
  • Download the attachment SFCFix.zip and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
    1p8eDnI.gif
  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Open the file, then copy and paste its content in your next reply.

Step 2:
Run SFC /SCANNOW in an elevated commandprompt and report the result.
If it fails copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.
 

Attachments

Hello!
The verification is 100% complete. Windows Resource Protection has not detected any integrity violations.
Thank you!!
Is everything ok now?
 

Attachments

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top