Reading descriptions in the knowledge base or in blog 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?
Hi.
Have you actually looked at the log to see what it's flagging?
SFC Command - Run in Windows 10 - Windows 10 blog
See option #5.
Did the Surface Pro 4 come with build 1511, and does it have Nvidia video? If yes, then there is a known issue. The Nvidia driver corrupts one of the Windows system files. It's really no big deal. If you do a search, you can find countless threads on the subject. Nvidia said it was Microsoft's problem and Microsoft said it was Nvidia's problem. I don't know if it was fixed with the Anniversary Update 1607.
Windows Modules Installer service is enabled and set to ManualThere are - I estimate - about 100-200 entries reporting "Error - Overlap: Duplicate ownership for directory [l:29]"??C:Windows<misc-paths-here>".Hi.
Have you actually looked at the log to see what it's flagging?
SFC Command - Run in Windows 10 - Windows 10 blog
See option #5.
Almost all of these seem to be some language files, since they end in codes like "en_US", "ru_RU", "sv-SE", "sr-Latn-CS", etc.
There are also many warnings like: DIRSD OWNER WARNING] Directory [l:72 ml:73]"??C:WindowsSysWOW64<some path>" is not owned but specifies SDDL in component Microsoft-Windows-<some component here>
There are also three entries referring to that file opencl.dll, that is mentioned in the reference forum entry and apparently can be ignored, e.g.:
2016-08-21 23:43:47, Info CSI 0000619e Hashes for file member SystemRootWinSxSwow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22opencl.dll do not match actual file [l:10]"opencl.dll" :
Any ideas or comments on those "duplicate owned" and the "not owned" files?
Yes, the opencl.dll was supposedly fixed and has evidently reappeared.
Try running the DISM commands:
DISM - Repair Windows 10 Image - Windows 10 blog
What version W10 are you on? V1511 or V1607? Type winverin the search box and run the command.
