Windows 10: No IPv6 inside WDAG, Sandbox and Hyper-V - Windows 10 Pro, v 1909

Hi everyone! Thanks for reading this!

I have tested my IPv6 connectivity on my Windows 10 Pro v1909 using Test your IPv6. and I have IPv6 available on my machine. It reports 10/10 tests ok. Nice!

However, when I repeat the same test inside Windows Defender Application Guard (WDAG) for Edge and Windows Sandbox I am informed that I have no IPv6 at all.

To make matters worse, I have installed Hyper-V. I have created an Hyper-V Virtual Switch, type "external", which "wraps" the wifi net adapter. The result: the first test which reported ok now reports no IPv6 at all. Of course, WDAG and Sandbox continue to report no IPv6.

As one might expect from above scenario, my Virtual Machine (another Windows 10 Pro v1909 run via Hyper-V and the aforementioned external vSwitch ) sees no IPv6 at all.

The only thing I have tried to solve the problem was to enable Routing and Remote Access, setting it to Automatic and Automatic (delayed start). No luck.

Nonetheless, IPv4 continues to work fine (otherwise I would not be able to create and type this thread!).

If anyone have any idea I would be glad to hear.

Thanks for your attention.

:)

 

No IPv6 inside WDAG, Sandbox and Hyper-V - Windows 10 Pro, v 1909

Hi everyone! Thanks for reading this!

I have tested my IPv6 connectivity on my Windows 10 Pro v1909 using Test your IPv6. and I have IPv6 available on my machine. It reports 10/10 tests ok. Nice!

However, when I repeat the same test inside Windows Defender Application Guard (WDAG) for Edge and Windows Sandbox I am informed that I have no IPv6 at all.

To make matters worse, I have installed Hyper-V. I have created an Hyper-V Virtual Switch, type "external", which "wraps" the wifi net adapter. The result: the first test which reported ok now reports no IPv6 at all. Of course, WDAG and Sandbox continue to report no IPv6.

As one might expect from above scenario, my Virtual Machine (another Windows 10 Pro v1909 run via Hyper-V and the aforementioned external vSwitch ) sees no IPv6 at all.

The only thing I have tried to solve the problem was to enable Routing and Remote Access, setting it to Automatic and Automatic (delayed start). No luck.

Nonetheless, IPv4 continues to work fine (otherwise I would not be able to create and type this thread!).

If anyone have any idea I would be glad to hear.

Thanks for your attention.

 

Hyper-V IPv6 & VPN issue

I have a Windows 10 desktop (64 bit version 1909)

Hyper-V is installed (I am running a Ubuntu VM)

IPv6 is installed and operational (native with DHCP-PD running on the router)

When I connect to my VPN provider, using OpenVPN it fails to connect on IPv6, although the provider supports this and I have verified this on a machine that does not have Hyper-V installed.

The issue seems to be how the TAP-9 interface is handled.

Specifically on the Hyper-V machine Tap-9 interface there is no IPv6 address (other than link-local) and no IPv6 DNS server address. Both exist on the non Hyper-V machine.

Looking at the registry I can see that HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters: DisabledComponents is set to 1(hex) and this appears to be the setting for 'disable IPv6 on all tunnel interfaces'. On the non Hyper-V this key
is absent.

My questions are

Is this key the cause of my issues (i.e. is the TAP-9 interface treated as a tunnel?)

What are the risks if I remove or disable this key while Hyper-V is installed and running?

Is there an alternate solution (registry setting) that will allow IPv6 through the VPN tunnel while Hyper-V is running?

Thank you

 

Hyper-V Fails to Install on Windows 10 v.1909

A mystery to me too, I've been running Hyper-V on two W10 Pro machines, both on 1909 (build 18363.592).

You should do if Hyper-V has been installed successfully. For reference, these are the services I have....






There is also the Hyper-V Manager, which is the virtmgmt.msc snap-in for the MMC management console.