Windows 10: Yet another "One or more network protocols are missing"

I'm running Win 10 and had a power outage/hard shutdown. On restarting, the network connection was broken.
I'm running on hardwire with a Realtek PCIe GBE Family Controller.
I've been troubleshooting this for days now, so it's hard to recall where I've started, but here's a rundown of everything I've tried.
Tried Network Troubleshooter, including letting it run as admin.
Tried deleting winsock and winsock2 from registry, and reloading protocols from c:\windows\inf.
Tried exporting winsock and winsock2 from a working computer to the broken one.
Tried reloading the adapter drivers.
Tried netsh winsock reset
Tried netsh int ip reset
I've gotten by all the permission issues (group policy, reset fails, etc).
Somewhere along the line, I got the BSOD with machine exception, so I ended up loading my Win 10 disk and doing a "reset". Even though it looks like it did a full install, evidently it only reloading keyfiles, as the network error still exists. After the reset, I'm running OS buld 10586.0.
With no application installed after the reset, no anti-virus software is running, so I know the error is not coming from interference with that.
Right now, I'm getting "One or more network protocols are missing on the computer" / "Windows Sockets registry entries required for network connectivity are missing."
It may be I'm simply not runnning the above "fixes" in the right order? I suspect there are some missing/corrupted files that the Windows reset doesn't fix.
I hope to avoid having to reload Win 10 for what will be the 4th time (Win 10 is not exactly a rock), but I'm running out of leads.
Any new ideas? Thanks in advance.

:)

 

Network Protocols are missing ,one or more network protocols are missing from this computer" error message.

I have the same problem, and tried what you listed on original post too. Been trying to fix this for over a months now, but no help at all. Windows 10 seems to be badly broken in the networking department. Very frustrated

 

Network Protocols are missing ,one or more network protocols are missing from this computer" error message.

Hello Khoin,

Thank you for your response.

Generally, the issues related to Windows on standalone personal computers or laptops with the basic queries regarding internet connection, no boot, installation and activation of retail versions and other simpler issue are answered in this forum, while
the issues related to servers, governed by group policies and other complex IT issues are mostly answered in the TechNet forums.

TechNet is looked at by amongst the best, Microsoft and other IT professionals in the world. You just need to re-post this question
in that forum. To make it more comprehensive and help the IT professionals, you ought to provide the exact error codes/messages (if any). Also, provide them the configuration details of your system and any significant changes that you made prior to this
issue.

I hope you get the issue resolved soon.

In addition to that, please feel free to post on this forum for any other of your issues with Windows on standalone systems in future. We'll be glad to assist you.

 

I have pretty much the same exact problem... I'm also hardwired to the router not WiFi.. This is frustrating would love some help with this. I'll let you know if I find anything out.

 

Try netsh int ipv4 install from elevated command prompt, that just worked for me today.

 

When I check the Ethernet properties (Realtek PCIe Family Controller) I see that Internet Protocol 6 (TCP/IPv6) and Internet Protocol 4 (TCP/IPv4) are already checked. Nonetheless, I try.
Type in "netsh int ipv4 install".
It says "Restart the computer to complete the action."
After restart, alas, no change.

 

I tried some more things last night. Things are mutating, but still broken.


I uninstalled and reinstalled the controller:
Bring up Device Manager.
Expand Network Adapters.
Right-click on "Realtek PCIe GBER Family Controller, then choose Uninstall.
Click on "Action" in Device Manager menu bar, choose "Scan for hardware changes".
The adapter got repopulated in the listing.
System restarted.
No joy.


I imported winsock.reg and winsock2.reg from Tech Grounds - How to restore Winsock/Winsock2.
After reset, my error message has changed. Now I've got:
"Ethernet" doesn't have a valid IP configuration.


I installed the latest device driver from Realtek - 0007-Install_Win10_10007_02192016.zip


I tried some ipconfig commands:
ipconfig /reset - Failed as there was no address to release.
ipconfig /renew - An error occurred while renewing interface Ethernet : unable to contact your DHCP server. Request has times out.

 

None of the answers above work for me.

Reboot a few times and it fixes itself.

I honestly think a bit of time and a reboot fixes it. Running ipconfig or netsh doesn't. You can reboot your router but that doesn't help either.

There is a bug here that didn't exist in the past but there we are. My Wife and I both use MBP. Her internet drops all the time, mine doesn't. A few reboots and she is OK again.

 

I've taken the cable from the back of my desktop and plugged it into my laptop. Good connection, so I now know (not that I ever doubted it) that it's not my router. So...I've turned off the desktop and unplugged it (that has worked for previous problems). Gonna let it sit for a while, then do multiple reboots. In the meantime, I think I'm going to need to warm up the Win 10 disk. I think I'm going to need it...

 

My experience is a clean install is to no avail.

I have a 3 year old laptop that runs fine with Ethernet, but limited connectivity with WiFi. Been thru all the drills described in the forum.

 

After all was said and done (that being a total reload of Win 10 and problem persisting), I think the issue is what I least expected - a fried network controller on the motherboard. I had an old PCI network card laying around. I installed in - using a Win 7 driver - and voila! the connection came back. So I will call this one done.

 

... and not a Windows issue.

Sorry about your hardware issue but glad it wasn't Window's fault.