2013 Razer Blade with Windows 10
1. Original issue: Wifi keeps dropping due to "Missing network protocols" that can't be fixed by Windows due to missing Registry sockets entries. So I googled it and found recommendations to run SFC /scannow which revealed a corrupted Opencl.dll which lead me to run DISM restorehealth (no change).
2. I've ran SFCFix.exe twice now, it hangs after running DISM and does NOT produce an SFCFix log as advertised, i.e. runs DISM and then nothing for 40+ minutes. Come to find out that Opencl.dll has little or nothing to do with network protocols and may or may not have an impact on my old laptop's performance (needs a new battery, runs hot), so I'm essentially just here hoping that someone will tell me I'm right or wrong in that a corrupt Opencl.dll is no big deal, and to let you know SFCFix hangs at DISM twice in a row. I will read the Opencl.dll GUIDE stickied above, after a work meeting.
3. For my original problems with missing network protocols I will be looking at the following, in case anyone would like to tell me I'm wrong: https://support.microsoft.com/en-us/kb/299357
BEST FIX: One or More Network Protocols Are Missing - Appuals.com
Solved Network Protocols - Windows 10 Forums
...which is obviously beyond the scope of this forum subsection. But - SFCFix hangs at DISM, if it's a common thing maybe people should be told ahead of time. Any help is appreciated, and thanks to niemiro for SFCFix, here's to hoping it gets bought up by Microsoft and that they and Nvidia fix these issues - which still leaves me and my missing network protocols...
1. Original issue: Wifi keeps dropping due to "Missing network protocols" that can't be fixed by Windows due to missing Registry sockets entries. So I googled it and found recommendations to run SFC /scannow which revealed a corrupted Opencl.dll which lead me to run DISM restorehealth (no change).
2. I've ran SFCFix.exe twice now, it hangs after running DISM and does NOT produce an SFCFix log as advertised, i.e. runs DISM and then nothing for 40+ minutes. Come to find out that Opencl.dll has little or nothing to do with network protocols and may or may not have an impact on my old laptop's performance (needs a new battery, runs hot), so I'm essentially just here hoping that someone will tell me I'm right or wrong in that a corrupt Opencl.dll is no big deal, and to let you know SFCFix hangs at DISM twice in a row. I will read the Opencl.dll GUIDE stickied above, after a work meeting.
3. For my original problems with missing network protocols I will be looking at the following, in case anyone would like to tell me I'm wrong: https://support.microsoft.com/en-us/kb/299357
BEST FIX: One or More Network Protocols Are Missing - Appuals.com
Solved Network Protocols - Windows 10 Forums
...which is obviously beyond the scope of this forum subsection. But - SFCFix hangs at DISM, if it's a common thing maybe people should be told ahead of time. Any help is appreciated, and thanks to niemiro for SFCFix, here's to hoping it gets bought up by Microsoft and that they and Nvidia fix these issues - which still leaves me and my missing network protocols...
