No network after Windows 10 build 10586 update

will try it when i get from work.

Probably running into the same issue others experienced when upgrading from 8.1 pro to Windows 10 when hyper-v was enabled in 8.1 pro, except you upgraded from 10 to 10 Nov Update when hyper-v was enabled on 10. Try this fix in this link

No Internet Access After Upgrading to Windows 10

Use method 2 and use your Ethernet connection where the link refers to the WiFi connection.

sciencegeek said:

Probably running into the same issue others experienced when upgrading from 8.1 pro to Windows 10 when hyper-v was enabled in 8.1 pro, except you upgraded from 10 to 10 Nov Update when hyper-v was enabled on 10. Try this fix in this link

No Internet Access After Upgrading to Windows 10

Use method 2 and use your Ethernet connection where the link refers to the WiFi connection.

Something similar worked for me.

I had no internet after the update and when I checked the Ethernet Properties and the connection uses only VirtualBox was active.


I activated some others including IPV4 and IPV6 and the internet worked again.

I have 3 machines in a home workgroup, which were all seeing each other and networking fine. Since a few days ago the Windows 10 Home (Lenovo All-in-one) has gone blind, can see no computer beyond itself, though it's okay and working with the two printers on the network. Other machines (Win 8.1 and 7 laptops) can see the Win 10 but cannot connect with it for sharing. All 3 machines share the same workgroup name, password, and wireless connection. Router is fine, and Internet working on all 3 of them.

I'm not strong on navigating Win 10 yet, have triple-checked everything I can think of on Control Panel Network, Workgroup, Settings...but am missing something. I see other laments here and on Google; might this have anything to do with the 10586 update, which I believe happened around the time my network failed? What to try?
Thanks for any assistance.

Two things I noticed was that location services and the onboard Vpn (not any private services you may have) were on once I disabled them my connection came back.

I posted in Laptop fail to update to build 10586 .... a method to isolate a device driver problem.

By the way, I had Hyper-V running Server 2009 R2 when the upgrade began. The virtual machine started right up after the 10586 upgrade.

Problem solved had to remove all network adapters including hyper-v network switches (before that had to remove it from all virtual PCs). Then re-scanned hardware reinstalled physical adapters and recreated hyper-v switches. problem was with hyper-v network.

razy60 said:

Two things I noticed was that location services and the onboard Vpn (not any private services you may have) were on once I disabled them my connection came back.

Good try, and thanks, but mine were already disabled.

Dear Colleagues,
I have four workstations running win10 Enterprise downloaded from MSDN. Exactly 30 days after the installation the Microsoft delayed bomb of 10586 has blown up and I perfectly lost the network connection. I tried everything described in this blog and anywhere google gave me without any success. I downloaded the new version from MSDN and I installed it over the MS upgrade but it did not want to work. A clean install of 10586 was the only thing helped.
We need to get used to that Microsoft regularly places a delayed bomb under our desks and these bombs sooner or later blow up. My advice is that making experiments with the dead system is longer than reinstalling everything from the scratch.