Windows 10: One or more network protocols are missing, solution

OK so disabling ipv 6 and using 4 seems to have partly solved this. However this is the 3rd time I've attempted to post this reply.

Wouldn't it be better to find out which protocol was missing and install it, though? Then I could use 6

 

So I just encountered this issue, and searched for a solution on my phone (WiFi was still up, computer just couldn't connect). I figured it out, mostly thanks to this forum, and I thought I would list what I did that didn't work, and what finally did.

What didn't work:
--Windows troubleshoot network problems (no surprise there)
--sfc /scannow
--netsh winsock reset catalog
netsh int ip reset
ipconfig /flushdns
--remove the tick next to 'Internet Protocol Version 6 (TCP/IPv6 )' in adapter settings
--netsh int ipv4 install
--netsh winsock reset catalog
netsh int ip reset
ipconfig /flushdns

What did:
I went to my Network Connections, right-clicked on my Local Area Connection, clicked Properties, selected Internet Protocol Version 4 (TCP/IPv4), clicked Properties, and selected both 'Obtain an IP address automatically' buttons.

Changing that immediately allowed my computer to connect, and the first thing I did was come here, make an account, and post this. For those still having this issue, might be worth a shot.

 

Got the same problem on a brand new Lenovo after 1511 update was installed on March 3.

I rolled back the install to check the problem went away (it did and I could instantly get on line again). I then switched to scheduled updates and downloaded 1511 again, once downloaded I disconnected my wifi and then disabled my AVG firewall and then selected install updates and shut down so that 1511 was installed again.

Once back up, all was good and I could connect to the internet again and so I've re-enabled my AVG firewall. So far so good.

The AVG might be a red herring and simply rolling back 1511 and then re-installing it may also do the trick.

Certainly no need to disable TCP/IP v6, or re-install it. Also no need to run any winsocks commands etc. Obviously every case is the different as can be seen by the many different solutions but this worked well for me, was easy and hopefully will help someone else

 

This worked for me, at least this time. Wife's PC has a usb wifi dongle and 9/10 times when win10 does an auto update this problem occurs. Sometimes the network troubleshooting wizard fixes it, but this time it did not. But this fix got it working after reboot.

 

THANK YOU. Worked for me perfectly. *kisses and hugs*

 

I tried this fix with my Windows 10 update, but no joy.

After reverting back to Windows 7, doing multiple attempts at other fixes, completing what seemed to be possibly an incomplete update application (crazy how these partial bits and pieces accumulate), and still getting no success, I tried this fix once again, restarted, and suddenly it worked.

Now I'm pushing my luck and trying to install Windows 10 again. *Smile At least I know I can repeat at least some of the above steps and get things back. I really would like to upgrade and I really would like internet connectivity!

But thanks, efta, for your fix. I had to fix some other things to enable the fix--at least, I guess that's what I did, who knows?--but in the end it was your advice that helped me go the last mile. So THANKS.

 

Quick update:

Installed Windows 10 again, problem recurred.
This time, two additional steps for a fix:
1. Turned Windows Firewall off -- theory: might conflict with AVG antivirus. This one seems a stretch, but I record it for completeness.
2. Went to adapter properties and made sure every possible installable protocol was installed. You can get the list by clicking on any protocol to highlight it, selecting install, selecting protocol, then installing every protocol you see there.

Having done these things, I restarted, with no luck.

THEN I ran efta's script again, and connectivity came back, for the first time in my attempt to upgrade to Windows 10.

FWIW, YMMV -- and thanks again to efta's initial suggestion as well as to all the informed and helpful discussion in this thread.

 

I had the same unsuccess. None of the commands made any difference.
I set the IP address manually to a static address and all was well. I could connect to the internet.

I did notice that the auto IP address was well out of the range defined in the dhcp server (router).
Either win10 is not reading the offered IP address, or it is making it up. Either way the IP address is not valid.

Where is MS support on this???? Why are we forced to troll the internet for help from others suffering from this problem??

 

Just yesterday I was experiencing this same issue with missing network protocols and I then changed my ethernet cable from one input to the next on the router and the problem was solved immediately. Come to find out the ethernet input is bad on the router.

 

Thank you dazz.. It's finally solved for me.

 

I'm having the same problem, I keep getting the error "One of more network protocols are missing..." I tried every solution under the sun that people have posted, nothing worked.

However, I noticed that when my internet disappears and I get this error message, I also don't have internet on my android.

Does that mean the problem is in Windows 10 or my router/Internet provider?

 

Microsoft just forced a Win10 upgrade on me and I had the same problem with the missing network protocols. I spent six hours working with three techs at the Answer Desk and nothing they tried worked. I gave up on them and tried deleting my anti-virus application (Avast). Restarted my PC, and that fixed the problem. I then reinstalled Avast, and everything is now working. Hope this helps someone else.

 

I have used this solution and it works fine - for a few days. But then the dreaded "One or more network protocols are missing...." error message appears.

 

Does the command work on subsequent attempts?

 

I had this as intermittent problem for a couple of months. I rarely turn my PC off so it is generally connected, but if I do restart, SOMETIMES I get the network protocol message. My first reaction was to unplug the ethernet cable and replug it after 10 seconds. This has worked on many occasions, though I have had to repeat the action sometimes to get the connection. Today after about 5 or 6 tries it still wouldn't connect, so I rebooted the router and restarted the computer. That did the trick, but I don't like these 'more by luck than judgement' fixes. It is clear that after reconnecting, sometimes miraculously the network protocols are reinstated. As there has been a lot of discussion about this problem, no doubt Microsoft are working tirelessly night and day to rush out a fix. Or NOT. *Mad