New
#1
SFC shows issues from day 1 - can one define the current state as OK?
Reading descriptions in the knowledge base or in forums like this part of the steps suggested is often to run SFC (System File Checker), specifically to run SFC /SCANNOW as admin to check and repair corrupted files.
I have had issues with that program already on my previous systems (a Lenovo ThinkPad and an MS Surface Pro 3), i.e. it ALWAYS showed "Windows Resource Protection found corrupt files but was unable to fix some of them. ..." Since any repair option also always fails, this tool is essentially useless under Windows 10, as it ALWAYS reports issues that it can't fix. Maybe that is just a stupid trick so that MS in case of issues can always claim, the user installed some virus, but I doubt that. I rather assume that this tool is buggy!
Due to this prior experience I ran this SFC command immediately after unpacking and switching on my new MS Surface Pro 4 for the first time and after having completed its initial setup (choosing time, keyboard, location etc.). I.e., SFC was essentially the very first action on my brand new SP4 and - as expected - it reported the very same error right there and then! So, Windows 10 on a brand new SP4 is already corrupted out of the box?!? Again - I doubt that!
Since there is practically 100% positively nothing corrupted on this machine: is there a way to reset this tool? I.e. make it accept the current setup as baseline and as non-corrupted. Only unapproved diffs (i.e. files not part of that baseline) and not installed via the System's update process) should be considered as an issue. Is there any such option?