BradenFerguson
New member
- Aug 6, 2024
- 1
Hi!
I believe i got into similar problem that is described here sfc-reporting-hash-mismatch-for-files-lserver_pkconfig-xml-tls_branding_config-xml.35419 and here server-2022-problem-with-dism-and-sfc-cannot-repair-member-file.39184
CBS.log shows:
The result of the DISM command follows:
Thanks for your help.
I believe i got into similar problem that is described here sfc-reporting-hash-mismatch-for-files-lserver_pkconfig-xml-tls_branding_config-xml.35419 and here server-2022-problem-with-dism-and-sfc-cannot-repair-member-file.39184
CBS.log shows:
Code:
...
2024-08-07 06:44:25, Info CSI 0000023e Hashes for file member [l:23]'tls_branding_config.xml' do not match.
Expected: {l:32 ml:33 b:045852938e96aa28197993a6efc401407d94185aff8c13172ad3252ff711ba45}.
Actual: {l:32 b:49c898176d9ad8669bb1761a62e4fddb9da3b98f8cc3a311db7ac374bc4d2c37}.
2024-08-07 06:44:25, Info CSI 0000023f [SR] Cannot repair member file [l:23]'tls_branding_config.xml' of Microsoft-Windows-TerminalServices-LicenseServer-TlsBrand, version 10.0.20348.1970, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2024-08-07 06:44:25, Info CSI 00000240 Hashes for file member [l:20]'LServer_PKConfig.xml' do not match.
Expected: {l:32 ml:33 b:d89ab0d7cf6262145ab3517febd26dbb95297bdf0adb72d551746f4e409eb089}.
Actual: {l:32 b:cfa5c1d46b882f7980fbacca01c6cfe80aad5ec96392d3f839dbd7ef27f40321}.
2024-08-07 06:44:25, Info CSI 00000241 [SR] Cannot repair member file [l:20]'LServer_PKConfig.xml' of Microsoft-Windows-TerminalServices-LicenseServer-LRWIZDLL, version 10.0.20348.681, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2024-08-07 06:44:25, Info CSI 00000242 Hashes for file member [l:23]'tls_branding_config.xml' do not match.
Expected: {l:32 ml:33 b:045852938e96aa28197993a6efc401407d94185aff8c13172ad3252ff711ba45}.
Actual: {l:32 b:49c898176d9ad8669bb1761a62e4fddb9da3b98f8cc3a311db7ac374bc4d2c37}.
2024-08-07 06:44:25, Info CSI 00000243 [SR] Cannot repair member file [l:23]'tls_branding_config.xml' of Microsoft-Windows-TerminalServices-LicenseServer-TlsBrand, version 10.0.20348.1970, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2024-08-07 06:44:25, Info CSI 00000244 [SR] This component was referenced by [l:102]'Microsoft-Windows-TerminalServices-Licensing-Package~31bf3856ad364e35~amd64~~10.0.20348.2461.Licensing'
2024-08-07 06:44:25, Info CSI 00000245 [SR] This component was referenced by [l:108]'Microsoft-Windows-TerminalServices-Licensing-UI-Package~31bf3856ad364e35~amd64~~10.0.20348.1970.Licensing-UI'
2024-08-07 06:44:25, Info CSI 00000246 [SR] This component was referenced by [l:139]'Microsoft-Windows-Server-Gui-Mgmt-Package-termsrv~31bf3856ad364e35~amd64~~10.0.20348.1970.Microsoft-Windows-Server-Gui-Mgmt-Package-termsrv'
.
.
.
I followed these steps from the similar problem linked above:
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 following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code:
DISM /online /cleanup-image /RestoreHealth
The result of the DISM command follows:
Code:
dism /online /cleanup-image /restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.20348.681
Image Version: 10.0.20348.2527
[==========================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 https://go.microsoft.com/fwlink/?LinkId=243077.
The DISM log file can be found at C:\windows\Logs\DISM\dism.log
Thanks for your help.