Tags
–Updates —
2016-03-11 Updated to note requirement to remove non-Microsoft anti-virus and firewalls
2016-01-24 refactored to give clearer path
2016-04-05 updated to remove anti-malware and suggest replacing the network card.
2016-04-06 updated to include restoring to a system restore point
—
I have a lovely new Microsoft Surface Pro 4 but after the November 2015 update to Version 1511 build 10.0.10586 (aka “Threshold”) I kept losing network connectivity with the error.
“One or more network protocols are missing on this computer”
After a lot of investigation and feedback in the comments sections I now know that there is no one single cause for this issue. Causes include,
- Upgrading to “Threshold”
- In November 2015 Microsoft released Threshold (Windows 10 version 1511). The process of upgrading to Threshold breaks can cause this issue.
- Refreshing your PC with Threshold.
- When you upgrade to Threshold it creates a recovery partition that containing Windows 10 version 1511. When you refresh your PC it is possible that you simply reapply the corrupt configuration.
- Using a USB to Ethernet dongle
- Having a bad router
- Having a dirty or damaged Ethernet cable or socket
- NetBIOS issues associated with a static IP
What I think is happening
I think that Windows 10 detects some sort of problem on the network adapter and then disables it. Our best fix is to find the root cause but this is very often impossible and therefore our second choice is to re-enable the network adapter.
Fixing the root cause and issue
Verify your DNS settings
If you are just using DHCP then you should not have broken your DNS but if you have changed your DNS servers on your router or network adapter then this could be the cause of your problem. In this case reset the devices to use the default DNS provider.
For wired Ethernet connections
These are simple non-destructive changes that you can make that may fix the root cause.
- Visually inspect your Ethernet port and the cable to the router. If there is any damage then repair it.
- Check your router logs for errors.
- Change the port you use on your router
- If you are using a Microsoft Surface or similar device change your inexpensive generic USB to Ethernet dongle to the expensive Microsoft branded one. (untested solution – I will update).
Remove non-Microsoft anti-virus and firewall
If you have a non-Microsoft anti-virus or anti-malware product it might stop your Windows updates applying properly. Remove it. I also don’t trust Windows 10 to play nicely with non-Windows firewalls. Remove it.
- Remove non-Microsoft anti-virus, anti-malware and firewall products
- Reboot
- Run Windows Update
- Reboot
- Retest
- Proceed with the suggestions below if necessary.
Fix Windows 10 and drivers
These are safe changes you can make that might fix the root cause. If one step does not work then proceed to the next.
- Run Windows Update
- Run SFC and DISM.
- Although these make changes to your Windows installation I believe that they are safe.
- Select the adapter in Device Manager, right click on it and choose “Update Driver Software”
- After step 3 above has completed successfully remove the network adapter and choose Action > Scan for Hardware Changes to add it again. If it was disabled it should now be enabled and working again without the need for a reboot.
If this does not work you may wish to restore to an earlier System Restore Point. This will revert driver changes that may be causing you issues without affecting your data.
Fixing the Registry
If the above changes did not work then you may need to fix your registry because when Windows 10 disables your network adapter it sets registry permissions that stop it being reset successfully.
Registry Permissions Fix
This can be fixed by a registry edit as shown in this video.
The key is
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Nsi\{eb004a00-9b1a-11d4-9123-0050047759bc}\26
And the correct permission is Full Control for everyone. You may find that on your device the key is “ControlSet” or “ControlSet002” etc – it depends on your device’s history.
After setting this permission you will need to run,
netsh int ip reset resetlog.txt
as shown in the video.
Registry Winsock keys fix
If this does not work you may have correct Winsock entries. You can replace these with ones from a good computer.
from Kyle’s entry on http://www.kapilarya.com/windows-sockets-registry-entries-required-for-network-connectivity-is-missing
- Create a Recovery Point and then,
As suggested by Nate J export the Winsock and WinSock 2 keys from another windows based computer (Windows 7, Windows 8 or Windows 8.1 regardless of version (Home, Enterprise etc.)). I exported the keys from a Windows 7 Enterprise laptop for use on my Windows 10 Home desktop. Only thing to ensure is to export them from an OS of the same type (i.e. 32-bit for 32-bit, 64-bit for 64-bit).
Once you have the exported keys:
1.)Backup Winsock and WinSock2 keys.
2.) Add the exported Winsock and WinSock2 keys you just exported from another system.
3.) Reboot
4.) Following reboot your computer should now be able to successfully establish a network connection and your apps should be able to connect to the internet as well.
Replace network card
If you have a desktop computer you can put in a new network card. This will instantly solve any driver or hardware issues that you might have.
A note from the author
If you know someone who lives in the UK and cares about global warming please send them this link.
My petition will require British petrol stations to sell fuel with 100% CO2 offset in addition to normal fuel. Eveyone wins and it won’t cost the taxpayer a penny.
Dr James Bayley 
Pingback: Windows 10 static IP bug | Dr James Bayley
I have followed the instructions in the video and get an error that reads
Resetting, failed.
Access is denied.
There’s no user specified settings to be reset.
Any suggestions would be great.
Steve, I had additional corruption issues and you might as well. Run SFC and DISM as described here.
https://blog.jamesbayley.com/2016/01/03/fixed-one-or-more-network-protocols-are-missing-on-this-computer/https://blog.jamesbayley.com/2015/12/19/how-to-fix-corrupt-windows-10/
reboot
and rerun the process described above to reset permissions and the TCP/IP stack.
Is that the correct link to describe running SFC and DISM?
I have been working on this issue for 6 weeks, even allowed a Microsoft Tech to remote desktop my machine. He worked on it for 90 minutes and could not repair the issue either.
This morning, I noticed a bit of dust on the screen behind the power source fan, so I shut everything down and disconnected all wires. Took the cover off and cleaned out the dust. I plugged it all back in and everything now works….nearest I can figure is that some capacitor or some conflict was stored in the hardware and was “bled dry” when the machine was unplugged.
So, when in doubt, power down, disconnect from the wall and let it sit I guess. This should not have worked, but it did….I am up and running now!
Thanks for your help!
Install all your drivers, driver updates, windows updates, also download and use a driver manager and install updates with that too and it will work!
Updating device drivers is very good advice. Unfortunately some device managers cannot be trusted. Can you recommend a good one?
The ONLY thing that worked permanently for me was to do a clean install back to Windows 7. And that is where I will stay… sorry not a techie (my son is and he tried ALL of the suggestions we had found EVERYWHERE on the internet and none worked for more than a day at most… usually less) so no need for me to have 10 just yet.
Shame – did not work for me.
I followed all the steps and all the things that were supposed to happen happened so I think I did it correctly. But still protocols missing. Annoyingly, after a reboot, the registry entry permissions had been changed back so Full Control was not checked. I will now move onto your next suggestion – DISM etc. This problem is driving me up the wall!
For feedback:
1. Your registry entry in the video does not match the text. ControlSet001 or CurrentControlSet? Or both?
2. Which entry should be used in the registry? I have 6 instances of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nsi\{eb004a00-9b1a-11d4-9123-0050047759bc}. More than one has the “26” folder in it. Should I select just the top one?
In the video it is CurrentControlSet but I don’t have one of those. I only have ControlSet001. I have no idea why you have 6 instances of the same key. I would have thought that was bad but I have absolutely no idea what they do. With that caveat my next act of desperation would be to backup the registry and delete all but one of the identical keys. Try the SFC and DISM first though. They are safe and might help.
Thanks for the reply. I have just managed to get back to this problem.
OK, bit of a correction in what I said. I do not have six instances of that registry folder. What I should have said is the entry name you highlight did not have a “26” folder on my system. So I looked at similar folder instances for a “26” folder. As I have little idea what this “26” folder is and what it should be under I am shooting in the dark somewhat and perhaps this is why it did not work. Could you elaborate a bit on how to identify the relevant folder and how the names “work”?
I don’t know. I got the magic from from some Google searches. I have recently added a lot more virtual boxes to my machine and I find that I now have many instances of that registry folder. Like you only some have the “26” folder, like you I cannot get TCP/IP to work properly. My physical adapter is fine after my fix but bizarrely some of my virtual adapters only allow traffic in one direction and complain about a lack of TCP/IP in the other! If I make any progress I will update you. This is a really stupid problem and Microsoft should be ashamed.
Thanks for the promise to keep me updated.
I have run “sfc/scannow” and I have no problems there.
It looks like I may have to move onto some of the suggested solutions I have seen on the internet that involve deleting various registry entries. (Winsock/Winsock2 etc). I am rather reluctant without more indication of success or at least not that I will have to rebuild my PC if it goes wrong. It all feels a bit hit and miss to me.
One other thing I have tried is reinstalling protocols (IPV4) from C:\Windows\INF. You may have seen this idea on the internet. It failed for me with a message saying it was against group policy. So I gave that up as I could not work out how to locate the relevant policy.
As you say, it is about time Microsoft got on top of this.
I share your concerns about the Winsock/Winsock2 fix although backing up the registry first might be a mitigation. I am tending towards thinking that I may need to do a clean install from official Microsoft media. This is less shocking than it sounds because I have a particular backup technique. You may find this interesting https://blog.jamesbayley.com/2016/01/03/the-definative-guide-to-backing-up-your-home-computer/.
I have made progress! 🙂
I eventually took the risk and went down the “alter the registry” route. This involves deleting registry entries for Winsock and Winsock2. (Details can be found quite easily on the internet.) The suggestion is to import new entries for Winsock and Winsock2 from a Windows 7 PC. I did not have access to that so I used a different WIndows 10 PC that did not have the missing protocols problem. Finished with a tcpip reset and a reboot or two and the symptoms are gone.
My actual problem that I was trying to solve was I could not share folders across my two PCs. And that problem was not solved. That turned out to be an issue with my Kapsersky Firewall. Confusingly I could share folders in one direction but not the other – even though the Kaspersky was configured more or less the same on both PCs. Anyway, after a bit of fiddling with the firewall (on the other PC) it worked. I am not quite sure exactly what change fixed it.
===========================================================
For what it is worth. I was also being driven up the wall by the Start not responding and the Cortana icon not responding.
This fixed the former and improved the latter:
http://home.bt.com/tech-gadgets/computing/has-your-windows-10-start-menu-stopped-working-here-are-four-ways-to-fix-it-11364000314532
Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}
I think Cortana is not responding because the “Application Identity” service is not working fast enough. If you start it then Cortana works, though temporarily.
==========================================================
So ends my torment of 2 months of my system being annoyingly unuseable. I do not know what Microsoft are playing at as they must be aware of these very basic problems.
Thank for your blog. It encouraged me to try again when I had given up.
==========================================================
I am pleased your PC is working again. It is very interesting that you also needed to apply the Get-AppXPackage fix. I think that this is also symptomatic of a bad upgrade. At work I had to format a Surface 3 and reinstall Windows 10 v1156 (Threshold) from an ISO.
Yes, I am thinking I may end up having to do a re-install if Microsoft do not fix it soon. Or I mess up my PC doing operations I do not really fully understand.
I have looked at your backup page with interest as I was not sure of the best strategy. I already take the occasional system image backup and I have a restore disk. Your blog has prompted me to download the Windows 10 media tool and create an ISO on a DVD.
It gets a bit confusing because it suggests some of it is for Windows 7. (For instance the system image). I assume it would still work. But that might be my first mistake …
The Window 7 and Windows 10 system image restore function is identical. However if you are using Windows 10 you must ensure you turn off bitlocker before making your system image. I will blog about this in a later post.
It is also important to create a recovery disk so that you have a copy of the correct drivers.
Randomly browsed back to your blog here today and noticed that once upon a time you had prompted me to take an ISO on a DVD. Just to say that came in use when I had a continuation of the taskbar problems in spades. After trying reset, recover, system image restore, restore from USB ISO, my last option was to use the DVD – which worked. So thanks.
SInce then I have given up on taking system images and using the WIndows 10 Backup system because it keeps crashing my PC. I have taken fresh ISO copies on DVD and USB stick. It really is unclear on what the intended operation is intended by Microsoft. It seems to be in a bit of a mess with various bits not working and a muddle with WIndows 7 documenting.
I seem to remember you said somewhere you were going to update your recovery suggestions. Have you done that? As I am re-investigating what to do that would be useful if you have investigated the topic.
Dear John,
I have indeed improved my recovery suggestions,
https://blog.jamesbayley.com/2016/01/03/the-definative-guide-to-backing-up-your-home-computer/
I very strongly recommend that you upgrade to Windows 10. I have been testing this in a production environment for about 2 years and I am not going to roll it out to 1200 machines. It offers great usability and security advantages over Windows 7. The most important of these is the ability of OneDrive to backup files in real time to the cloud. I recently recovered files from the OneDrive cloud recycle bin after an accidental deletion and complete hard drive failure.
If you want to continue to use Windows 7 then the minimum protection I would recommend is to use Veeam EndPoint Backup and a 1 TB external drive (preferably RAID).
James
Sorry, I muddled you there. I am on Windows 10. My reference to Windows 7 was because when you do a copy System Image under Windows 10 it refers to WIndows 7 – raising doubts in my mind about compatibility. But since Backup/System Image has packed up completely on Windows 10 it is all a bit moot now.
Just after I posted I realised you had updated your Backup ideas – thank you. I will have a look and work out what to do next.
Yes. System Image under Windows 10 is available but deprecated and cannot be trusted. I recommend Veeam Endpoint Backup for this purpose.
Thank you for pointing out my error. The correct link is
https://blog.jamesbayley.com/2015/12/19/how-to-fix-corrupt-windows-10/
Wow, nice work! This is one nasty bug – until now, there were no practical solutions. Thanks!
I’m really unimpressed by the lack of maturity of Windows 10. We see this issue, I see old snap-ins that are still present but do not work with 10. ipconfig is still around, but it doesn’t really work any longer – need to use netsh commands. Etc. This stuff needs to be cleaned up.
The computer with W10 is only connected wirelessly. I triggered this problem before by changing IP address to administer a router that I temporarily connected directly. Could not recover from touching the IP stack! Ended up reinstalling wireless software and fixed that issue. Today, I decided that I wanted this PC to quit jumping around and assigned it a (local) static IP address. It would not recover. Made this permissions change, issued the reset and voila it worked again.
Thanks for for the feedback Brian. I am pleased that I could help.
Good Sir,
Thank you thank you! I’ve been struggling with this issue since upgrading to Windows 10 several months ago, though my connectivity has been intermittent. My troubleshooter would sometimes fix the issues temporarily but not for long. The troubleshooter has sometimes found “binding set incorrectly (906)” if that helps, it’s all Gaelic to me. Thanks again.
I had this error code which it turned out was caused by my powerline adaptor being plugged in to the wrong RJ45 socket on my VDSL hub. The hub has four regular yellow ethernet ports and a red one for connecting to an external router if it is only being used as a wireless access point. Perhaps it is worth checking all the physical stuff before assuming it is a Windows 10 error.
Phil, You might be onto something here. I have a Microsoft Surface 4 and they don’t have a proper Ethernet port. To connected to a wired network I use a USB to Ethernet adapter on a USB hub. At work I have been imaging Microsoft Surface 3 and it has have been very difficult. One challenge is getting it to recognize a USB to Ethernet adapter, I have come to the conclusion that it is prudent to use Microsoft’s own adapter even though it costs twice as much as anyone elses. I am going to exchange my ANKER adapter for a Microsoft one and see if my problems go away, it could be that each time the adapter glitches Windows 10 permanently disables it.
Having fixed this problem for a few weeks it has now started happening again. I found that removing the disabled USB network adapter in Device Manager and then doing a Hardware Scan to find it again fixed the connection without the need for a reboot.
Thank you so much for this!
I have a similar problem, Sometimes I can’t find one computer on the network and I get the error message about missing protocols. So after reading this I tried an experiment.
I disabled my ethernet connection and enabled wifi. Now it works.
I then disabled my wifi and enabled ethernet. It still works.??????
Tomorrow it will probably stop again.
We have been having this “missing protocol” problem for a week or so. It would just suddenly kick us off wifi and rebooting my PC or the router seemed to do no good, nor have various other fixes I’ve been reading online. If I lost the connection on my PC, my husband also lost his connection on his Mac. The last two times when this has happened, however, and this might just be coincidental, I have turned off my PC, restarted the router, and then told my husband to try to get on the internet again with his Mac FIRST. He was able to get on – and then I was able to start my computer again and get on too.
Thank you for this report. The behaviour you see is consistent with my theory that network issues cause the network card to be disabled. However unlike other users a PC reboot fixes it.
I think that this is the first time in this thread that we have seen this error due to other devices on the network. A suitable non-destructive test is to turn off all other network devices and reboot the router and then reboot the PC. If the error is fixed then the issue is of this type.
Many thanks for this, I’ve been struggling with this issue for a little while and tried all the usual tactics. Just now I turned off all our other wifi devices, rebooted the router and the errant PC and hey presto the wifi connection came back on! Fingers crossed for the future.
I had this problem with a clean install of Windows 10 after updating and then installing Sophos AV and Sophos Client Firewall. Uninstalling just the Client Firewall solved it.
I do not have any problems with the Client Firewall on another Windows 10 PC that I had upgraded from Windows 7.
Thank you for the update. Unless you have a good reason to like the Sophos products you may wish to uninstall them. I run a network of over 1000 PC in a school and find that Windows Defender does the job fine and it costs nothing. It gives me one less thing to worry about.
Thanks. I completely uninstalled Sophos from the PC, and haven’t seen any more network problems. I’ll use Windows Defender from now on.
I have followed your blog on this issue to a T. I have tried every single thing you have described, in order…..still nothing.
Any new updates on this issue? I’m running win 10, version 1511 on a Dell xps 8700. I don’t have access to a wired connection, WiFi only. I have a HP G7 laptop running the same version of windows 10 with no issues….
If you have done the SFC and DISM checks then you can be confident that your OS is OK. I think the issue is that Windows 10 is wrongly disabling the adapter after a network issue. If you have an anti-virus product you may wish to remove it and use Windows Defender (see other comments). The next place to look is your Wireless hub. Login and check the firmware is upto date and the log file contains no errors. If all looks good then turn it off, wait one minute and then turn it on again. If it is an old or cheap one you may wish to replace it with a high quality one.
Wireless is not really a good networking solution for production use so you may wish to invest in a USB Ethernet dongle or Pluggable Hub (say) and a cable as a backup. If you can’t reach the router then you can use a powerline adapter (Ethernet over power). At work I run 1000 wired computers with little trouble, it’s the wireless that cause grief. At home each person’s main computer has a wired connection, either direct, or through powerline and or a USB to Ethernet hub.
Good morning everyone,
Another solution for those still experiencing this problem. My network of 5 machines, Win7 and Win 10 mixed, started suffering this problem. One of the Win10 machines acts as a server. Two days ago the other two Win10 machines could not see the Win10 server. The client error was precisely as described.
I focused on fixing the client machines. None of these solutions worked. Curiously, the Win10 clients could see a share on the Win7 machines.
After a good nights sleep, it occurred to me I should check settings on Win10 server. That’s where my problem was. This cleared it up:
1. Settings > Network & Internet
2. Ethernet or Wi-Fi > Related Settings > Change advanced sharing options
3. Scroll to ALL NETWORKS > I changed from 128 to 40-50-bit encryption and turned off password protected sharing.
In my case, password protected sharing does not help me, so I don’t enable it. For reasons I have yet to discover, it had been enabled.
I favor the password protection theory as fault. The decision on my part to change encryption type was diagnostic impulsiveness. Win10 machines should be able to see each other’s 128-bit encryption connections.
Cheers!
Thanks for all your helpful suggestions. Unfortunately not a single one is working for me. And this just started after Windows update this last Tuesday. Looks like a full re-install is in order. Pretty disappointing if you ask me.
Make sure you have carefully inspected the physical parts of the network and your router (see other comments) first.
What symptom do you have besides the one being discussed here? I think that these are mostly red herrings but it seems difficult to get people to start thinking of that possibility. They seem to believe the troubleshooter more than the facts that they could find on their own!
C.f.
http://answers.microsoft.com/en-us/windows/forum/windows_10-networking/windows-10-missing-one-or-more-network-protocols/6f57c0f8-2968-4a8a-a59a-255e87e1d6c7?page=4#LastReply
What are you trying to say Robert? That people should ignore what the troubleshooter is telling them? Based on what? And then they should go on a random search for “facts they could find on their own”?
I think that what Robert is saying (although perhaps not as clearly as he might wish) is that this error can have multiple root causes. The thread he links to addresses some of these but this article remains the best resource on the web at the moment.
I would say that the Microsoft trouble shooter doesn’t address the possibility of a hardware/network fault. So it is possible to make changes/fixes as recommended that do not address the problem and may compound it.
Yes. Exactly
All else fails, a system restore did the trick for me 🙂
I also am experiencing this missing protocol issue of Win 10 after I upgraded to Win 10.
I do have internet access to some sites but not to others. Very strange. For example, I cannot access my Dropbox (https://www.dropbox.com) or my UBS e-banking site but can access some news sites.
I tried all the suggestions in the video but none worked. As someone above mentioned, I enabled the permissions but after the reboot, they were disabled again.
I also had around 6 entries in the Regex, not one, and I changed the permissioons to all the ones that had folder 26.
Tried also rebooting the router and the laptop, which did not help.
So, I am now at a point where I do not know what to do anymore.
Any help is appreciated.
This sounds like a anti-virus or firewall problem. Uninstall any 3rd party products and re-test. If you don’t have any 3rd party products then turn-off Windows firewall and re-test. If none of these work consider re-setting your PC and choosing the keep your files option. http://windows.microsoft.com/en-us/windows-10/windows-10-recovery-options#. Before doing that you may wish to consider if elements of my backup strategy apply to you. https://blog.jamesbayley.com/2016/01/03/the-definative-guide-to-backing-up-your-home-computer/
Hi James – I’m experiencing this issue on a WIn10 machine – IE11 & Edge show the error, but I can connect to the internet with Chrome & Firefox (unfortunately I have to use IE11 to connect to work). I’ve tried the fixes you’ve suggested but with no luck. I don’t suppose you have any more suggestions do you (I did notice a new win update go through last night on my machine & I believe this is the cause).
Thanks
This is bad, we don’t expect Edge to work reliably but IE11 should be rock solid. Can you please verify and confirm that don’t have any non-Microsoft anti-virus or firewalls installed?
Hi – I use the paid-for version of AVG – but only the standard MS Firewall. However, I’m assuming as Chrome & FF can get out through it then that’s configured correctly. The machine is pretty stripped down as I use it to connect to work & therefore *need* it to work. So that’s worked well… 🙂
I manage over 1000 PCs. Third party anti-virus is nothing but trouble and a waste of money unless you have truly exceptional security needs and really know what you are doing (which I don’t). This is particularly true with Windows 10, Microsoft has enough difficulty making it work at all without having to worry about AVG.
I think that there is a good chance that AVG corrupted an update. IE 11 is part of the OS so this fits my theory.
Your test for resolution is IE 11 should work perfectly. Your may wish to inspect the event logs. You might get lucky. Good luck
OK, thanks
Thank you for all the help that you have given to other people. I also have the same problem (one or more internet protocols are missing). I am using windows 10 with defender, malwarebytes antimalware and malwarebytes antiexploit.
I enabled the permission to 26 but it but after reboot, it changed back. Already reset pc, no success. Could you please suggest what i should do? Thanks in advance.
Nick,
I suggest that you remove all network defence products including Malwarebytes and then try again following the procedure from the top of the page down. Good luck.
James
Thank you very much, this fixed my problem. How Microsoft can insist that we install windows 10 them leave the computer unable to connect to the Internet to solve the problem is beyond me. How can they continue to be successful when they make such obviously avoidable mistakes?! Somebody needs to make a better operating system. Thanks again!
I have been having this error msg. for ages now. I did not have the issue until after upgrading from Windows 7 to Windows 10. The computer I am having the issue with is approx. 1 year old. I get the error msg. whether I am using WiFi or Ethernet. My son (who is a whiz with computers… has a BSc in Computer Sciences from FSU) and I have tried every “fix” we have come across with no luck. I did a complete re-install of 10 a couple of weeks ago…. no difference. I have no third party firewalls or anti-virus software installed. It happens very randomly… sometimes every few minutes, sometimes not for hours or even a day…. it is very aggravating when I am trying to do research for classes I am taking!!
I suggest that you run SFC again. If this comes back clean then it is likely that your computer is OK. If it is OK that means that the problem may be with your router. Verify that the firmware is up to date. If it is more than 4 years old (say) you may wish to replace it.
My setup
CABLE MODEM —->> POWERLINE ETHERNET —>> GIGABIT SWITCH –>> PC
This is a disgraceful bug in Windows 10 – that is causing thousands of hours of heartache for many users. I had tried the following
– Winsock reset
– Replacing Winsock registry entries with those from a working Windows 10 install
– All the tips in the above video
What seemed to help was running SFC /SCANNOW in an admin command line window – this replaced the error with an error around “IP Configuration not being valid”
I think completely uninstalled my NIC card, including the driver…and restarted the PC
This fixed the error – after hours of troubleshooting. From reading Google, it appears Windows 10 doesn’t play well with Powerline Ethernet either…..which is unacceptable because it is a popular way to extend networks.
Microsoft should be ashamed of themselves that this bug is still live for so long….
Thank you for these detailed methods of troubleshooting.
I have tried many times to solve this issue in the last 12 hours and the problem I was having that gave me the protocol issue was just the dns.
My solution: change your adapter settings to use automatically assigned dns instead of manually. ( This is automatic by default but you may have changed it or a program could have done it)
Thank you for this feedback. I have updated the post accordingly.
Well the best solution that worked for me was to go to device manager and uninstall all the network drivers. Then restart the computer. Windows will itself install the required drivers.
Works just fine for me.
In the end I went back to the last working restore point and rolled forward, all working now.
Thank you for this hint. I have updated the post to include this suggestion.
Hi. I had this problem after the last Windows update. Tried most of the fixes suggested here and elsewhere to no avail. The solution I found is probably not for the purists but it worked – Instantly! I bought a PCIE Ethernet card from Maplins and installed it. Didn’t even need to install from the driver disc – system came up straight away. A USB wireless dongle would probably work as well. Cheers
I followed your video. My steps went correctly,but after rebooting,I’m still getting missing protocol error!!!!
If anybody else is having this complete JOKE of a problem and NOTHING seems to help, I may be able to. Last night I spent roughly 3 hours going through every last fix on the internet for this problem and trying each one until I finally found one that worked. The thing is that it took quite extensive research because I have not seen anyone mention in the various community help forums about this program.
This program called WinsockReset did the trick for me. It basically overwrites the winsock registry files with fresh ones that would come from installing a clean copy of whatever Windows version you are using.
You can download this program here: http://www.majorgeeks.com/files/details/winsockreset.html
I had to download the .exe on my Kindle and then USB it over to my “network-protocol-less” computer. Thank God it worked. I need my internet.
Thank you for this helpful advice. It looks like it is an automation of my instructions in “Registry Winsock Keys Fix” and could be very useful to other readers.
Thank you so much it worked for me. Great job!
Thanks a lot for the guide. There are tools you can download (be wary and skeptical), then there’s the “netcfg -d” command in command prompt that can fix the issue for you. You can also tweak your NetBIOS and Firewall or Antivirus to get it to work.
Here: http://errorcodespro.com/fix-one-more-network-protocols-missing-windows-computer/ I found this helpful guide you can check out..
Thank you for this tutorial help me. After deleting Windows Sockets Registry, i facing the error “This program is blocked by group policy”
Lienvietlog,
I assume that you have verified that your router and cables are sound.
I have not had this problem with any recent builds of Windows 10 and I believe that the original issue was fixed by a Microsoft patch. Therefore I suspect that you have a corrupt operating system.
First – remove any third party antivirus and firewalls. You should never use these with Windows 10 and reboot twice.
Second – run SFC /scannow
If this does not fix the issue then you may wish to consider reinstalling the operating system. This is a standard fix in Windows 10. You may need to read my article on PC backup and reconfigure your computer first.
https://blog.jamesbayley.com/2016/01/03/the-definative-guide-to-backing-up-your-home-computer/