v6v4tunnel working in builds newer than 17133.1?

I found this out by digging a bit deeper and finding that "nettun.inf" is missing from 1803. 

Yes.  Searching for tunnel with File Explorer shows that there were 11, now there are 10 but they have all been updated?

Also, are you sure that the nettun.inf was used?  Here's a possible way of comparing your two cases

PS C:\Windows\system32> netcfg -v -m | clip
PS C:\Windows\system32> $MV = Get-Clipboard
PS C:\Windows\system32> $MV.count

PS C:\Windows\system32> $MV | sls "\.inf" | sort Line | group Line | ft Count, Name

So, does  nettun.inf  show up?  FWIW I have Tunnel stuff but don't see nettun.inf referenced that way.

No, it doesn't show up on neither of the machines. I only think nettun.inf is involved because it lists the "Microsoft Direct Point-to-Point Tunnel Adapter" which is added when I start a tunnel. Also, after copying the nettun.inf from 1709 over to 1803 and installing it there, the error message of netsh changed to "Element not found". I also tried copying over all registry keys concerning nettun.inf over. I used TrustedInstaller privileges to make sure I am able to access every part of the registry. I also loaded the additional hives "DRIVERS" and "COMPONENTS" into the registry to make sure I will indeed copy everything. However, no success here.

I seem to be at my wits' end here. Hopefully Microsoft will release a fix. I can't understand how they can label IPv6 transition technologies as deprecated. They are clearly still needed in many places.

Do you have one of these?

C:\$GetCurrent\media\sources\hwcompat\nettun.inf_windows_hwcompat.txt

The clue was this.

PS C:\windows\inf> LS -Re -Fi *.log -Fo -EA:SilentlyContinue |% {if ( $(gc $_.FullName -EA:SilentlyContinue) -match "tun
"){$_.FullName}}
C:\windows\inf\setupapi.upgrade.log

which contains this

set: Driver service 'tunnel' owned by 'nettun.inf'.

which was my clue to search the whole drive  

PS C:\windows\inf> cd\
PS C:\> LS -Re -Fi nettun* -Fo -EA:SilentlyContinue | ft FullName

and find the above file.

I'm on my mother's 17134.81.  I tried doing more detailed analysis on my VM but PowerShell kept getting closed for an unknown reason.  Then I forgot to get back to it.

HTH

Robert

---

Hey, no, I don't have this setupapi.upgrade.log. I mean, the problem exists also on fresh installs, not only on upgraded. So it's not a problem of updating per se.

Above first command finds a NetSetupMig.log, but it doesn't mention nettun.inf.

Second command doesn't find anything.

Above first command finds a NetSetupMig.log, but it doesn't mention nettun.inf.

Second command doesn't find anything.

I would have had that result by starting from  C:\Windows\System32 ?  On my mother's machine this is all that would have matched

19:32:39: Adding ms_tcpip_tunnel
19:32:39: Adding ms_tcpip6_tunnel

Anyway here is what that mystery file contains

nettun.inf:
*ISATAP
*6TO4MP
*TUNDIRECT
*TEREDO
*IPHTTPS

I don't want to do a full volume GREP on here but backing out of  %windir%\Inf  and still filtering with just  *.log  finds a few more 

C:\WINDOWS\INF\setupapi.upgrade.log
C:\WINDOWS\Logs\CBS\CBS.log
C:\WINDOWS\Panther\setupact.log
C:\WINDOWS\security\logs\scesetup.log
C:\WINDOWS\System32\NetSetupMig.log
C:\WINDOWS\System32\config\COMPONENTS.LOG2
C:\WINDOWS\System32\config\ELAM.LOG1
PS C:\WINDOWS>

Those LOG2 and LOG1 were unexpected bonuses of what I thought was a tighter search.

Next cumulative update (June 2018)

Build 17134.112 and STILL broken. Really, Microsoft? Network doesn't seem to be an important thing for the Windows OS....

Dear Robert,

I was able to get it running. What I had to do:

1. turn on testsigning

2. copy over nettun.inf&tunnel.sys from 1709

3. using RunAsTi-program I was able to get TrustedInstaller permissions, with this I could copy tunnel.sys into c:\windows\system32\drivers\

4. right-click nettun.inf and click "Install"

However, that only works with testsigning turned on, which also means that I have to turn off SecureBoot in BIOS/UEFI, which is unacceptable in terms of security measures to protect the system from threats.

So, it really boils down to the missing nettun.inf, which needs the correct certificate to run on the current version of Windows.

Hey Robert,

this is just to let you know that Microsoft listened to our demands and fixed the bug with insider build 17711. Probably, it won't be backported to final build of 1803. Everyone who wants to use it has to switch to insinder builds or wait for the release of 1809 this fall.

Small technical details: nettun.inf is not used anymore. Also, no tunneling adapter is visible in device manager anymore. Not sure how it is done now, but it works.

Thank you very much also for your help and efforts, Robert! I really appreciate it!!