It will not solve anything, but just broke all opencl x86 apps instead.
Moreover, this issue will return back on the next nvidia driver install.
IMHO, people suggesting DISM in this particular case...
Type: Posts; User: Ache
It will not solve anything, but just broke all opencl x86 apps instead.
Moreover, this issue will return back on the next nvidia driver install.
IMHO, people suggesting DISM in this particular case...
It may work with new MUI but to be on safer side you'll need MUI from the corresponding version too.
It is already discussed, see prev. pages (and I don't know better methods too, unless someone upload this stuff somewhere, violating their copyright by that).
Of course, anything, Martians invasion etc., but not Micrisoft stupidity.
Apparently it was too soon, for me too, 8.1 is in pretty good shape. BTW, opencl.dll bug happens on ATI cards too, i.e. with any driver which install accelerated opencl.dl, older card does not help....
Perhaps they recently update their RemoteFX driver for TH1 too. I don't have this problem before.
This problem started on 64bit systems only with so-called TH2 or 1511 or 10586 Windows version with any Nvidia/ATI driver.
I try to make people aware at least on first few forums google show about the problem. Sorry I have absolutely no contacts with Microsoft developers and Microsoft support do their best to guard...
Technical details:
The correct fix will be to remove wrongly installed and activated by Microsoft ...
BTW, see http://answers.microsoft.com/en-us/windows/forum/windows_10-update/regeditexe-search-crashing-in-w10-1511th2/a70e0cb9-46a3-4fac-a103-4fee65d19eb8
The correct fix will be to remove wrongly installed and activated by Microsoft wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22 directory...
All this does not matter. Surely you can restore uncorrupted Miscrosoft opencl.dll back using DISM and install.wim followed by sfc by the method posted in this forum already many times, but it will...
1) No. With corruption you got correct Nvidia/ATI/Intel opencl.dll
2) No, it makes things worse, breaking 32bit applications wich use OpenCL API, by replacing opencl.dll with Microsoft one with...
Please stop giving standard DISM "restore from install.wim" advise, it breaks Nvidia/ATI/Intel driver.
The correct fix will be to remove wrongly installed and activated by Microsoft ...
Device Driver Updates have nothing common with this bug. MS install (and not update yet) x86 part of their Remote FX driver (without x64 part). MS do it in any case, independently of Device Driver...
regedit.exe and en-US\regedit.exe.mui should be enough.
As popular alternative looking very similar you can try OO RegEditor
1) Just copy old regedit and its MUI file from any working 10240 system to any directory (preserve subdir for MUI) and use.
2) It happens because Microsoft broke regedit in 10586.
3) To see this...
As I already write here, any long >255 chars registry key cause this in new regedit. Use regedit from 10240 instead and ask your Microsoft support to fix their bugs.
It is corruption, if we look from the file integrity point, and it does not affect system stability in any variant.
This Microsoft file simple should not be there (corrupted or not corrupted). If it...
The conclusion is wrong, it is actually the corruption. Micrisoft's opencl.dll is corrupted. With its last strength Microsoft tries to fix it, but because it made hadrlink, original is corrupted too....
This problem can't be fixed on Nvidia side at all. Nvidia writes \SysWoW65\opencl.dll only and this name and place can't be changed because other programs expects it there. WinSxS copy is replaced...
This is scene demo, designed to work on bare minimum of OpenCL API, so MS one works too.
You need 32bit application or game which directly use OpenCL API to see this dll loaded. The driver itself does not need it.
This demo for example: Scenic by UnRAVeL :: pouët.net
If new regedit finds a long enough key, it loops as you show. Just use regedit from 10240, it don't have this bug.
I can't reproduce this success story.
1) I have 27kb opencl.dll in WinSxS and 103kb opencl.dll in SysWoW64
2) I run sfc /scannow and got
"Windows Resource Protection found corrupt files and...