Hyper-V Virtual Switch Creation Error: Causes and Solutions

What Does the Hyper-V Virtual Switch Creation Error Mean

The error "Hyper-V Virtual Switch Creation Failed" occurs when the system cannot complete the operation of creating a virtual network switch in Hyper-V. It is usually accompanied by an error code, for example:

• 0x80070005 — "Access is denied"
• 0x8007045D — "The device is not ready"
• 0x8007000E — "Not enough storage is available"
• 0x80070057 — "The parameter is incorrect"

The error appears when attempting to create a switch via Hyper-V Manager or PowerShell and blocks the configuration of network connectivity for virtual machines.

Causes

1. Insufficient account privileges — the operation is performed without administrator rights.
2. Conflict with an existing virtual switch — a switch with the same name or on the same physical adapter already exists.
3. Hyper-V services are not running — Hyper-V management services are stopped.
4. Corrupted or outdated drivers — issues with network adapter or Hyper-V drivers.
5. Blocking by antivirus/firewall — third-party software is preventing the creation of virtual networks.
6. Lack of system resources — insufficient memory or hardware conflicts.
7. Incompatible network settings — for example, the physical adapter is already in use by other software (VPN, Docker, etc.).

Method 1: Run as Administrator

The most common cause is launching without administrator privileges.

1. Close Hyper-V Manager if it is open.
2. Find Hyper-V Manager in the Start menu.
3. Right-click → "Run as administrator".
4. Try to create the virtual switch again.

For PowerShell:

# Open PowerShell as Administrator (Win+X → Windows PowerShell (Administrator))
# Then execute the switch creation command, for example:
New-VMSwitch -Name "ExternalSwitch" -NetAdapterName "Ethernet" -AllowManagementOS $true

Method 2: Check and Restart Hyper-V Services

Ensure that key Hyper-V services are active.

1. Press Win+R, type services.msc, press Enter.
2. Find the services:
   • Hyper-V Virtual Machine Management
   • Hyper-V Host Compute Service
3. For each: right-click → "Start", if the status is "Stopped".
4. Also check "Hyper-V Guest Service Interface" and "Hyper-V Data Exchange Service".

Or via PowerShell:

# Check service status
Get-Service -Name vm*, hv*

# Start services if stopped
Start-Service -Name vmms
Start-Service -Name vmcompute

After restarting the services, try to create the switch again.

Method 3: Remove Conflicting Virtual Switches

Sometimes the problem lies in already existing "broken" switches.

1. Open PowerShell as Administrator.
2. View a list of all virtual switches:

Get-VMSwitch

3. If you see unnecessary or duplicate switches, remove them:

Remove-VMSwitch -Name "SwitchName" -Force

4. Restart the computer and try to create a new switch.

⚠️ Important: Only delete switches that are not used by active virtual machines.

Method 4: Update Drivers and System

Outdated drivers can cause errors.

1. Update Windows:
   • Open Settings → Update & Security → Windows Update.
   • Install all available updates, including optional ones.
   • Restart the computer.
2. Update network adapter drivers:
   • Press Win+X → Device Manager.
   • Expand Network adapters.
   • Right-click on the physical network adapter (the one you plan to use) → "Update driver".
   • Select "Automatically search for updated driver software".
   • Restart the computer.
3. Install the latest versions of Hyper-V components:
   • In Control Panel → Programs and Features → Turn Windows features on or off.
   • Ensure the following are checked:
     • Hyper-V
     • Hyper-V Platform
     • Hyper-V Hypervisor
   • Click OK, wait for installation, and restart.

Method 5: Temporarily Disable Antivirus and Firewall

Antivirus solutions often block Hyper-V operations.

1. Open your antivirus control panel (e.g., Kaspersky, ESET, Avast).
2. Find the "Protection" or "Firewall" section.
3. Temporarily disable all protections (for 5-10 minutes).
4. Try to create the virtual switch.
5. If successful — add an exception for Hyper-V in the antivirus:
   • Process paths: C:\Windows\System32\vmms.exe, C:\Windows\System32\vmcompute.exe
   • Folders: C:\Windows\System32\Hyper-V\
6. Re-enable the antivirus.

For the Windows Firewall:

# Temporarily disable (PowerShell as Administrator)
Set-NetFirewallProfile -Profile Domain,Public,Private -Enabled False

# After creating the switch, re-enable
Set-NetFirewallProfile -Profile Domain,Public,Private -Enabled True

Method 6: Check the Physical Network Adapter

Ensure the selected physical adapter is available and not in use.

1. Open Device Manager → Network adapters.
2. Make sure the required adapter (Ethernet, Wi-Fi) is not disabled (no gray arrows).
3. If the adapter is used by a VPN client (Cisco, OpenVPN, etc.) — disconnect the VPN before creating the switch.
4. In PowerShell, check which adapters are free:

Get-NetAdapter -IncludeHidden | Where-Object {$_.Status -eq "Up"}

5. When creating the switch, specify only a working adapter.

Prevention

• Always run Hyper-V Manager and PowerShell as Administrator.
• Regularly update Windows and drivers, especially after major system updates.
• Avoid conflicts: do not use one physical adapter for multiple virtual switches simultaneously.
• Manage antivirus: add exceptions for Hyper-V folders and processes.
• Before creating a switch, ensure there are no active VPN connections or other network software that intercepts adapters.
• Create switches via PowerShell — it provides more detailed error messages:

New-VMSwitch -Name "MySwitch" -NetAdapterName "Ethernet" -AllowManagementOS $true -ErrorAction Stop

If the problem persists, check the Windows Event Log (Event Viewer → Windows Logs → System) for errors from sources Hyper-V-VmSwitch or Hyper-V-Worker.