New
#11
Hmmm, Get is not recognized as the name of a cmdlet, Function, … etc. error when I try this command:
Get -VMSwitchExtension -VMSwitchName ('Default Switch')
Hmmm, Get is not recognized as the name of a cmdlet, Function, … etc. error when I try this command:
Get -VMSwitchExtension -VMSwitchName ('Default Switch')
I believe I tried with and without space after Get.
I moved ahead with the rest of the process you recommended. I was also on the same wavelength and anticipating a repair installation. Great Minds !
Anyway it is in process and I will update with results hopefully before I retire for the day. Currently at 75%!
Sadly... the repair installation did not resolve the issue. Same issue and symptoms remain. The Virtual Switch Manager just is unable to get the Default Switch created. I can see it trying but it only exists for a few seconds then vanishes.
That comment makes me a bit confused. Default Switch cannot be created in Virtual Switch Manager. It is created automatically, and now in your case it has disappeared. The only way to get it back is to let system "to start from scratch", to recreate it.
Next thing you could try is to first delete all existing virtual switches in Virtual Switch Manager. When done, restart. After restart, open Device Manager and one by one uninstall all Hyper-V network adapters:
Now disable Hyper-V in Optional Features and restart. After restart, enable Hyper-V and check if the Default Switch has been recreated.
Kari
I'll give this process a try and post results.
In the mean time, I am asking help from the best Hyper-V expert I know. Although she's now working for Microsoft HoloLens team, she used to be a team lead in Hyper-V team.
The tweet shown in screenshot on Twitter
Kari
Last edited by Kari; 20 Mar 2019 at 21:35. Reason: Typo fixed
Roger that. Thanks.
FYI re the Virtual Swithch Manager comment... what I am seeing is if I am viewing Network Connections when I have the Hyper-V Manger open and select the Virtual Switch Manager, I see the Default Switch appear for a few seconds, typically multiple times.
FYI, I may not have anytime to spend on this until Friday afternoon.
I believe this is a bug with the Default Internet Switch. I have had a lot of different issues with it including the one you describe. I haven't been able to solve this without a Windows clean install.
On one of my computers, I've simply ignored and disabled the Default switch and created a new one that works flawlessly.
This is a big and long time issue and this Switch creation spaghetti mess should have been solved by MS a long time ago but nothing has changed.
If Default Switch is not working, or missing like in OP's case, and NAT is required, the easy workaround is of course to create an internal switch, then share LAN / WLAN connection with internal switch. Now VMs using internal switch will get a NAT connection.
I have had no issues with switches, not in 1809, not in Fast ring and Skip Ahead ring Insider previews.
Kari