#Limited internet access windows 10 drivers#
#Limited internet access windows 10 driver#

So while I was trying to get hold of a non-realtek NIC to try, which I found, I had to shut down my machine. This problem has come about before with Windows 7, but very rarely, and the fix was resetting the network stack.Д¬an anyone share any insight? I unloaded our Kaspersky endpoint protection to rule that out, I can't see it being our perimeter firewall (SonicWALL) as why only with the realtek driver? I am trying to track down an ethernet adapter that isn't a realtek to try, but until then, I wanted to put this out there to see what anybody else could tell me.

#Limited internet access windows 10 driver#

You get issues with power management on the default driver too, as you can't disable power management on the NIC until you run a proper realtek/HP driver. We could leave the driver alone I suppose, but I can't imagine this is sensible. As soon as you roll back to that 2015 driver, you're good.

#Limited internet access windows 10 drivers#

But as soon as you update the NIC drivers from HP (note, 3 different versions across multiple different machines is more than enough troubleshooting to rule out a specific driver surely) but once it happens, it doesn't seem to go away until you apply the workaround - and that is, uninstall the driver, and go back to the default microsoft driver from (I assume) when Windows 10 first shipped. It doesn't happen right away, as the default driver is an MS driver from 2015. This happens whether from an image, or from the HP build. But not only annoying, it stops O365 products, they report no connection so are not available properly. The (wired, we don't have wifi internally to test) network connection shows a yellow exclamation mark with 'no internet access' next to it.

The fact is, they are all HP Prodesk/Probook machines, and all seem to use Realtek network adapters. Some machines develop the error at some point soon after rolling them out, there is seemingly no solid pattern, but it's happened to nearly all of them. Since moving to Windows 10 Pro (straight to 1709), we've had this on nearly all our machines.