If you do not install video drivers (Nvidia, Intel, latest version, or Windows Update ones that I installed on my Dell E6530) then yes sfc /scannow fix everythings. But installing the video drivers, then files corruption is there and unfixable. I have tried many times with 10240. TH2, Server 2016 preview 4, LTSB., Enterprise. etc.
On 10240 it always whas repairable, on 10586 it's more of a problem. But my statement whas meant to give a counterreport, it's mostly driver/third party stuff what makes the corruption a bit more difficult to repair. The system on which i did my latest tests windows already installed the AMD vga drivers.
Well, it seems that AMD do the right thing, not Intel nor Nvidia. Microsoft must fix this, since they build the operating system, drivers builders must fellow Microsoft advices and rules to protect the integrity of the operating system. This is bad for the ones of us that are having this problem.
for me it seems the ltsb is more error and bug prone- my pc just borked this morning and i am switching to enterprise, for the newest build and some software like SSD samsung magician works.
I didn't only test it at my own systems, also on a few notebooks (also with nvidia gpu's but older ones). All my mainboards are intel based, i've encountered no problems so far. This week i'm going to reinstall my main system with 10586, it has an intel c216 chipset and intel i7 3770 with only the onboard gpu (inside the i7 cpu). At the moment i run a 10240 upgraded to 10586 pro x64, so i'll see what happens.
I did a sfc /scannow right after fresh installation of stock LTSB. It found this: Code: 2015-12-03 17:59:12, Info CSI 00004241 [SR] Repairing corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\en-US"\[l:30{15}]"msprivs.dll.mui" from store 2015-12-03 17:59:16, Info CSI 000042f0 [SR] Repairing corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\en-US"\[l:26{13}]"mlang.dll.mui" from store 2015-12-03 17:59:43, Info CSI 00004952 [SR] Repairing corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\en-US"\[l:68{34}]"Windows.Media.Speech.UXRes.dll.mui" from store 2015-12-03 17:59:44, Info CSI 0000498d [SR] Repairing 3 components 2015-12-03 17:59:44, Info CSI 0000498f [SR] Repairing corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\en-US"\[l:68{34}]"Windows.Media.Speech.UXRes.dll.mui" from store 2015-12-03 17:59:44, Info CSI 00004991 [SR] Repairing corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\en-US"\[l:30{15}]"msprivs.dll.mui" from store 2015-12-03 17:59:44, Info CSI 00004994 [SR] Repairing corrupted file [ml:60{30},l:58{29}]"\??\C:\Windows\SysWOW64\en-US"\[l:26{13}]"mlang.dll.mui" from store 2015-12-03 17:59:44, Info CSI 00004997 [SR] Repair complete 2015-12-03 17:59:44, Info CSI 00004998 [SR] Committing transaction Only some minor files corruption fixed altogether. Right after I installed Intel video drivers from Windows Update (HD Graphics 4400), reboot and re-checked with sfc and I got this: Code: 2015-12-03 23:32:37, Info CSI 000038b9 [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10240.16384, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch 2015-12-03 23:32:37, Info CSI 000038c3 [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10240.16384, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch 2015-12-03 23:32:37, Info CSI 000038c4 [SR] This component was referenced by [l:258{129}]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10240.16384.RemoteFX clientVM and UMTS files and regkeys" 2015-12-03 23:32:37, Info CSI 000038c7 [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:20{10}]"opencl.dll"; source file in store is also corrupted 2015-12-03 23:33:57, Info CSI 0000499a [SR] Repairing 1 components 2015-12-03 23:33:57, Info CSI 0000499d [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10240.16384, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch 2015-12-03 23:33:57, Info CSI 000049a0 [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10240.16384, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch 2015-12-03 23:33:57, Info CSI 000049a1 [SR] This component was referenced by [l:258{129}]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10240.16384.RemoteFX clientVM and UMTS files and regkeys" 2015-12-03 23:33:57, Info CSI 000049a4 [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:20{10}]"opencl.dll"; source file in store is also corrupted 2015-12-03 23:33:57, Info CSI 000049a6 [SR] Repair complete 2015-12-03 23:33:57, Info CSI 000049a7 [SR] Committing transaction So, if I unsterstood correctly, video drivers place (or replace) their version of opencl.dll in the system folders and Windows complains about this. But apart some log errors, the system continue to works perfectly fine, because it's better to have the opencl.dll version from the video drivers?