Page 9 of 10 FirstFirst ... 78910 LastLast
  1.    21 Nov 2015 #81
    Join Date : Aug 2015
    Maine
    Posts : 36,244
    Windows10Pro 64Bit

    Now here is same screen shot AFTER you run sfc /scannow

    Click image for larger version. 

Name:	opencl.PNG 
Views:	8 
Size:	38.8 KB 
ID:	49628
      My ComputersSystem Spec
  2.    21 Nov 2015 #82
    Join Date : Oct 2014
    Posts : 26
    Windows 10 Pro, 64 bit, 1703, build 15063.483.

    Quote Originally Posted by Gator5000e View Post
    So if I understand correctly, you opened CMD and then typed in "net view" (two words?), hit enter and you then you saw all your network computers again? Is that correct?

    Were you able to access them as well or were additional changes required? If so, could you spell those out possibly?

    Thanks.
    Hi Gator,
    Apart from the usual network troubleshooting step of rebooting my router, and my Windows 10 computer, all I did was to issue the "net view" command at a command prompt, and it listed all the computers on my network!
    After that, the Networking section of File Explorer on Windows 10 is working as normal, and I have full access to all shared Folders on my network.

    The "net view" command is indeed two words, separated by a space.

    My network is pretty simple, just my Windows 10 desktop, a Windows XP laptop, and two Raspberry Pi's both running Linux & Samba, all connected through a wireless Huawei E5372 4G device.

    I still think there is a networking bug in Windows 10 v11586, as these and other Forums are full of people with broken networks since the update. I never had problems with Vista, 8.0, 8.1 or 10 v102408.

    Hope this helps,
    Dave.
      My ComputerSystem Spec
  3.    21 Nov 2015 #83
    Join Date : Feb 2015
    Bamberg Germany
    Posts : 16,954
    Win10 Pro, Win10 Pro N, Win10 Home, Win10 Pro Insider Fast Ring, Windows 8.1 Pro, Ubuntu

    Then you can try what I did with a Catalyst library(AMDMantle64):

    1. First unregister the .dll's that need to be fixed, example : regsvr32 /u opencl64.dll
    2. Reboot
    3. Then run the 1st command above in post #71 to clean up everything.
    4. Reboot
    5. Reinstall driver
    6. Then run the 1st command above in post #71 to clean up all the old dll copies.
    7. Reboot
    8. See if everything runs as it should, and wait until the next time, to see if the corruption recurs, if it does, need to find another solution.
      My ComputersSystem Spec
  4.    21 Nov 2015 #84
    Join Date : Aug 2015
    Maine
    Posts : 36,244
    Windows10Pro 64Bit

    Like I reported earlier this problem should happen to anyone (I know of 4 users so far) who updates their Nvidia drivers to current drivers. (359.00) and at some point in time, run sfc /scannow, doing so Windows will remove the correct Opencl.dll file 103kb with its own incorrect file of Opencl.dll 27kb. But if you DON'T run sfc /scannow, Opencl.dll will not be removed. I believe their are lots of people with this same problem, but they haven't noticed it yet.
      My ComputersSystem Spec
  5.    21 Nov 2015 #85
    Join Date : Aug 2015
    Maine
    Posts : 36,244
    Windows10Pro 64Bit

    Quote Originally Posted by Cliff S View Post
    Then you can try what I did with a Catalyst library(AMDMantle64):

    1. First unregister the .dll's that need to be fixed, example : regsvr32 /u opencl64.dll
    2. Reboot
    3. Then run the 1st command above in post #71 to clean up everything.
    4. Reboot
    5. Reinstall driver
    6. Then run the 1st command above in post #71 to clean up all the old dll copies.
    7. Reboot
    8. See if everything runs as it should, and wait until the next time, to see if the corruption recurs, if it does, need to find another solution.
    Well that file Opencl64.dll is fine, no problems with that driver, its Opencl.dll file that is the problem.
      My ComputersSystem Spec
  6.    21 Nov 2015 #86
    Join Date : Feb 2015
    Bamberg Germany
    Posts : 16,954
    Win10 Pro, Win10 Pro N, Win10 Home, Win10 Pro Insider Fast Ring, Windows 8.1 Pro, Ubuntu

    Quote Originally Posted by OldMike65 View Post
    Well that file Opencl64.dll is fine, no problems with that driver, its Opencl.dll file that is the problem.
    Just substitute the .dll name.
      My ComputersSystem Spec
  7.    21 Nov 2015 #87
    Join Date : Jun 2015
    Posts : 531
    Windows 10 Pro 64bit; Windows 10 TP; KDE Neon

    Quote Originally Posted by Cliff S View Post
    I also found this:
    Hello,

    I've tried to register that file in my system and I get this:

    Click image for larger version. 

Name:	1.png 
Views:	5 
Size:	30.9 KB 
ID:	49636Click image for larger version. 

Name:	2.png 
Views:	5 
Size:	20.3 KB 
ID:	49637

    I am using the latest NVIDIA driver and I have not run SFC /SCANNOW due to this issue. Why can I not register it?

    Thank you.
      My ComputerSystem Spec
  8.    21 Nov 2015 #88
    Join Date : Feb 2015
    Bamberg Germany
    Posts : 16,954
    Win10 Pro, Win10 Pro N, Win10 Home, Win10 Pro Insider Fast Ring, Windows 8.1 Pro, Ubuntu

    I'm sorry I gave a short instruction, the following tutorial is how to register and un-register .dll & .ocx files:

    Unregister and Re-register a.. .dll or .ocx file and delete them
    One has to be careful with dll files in case they are shared. try renaming it first ProgramName.dll old-- and run your system awhile to see if you get any warnings first, especially at boot up. Then when no problems appear or crashes show up in Reliability History(in the Action Center) then you can unregister the dll.

    Open an Admin command prompt by right clicking the windows icon and choose it.

    For the path name you can use drag and drop in windows 8 by opening file explorer and dragging the dll to the command prompt after you type regsvr32 /u"
    example: regsvr32 /u "C:\Windows\System32\amdmantle64.dll"(this is for an AMD ´graphics dll)
    Don't forget quotes


    Register dll file

    To register a dll or ocx file, open a command prompt windows as an administrator, type the following and hit Enter:
    regsvr32 “path & filename of dll or ocx“
    Unregister dll file

    To un-register a dll or ocx file, open a command prompt windows as an administrator, type the following and hit Enter:
    regsvr32 /u “path & filename of dll or ocx“
    This will register or unregister the dll file.

      My ComputersSystem Spec
  9.    21 Nov 2015 #89
    Join Date : Aug 2015
    Maine
    Posts : 36,244
    Windows10Pro 64Bit

    Don't actually see how this might work, as we are dealing with TWO Opencl.dll files with the SAME name, difference being, file size, and maker of said dll . One is a MS dll file the other is made by Nvidia. The ONLY Opencl.dll that is the problem is the file by MS which is located in wow64_microsoft-windows-r..xwddmdriver-wow64-C_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22 <------ One location only, the other 3 Opencl.dll files are correct, which are in completely different locations.

    Added: Almost forgot to mention, This is the file the one located in that ONE location which is 27kb in size, and the incorrect opencl.dll file, is the one that windows uses to replace the CORRECT Opencl.dll files IF you run SFC / SCANNOW.
      My ComputersSystem Spec
  10.    21 Nov 2015 #90
    Join Date : Feb 2015
    Bamberg Germany
    Posts : 16,954
    Win10 Pro, Win10 Pro N, Win10 Home, Win10 Pro Insider Fast Ring, Windows 8.1 Pro, Ubuntu

    Quote Originally Posted by OldMike65 View Post
    Don't actually see how this might work, as we are dealing with TWO Opencl.dll files with the SAME name, difference being, file size, and maker of said dll . One is a MS dll file the other is made by Nvidia. The ONLY Opencl.dll that is the problem is the file by MS which is located in wow64_microsoft-windows-r..xwddmdriver-wow64-C_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22 <------ One location only, the other 3 Opencl.dll files are correct, which are in completely different locations.
    I said I didn't have experience with Nvidia and Opencl or this specific problem Mike, sorry.
      My ComputersSystem Spec

 
Page 9 of 10 FirstFirst ... 78910 LastLast


Similar Threads
Thread Forum
problem with upgrade to windows 10 home, version 1511, 10586
tried to install the upgrade to windows 10 home, version 1511, 10586, and it refuses to take, keeps telling me there's a problem and to try again later.
Installation and Upgrade
Solved Version 1511 Updates: Advice or Help uninstalling this update needed
I opened my laptop the other day and all of a sudden the user interface with Windows 10 had totally changed. What this means for me as a student is that I've lost the usability I depended on to switch between OneNote for Desktop/Edge/word and I have...
Windows Updates and Activation
Upgrade to Windows 10 Pro, version 1511, 10586 - Error 0xc1900107
So today the big Fall update came out and I wanted to install it so after over 2 hours of my slow internet downloading everything I need and installing it I was given a message that I need to restart my PC to finish everything up. So I did and while...
Windows Updates and Activation
Cumulative Update for Windows 10 (KB3097617)
42580 Info: https://support.microsoft.com/en-us/kb/3097617 Download x64 KB3097617: 496 MB http://t.co/bgMy2WebuS Download x86 KB3097617: 223 MB http://t.co/FSYejVRx7B
Windows 10 News
Solved Cumulative Update (KB3081424) won't show up in Windows Update
I know that a lot of people have been having issues with this update, but I haven't even been able to get the update to appear in Windows Update, it's not in my Update History so im pretty sure it didn't install without me knowing, and when I check...
Windows Updates and Activation
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 17:39.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums