Hyper-V - Unable to Create External Virtual Switch

I get the error "bind failed: General access denied error" when I try to create an external virtual switch.



I tried running Hyper-V with as admin without success.

Kevin

Please run PowerShell, type Get-VMSwitchand hit Enter. Take a screenshot of results and post here, see below for an example:

In case you need help with posting screenshots:

• Screenshot - Take in Windows 10 - Windows 10 blog
• Screenshots and Files - Upload and Post in windowssh blog - Windows 10 blog

Nothing is listed:



Kevin

OK.

Which Windows 10 build you are using? Are you signed in with an admin account? Are you trying to create an external switch using Ethernet adapter or the wireless adapter?

Windows 10 Enterprise, Version 1511, OS Build 10586.122.

I am signed in as myself, an admin.

I'm trying to connect to a wireless adapter.

Kevin

Two suggestions. First a safe workaround, then a bit more risky solution which might or might not work.

A safe workaround:

1.)Create an Internal virtual switch

2.)Change your virtual machine Network Adapterto your new Internal switch



3.)Before starting the vm, make sure your host physical wireless adapter is connected, then open its Properties and under the Sharing tab, enable sharing the connection with your new Internal switch:

That's it. Your vm is now using an Internal switch which then gets a shared connection from the wireless adapter on host.


A not so safe but more permanent solution:

1.)Open an elevated admin Command Prompt

2.)Enter command netcfg -d, hit Enter. All your host network connections will be reset, all possible virtual switches removed, even those "half there" not shown but yet making it impossible to create new switches as in your case

3.)Restart, reconnect the wireless adapter (notice that it's reset, you need to enter the network security key again)

4.)Create the external switch

5.)If you can now create the external switch, everything is OK. If not, you can still use the above workaround

   Warning

Please notice: The netcfg -dcommand when it works can show a few errors, followed by a few "Success" messages. It's totally normal.

The command might crash the PC causing a BSOD, for instance when I tested this just now, the first netcfg -dgave a BSOD, the second one after the restart worked.

I will take no responsibility, if you decide to test this scenario you do it at your own risk!

Kari

Before I try these solutions, what about using RDP? I was reading about that was a good way to get the screen resolution to match my host system. Would that somehow change how the networking works or would I still have the same problem?

Kevin

Before I try these solutions, what about using RDP? I was reading about that was a good way to get the screen resolution to match my host system. Would that somehow change how the networking works or would I still have the same problem?

The vm needs to be connected to the network before you can remotely connect to it. To connect, a vm needs a virtual switch. To use Remote Desktop, you first need to create a working virtual switch and set the vm to use it.

Nothing is listed:



Kevin

I see Windows PowerShell Listed at top left corner - It Does Not Say "Administrator" Maybe problem

I see Windows PowerShell Listed at top left corner - It Does Not Say "Administrator" Maybe problem

No, that's not an issue. Get-VMSwitch does not need elevated PowerShell. See my screenshot in post #2.