Share via

Cannot remove vEthernet (Ethernet), Hyper-V Virtual Ethernet Adapter

Anonymous
2020-06-10T21:52:51+00:00

Problem: Have to disable 'vEthernet (Ethernet)' after every reboot to be able to use my local network.

Cannot permanently delete this Hyper-V Virtual Ethernet Adapter, which is of no use for me.

Windows 10 Pro (ver.2004): no VPN, no Virtual Machine, no Sandbox (But I have had them installed before), no WiFi, one Ethernet.

Hyper-V manager (virtmgmt.msc) is empty, never used.

Windows Features: Hyper-V, Virtual Machine Platform, Windows Sandbox are unchecked.

During a session I can delete vEthernet in Device Manager but it comes back after Reboot. (IP: 172.xxx.xxx.1)

When uninstalled in Network connections I get following error:

Could not uninstall the Client for Microsoft Network features.

The error is 0x80071779.

Using 'Disable-NetAdapterBinding to change 'ms_client to False' goes back to True after Reboot

Network Connection->Diagnose this connection: Couldn't identify the problem.

sfc /scannow: didn't find anything.

Network reset in Settings did not make any difference.

There are some useful information in the Device Managers Events tab shown below, but I do not know how to use it!

2020-06-10 0:31:54 Device deleted

Device ROOT\VMS_MP\0000 was deleted.

Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}

[after reboot]

2020-06-10 0:53:24 Device configured (wvms_mp_windows.inf)

Device ROOT\VMS_MP\0000 was configured.

Driver Name: wvms_mp_windows.inf

Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}

Driver Date: 06/21/2006

Driver Version: 10.0.19041.1

Driver Provider: Microsoft

Driver Section: VMSMP.ndi

Driver Rank: 0xFF0000

Matching Device Id: vms_mp

Outranked Drivers:

Device Updated: true

Parent Device: HTREE\ROOT\0

2020-06-10 0:53:24 Device started (VMSNPXYMP)

Device ROOT\VMS_MP\0000 was started.

Driver Name: wvms_mp_windows.inf

Class Guid: {4d36e972-e325-11ce-bfc1-08002be10318}

Service: VMSNPXYMP

Lower Filters:

Upper Filters:

How do I remove this virtual adapter?

Windows for home | Windows 10 | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
  1. Anonymous
    2020-07-15T20:06:57+00:00

    Hi,

    I was facing the same issue and under the "Turn Windows features on or off" I already tried removing the HyperV features but that did not help. I followed your post to find that under services some Hyper V services were getting triggered. I checked the dependencies and thought of disabling just one service and one step of yours at a time. I first disabled the "Microsoft Defender Application Guard" (this has recently been renamed if I remember correctly, others may find this name under the Windows feature as Windows Defender Application Guard) and restarted the computer.

    And Bingo... just this feature along with Hyper V must have been triggering the virtual adapters. Hope this works for others too.

    Regards.

    20+ people found this answer helpful.
    0 comments

15 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-07-17T17:09:51+00:00

    Thank you inevitable!

    I unchecked the Microsoft Defender Application Guard and everything is now OK. The Hyper-V service previously disabled, has also disappeared. I thought earlier that this had something to do with Microsoft Defender Firewall (which I am using) and missed it.

    I have for some reason installed the latest EDGE even if I am not using it. The feature seems to be that the Application Guard gives the possibilities to surf in a safe environment. But the program should be unchecked in Windows Features by default, but in my case something had initiated it.

    From the beginning my problem was that I got a vEthernet Adapter active and then couldn't see my local network. Had to disable it all the time. And I couldn't either get rid of the Virtual 8GB disk.

    Thanks

    In my case the problem is solved

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2020-10-20T17:43:53+00:00

    I also wanted to get rid of the virtual Ethernet adapter because it created a local networking problem.

    In my case Hyper-V was unchecked. Also the Microsoft Defender Application Guard was unchecked. But after reboot VEthernet adapter was coming up.

    Accidentally I noticed that Microsoft Sandbox was checked. After unchecking that and rebooting, my VEthernet adapter was gone, so this is exactly what I wanted.

    Hope this suggestion is of any help.

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2020-06-13T22:10:36+00:00

    I am back, missed an acceptable (temporary?) solution in the Device Manager.

    The default view in Device Manager doesn't show hidden devices.

    When checking this under the View folder, another Hyper-V Switch Adapter poped up.

    I disabled the vEthernet (Ethernet) adapter, uninstalled the now 2 Hyper-V adapters and

    all the Hyper-V connections shown under the View folder. Reboot and the vEthernet Adapter was gone.

    And my local network is shown again in the File explorer. So far so good.

    The Sandbox (the reason to the problem) also installed an 8 GB Virtual Disk and later I also tried to uninstall the Microsoft Virtual Disk in the Device Manager.

    Well, it came back after Reboot and at the same time installed the vEthernet back again!

    At the moment I have to live with the 8 GB Virtual Disk (MS solution: not showing it in MS Disk Management after 2004 upgrade). At least the annoying vEthernet Adapter is gone at the moment.

    The only solution to this Sandbox mess I have seen so far is to reinstall Windows 10 again.

    1 person found this answer helpful.
    0 comments
  4. btbt 11,826 Reputation points Volunteer Moderator
    2020-06-14T01:22:08+00:00

    Turn on, then turn off the Hyper-V feature. Check Method 1 under Resolution on this support page on how to do that. See if toggling it does anything.

    0 comments