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,
Then you can try what I did with a Catalyst library(AMDMantle64):
- First unregister the .dll's that need to be fixed, example : regsvr32 /u opencl64.dll
- Then run the 1st command above in post #71 to clean up everything.
- Reinstall driver
- Then run the 1st command above in post #71 to clean up all the old dll copies.
- 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.
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.
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 themOne 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.
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.