question

jeromezheng-6551 avatar image
0 Votes"
jeromezheng-6551 asked ·

Hyper-V Create External Virtual Switch Issue

I was trying to restore my hyper-v virtual switch network. it was working fine before the last windows 10 Pro update. I was able to bind the External Virtual Switch to my Wireless NIC which is AC3165. however, after windows updates. my network settings was not working. when I tried to restore the configuration, I got errors like "Error applying Virtual Switch Properties changes failed whiled adding virtual Ethernet switch connection (0x80070490) " and after I use the Microsoft resolution to run "MicrosoftEasyFix20159.mini.diagcab", then try to do the same setup for the External Virtual Switch, it give me the error like " Error applying Virtual Switch Properties changes. The operation failed because the object was not found. " I tired. 1. "netcfg -d" 2. uninstall and reinstall the "Hypver-v" 3. use Microsofteasyfix20159.mini.diagcab none of these above worked out for me. please help and give me some clue where I should tune to make it work again.

windows-10-virtualization
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

jiayaozhu-MSFT avatar image
0 Votes"
jiayaozhu-MSFT answered ·

Hi,

Good for you to follow the public document at the first hand! The reason why you still cannot create an external virtual switch needs further troubleshooting and here are some tips you could try:

Firstly, I would like to collect your KB number of your current Windows version to further check the non-compatibility issue of your wireless NIC and your Hyper-V host version.

Secondly, any WAN miniport devices such as WireShark / NCap are supposed to be removed when you set up an external virtual switch. Check if you have any of these network devices, if so, I’d like you to remove them and run Microsofteasyfix20159.mini.diagcab to set up your external virtual switch again.

More information about WAN miniport devices can be seen from
https://social.technet.microsoft.com/Forums/en-US/233054fe-8f99-4a5a-bfa6-437973f449b8/rasclient-event-id-20227-the-user-pcasuslocaluserasus-dialed-a-connection-named-contosocom

Thirdly, try to use PowerShell commands to get the information of your network adapter and Hyper-V virtual switch to see whether you have actually created successfully. Then try to use PowerShell to setup an external virtual switch.
A. To get the information: Get-VMNetworkAdapter
B. To create an external virtual switch: New-VMSwitch -name ExternalSwitch -NetAdapterName Ethernet -AllowManagementOS $true

If you still cannot work out the problem, then I am afraid that it is quite hard to solve the non-compatibility issue with wireless NIC. The usual answers of driver updates, software version updates help some but for those trying these ways from a wireless network adapter there seems no solid fix.

There are some tips that you can try from:
https://appuals.com/error-applying-hyper-v-virtual-switch-properties/
https://pomeroy.me/2020/08/hyper-v-virtual-switch-creation-woes/#comment-411452
https://niallbest.com/hyper-v-virtual-switch-wireless-error-and-limited-ics-fix/.
Note: Information posted in the given link is hosted by a third party. Microsoft does not guarantee the accuracy and effectiveness of information.

Thank you for your time! If you have concerns or questions, please feel free to feedback.

Best regards
Joann Zhu


If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

· 2 ·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi Joann,

Thanks for your reply. Actually, I used to have Wireshark and NMap installed, however, before I bind the external switch with my WiFi card, I already removed them and did run the Microsofteasyfix20159.mini.diagcab as well.

My windows build is Version 20H2 (OS Build 19042.844)

The wireless card already updated to the latest driver.

Unfortunately, The PowerShell method didn't work out for me. however, I am curious whether there is any difference when I created in the GUI and the PowerShell command.

I ended up with setting up the network share as a workaround. but I don't think this is would be a permanent solution though. it's very inconvenient especially when I want to work with multiple machines at home lab.

Hope Microsoft could fix this in the future Hyper-V patches.

0 Votes 0 ·

Hi,

Thank you for your share! Your suggestion means a lot for us and improving the quality of the products and services is a never-ending process for Microsoft. Thanks again for your understanding!

Could you please help Accept Answer? So that others meet a similar issue can find the latest information quickly.


Best wishes
Joann

0 Votes 0 ·