Windows 10: Optional feature "RSAT: File Services Tools" contains files which sfc flags as corrupt and...

This is more a statement of fact than a question. I have been trying to report these bugs since I discovered them months ago with no luck so far, so maybe I will have some luck here. Ever since I updated to Windows 10 2004, I have been receiving the error "Windows Resource Protection found corrupt files and successfully repaired them", but the error keeps occurring no matter how many subsequent restarts and sfc /scannow commands I perform.




I checked the cbs.log file, and identified the files that sfc keeps flagging these two files:

Repairing file \??\C:\WINDOWS\SysWOW64\\srmclient.dll from store

Repairing file \??\C:\WINDOWS\SysWOW64\\srmscan.dll from store


After doing some research, I found that these two files are related to Microsoft file server, and was then able to run some tests using clean installations of windows 10 2004 on virtual machines that that the "RSAT: File Services Tools" Optional feature in the apps & features menu in settings is what is causing this issue. In my attempts to troubleshoot, I foundthis very interesting and useful article which allowed me to locate the windows store files associated with the "corrupt files" so that I could manually compare the file hashes myself. These are the results:








So, as you can see, the file hashes for the "Corrupt files" and their associated windows store backup file are the same, indicating that there is, in fact, no corruption. So why is sfc continuously finding corruption. For those of you who looked at the corrupt file paths closely, you may notice that there are 2 forward slash characters between the file and its parent directory when looking at the full path. That is not a typo. That is the text that was pulled out of the cbs.log. So it could be that sfc is scanning for those files using an invalid file path. I am not 100% if that is the case, but I am absolutely 100% certain the "RSAT: File Services Tools" Optional feature is the cause. Unfortunately, uninstalling the package does not fix sfc and nor does a repair installation. This problem has existed since windows 2004 was released months ago, so it would be great if Microsoft would fix it.

:)

 

Corrupted file RAR

If the archive has been created using WinRAR, why don't you try WinRAR itself? It has a built-in repair feature for repairing corrupted archive (ZIP as well as RAR). Follow the steps given below:

• Open WinRAR application in your system.
• Now click on File tab > Open or simply press Ctrl+O.
• A small window "Find Archive" will pop up. Locate the corrupt RAR archive from your system directory and select it.
• Now click Open button.
• Click Tools tab > Repair archive or simply press Alt+R.
• Again a small window "Repairing File name.rar" will pop up.
• Now click Browse to select a location to save the repaired archive.
• Check the box "Treat the corrupt archive as RAR" and click OK.
• WinRAR will start repairing of corrupt RAR archive. Once it gets completed click Close.

I hope the above steps will help you repair the corrupted RAR archive.

Thanks.

 

RSAT Tools missing

Hi Darwin

My name is Jon and I am an independent technical adviser. Sorry to hear you are experiencing issues and I would really like to help you find a resolution.

Starting with Windows 10 October 2018 Update, RSAT is included as a set of "Features on Demand" right from Windows 10. Do not download an RSAT package from the Microsoft Download Center. Instead, just go to "Manage optional features" in Settings and click "Add
a feature" to see the list of available RSAT tools. Select and install the specific RSAT tools you need. To see installation progress, click the Back button to view status on the "Manage optional features" page.

Hope this helps.

 

SFC cannot repair corrupt files

Hi,

When you’ve run the System File Check tool, it seems like it fails to repair the corrupted files due to a possible software conflict. To help us isolate this concern, we suggest that you perform a
clean boot. This troubleshooting technique can help to identify if there are application that may cause the issue. Click
here for the steps.

Once you’re in the clean boot state, try checking your computer if you’ll observe any unusual behavior while you navigate the system.

Note: After the troubleshooting, refer to this section: “How to reset the computer to start normally after clean boot troubleshooting” on the same support
article to boot the computer in normal setup once the issue has been resolved.

After you’ve booted in the normal mode, we suggest running again the
SFC tool and also use the Deployment Image Servicing and Management (DISM) tool. These tools are commonly used to repair errors or any corrupted files. Click this
Forum
Article by ZigZag3143 (MS -MVP) for the instructions.

Let us know the outcome after performing the suggested steps.