New
#190
So the 103KB Opencl.dll are being reported as corrupt by SFC ???
Because it is funny that MS does not put the Opencl.dll into SysWow64 Folder
But is present in Winsxs
From Windows 10.0.10586 x64 OS
Attachment 63355
So the 103KB Opencl.dll are being reported as corrupt by SFC ???
Because it is funny that MS does not put the Opencl.dll into SysWow64 Folder
But is present in Winsxs
From Windows 10.0.10586 x64 OS
Attachment 63355
Yes Kyhi but only since we went to Windows 1511 This did not happen with the older release of Windows 10. Its been reported on NVidia's web site in their user forum for months. So Nvidia is well aware of this, also been reported to MS months ago, even by some insiders. This IS a Microsoft issue thou, not much Nvidia can do to fix it.
If you upgrade your Nvidia drivers and Don't run sfc /scannow then the Nvidia drivers will not be removed, and the other 2 will not be replaced. We discussed this about 2 or 3 months ago for weeks if I remember right here in one of the forums. We just finally gave up trying to figure out how to fix this issue.
Oh I know we did... But now I see pictures...
Purple Arrows are WinSXS component store MS Files, due to size
Red arrows Match AMD's file Size, but are also in driver store..
your NVidia are not in your driver store, and Both x86 and x64 opencl.dll are the same file size..
Note. it is very rare to find x86 and x64 files the same size..
So it is a Nvidia Issue.. For which MS SFC is trying to Fix..
I guess I was late to that party before..But now I see pictures...
Or OldTimers set in, in that moment..
I don't know how to take this response?... I have other computers running the exact same Windows 10 build, NO sfc /scannow issues.
The computer I am currently on, is the only one with an NVIDIA gpu. I also have a problem where it wakes from sleep, and the computer temps almost fry itself (I installed all new hardware)
Even in the beginning of the SFC Command guide, it states.
Yes, it does sayIf you have the NVIDIA 359.06 graphics driver installed, you will get a hash mismatch for the opencl.dll file like below. You can safely ignore this.Yet it is still a problem for advanced users that use sfc /scannow when there is a problem.You can safely ignore this.
No one here is a Microsoft tech that can fix the issue. I was just stating my issue and the help that temporarily fixes it.
Does this Dism function ever work? I've tried this dozens of times using the examples shown here and elsewhere and ALWAYS get the 'source' not found. In this case, I'm trying to sort a Windows 10 installation - new and clean - which fails with corrupted files message from the scannow function.
Thanks - relieved it's not just me but disappointed that there seems no way to fix the installation. It just refuses to update 2 updates. It beats me why they put out stuff like this that does the opposite of help.
Make sure you're pointing to the right path, for instance once the ISO is mounted it will be a different drive number than where the install.wim resides. See my post #183 from page 19 on this Tutorial:
richieOne note: Altho I downloaded the TechBench ISO to drive letter J: when mounted it showed on drive letter K:? I went to install.wim on the J: drive & using a trick I learned from Edwin = to fetch the 'path' yourself the easiest way is: navigate to the item, Shift/Right Click/Copy as Path and Paste into the dialog but remove the quotation marks.
The path it copied was in fact K:\sources\install.wim. I was a little confused as to what the full path name to install.wim might be but the Shift/Right Click/Copy as Path and Paste removed all doubt.