Virtual Switch Manger Unable to Create Default Switch in v1809

jareinertson · 19 Mar 2019

After upgrading to v1809 I turned Hyper-V feature Off then On. Since then the Default Switch no longer exists and the Virtual Switch Manager is unable to crate it automatically as it would normally. I can see the Default Switch appear for a few seconds in the Network Adapters, then its gone. This happens several time whenever I launch the Virtual Switch Manager.

I can create other virtual switches.
Once the Virtual Switch Manager lists the Default Switch with a Load Failed message.

I have used netcfg -d command and Turned Hyper-V feature Off/On several times with no success.

Suggestions welcome. :) Thanks

Kari · 19 Mar 2019

Could you please run following command in elevated PowerShell to copy all possible information about Default Switch to clipboard:

Get-HNSNetwork | clip

Reply to this thread, click the CODE tags button to create a CODE box in your post:

Virtual Switch Manger Unable to Create Default Switch in v1809-image.png

Now paste the content of clipboard in CODE box:

Code:

Paste output of Get-HNSNetwork here.

That helps us to check if there's an obvious cause for your issue.

Kari

jareinertson · 19 Mar 2019

Hi, I was hoping you would see this issue... :) I 've appreciated your other support posts. Since there actually is no Default Switch, should I still try the Powershell command you suggested?

Kari · 19 Mar 2019

jareinertson said:

Since there actually is no Default Switch, should I still try the Powershell command you suggested?

Yes.

jareinertson · 19 Mar 2019

Powershell clip ...

Code:

ActivityId             : F7089A6D-AF83-4EF0-8A30-DBA1D9B427DB
AdditionalParams       : 
CurrentEndpointCount   : 0
Extensions             : {@{Id=E7C3B2F0-F3C5-48DF-AF2B-10FED6D72E7A; IsEnabled=False; Name=Microsoft Windows Filtering 
                         Platform}, @{Id=E9B59CFA-2BE1-4B21-828F-B6FBDBDDC017; IsEnabled=False; Name=Microsoft Azure 
                         VFP Switch Extension}, @{Id=EA24CD6C-D17A-4348-9190-09F0D5BE83DD; IsEnabled=True; 
                         Name=Microsoft NDIS Capture}}
Flags                  : 0
Health                 : @{LastErrorCode=0; LastUpdateTime=131975016067872695}
ID                     : C6A303B8-C03B-44F8-801A-7025DD9336D1
IPv6                   : False
LayeredOn              : 8B8D7BC8-C549-4AF5-BBC8-493C96DB9A53
MacPools               : {@{EndMacAddress=00-15-5D-2E-BF-FF; StartMacAddress=00-15-5D-2E-B0-00}}
MaxConcurrentEndpoints : 0
Name                   : Internal Virtual Switch
Policies               : {}
Resources              : @{AdditionalParams=; AllocationOrder=0; Health=; ID=F7089A6D-AF83-4EF0-8A30-DBA1D9B427DB; 
                         PortOperationTime=0; State=1; SwitchOperationTime=0; VfpOperationTime=0; 
                         parentId=2EAACA08-178C-4A20-A3CC-775C7D55EAC6}
State                  : 1
Subnets                : {@{AdditionalParams=; AddressPrefix=172.24.112.0/20; Health=; 
                         ID=270CF8D0-9254-4420-B1DF-1EFE3E72037A; Policies=System.Object[]; State=0}}
TotalEndpoints         : 0
Type                   : Internal
Version                : 38654705666

ActivityId             : 3E59B364-DD3C-4E4D-9C90-09A4E632EFEA
AdditionalParams       : 
CurrentEndpointCount   : 0
Extensions             : {@{Id=E7C3B2F0-F3C5-48DF-AF2B-10FED6D72E7A; IsEnabled=False; Name=Microsoft Windows Filtering 
                         Platform}, @{Id=E9B59CFA-2BE1-4B21-828F-B6FBDBDDC017; IsEnabled=False; Name=Microsoft Azure 
                         VFP Switch Extension}, @{Id=EA24CD6C-D17A-4348-9190-09F0D5BE83DD; IsEnabled=True; 
                         Name=Microsoft NDIS Capture}}
Flags                  : 0
Health                 : @{LastErrorCode=0; LastUpdateTime=131975019711018509}
ID                     : 2F7ADE23-3C29-494A-B7A4-4575DE79C37F
IPv6                   : False
LayeredOn              : 1616946B-FBC7-4D7A-987B-0D04B8A8FE48
MacPools               : {@{EndMacAddress=00-15-5D-73-1F-FF; StartMacAddress=00-15-5D-73-10-00}}
MaxConcurrentEndpoints : 0
Name                   : External Virtual Switch
Policies               : {}
Resources              : @{AdditionalParams=; AllocationOrder=0; Health=; ID=3E59B364-DD3C-4E4D-9C90-09A4E632EFEA; 
                         PortOperationTime=0; State=1; SwitchOperationTime=0; VfpOperationTime=0; 
                         parentId=70E72300-5653-4A81-8934-626D74E24D84}
State                  : 1
TotalEndpoints         : 0
Type                   : Transparent
Version                : 38654705666

jareinertson · 19 Mar 2019

I posted the results twice (I think) but do not see them here...

OK there it is...

jareinertson · 19 Mar 2019

FYI, I just received this reply in a answers.microsoft.com site posting of this issue...
https://support.microsoft.com/en-us/...sions-of-windo

Kari · 19 Mar 2019

jareinertson said:

FYI, I just received this reply in a answers.microsoft.com site posting of this issue...
https://support.microsoft.com/en-us/...sions-of-windo

That fix has nothing to do with Default Switch, it only fixes other switches. I'll check your Get-HNSNetwork output, will post back but it might take some time.

jareinertson · 19 Mar 2019

Thanks!

Kari · 19 Mar 2019

OK, your output shows absolutely no trace of Default Switch. In my opinion, repair install would be the best option now. Before doing it, just to be sure, run this in elevated PowerShell:

Get-VMSwitchExtension -VMSwitchName ('Default Switch')

If you get any output other than error, run the command again adding that | clip to the end of command and paste the output here.

If it just shows error in red text, continue from here:

Your specs show you are running W10 v.1809.

Default Switch can be manually deleted, but only for current session; a reboot recreates it. However, it cannot be manually recreated. Therefore, my recommendation is to perform a repair install of 1809 (tutorial). It is important to disable Hyper-V in Optional Features before you start!

Also, before doing the repair install, after disabling Hyper-V, turn hypervisor off with following command in elevated Command Prompt (not PowerShell!):

bcdedit /set hypervisorlaunchtype off

Restart, then perform repair install to fix the system.

After the repair install, turn hypervisor on and restart:

bcdedit /set hypervisorlaunchtype auto

After restart, hypervisor now enabled, enable Hyper-V and restart. Check if the Default Switch exists, if not post back and figure out something else.

Kari