Windows 10: Network Protocols

Thanks
Worked for me got my "WD TV" connected
Was working yesterday "not today"

 

this gave me SetupDiCallClassInstaller Erorr: 0x6
this gave me SetupDiCallClassInstaller Erorr: 0x6
this gave me SetupDiCallClassInstaller Erorr: 0x6
this gave me SetupDiCallClassInstaller Erorr: 0x6
this gave me SetupDiCallClassInstaller Erorr: 0x6
this gave me SetupDiCallClassInstaller Erorr: 0x6
Unable to stop the vmms service: 0x4287f740Successfully commited changes to the registry
Successfully commited changes to the registry

and then it failed to reboot and i had to do it manually,but... my internet seems to be working since then? i guess i will post back if it dies again lol. thanks!

 

Hi All,

Having the worst time ever on this one. nothing on here seems to work.

Have un-installed re-installed drivers over and over.

Tried manually configuring the IP Address attempted to un-install all IPv6 Drivers and anything to do with it.

Still not able to get online, any help would be incredible!

System:
Motherboard - MSI H170-Gaming 3
Ethernet e2200 Killer
CPU: i5-6400
16gb Ram
MSI GTX 970

 

This took me three hours to solve. I first tried updating the Broadcom ethernet driver card, which I had to manually uninstall and then reinstall. Broadcom's website Ethernet NIC NetXtreme I Desktop/Mobile | Broadcom (v17.2.0.2 vs v15.6.1.3). This didn't work although I liked how this driver, as opposed to the older version, was listed for Windows 10. I then rebooted my network router and everything worked perfectly. Argh, if only I had tried that earlier in the process!

 

Paolo,

You're absolutely correct in your statements here and I don't think you need to be concerned with "diverting from the original question" since there is some advice given here that may be flawed since it fails to recognize your first point. I have been at this as a professional in the industry for nearly 30 years now and can't tell you how often we see problems (bugs or whatever) with an OS that is same the version & build, exhibiting behaviors not observed on other hardware platforms. Besides, it doesn't take much Googling to come to the conclusion that this issue with "network protocols are missing" is indeed a Windows 10 issue - apparently with the 1511 version if not another update. Users are reporting that uninstalling or rolling back is resolving their issues. I laughed when I read the poster comments about how if this was an OS bug then millions of users would be having the same issue. It is NOT an issue related to anyone's existing network or router, or whatever. Could it have been, possibly, but the commonality of this widely reported issue makes the case pretty cut and dry. When Microsoft first released the Surface Pro a few years back, thousands of users experienced WiFi issues, even some early Windows 8 tablets had the same problems (devices refused to connect to a WiFi network, would connect then drop, would show no networks available, and even show there was no WiFi adapter installed!). Just recently, Microsoft released a security update that could crash Microsoft Outlook - uninstall the update and the issue went away. This didn't affect all users - we manage 150 users and only a few experienced the problem. Within 24 hours, Microsoft re-released the update, with whatever fix was needed, and they never said a word to anyone so you know they won't acknowledge it even when there is a proven bug in their software. In the case of this missing network protocol and otherwise 'WiFi" crashing issue, I know a) a lot of people are reporting it and b) I've recently setup 5 laptops of the identical make and model, 4 with Windows 8.1 (fresh install via the manufacturer's recovery media), and 1 with Windows 10, an upgrade off the factory-installed Windows 7, which I did specifically to test the process and Windows 10 in general.

Microsoft is PUSHING the free upgrade hard on users so it darn-well better work flawlessly, AS AN UPGRADE, even though anyone who's been at this for a while knows that an OS upgrade is suicidal at best. But even then, yes an OS can have a bug that raises its ugly head even with a clean install on hardware platform/environment A, while working just fine on hardware platform/environment B.

So if uninstalling or rolling back is necessary to restore the functionality of a computer, then a user should do that vs. holding off on not doing so just because a forum bully chooses to chastise forum members who do not, under the claim they've become a walking time bomb for the Internet community. What good is a "secured" computer that's useless because it won't connect or stay connected to a network?

In my case, I was experiencing the issue that started this thread, and I came here looking for a solution but ended up finding one in this discussion and it seems to have solved the issue for me:

[FIX] Windows Sockets Registry Entries Required For Network Connectivity Are Missing

The fix posted there has you resetting Winsock registry entries. The fastest and easiest method for me was to download the .reg files posted by Kapil Arya, about 1/2 way down the page, and then import them. Haven't had any WiFi issues since.

QUOTE=Paolo;513476]dear JW0914,

• most software bugs show their incorrect behaviour when some environmental conditions exists; in the case of this particular network issue, the fact that 90% of users did not experienced the problem is not a prove that the bug does not exists
• you claim that this is not a bug as with a clean install the problem does not show; I agree with you that many OS issues are related to problems during the upgrade procedure and that a clean install will prevent many problem from happening; however, if my OS is prompting me to upgrade from an older version to Win10, it means that the upgrade us considered to be a standard feature of the OS, as such, is expected to work properly

Cordially
Paolo[/QUOTE]

 

I have Bluetooth on my laptop, the drivers for them were corrupt, after deleting and re-installing them the "Network protocols" issue cleared up.

This worked for me so I figured it might work for someone else. O_O

 

I had the same problem on my windows 10. It update and wouldn't allow me Internet access via wifi. At first I rolled back windows to previous backup and that sorted it then windows updated again and back to square one. Anyway it's now fixed. I followed the below link

Fix DNS Server Not Responding on Windows - XtremeRain

And replaced the DNS.


There are three methods two solve DNS server not responding problem. Now you will know these methods one by one.



Method 1: Fixing Network Address
This is the most successful method to solve dns server not responding problem. It’s not too long process. Lets know the process-

1. At first go to Control Panel > Network and Internet > Network and Sharing Center.

fix dns server not responding

2. Now click on Change Adapter Setting.

3. Select your network adapter and right click on it and go to Properties.

fix dns server not responding

4. Now double click on Internet Protocol Version 4 (TCP/IPv4).

5. Now set your DNS. Use Preferred DNS: 8.8.8.8 and Alternative DNS 8.8.4.4

You also can use open DNS. That is 208.67.222.222 and 208.67.220.220

6. Now mark on Validate settings upon exit and click on OK.

7. Now open Command Prompt. To open it just go to Start and type CMD. Then press enter.

8. Type IPCONFIG /ALL and press enter.

fix dns server not responding

9. Now you will see your Physical Address. Right down it. Example: 78-DD-08-F1-DF-B0

10. Now press Windows Logo Key + R from Keyboard to open RUN.

11. In RUN, type NCPA.CPL and press enter.

12. Now go to your network adapter properties.

fix dns server not responding

13. Click on Configure and Select Advance Tab.

14. In Advance Tab, find Network Address in property section and select it.

15. Now mark on value and type your physical address without dashes. Example: My physical address is 78-DD-08-F1-DF-B0. So i’ll type 78DD08F1DFB0.

fix dns server not responding

16. Now click on OK and restart your PC.

I hope by following this method you can fix your dns server not responding error.
Please read further via the link

 

---
Many thanks, eden.
I have had internet issues for several days - the same constant message about missing protocols. At first I thought it was my ISP, and then I blamed my router. Reset after reset, updating drivers and reinstalling, and the same problem occurred. I have almost been pulling hair trying to resolve the issue until I scrolled through this thread and found your solution. It worked like a charm and I had no problems following your instructions.
Luckily my fiancee's laptop is Windows 7, so I could breath a sigh of relief. He is extremely happy that I've found a fix all on my own!! LOL. It definitely feels good to fix something by ones self. Obviously with a little help *Wink

I'm not getting my hopes up just yet though, as previously I had reset the router to factory default and I would have internet for a short while and then it would break again.
I'm keeping my fingers crossed that this reg fix is permanent.

I have also copied and pasted your solution into wordpad just in case this issue happens to arise in the future, or if anyone else has similar issues.

Thank you, thank you, thank you. *Cool

PS. I made an account here just to thank you!

 

I just encountered this issue in the last hour after installing VirtualBox. I thought that may have had something to do with it, since it had added protocols for virtualization. I ran through a couple of the threads to see what types of issues other people have had. I didn't try anything that any of the other users had posted but I did notice a few posts about firewall configurations, so I went ahead and reset the windows 10 firewall settings to default, rebooted and the issues was resolved. This solution worked for me, not sure if it will for anyone else but I hope that it may be of some help to someone.

 

Networking is verry 'buggy' with Windows 10. I have this same annoying problem. I have four windows 10 PCs on a homegroup network. The only AV installed or running is Windows Defender. When I attempt to backup files between these PCs, I have trouble with access, despite all being set up on the homegroup. I get the same errors mentioned by previous posters. Interestingly, after I run the diagnostics and get the message that one or more network protocols are missing and the problem is not fixed, I then exit the diagnostic screen. After that, I can access the files. This is a ridiculous process to go through each time I want to sync files between PCs. I never had this trouble when using the homegroup network protocol in Windows 7.

 

I also have this issue for a week. And today, I have fix this problem. Here is how I fix this issue.
1. Go to Registry Editor (Press Start and R button, and then type "regedit" without quotation mark, click OK or hit Enter).
2. In the Registry Editor, go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
3. Find Winsock, and create backup of it. To do the backup, right click on Winsock, and select Export. Give a name (e.g. Winsock.reg or whatever you want).
4. Find Winsock2, and do the backup of Winsock2 like point 3.
5. Now, delete Winsock and Winsock2. To do this, right click on Winsock or Winsock2, then select Delete.
6. Restart the PC.
7. Now, just import Winsock and Winsock2 from the backup file before.
8. Restart the PC and Done. The network issue is fixed.

Hope this can help anyone who get this issue. *Smile

 

fefaz, I want to try your fix. But could you add the instructions to UNDO (in case of something dont work)?

 

I'm posting this as a rant, more than anything else. My new Win10 Pro HP laptop has been plagued with a series of these network connectivity issues. They seem to crop up after every other update. My angst is that I recall spending hours setting up network protocols way back in the days of Windows 3.1 and other early versions. I was very competent with DOS commands and network protocols. By the time Windows 7 came along, having to tinker with networks and other machine settings was a distant memory - as it should be. Now, here I am again, spending hours correcting network bugs. I've always been an IOS hater. Suddenly, iPads aren't looking so pad. Ain't progress great!!

 

Do a backup by exporting registry key of Winsock and Winsock 2. So, if something doesn't work, you can revert back by importing those backup.