Common reasons for this error are a missing or damaged Default Switch, issues with network adapter settings, or if the Hyper-V Extensible Virtual Switch protocol was removed. Sometimes, leftover files from uninstalled VPNs or network tools can also cause the problem. In this article, we will discuss different ways to solve this error.
1. Enable the Protocol in Hyper-V Extensible Virtual Switch
For our first solution, we will enable the necessary protocol in the Hyper-V Extensible Virtual Switch settings on your physical network card. Select the network card you plan to use as an external switch. The external switch allows your virtual machines to communicate with the rest of your network.
2. Create a Virtual Switch Using PowerShell
If you’re facing issues when using the graphical interface, some users have found success by creating an external switch using PowerShell.
3. Reinstall the Hyper-V Role
For this solution, we will temporarily disable and then re-enable the Hyper-V role in Windows 10. Don’t worry—your virtual machines will remain available in Hyper-V Manager throughout this process. We’ve previously shared a guide on how to enable the Hyper-V role in Windows 10. If you need step-by-step instructions, you can check out this Hyper-V Role article.
