DISM, sfc /scannow Failing after Remote Desktop Services installation, Windows Server 2022

Question

Hello everyone,

I encountered a problem in many of my Windows Server 2022 machines,

Performing sfc /scannow gives

Windows Resource Protection found corrupt files and successfully repaired them.

For online repairs, details are included in the CBS log file located at

windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline

repairs, details are included in the log file provided by the /OFFLOGFILE flag.

Checking the CBS.log

Cannot repair member file [l:23]'tls_branding_config.xml' of Microsoft-Windows-TerminalServices-LicenseServer-TlsBrand, version 10.0.20348.1726, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

??\C:\Windows\System32\tls_branding_config.xml; source file in store is also corrupted

f081f [CBS_E_SOURCE_MISSING], download results: Server.OS.amd64:0x800f0954;Microsoft.Edge.Stable.amd64:0x800f0954;Windows.Appraiser.amd64:0x800f0954;Windows.AppraiserData.amd64:0x800f0954;Windows.EmergencyUpdate.amd64:0x800f0954;Windows.UpdateStackPackage.amd64:0x800f0954;

ession: 31034288_584928308 failed to perform store corruption detect and repair operation. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]

Ive tried deleting My wsus server from registry, restarting the Win update service after, still no solution.

DISM /Online /Cleanup-Image /CheckHealth gives -

the component store is repairable.

the operation completed successfully.

DISM /Online /Cleanup-Image /ScanHealth gives -

the component store is repairable.
the operation completed successfully.

But DISM /Online /Cleanup-Image /RestoreHealth gives -

[==========================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

Anyone encountered that before? The only thing i installed on the machine is installing remote desktop services.

Before installing Remote Desktop Services, sfc /scannow is finishing with "Windows Resource Protection did not find any integrity violations."

BUT after installing RDS via server manager, getting all of this.

Any help would appreciated.

Answer 1

Hi,

I'd be happy to help you out with your question. Sorry for the inconvenience caused.

Please refer to following self troubleshooting approach to resolve this issue :-

Firstly, it's important to ensure that your Windows Server is up to date with the latest updates from Windows Update. Sometimes, installing the latest updates can fix file corruption issues. Please verify that you have installed all available updates.

Regarding the error message you received, it indicates that the source files required for the restoration process are missing. To resolve this, you'll need to provide a valid source location to restore the feature. If you have an installation media such as a Windows Server 2022 ISO file, you can specify it as the source using the "/Source" option in the DISM command. Here's an example command you can try:

DISM /Online /Cleanup-Image /RestoreHealth /Source:D:\sources\install.wim

Please replace "D:\sources\install.wim" with the appropriate path to your installation media.

I also recommend checking the CBS.log file mentioned in the error message. The log file contains additional details about the corruption and repair process. Reviewing the log can help identify any other corrupted files or components. Look for any additional errors or warnings that might provide insights into the underlying issue.

If the problem persists after trying the above steps, you might consider uninstalling Remote Desktop Services (RDS) to see if it resolves the corruption problem. You can use the Server Manager or PowerShell to remove the RDS role. After uninstalling, run the "sfc /scannow" and "DISM /Online /Cleanup-Image /RestoreHealth" commands again to check for any remaining corruption.

Please remember to back up critical data before attempting any major changes to your system.

If none of the suggestions provided resolve the issue, I’ll recommend contacting Microsoft Technical Support, they can connect with you remotely, check what causing this issue and fix it for you, you can contact them here :- https://support.microsoft.com/home/contact/

If you have any other questions or need assistance with anything, please don't hesitate to let me know. I'm here to help.

If the reply was helpful, please don’t forget to upvote or accept as answer, thank you.