Blog Post
Very cool. Works well (like the preview already did)
It is a good move to leave it disabled by default and let admins (or endusers like myself) until a yet broader community tried it out. I definitely urge application developers to try this out to know in advance if some modifications in their software are needed.
On my part there are two things I am missing (not part of the network team at Microsoft that developed this feature)
- the UI shows "address assignment" as manual for IP in the system settings dialog (ui/system settings team).
- the 192.0.0.x addresses are still registered in dns (on a domain joined computer) (dnscache team I think?).
To application developers: There is a pitfall: you can bind to the 192.0.0.1 address, but sending data to that address does not loop back but instead goes out to the network, to be precise to the ipv6 representation of that address in you current pref64 prefix.
- JimAlumbaughNov 09, 2026
Microsoft
On your first bullet, do you mind unicasting me a screenshot of what you're seeing along with the output of netsh interface clat show instance interface = [interface-name]?
For you send bullet, this issue is fixed but not in a current retail build. You should be able to find it in this Windows Insider Experimental build and later: Windows 11 Insider Experimental (Future Platforms) Preview Build 29683.1000 - Windows Insider Program | Microsoft Learn. It will hit retail in the next release of Windows.
- saxl23Nov 09, 2026Copper Contributor
glad to hear that the loopback issue is already fixed 👍.
The only way one could be hit by this if the application does loopback communication via ipv4 only and not using localhost but the own hostname as destination anyway, so probably not a big deal.
I've sent you the requested image regarding the UI inconsistency. Again, not a real issue since people opening this dialog probably know what they are doing.
The dns registration on the other hand might be something that annoys more people in a managed environment.