Windows 10: Ver. 20H2 kills Network

I have relatively new HP tower. Running VER.1909.

It has the Realtek PCIe Network driver. I have tried to install 20H2 4 times adn tried all teh fixes. rest driver, installed new driver, modified Reg. edit. Did all the Win. Network troubleshooting apps, Change PC name.. etc. still shows Network connected with Internet access, but cannot access anything on the internet.

Strangely, does an IP return on an outside IP address. But cannot VPN in to work, or open any browser page.. get the ole Page cannot be displayed. Outlook doesn't connect either.

I saw somewhere that certain models of HP computers were not compatible with this build? Also, saw that MS knows about the issue and is working on a new push fix???

PS: wifi doesn't work either. Also tired a USB LAN adapter connection,,, same there.

Any more Ideas' on when or if MS is coming with a fix as from what I see there are a lot users with the same issue.?


Thanks

:)

 

Windows update and killing the network adapter

My update list shows KB4338818 waiting, and the more info lists this update as having an issue which kills the network adapter.

So, why would anyone elect to install this KB knowing it will kill the internet? Right now, for that issue alone, this KB item is not installed on my PC.

There are (manual) workarounds listed, and therefore why hasn't MS embodied them in the KB so this issue just "isn't there"?

 

July 13 update killed ability to connect to the internet

Hi Elizabeth,

This issue may have occurred either due to a corrupt network driver or incorrect network settings. To resolve your concern we suggest that you follow the methods listed on this
link. The link contains basic troubleshooting steps such as the Network troubleshooter and steps on resetting
the network devices that can help fix the issue.

Let us know how it goes after performing the suggested steps.

 

Did our Epson printer get hacked?

Another question, is this on a home network or a work network? The steps @eidairaman1 listed are always a good first step. If this is on a work network you manage, I'd be much more concerned than the home one. It is possible someone is screwing with you, but malware could also be the culprit.