Skip to main content

Failed while adding virtual Ethernet switch

By
Well you know bad things happen right before you make a presentation.  I have no idea how this happened.  Tomorrow I am presenting PowerShell Desired State Configuration to my Advanced PowerShell class.  I’m going through a test run of my code and I lose my external internet connection in my VMs.  I am unable to create a new external VM switch connected to my wireless NIC on my Windows 10 Pro client.  Here is my error:

Failed while adding virtual Ethernet switch connections. Ethernet Port (long guid) bind failed: Catastrophic failure (0x8000FFFF)

Not funny!!!!!  I went through a lot of documentation which did not work.  Here is my final solution. 

Open the Network and Sharing Center
Click Change Adapter Settings
Open the properties of your wireless network adapter.
Click the Sharing tab.
Check Allow other network and users to connect through this computer’s Internet Connection.
Click OK.
Open the properties of your wireless network adapter.
Click the Sharing tab.
Uncheck Allow other network and users to connect through this computer’s Internet Connection.
Now go ahead and create you external VM Switch in Hyper-V

Labels

Labels:

Comments

Balaz said…
Thank you for this.
October 13, 2016 at 2:15 PM
Jason Robert said…
Saved me a lot of time here. Thanks for sharing!
June 6, 2017 at 10:01 AM
Post a Comment

Popular posts from this blog

How to list all the AD LDS instances on a server

By
AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.
Post a Comment
Read more

How to run GPResult on a remote client with PowerShell

By
In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.
Post a Comment
Read more

Where did a User’s Account Get Locked Out?

By
Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...
18 comments
Read more