News, tips, advice, support for Windows, Office, PCs & more. Tech help. No bull. We're community supported by donations from our Plus Members, and proud of it
Home icon Home icon Home icon Email icon RSS icon
  • No IPv6 (via DCHPv6) on WDAG, Sandbox and Hyper-V

    Home Forums Networking – routers, firewalls, network configuration No IPv6 (via DCHPv6) on WDAG, Sandbox and Hyper-V

    Viewing 2 reply threads
    • Author
      • #2288051 Reply
        AskWoody Lounger


        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. The IPv6 connectivity was automatically configured by Windows using data from DHCPv6. 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 after these tests. 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 running via Hyper-V and the aforementioned external vSwitch ) sees no IPv6 at all.

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

        I do not want to have to set IPv6 parameters manually. If anyone have any idea I would be glad to hear.

        Thanks for your attention.

        • This topic was modified 1 month, 1 week ago by Sandro. Reason: underline unavailable (?)
      • #2288091 Reply
        Paul T
        AskWoody MVP

        IPv6 is probably not supported on those platforms – there is no reason it should for internal use. IPv6 is only needed on the internet, with v4 translated at your network edge.

        cheers, Paul

      • #2288125 Reply
        AskWoody Lounger

        Thanks Paul T,

        You have a sensible point here.

        This problem (with IPv6) does not seem to be a bug: either this has yet to be implemented or it was rendered by Microsoft as not needed inside the machine.

        Nevertheless, it is quite strange to me that we are in 2020 and were are still talking about things like the full adoption of IPv6.

        Bye, Sandro

    Viewing 2 reply threads

    Please follow the -Lounge Rules- no personal attacks, no swearing, and politics/religion are relegated to the Rants forum.

    Reply To: No IPv6 (via DCHPv6) on WDAG, Sandbox and Hyper-V

    You can use BBCodes to format your content.
    Your account can't use Advanced BBCodes, they will be stripped before saving.