No net access after Win 10 ISO file upgrade

Hello,

So I very finally managed to upgrade to Win 10 without any issues, yet in choosing to do updates later, I now find myself with the net driver not working (and a couple of other issues). So there was that yellow triangle over the net icon, and after troubleshooting it stated that 'there might be a problem with the driver for the Local Area Connection adapter.' I got the latest RealTek driver for Win 10 64-bit, updated, and same issue.

First with this: Download Realtek PCIe GBE Family Controller LAN Driver 10.1.505.2015 for Windows 10 64 bit

Then with this: Download Realtek PCIe GBE Family Controller LAN Driver 10.7.107.2016 for Windows 10 64 bit

Poking around Device Manager, on RealTek's properties, it says the device is working properly (and indeed it was before the update as well) but in the 'events' tab it says (after a long string of characters) that 'Device PCI ... requires further installation'. What does this mean? And how can I fix the LAC adapter driver problem? Thanks.

Stop downloading drivers from questionable websites. The Realtek drivers should have loaded when Windows 10 was installed. If not, you need to go to Realtek and download the driver for your Ethernet chipset from there. As for an update. There really is not much change between the one that Windows 10 installs vs. the Realtek one.

Didn't work...

I uninstalled then reinstalled the Realtek driver from the RealTek website which had the same yellow exclamation mark result, but when I ran troubleshooter it now says that 'there's a problem with the driver for Ethernet adapter.'

Seems like quite a few people have run into this issue, with different fixes working, none of which did for me. A clean install has everything functioning smoothly. Not sure if Windows has a standalone driver for such an issue, but it should (if it doesn't; couldn't find one) as it would alleviate a lot of trial and error, and offer a quicker solution.

I uninstalled then reinstalled the Realtek driver from the RealTek website which had the same yellow exclamation mark result, but when I ran troubleshooter it now says that 'there's a problem with the driver for Ethernet adapter.'

Did you try a different Ethernet cord? Did you make sure that it was firmly plugged into the Ethernet jack on the computer and also on the Gateway?

When you get that error, it is not getting the IP lease from the Gateway. You can try Farbar's Service Scanner and minitoolbox. They are available at bleepingcomputer.com in their download area.

Seems like quite a few people have run into this issue, with different fixes working, none of which did for me. A clean install has everything functioning smoothly. Not sure if Windows has a standalone driver for such an issue, but it should (if it doesn't; couldn't find one) as it would alleviate a lot of trial and error, and offer a quicker solution.

It is an error that happens when the computer network adapter is not getting an IP Lease. It is not a lot of people that get that error, because it is one of those that too many jump the gun and automatically post online, instead of working through troubleshooting steps.

If the Ethernet is built onto the motherboard, try Asus's driver. Also check the Bios to make sure that the onboard Ethernet/LAN is not disabled.

It is an error that happens when the computer network adapter is not getting an IP Lease. It is not a lot of people that get that error, because it is one of those that too many jump the gun and automatically post online, instead of working through troubleshooting steps.

If the Ethernet is built onto the motherboard, try Asus's driver. Also check the Bios to make sure that the onboard Ethernet/LAN is not disabled.

It IS a lot of people, because I've been reading around various blog. While I appreciate responses in general, I don't know why you're posting on a 'solved' thread, and with a prickly, contrarian tone (for the sake of I don't know what) throughout at that, but neither is necessary. None of your suggestions were the problem, and even MS has stated that this is an issue that many encounter in the upgrade, with offers of several different fixes. Again, a clean install took care of everything.