Network Protocols

Problem trying to connect to internet on laptop, but all working as normal on desktop.

Investigations revealed....one or more Network Protocols are missing on this computer, also Windows sockets registry entries required for network connectivity are missing....this on both Ethernet and wireless but they had been working perfectly since the update last week.

My laptop supposedly required "Internet connections Package Version 3.0 Publisher Microsoft Windows."

After messing about for an hour without success I loaded the 1511.. ISO.. knowing that I could not connect to the internet to download anything, this seemed to solve the problem, (fingers crossed) I can only assume this made the internet connection possible.

Windows troubleshooter said that I have "Missing Socket Level Protocols". Had to restart the PC and wait a few minutes just to type this message. Another day of Windows-10 error investigation begins.

AllenChicago said:

Windows troubleshooter said that I have "Missing Socket Level Protocols". Had to restart the PC and wait a few minutes just to type this message. Another day of Windows-10 error investigation begins.

Do try my above suggestion by inserting your ISO, I think it corrected the "Protocols" when it states setting up a few things.

You can also try running the command

sfc /scannow

in Run. Press Win+R to load a Run dialog.

I had this error on all three of my network computers after upgrading to 1511. Unable to share files between network computers. Intenet connection okay. Finally found it was my Kaspersky Internet Security 2016. I termporaraly disabled Kaspersky and that fixed the problem. I had to do it on all 3 of my upgraded computers. Also looked at my network connections in Kaspersky firewall and changed my private network, there, from publc to private. Windows was already set to private as well.

So for me, it wasn't the Windows 10 upgrade. It was something that changed with Kaspersky during upgrades.

I clean installed Windows 10 with the recently released ISO on a laptop. Everything was working fine before I gave it back to my friend. They called me the next day and said they couldn't get on the Internet and getting the missing protocols error as well.

Brought the laptop home, performed an In place upgrade using the same ISO and everything is fine. They've had it back for a few days and no complaints. They didn't install or change anything, so I have no idea what happened. Just one of those wtf moments with Windows 10.

Windows 10 is like a box of chocolates. You never know what you're going to get. -FG.

That's why it is recommended to fully disable (not until next startup) or even uninstall the antivirus before upgrading. To avoid such issues.

There was no AV present at the time of install.

spapakons said:

That's why it is recommended to fully disable (not until next startup) or even uninstall the antivirus before upgrading. To avoid such issues.

It's not due to antivirus or internet security products... This is a bug that popped up prior to RTM and appears to be back again. Anyone experiencing the issue is recommended to file a bug report with Microsoft.

In regards to internet security products and Windows 10 installs... if upgrading from a prior OS version, they should be installed, however once on Windows 10, it's not necessary to disable/uninstall them prior to doing a repair install or upgrading/downgrading to/from the insider builds. If you have the opportunity, it wouldn't hurt, however it appears Microsoft has changed how the Windows 10 installer works when running within Windows 10 that bypasses the need to disable/uninstall IS software.

• While I know of no documentation to support this hypothesis, the following seems to indicate this:
  
  • Moving to or from the Insider Builds requires a reinstall of Windows, all done automatically on the backend and processes similar to a repair install
  • Insider build upgrades must reinstall the OS upon every major revision, performed automatically and without user notification
  • Once revisions from the Insider Builds are pushed to the public [users not on Insider Builds], users on an Insider Build are upgraded to the release via a Windows install and removed from the insider build until a new Insider Build is released, performed automatically and without user notification, and these 3 steps repeat.

My problem is not the same as OP since I can connect to internet just fine, but since it's related to Treshold 2 update and networking I'll post this here anyway.

My problem after the update was connecting to computers on my network from network browser. I would get this error:



Trying to diagnose the problem I get this:



Further details show this:



Trying to fix it does not work.

Again, no such problems before the 1511 update. I first noticed, the problem only manifested itself if I used a static IP on my computer. Switching back, to obtain IP automatically, fixes it.

Upon further investigation it seems this bug is related to NetBIOS over TCP/IP. If it's disabled, problem disappears. It seems it's enabled by deafault when using static IP.



I also disabled LMHOSTS lookup but I don't think it's related to this. Hope this helps somebody.