Hyper-V VMs do not have internet acces

Varughese, Biju 0 Reputation points
2026-09-08T20:27:04.71+00:00

The Hyper-V VMs do not have internet access. The Default Switch is configured as the network adapter for all VMs, and the Wi-Fi network profile is set to Private.

Windows for home | Windows 11 | Internet and connectivity
0 comments

3 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-09-08T20:27:21.9766667+00:00

    For Hyper-V, the switch type determines whether a VM can reach the internet:

    • External switch: connects VMs to the physical network.
    • Internal switch: connects VMs to the host and other VMs on the same host, but not the external network.
    • Private switch: connects only VMs on the same host.

    If VMs are attached to the Default Switch and still have no internet access, a reliable workaround is to stop relying on the existing switch path and create a new network path for the VMs.

    A practical fix is:

    1. Open an elevated PowerShell session.
    2. List adapters: 
         Get-NetAdapter
    3. Create a new external virtual switch bound to the physical network adapter that has connectivity: 
         New-VMSwitch -Name <switch-name> -NetAdapterName <netadapter-name>
    4. In Hyper-V Manager, connect each VM to that new external switch.

    If the host is in a nested virtualization scenario or the external switch path does not work, use an internal switch with NAT instead. Example PowerShell flow:

    New-VMSwitch -SwitchName "VM-Internal" -SwitchType Internal
New-NetIPAddress -IPAddress 192.168.100.1 -PrefixLength 24 -InterfaceIndex 34
New-NetNat -Name VM-Internal-Nat -InternalIPInterfaceAddressPrefix 192.168.100.0/24

    Then configure the guest VM to use that NAT-backed network.

    If a VM lost connectivity after updates, another documented workaround is to add a new network adapter to the VM, assign it to the working external switch, confirm connectivity, and then remove the old adapter.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Varughese, Biju 0 Reputation points
    2026-09-08T20:36:27.6066667+00:00

    Error -
    New-VMSwitch: Failed while adding virtual Ethernet switch connections.

    Ethernet port '{FE0B29C4-39C2-4F33-9312-B04E17BB43E6}' bind failed: Catastrophic failure (0x8000FFFF).

    Was this answer helpful?

    0 comments
  3. Hendrix-V 18,605 Reputation points Microsoft External Staff Moderator
    2026-09-09T03:16:59.3833333+00:00

    Hi Varughese, Biju,

    Thank you for providing the error details. The 0x8000FFFF (Catastrophic failure) message typically indicates that Hyper-V is unable to bind the virtual switch to the physical network adapter, which can occur if a network binding, virtual adapter, or networking component is not functioning correctly.

    As this issue appears to be occurring during virtual switch creation rather than within the VM itself, you could try the following:

    1, Reset the network configuration

    • Open Command Prompt as Administrator.
    • Run: netcfg -d
    • Restart the computer.
    • Try creating the virtual switch again.

    2, Check for VPN or network filtering software

    • If VPN, endpoint security, or network monitoring software is installed, temporarily uninstall it and test again.
    • Some networking drivers can prevent Hyper-V from binding to the physical adapter.

    3, Recreate Hyper-V networking components

    • Turn off Hyper-V in Windows Features.
    • Restart the device.
    • Re-enable Hyper-V and restart again.
    • Attempt to create a new virtual switch.

    4, Verify the physical network adapter

    • Open Device Manager and check whether the Wi-Fi/Ethernet adapter is working properly with no warning icons.
    • If available, install the latest network adapter driver from the device manufacturer's website.

    If the issue persists, please let us know whether you're using a Wi-Fi or Ethernet connection and whether any VPN or security software is installed. That information can help narrow down whether the binding failure is related to a specific network adapter or third-party networking component.

    I hope this helps point you in the right direction. Feel free to ask me by clicking "Add Comment" or "Add Answer" if you cannot add comment so your response will be visible. Thanks for your effort.

    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.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.