Windows 10: Network Protocols Solved

Page 5 of 27 FirstFirst ... 3456715 ... LastLast

  1. Posts : 181
    Windows 10 Pro x64
       23 Dec 2015 #41

    tomko44 said: View Post
    After spending a day trying to fix the problem caused by rev 1511 I just did a roll back to the previous version. It took ten minutes and all is well, just not using version 1511.
    This is NOT recommended under any circumstances

    You've now exposed your PC to exploits that were patched, not to mention since 1511 is such a major update, many Windows Updates after it's release will have 1511 as a prerequisite.

    I'm also quite baffled as to what you were hoping to accomplish by uninstalling 1511... this specific network protocols error doesn't actually affect a PC in a critical manner, nor does it result in an inability to utilize networking features... not to mention a workaround for network connectivity was posted a few posts back
      My ComputerSystem Spec

  2.    23 Dec 2015 #42

    JW0914 said: View Post
    This is NOT recommended under any circumstances

    You've now exposed your PC to exploits that were patched, not to mention since 1511 is such a major update, many Windows Updates after it's release will have 1511 as a prerequisite.

    I'm also quite baffled as to what you were hoping to accomplish by uninstalling 1511... this specific network protocols error doesn't actually affect a PC in a critical manner, nor does it result in an inability to utilize networking features... not to mention a workaround for network connectivity was posted a few posts back
    Let's see.... a total inability to connect to the internet is NOT CRITICAL? The inability to shutdown the PC without holding down the power button also not critical? I tried every single suggestion posted on multiple sites and none worked. What, am I supposed to do nothing with my PC until MS figures out a fix to their problems?
      My ComputerSystem Spec


  3. Posts : 181
    Windows 10 Pro x64
       23 Dec 2015 #43

    tomko44 said: View Post
    Let's see.... a total inability to connect to the internet is NOT CRITICAL? The inability to shutdown the PC without holding down the power button also not critical? I tried every single suggestion posted on multiple sites and none worked. What, am I supposed to do nothing with my PC until MS figures out a fix to their problems?
    "...a total inability to connect to the internet"
    • Not caused by 1511, nor do your problems have anything to do with this specific thread it seems...

    "...inability to shutdown the PC without holding down the power button"
    • Also not caused by 1511

    "...tried every single suggestion posted on multiple sites and none worked"
    • Did you review the event logs?

    I'm going to assume you probably didn't clean install Windows 10 after you upgraded, of which would have entailed following the proper clean install procedure, which is at the core of your problems. I'm not going to explain why, as I've done so repeatedly on at least 5 different forums and countless threads. If you wish to understand why, please view my profile and review prior posts of mine.

    Review
    Last edited by JW0914; 23 Dec 2015 at 13:30.
      My ComputerSystem Spec


  4. Posts : 3
    Windows 10 Pro x64
       24 Dec 2015 #44

    JW0914 said: View Post
    "...a total inability to connect to the internet"
    • Not caused by 1511, nor do your problems have anything to do with this specific thread it seems...

    "...inability to shutdown the PC without holding down the power button"
    • Also not caused by 1511

    "...tried every single suggestion posted on multiple sites and none worked"
    • Did you review the event logs?

    I'm going to assume you probably didn't clean install Windows 10 after you upgraded, of which would have entailed following the proper clean install procedure, which is at the core of your problems. I'm not going to explain why, as I've done so repeatedly on at least 5 different forums and countless threads. If you wish to understand why, please view my profile and review prior posts of mine.

    Review
    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.
      My ComputerSystem Spec


  5. Posts : 181
    Windows 10 Pro x64
       24 Dec 2015 #45

    inesvieira said: View Post
    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.
      My ComputerSystem Spec


  6. Posts : 3
    Windows 10 Pro x64
       24 Dec 2015 #46

    JW0914 said: View Post
    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.
      My ComputerSystem Spec


  7. Posts : 181
    Windows 10 Pro x64
       24 Dec 2015 #47

    inesvieira said: View Post
    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?
      My ComputerSystem Spec


  8. Posts : 3
    Windows 10 Pro x64
       24 Dec 2015 #48

    JW0914 said: View Post
    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.
    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.
      My ComputerSystem Spec

  9.    24 Dec 2015 #49

    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.
      My ComputerSystem Spec


  10. Posts : 181
    Windows 10 Pro x64
       24 Dec 2015 #50

    inesvieira said: View Post
    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.
    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.

    inesvieira said: View Post
    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!
    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.

    inesvieira said: View Post
    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?
    Yeah, it is your obligation... it's your PC isn't it?

    inesvieira said: View Post
    Do you understand that most users do not even know how to install windows?
    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.

    inesvieira said: View Post
    So no, pal. If something that was working fine just stopped working = bug. And bugs are not users fault.
    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.
    Last edited by JW0914; 24 Dec 2015 at 16:30.
      My ComputerSystem Spec


 
Page 5 of 27 FirstFirst ... 3456715 ... LastLast

Related Threads
EDIT: Solved! The second error message I found (about missing ordinal #581 in ieframe.dll) was the clue I needed. The problem happened because I had IE Dev Preview installed. It's an App-V package and it can be easily uninstalled by running these...
28883 My pc wifi 2 adapter network no screnn :(
Hi, I understand the new media player in Windows 10 will cast to a media center such as an Nexus Player or Amazon Fire TV, much like Airplay, but will access local media. Is this a Google Cast (Chrome cast), Miracast, DNLA or some other...
I can no longer see my Network Attached Storage in this build(10049) Enterprise. I have Network Discovery enabled and can get to the device by IP Address in a browser but am unable to map a drive to any share. Anyone else having these issues. I have...
Hi there It seems that for earlier computers such as XP / W7 or even Linux machines connecting TO a W10 machine causes problems unless you connect via an IP address. Even if you apply the "Fix automatically" it still doesn't work and if you...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 14:02.
Find Us