question

AhmedJabirZuhayr-7224 avatar image
0 Votes"
AhmedJabirZuhayr-7224 asked saldana-msft edited

Ethernet media disconnected after enabling Virtual Machine Platform

I enabled WSL and VMP from Windows Features. But after the restart, Windows showed my ethernet cable is disconnected. ipconfig shows the ethernet media is disconnected.

14904-image.png


It fixes itself after I disable Virtual Machine Platform (WSL2). WSL1 works fine.

I've tried

1) Updating Killer Network drivers to the latest version.
2) Enabling VMP but disabling WSL
3) Enabling Hyper-V Manager (Screenshots below)
14856-image.png


Some more screenshots

1) Network Manager
14866-image.png

2) ipconfig /all output after enabling VMP
14884-image.png

3) ipconfig output after disabling VMP
14826-image.png


Additional Information:

Windows Build: Microsoft Windows [Version 10.0.19041.388]
First time enabling WSL/2
Github issue: https://github.com/microsoft/WSL/issues/5676


windows-server-hyper-vwindows-10-hyperv
image.png (16.0 KiB)
image.png (47.1 KiB)
image.png (12.3 KiB)
image.png (54.8 KiB)
image.png (30.7 KiB)
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

A bit of an accidental discovery today, in Windows Network properties I found this.
![14885-hw-props.png][1]


Now even though the media says it's disconnected, it's IPv4 is 169.154.
However, my ethernet cable is connected to a router with default gateway 192.168.0.1 and IP ranges in the 192.168.0,
range as you can see below in the screenshot taken from when VMP is disabled

![14839-hw-props-working.png][2]



Could this be a ip configuration mishandling/DHCP settings issue after enabling VMP?
[1]: /answers/storage/temp/14885-hw-props.png
[2]: /answers/storage/temp/14839-hw-props-working.png

0 Votes 0 ·
hw-props.png (31.7 KiB)
MisterJ-6435 avatar image
0 Votes"
MisterJ-6435 answered AhmedJabirZuhayr-7224 edited

AhmedJabirZuhayr, please try this in an Administrative Command Prompt: netsh int ipv4 reset, then again for ipv6 and Restart. Enjoy, John.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi, thanks for the reply.

Initially I tried that but powershell kept giving me a "Access denied" even though it was administrative.

Then I found some resources in the internet (Reference below (1)) where in regedit I edited Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nsi\{eb004a00-9b1a-11d4-9123-0050047759bc}\26 permission's to change owner to "Everyone" and give "Everyone" Full control. After that, ipv4 reset worked but ipv6 still gave access denied.
I also tried netsh int ip reset all which also worked fine after the regedit. But unfortunately, the issue persisted after all anyway.


It's also worth mentioning after every restart, for some reason that registry's permission would reset back by unchecking the "Full Control".


Logs:
netsh commands
netsh commands after regedit


0 Votes 0 ·
MisterJ-6435 avatar image
1 Vote"
MisterJ-6435 answered AhmedJabirZuhayr-7224 edited

AhmedJabirZuhayr, huh? The address you saw is 169.254 not 169.154. Please search this and you will see it is special error address needing attention. Your second post makes no sense to me because I did not say to use Power Shell. I use a Command Prompt and get none of these errors. See here:

C:\Users\John>netsh int ipv4 reset
Resetting Compartment Forwarding, OK!
Resetting Compartment, OK!
Resetting Control Protocol, OK!
Resetting Echo Sequence Request, OK!
Resetting Global, OK!
Resetting Interface, OK!
Resetting Anycast Address, OK!
Resetting Multicast Address, OK!
Resetting Unicast Address, OK!
Resetting Neighbor, OK!
Resetting Path, OK!
Resetting Potential, OK!
Resetting Prefix Policy, OK!
Resetting Proxy Neighbor, OK!
Resetting Route, OK!
Resetting Site Prefix, OK!
Resetting Subinterface, OK!
Resetting Wakeup Pattern, OK!
Resetting Resolve Neighbor, OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , failed.
Access is denied.

Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Resetting , OK!
Restart the computer to complete this action.

I ignore this:
Resetting , failed.
Access is denied.

I would suggest not messing around in the Registry! Enjoy, John.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Well access denied or not, it didn't work. Nor even if I undo the registry changed.
And ya, my bad, it's .254. but it's supposed to be on the 192.168.0.100/24 range according to my router.

0 Votes 0 ·