none
Will v6v4tunnel be fixed in final version of April 2018? RRS feed

  • Question

  • All Insider builds starting from at least 17046 cannot start a v6v4tunnel anymore:

    > netsh int ipv6 add v6v4tunnel "IP6Tunnel" 10.0.0.1 10.0.0.2

    There is no driver selected for the device information set or element.

    Will this be fixed in the final rollout of April 2018 update? Or is there any way to fix this error manually?

    Thanks!

    TJ

    Friday, April 27, 2018 1:32 PM

All replies

  • Hi,

    Please don't use Windows 10 insider builds for IPv6. It seems  broke IPv6 with some of the more recent builds. I started out from scratch with the current version (Fall Creators), and the commands ran without issue.

    Also, I will submit this feedback onto our platform. let's see further release.


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Saturday, April 28, 2018 3:02 AM
    Owner
  • Hello Kate,

    I understand that insider builds might not work as well as final builds. So I just updated to the official build of 1803 that was distributed by Windows Update today. Unfortunately, I am still not able to get my v6v4tunnels back to work as they used to in 1607, 1703, and 1709. Please, try to run the commands again on the current April 2018 release and see for yourself that this is broken. How and when will this get fixed?

    Wednesday, May 2, 2018 1:38 PM
  • Read this part

    Features we’re no longer developing

    We are no longer actively developing these features and may remove them from a future update.

    https://docs.microsoft.com/en-us/windows/deployment/planning/windows-10-1803-removed-features

    IPv4/6 Transition Technologies (6to4, ISATAP, and Direct Tunnels) 6to4 has been disabled by default since Windows 10, version
    1607 (the Anniversary Update), ISATAP has been disabled by default
    since Windows 10, version 1703 (the Creators Update), and Direct Tunnels
    has always been disabled by default. Please use native IPv6 support
    instead.

    Wednesday, May 2, 2018 3:32 PM
  • v6v4tunnel uses 6in4, not 6to4. Mentioning it is disabled by default, means it should have been disabled also before in 1607, 1703, and 1709, but it was always working. Also, if it is only disabled, there should be a way to activate it. So this cannot be it. It's a bug that should be fixed.
    Thursday, May 3, 2018 11:00 AM
  • Sorry about that. I thought v6v4tunnel did use 6to4.
    Thursday, May 3, 2018 7:10 PM
  • Hey Kate,

    Still broken in final 1803 build 17134.48.

    Also still broken in 1803 insider build 17661.1001.

    When can we expect a fix for this?

    Wednesday, May 9, 2018 8:37 AM
  • I have feedback this issue in our platform and hope it can be fixed in next release. 

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, May 9, 2018 8:42 AM
    Owner
  • It's still broken in the newest insider build 17672.

    Do you have any news from your engineers, Kate?

    Friday, May 18, 2018 3:53 PM
  • Hello Kate,

    the function is still broken in insider build 17677.1000. Do you have any news from your engineers regarding the next cumulative update in June?

    Friday, May 25, 2018 6:11 PM
  • Hi Kate,

    I have just updated to the newest 1803 build, 17134.81, which was just rolled out by Microsoft on the release channel. Unfortunately, the v6v4tunnel issue hasn't been addressed.

    Do you have any news on the status? Will it be fixed in the next cumulative update?

    Monday, May 28, 2018 10:05 AM
  • I have feedback this issue in our platform and hope it can be fixed in next release. 


    Hi Kate, any news?
    Wednesday, May 30, 2018 4:50 PM
  • Hi Kate,

    I just updated one of my insider program machines to the newest 17682.1000 build, and it's still broken :(

    Can you update me on the situation? You haven't been back in 3 weeks.

    Cheers, T

    Sunday, June 3, 2018 7:27 PM
  • I have feedback this issue in our platform and hope it can be fixed in next release. 
    Hey Kate. Why the silence?
    Friday, June 8, 2018 1:27 PM
  • Really Kate, I need an update on this.

    Insider build 17686.1003 still suffers from this. Microsoft has just decided that either your ISP offers IPv6, or you're doomed, or what?

    Friday, June 8, 2018 5:13 PM
  • Sorry to say that I haven't received any update on if this feature will be fixed in which released version. 

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, June 11, 2018 10:24 AM
    Owner
  • Hm, unfortunately I had to realize it hasn't been addressed in June's cumulative update.

    That is: today's 17134.112 and STILL broken!

    Do you have any information if anyone has decided to look into this problem? From what I can see, it is just that nettun.inf has been kicked out.

    Tuesday, June 12, 2018 5:47 PM
  • Hello Kate. Do you have any news now? Just installed the latest insider preview build 17704 an it is still broken. As workaround you can copy over the old inf&sys files, but that will need at least testsigning-mode, which doesn't work with SecureBoot turned on.
    Monday, July 2, 2018 4:43 PM
  • Hey Kate,

    this is just to let you and everyone know that it has been fixed with insider build 17711. However, my sources told me it seems unlikely it will be backported to build 17134 (or 1803, or Spring Creators Update, or April 2018 update).

    Monday, July 9, 2018 8:34 PM