Cannot create virtual switch Hyper-V (0x80070002)

3

I get following error while creating any type(external, internal and private) of virtual switch on Hyper-V using Hyper-V manager.

Failed to create virtual ethernet switch.

The system cannot find the file specified. (0x80070002)

Here is a to screenshot of error:

enter image description here

OS: Windows 8.1 (x64) + Update 1

Getting the same error when trying to create from Powershell.

windows
networking
windows-8
virtualization
hyper-v
asked on Super User Jun 1, 2014 by Kedar Vaidya • edited Jun 1, 2014 by magicandre1981

3 Answers

3
  1. Go to Settings -> Network & Internet

  2. Select Change adapter options

  3. Right click on NIC Adapter -> Properties

  4. Check if the Hyper-V Extensible Virtual Switch is installed in your NIC's Properties

  5. Reinstall the Hyper-V Extensible Virtual Switch

    5.1 Select Install

    5.2 Select Protocol

    5.3 Select Hyper-V Extensible Virtual Switch

  6. Create the virtual switch on Hyper-V using the Hyper-V manager

Source: https://www.tenforums.com/virtualization/10699-hyper-v-error-when-creating-virtual-switch.html#post306179

answered on Super User Dec 2, 2017 by Alejandro
0

All resolutions suggested failed!

This did work immediately and I have had no issues since. Here is how you do it:

Open the following registry key and give "All Applications" full control permissions

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WcmSvc

That was it, no more issues after that.

answered on Super User May 24, 2019 by Matt N • edited May 25, 2019 by Run5k
0

All I did was delete the NICs from device manager one at a time (was logged in remotely). After deleting, right click and click Scan for hardware changes.

Windows re-found the deleted NIC and installed it, then Hyper-V manager was able to create a V-Switch.

For the Intel NICs, I did need the latest driver from Lenovo's site. I did not have to uninstall and reinstall the Hyper-V role; maybe because I had already tried the remove role → reboot → netcfg -d (PowerShell) → reboot again. (I had to use LogMeIn scheduled restart as I was working remotely)

answered on Super User Aug 19, 2019 by James Wirth • edited Aug 19, 2019 by Worthwelle

User contributions licensed under CC BY-SA 3.0