Windows update breaks WIFI and LAN network connections

Try open start and search for Feedback and open Feedback Hub and report this issue.

Try check your PC manufacturer's website and see whether is there any new driver available there.

I had the same problem and had to use my wife's laptop dll a win ISO and do a repair install.

Same problem here. I have seen this on 2 windows 10 machines. One desktop (parents) with a wired LAN and one laptop (wifes) with wifi. The  I opened a command window and ran ipconfig /renew. And it was able to pull a new IP.

I think something in the update broke dhcp.

Rebooting did not help. Looking at other posts, some have had to ipconfig /release before it would renew.

If problem persist, restart your PC.

Actually, it is better if you restart your PC, if you are not in middle of some tasks.

So this happened again this morning to both computers - again!

There are not on the same network - not even the same city, so its not the router.  I have an ASUS router and the parents have some centurylink one... And my windows 8 laptop is having 0 problems.

I reviewed all setting and both machines are set to auto everything. There is 0 customization of the IPv4 or v6. Although both are enabled.

Reboots do nothing.

Again the IPCONFIG /Renew does the trick, but walking a 79YO though that everyday is not my idea of fun. I updated to the latest intel drivers on my laptop, so we shall see if that takes care of the problem. But I doubt it.

We have found that running the HP Driver Installation pack to REINSTALL the network drivers for our ELITEBOOK 840 G3 workstations (Win 10 x64).

We obtained the driver installation packs from the HP Support website (support.hp.com).

We downloaded these drivers from a different PC, loaded them onto a thumb-drive, and then used the thumb-drive to load them onto the affected PC.

It seems the same actions could be taken regardless of make/model.

Incredibly inconvenient - but it works, and the issue does not appear to reoccur.

Furthermore, for the rest of our environment - we used an MDM tool to deploy the driver installation files to each of our user's PCs in case the issue should happen to other PCs in the future  - that way we can simply advise the user to run the file from the hidden location over the phone - and they are up and running in <5 minutes.

It was an awful thing to have happen - but we believe we've gotten past the worst of it (KNOCKS ON WOOD).

Maybe a dozen users affected out of 80 or so that are running on HP ELITEBOOK 840 G3's for our organization.

Its a new network card and I installed the latest driver 1030.6.1201.2015.

This is a registry thing I believe, last time it happened I found some guide about what the registry should look like to populate the Network Connections page. The registry was missing, somehow the update is corrupting the registry.

Thanks for this! However, I dare not go through the whole thing again in case the restore fails.

But yes last time I tried to install the latest driver again and it wouldnt let me as it said I had the latest version of the driver already. 

So this is a handy fix for the network connectivity issue.  It is being acknowledged by many in the IT Professional community as a 'known issue' with a windows update.

http://www.theregister.co.uk/2016/12/12/ongoing_windows_8_10_dhcp_problems_affecting_all_isps/

As noted, you can run the following from an elevated command prompt (Run As Administrator):

netsh winsock reset catalog
netsh int ipv4 reset reset.log

These two commands should clear the issue which is actually tied to a breakdown in the local DHCP capabilities.  This problem does not appear to have affected windows devices with statically assigned IPs.

Microsoft posted an update recommending restarting the OS via Start -> Shutdown -> Restart (vs. hybrid shutdown) as a temporary workaround. KB3206632, released earlier today,  as listed the long-term fix.

Installing drivers or other updates or configuration changes that trigger a restart of the OS may appear to fix the issue when in fact,  the simple act of restarting the OS may well be what is allowing affected 1607 machines to temporarily obtain IP addresses.

If wired or wireless network adapters are being assigned a 169.254.XX.YY IP address on Windows 10 build 1607 devices only that haven't performed an OS restart rebooted recently, I would

1. Skip running the NETSH commands above or any commands that arbitrarily rebuild the network stack
2. Skip running the IPCONFIG /RELEASE & IPCONFIG /RENEW commands listed in TheRegister.co.uk link above and the linked Virgin article
   
3. Take a hard look @ https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/problems-connecting-to-the-internet/f121306e-fab5-411d-833f-e4490ecb8b5c

That the URL above is Windows 10 specific suggests that network problems on other operating system versions like Windows 7 and Windows 8.1 has a different root cause.