Cumulative Update for Windows 10 Version 1511 KB3140743
-
Although the Redstone preview has addressed this issue, and SFC /SCANNOW comes back clean on those versions, the current cumulative update still shows "corruption" galore in the Windows system files owing to a mismatch between MS and Nvidia versions of these files. It's looking increasingly like that fix won't come into the current branch until the current branch moves over to Redstone later this year.
--Ed--
Here's a CBS.log snippet, by way of illustration:
Found: {l:32 K3lezpDxFASqie1FeLtIjMB+9APl+XDp7TVGphCEKco=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-03-01 15:18:29, Info CSI 000050f8 [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\Windows\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
Interesting, so much talk about this here and when it will be fixed or if ever...ongoing saga.
-
-
Interesting, so much talk about this here and when it will be fixed or if ever...ongoing saga.
Running this with a WIM based ISO fixes it, but it will come back next build. Soooo, it's a temp fix which doesn't really do much.
1. Mount the .ISO file.
2. Open 'Windows Powershell' or 'Command Prompt' with Admin privileges.
3. DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:X:\Sources\Install.wim:1 /LimitAccess
--------------------------------> Note: replace "X" with the drive letter of mounted ISO.
4. Now repair any damage in the system files.
5. sfc /scannow
-
Running this with a WIM based ISO fixes it, but it will come back next build. Soooo, it's a temp fix which doesn't really do much.
1. Mount the .ISO file.
2. Open 'Windows Powershell' or 'Command Prompt' with Admin privileges.
3. DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:X:\Sources\Install.wim:1 /LimitAccess
--------------------------------> Note: replace "X" with the drive letter of mounted ISO.
4. Now repair any damage in the system files.
5. sfc /scannow
Or what i find reinstalling the NVIDIA Driver brings back right opencl.dll, because if you run SFC and DISM after driver update it will rewrite the Opencl.dll to MS one. I had done that for other reasons before what you listed i am familiar with use of WIM file, long story here..........
SFC some corrupt files can not be fixed
-
Edit: glad to see update worked for you after 2nd try.
@
thegeriatric WU installs KB3139907 first then WU tells you a restart is required while cumulative update KB3140743 is waiting to be installed.
After a restart both should be installed and can be verified by checking WU history.
Attachment 67224
Thanks for the info. :)
-
-
Or what i find reinstalling the NVIDIA Driver brings back right opencl.dll, because if you run SFC and DISM after driver update it will rewrite the Opencl.dll to MS one. I had done that for other reasons before what you listed i am familiar with use of WIM file, long story here..........
SFC some corrupt files can not be fixed
Yeah, I know, it just hides the issue for those NOT on NVidia graphics. Not a fix. at all, for NVidia.
-
Yeah, I know, it just hides the issue for those NOT on NVidia graphics. Not a fix. at all, for NVidia.
Thanks for the thoughts...as said an on going saga......to be continued..............
-
Updated fine on 2 Laptops and old desktop HP m9040 desktop (Nov 2007).
-
Thanks for the thoughts...as said an on going saga......to be continued..............
Interesting, as I USED to have the same problem with opencl.dll, actually we use to talk about this a lot few months back. BUT since Nvidia's last 2 driver updates, my opencl problem has GONE. I have taken screen shots over the past 2 months, on when it was giving me problems, and now, when it does not. sfc /scannow runs without finding ANY errors after updating with the last 2 Nvidia update releases. Latest one was today. The way Nvidia installs the opencl.dll files has changed, in the last 2 updates. At least for me. I just thought it was the same for everyone else. I guess not. But the problem seems fixed for me.
-
Nvida and OpenCl.dll
Must be my graphics card, which is a 7XX model and perhaps getting too long in the tooth (too old!).
Thanks for all the helpful suggestions. I'm procuring an ISO file and will take repair action after that.
--Ed--
-
-
Interesting, as I USED to have the same problem with opencl.dll, actually we use to talk about this a lot few months back. BUT since Nvidia's last 2 driver updates, my opencl problem has GONE. I have taken screen shots over the past 2 months, on when it was giving me problems, and now, when it does not. sfc /scannow runs without finding ANY errors after updating with the last 2 Nvidia update releases. Latest one was today. The way Nvidia installs the opencl.dll files has changed, in the last 2 updates. At least for me. I just thought it was the same for everyone else. I guess not. But the problem seems fixed for me.
Thanks Mike, i have not attempted to run SFC in past 2 updates for NVIDIA, i will have to try and see if it is fixed for me.