Windows 10: Network Protocols

I did a clean install, a reset and tried everything said on this thread and still got the problem, untill i got tired and just installed a previous version: everything now is fine.

So yes, the problem is the update.

 

So you followed the proper clean install procedure of installing nothing, including Windows Updates, prior to installing drivers, and you installed those drivers in the proper order with Chipset being first?

• If so, did you ensure you were disconnected from the internet prior to and during driver installs (as Windows update will attempt to install updates almost immediately following an OS install)
  • If so, did you ensure you were using updated drivers from the component manufacturers and not from the OEM's support site?
  • Did you also ensure every driver install, except CPU related drivers [Chipset, IMEI, thermal mgmt. etc.], was a Windows 10 version
• Do you have a Broadcom/Dell wireless card installed? If so, their Windows 10 drivers contain Windows 8 system and dll files and the card needs to be disabled, and all drivers for it removed.

Your perspective is fundamentally flawed... if, as you believe, 1511 caused this, millions of other computers, from consumer devices to corporate workstations, would be experiencing the same issue, and they [nor I] are not. Your issue is environment related and Windows 10 is not the cause.

Since this thread doesn't cover a single issue you're having, I would recommend creating a thread and doing some troubleshooting. Just so you're aware... every time a Windows update is release that patches exploitable code, it also points directly to how to take advantage of that exploit on devices that haven't been patched... in other words, if you uninstall 1511, or any update that patches exploitable code, your device is a walking time bomb and you're playing the equivalent of PC russian roulette.

 

1 - I did a clean install using 1511 ISO from MS.
2 - Yes, i was disconnected.
3 - Yes, lastets drivers from manufacturers, especially the latest LAN driver.
4 - No.

And yes, a lot of people are having the same "protocols" problem, just google it and you will see. Tenforums already have similar threads.

 

I didn't say others were not, I said if the problem was being caused by Windows, millions of users would be affected, consumer and corporate alike, of which is not the case.

90% of all end user issues experienced on Windows 10 are due to either the user not clean installing and following the proper clean install procedure, the end user installing drivers that are either not compatible with Windows 10 or of which the developers screwed up and incorporated Windows 8 sys and dll files into, end users installing software with deep hooks that isn't compatible, or something within the end user's environment.

Simply put, if 1511 was the cause of yours and others' issues, it would mean Windows 10 and the 1511 update were the underlying cause. If this were true, then, by default, all devices, not some, but all, would have the same problems, which is obviously not the case... therefor, the only other explanation is the end user's environment.

You obviously haven't looked at your event log, nor does it appear you've made any attempts to do in depth troubleshooting. In what order did you install your drivers (specifically were the first 2 installed in this order: CPU Chipset, then CPU IMEI) and did you reboot the PC following each install?

What exact problem(s) are you having?

 

Since 12/19 i got the problem, tried a lot of things already said in a lot of other threads and the problem continued.

So i gave up, even in MS forums they do not have a solution, so i just sent a bug report to them and installed Win 10 again using an old version ISO and kept myself away from the updates.

You can't say that we cannot blame Microsoft when something was working fine and suddenly doesn't work after an update. And when a lot of users are complaining about the same protocol problem.

Also, it doesn't make sense that the common user gonna have to clean install Windows/do these driver install steps everytime when a problem shows up, do you think that every Windows user have time to read forums about it or even know how to do it? If an update messes up with a common user computer, it is not his problem!

Do you really think that we (Windows users) have the obligation to know that something can go wrong with Winsock/whatever the problem this is out of nowhere ('cause everything was perfect fine), that we must have Win 10 ISO avaliable to clean install it whenever something goes wrong when this something was working fine and that we must know how to type commands, edit the register or even search trough days in the internet about the problem?

Do you understand that most users do not even know how to install windows?

So no, pal. If something that was working fine just stopped working = bug. And bugs are not users fault.

 

I just wanted to post a reply. Google sent me here when I typed in that network protocol error.

I figured out a way to fix it, not sure if it will work for everyone but this is what I did.

Right click your network adapter, hit properties, highlight the TCP/IP V4 and go to properties. After receiving this error, my settings were on "Use the following IP address" and "Use the following DNS server". It was manually pointing me to 192.168.1.7 for my router. I set both of these "Obtain automatically" and clicked OK. Internet came right back on.

Hope this helps someone. Also, my router address is 192.168.1.3... so maybe windows was pointing me to the incorrect router address? I'm not sure.

 

This is another fundamental misunderstanding or misconception too many users seem to have, mainly because these specific end users have never had to do a clean install as they've relied on the OEM, tech support companies, or friends to do everything for them. While I understand most aren't power users, this specific subset of users needs to have some personal responsibility for failing to educate themselves about what the proper way to install an OS is and why it must be done the way I, and others, have repeatedly stated. It's to the point where I've come to the realization of what's the point of helping users, like yourself, when this specific subset of users doesn't get an OS install is not plug and play. If users wish to maintain that point of view, there are companies they can pay to have them do this for them.

Where are you getting the information that you need to clean install every time an issue arises?

A clean install is required when upgrading an OS, and failure to do so, in combination with the proper clean install procedure, will cause, with 100% certainty, wonkiness at some point, resulting in more time spent troubleshooting than it would have taken to do a proper clean install in the first place. In other words, you're simply making your life harder as a user by not performing one and doing it correctly.

More than 90% of the 90% with issues, failed to perform a clean install and instead ran with their upgrade. Windows 10 may look, from a GUI standpoint, a more polished 8.1, however it's coding is extremely different. Windows 8 drivers, sys files, and dlls for critical components (i.e. anything attached to the motherboard) are not compatible with Windows 10, and more importantly will cause serious OS issues and BSODs. A substantial amount of drivers, sys files, and dlls for Windows 7/8/8.1 are copied over to the Windows 10 Windows directory during an upgrade... this is why a clean install is necessary. If you wish to understand more, please see my previous posts or use google.

Yeah, it is your obligation... it's your PC isn't it?

Then this specific subset of users should either educate themselves with how to do so or be willing to pay for a third party tech support company to do it for them... ignorance on this issue is not an excuse and end users have no one to blame but themselves. Installing an OS, and doing it properly, is extremely easy and simple, with thousands of posts on forums, as well as from OEMs, detailing exactly how to do it properly. Amazing how a user can find a way to complain in a post on a forum, but can't seem to manage using google.

Yet again, you have a serious lack of knowledge which has caused numerous fundamental flaws in your perspective.

I would encourage you to research what an OS actually is, what drivers actually do, and learn why it is you're able to type on a keyboard, move a mouse, hear a sound on the PC, or see video on your screen.... as none of those are due to the OS, but due to drivers. Drivers are what allows the OS and hardware, from your CPU to your mouse, to interface [communicate] with an OS.

Drivers are not the responsibility of Microsoft to develop, but the responsibility of the component manufacturers. It is also not Microsoft's job, nor responsibility, to ensure component manufacturers' drivers interface properly with Windows 10... that is the responsibility of the individual component manufacturers.
Please do some research on your end to understand the fundamental flaws in your perspectives.

 

Thank you for trying to be helpful, however that's simply end user error... no update would result in DHCP being turned off since Windows' default is DHCP enabled. A user of that device would have had to disable DHCP for it to be disabled and set to manual.

 

Let's not make things complicated. A clean-install is necessary only when the current OS is already a mess by installing and uninstalling stuff. If it is OK, you shouldn't need to clean-install. An update of the drivers should be enough.

However it is a known annoying behavior of Windows 10 to replace all drivers after each version upgrade with Microsoft generic drivers and there is where all the problems arise. To make the computer working properly again, unfortunately, the user must reinstall all the drivers starting from the chipset driver.

This issue was never appeared in Windows 8 and earlier since it was ALWAYS keeping the currently working drivers and only in very rare cases replaced older drivers through Windows Update. So yes, it is a Windows 10 issue. But the solution is simple for the 99% of the cases (there are exceptions). Just update all your drivers starting from the chipset after each version upgrade and you should be OK.

Another annoying issue is that all security settings in Internet Explorer and elsewhere are reset to default and you have to redo your custom changes. As long as you keep an eye and correct things, you should have no problem with Windows 10.

Important: If anyone has used the show/hide tool to disable some unwanted driver updates he should use it from time to time to block any newer driver updates and avoid any BSOD. I suggest to use it before each manual search for updates just to be on the safe side.

 

Any idea on why drivers would be replaced only within select environments? I've re-deployed Win 10 to my Alienware 18 three times [not due to Windows 10 or an update] at this point, as well as flip flopped between insider and public builds, with my drivers never being replaced with generic ones by Windows. I do know Dell doesn't provide a Win 10 driver for the freefall sensor, of which Windows Update was able to pull and install a compatible Win 10 driver.

Were any of the users experiencing this able to verify whether they had installed Win 10 drivers prior? Windows 7/8/8.1 drivers are copied over to the new Windows directory during a Win 10 upgrade, with Windows not always replacing those previous drivers with Windows 10 versions.

• Since it's inefficient to track down the oemxx.inf name for each driver copied over, it's far less time consuming to simply do a clean install, also providing the opportunity for the end user to guarantee they're starting from a base install with no issues (at which point a WIM should be taken once drivers are installed in the proper order and Windows updates applied).

It would make sense Windows 10 would replace those specific drivers with generic ones, especially if they're system critical drivers. This seems to be the only plausible explanation, at least that I can see, going back to the fact it's environment related and not due to Windows 10, or Windows 10 updates, per se.

 

I never touched my settings. Found them that way. Potentially because I have VPN software running. Maybe it alters it? Not sure.

 

VPNs have their own virtual interface which is created by Windows if IPSec or the client app if an SSL VPN. Does anyone have access to your device, as in order for DHCP to be disabled, it must be done by a user, local or remote.

 

No sir, personal computer! I had internet the night before. Shut it down. Turned it on today, just decided not to work.

Second or third time its happened actually. I formatted the other two times, glad I figured out the cause this time.

I wish I could tell ya. I don't know how it changed, or why. My VPN software installs its own network device (TAP driver?). I also have Team viewer running but I don't think that'd do anything.

Can't say I know too much about the subject.

I occasionally have problems on my other win 10 laptop where the internet stops working, when I run Windows troubleshooter it resets the dhcp itself and it works.

 

Something you're doing on the PC is causing DHCP to be disabled... You should be able to narrow down exactly what you're doing to cause it by configuring an event to log the change in event viewer. TAP interfaces are virtual interfaces, installed when you utilize an SSL VPN.

 

Interesting. I'll have to take a look.