Illustration of smart-home devices connected through a Wi-Fi router to the internet.
IPv6 has not replaced IPv4 on the public internet. Google's own figures only crossed 50% IPv6 access for the first time on March 28, 2026, and other trackers still put adoption lower. On a typical home network, though, IPv6 is already running: Windows turns it on and prefers it by default, and Thread smart-home gear is built on it. The public-internet story is a slow coexistence rather than a handover, and How-To Geek's recent argument that IPv6 is "secretly winning" at home holds up once you check it against Microsoft's documentation and the standards bodies. For Windows users and admins, the practical point is simple: IPv6 is part of the plumbing now, and Microsoft says switching it off to troubleshoot causes more trouble than it solves.

Google's 50% IPv6 milestone and what it actually measures​

How-To Geek's point that adoption made "a lot of progress" is backed by a dated milestone. The Internet Society reported that 18 years since Google started recording this data, access via native IPv6 has for the first time exceeded 50% (50.10% on 28 March 2026, to be precise). The Register covered the same number and gave the year-earlier baseline: on March 28th, 50.1 percent of the traffic the company detected used IPv6, up from 46.33 percent a year earlier.

The number needs careful reading. APNIC explains that Google's measurements are based on Google's continuous monitoring of the availability of IPv6 connectivity among its users, and reflect the proportion of users who access Google services over IPv6. So it measures people reaching Google, not a count of all internet traffic. It carries weight anyway: The Register notes that Google has a decent view of the internet because its main domain and YouTube are the world's two most-trafficked websites.

It is also a single day, not a new plateau. The Internet Society says access came tantalizingly close to passing the 50% mark a year ago (49.56% on 21 June 2025), but has bumped along below 50% over the last several months. One analysis of the dashboard notes that Google's dashboard fluctuates daily, running higher on weekends (when residential and mobile traffic dominates) and lower on weekdays (when enterprise IPv4 networks weigh more heavily). March 28, 2026 was a Saturday, which fits that pattern. The weekend swing also backs up How-To Geek's thesis: home and mobile networks are where IPv6 is furthest ahead, and offices are where IPv4 hangs on.

Why IPv4 survived: NAT, CGNAT and two internets glued together​

Adoption varies hugely by country. The Internet Society lists France at 73%, India at 72% and Saudi Arabia at 65%, against Italy at 17%, Spain at 10% and Egypt at 4%. Across the several data sources it tracks, its average is about 43%. The Register also notes that other sources don't currently report IPv6 at 50 percent of visible traffic. These trackers measure different things in different ways, so the gaps between them are expected and don't contradict each other.

The reason for the long overlap is in the address format. IANA, which coordinates global IP addressing, describes IPv4 addresses as 32-bit numbers, first deployed on January 1, 1983 and "still the most commonly used version." IPv6 addresses are 128-bit numbers written in hexadecimal, and deployment began in 1999. A 32-bit space gives the roughly 4.3 billion addresses How-To Geek cites. The Internet Society describes IPv4 as able to support "an Internet of a few billion devices", while IPv6 can support an Internet of billions of billions of devices and can provide enough address space to meet the needs of the growing Internet for decades to come.

IPv4 got past that ceiling with address translation. At home, your router's NAT lets every device on the private network share one public IPv4 address. Carrier-grade NAT (CGNAT) does the same thing one level up, letting an ISP share public IPv4 addresses across many customers. Neither is a move to IPv6. They stretch IPv4, which is why How-To Geek describes today's internet as a mix of direct IPv4, IPv4 behind NAT or CGNAT, and native IPv6.

Translation and dual-stack operation are what make this mix work. A dual-stack device runs both protocols and picks one per connection. Google's own history shows how far this has come: the Internet Society notes that in 2008 most users reaching Google over IPv6 relied on transition technologies such as 6to4 and Teredo. Native IPv6 overtook those tunnels in 2010, and their use soon dropped to nothing.

Windows 11 and IPv6: on by default, preferred when available​

This is where the story hits Windows users most directly. How-To Geek says Windows "may actually prioritize" IPv6, and Microsoft's documentation confirms it outright. A Microsoft Learn article on configuring IPv6, which is the former KB 929852, last updated February 12, 2026, says Windows Vista, Windows Server 2008 and later versions implement RFC 3484. They use a prefix table to choose which address to use when a DNS name resolves to more than one. By default, Windows favors IPv6 global unicast addresses over IPv4 addresses.

In practice, a Windows PC on a network with working IPv6 connectivity will often reach dual-stack sites over IPv6 without the user ever touching a setting. The page is labeled for supported Windows Server versions, but the behavior it describes covers Windows Vista and every later client release. That doesn't mean every app or connection uses IPv6. It means the operating system's default is to prefer IPv6 when a usable global IPv6 address and route exist.

How-To Geek also points to the fe80:: addresses that show up in ipconfig. These are link-local addresses, which devices assign themselves so they can talk to neighbors on the same network segment. As the piece says, seeing one doesn't mean you have working IPv6 internet. It only shows the IPv6 stack is running. A global IPv6 address still depends on your ISP providing IPv6 and your router passing it through, and plenty of homes don't have that yet.

Microsoft's warning against disabling IPv6 to fix network problems​

The most useful guidance for WindowsForum readers is Microsoft's position on a very common troubleshooting habit. The Learn article admits that IT administrators often disable IPv6 to troubleshoot problems such as name resolution. Then it pushes back hard. It states that IPv6 is a mandatory part of Windows Vista, Windows Server 2008 and newer versions, and that Microsoft doesn't recommend disabling IPv6, disabling IPv6 components, or unbinding IPv6 from interfaces, because "some Windows components might not function."

Microsoft recommends a different lever: tell Windows to prefer IPv4 through the prefix policy instead of removing IPv6. The article also shows that "off" never fully means off. Microsoft says IPv6 can't be completely disabled because Windows uses it internally for many TCP/IP tasks, so ping ::1 (the IPv6 loopback address) still works after you apply the disable setting.

The same page gives concrete examples of what breaks. On domain controllers, LDAP over UDP port 389 can stop working. Exchange Server 2010 can stop working. Failover Clusters also depend on IPv6. Removing the IPv6 binding from an Ethernet or Wi-Fi adapter with no justifiable need can leave Windows in an unsupported configuration, because Windows is tested with IPv6 bound and some products and features expect it.

Preferring IPv4 in Windows without disabling IPv6​

If an app or network really does behave better over IPv4, this is the supported route Microsoft documents. Editing the registry incorrectly can cause serious problems, so back it up first.

  1. Open an administrative Command Prompt.
  2. Set the DisabledComponents value under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters to hexadecimal 0x20 (decimal 32) with: reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters" /v DisabledComponents /t REG_DWORD /d 32 /f
  3. Restart the computer. The change doesn't take effect until you do.
  4. Run ping bing.com. If IPv4 is now preferred, the reply shows an IPv4 address.
  5. Run netsh interface ipv6 show prefixpolicies and confirm that the ::ffff:0:0/96 prefix has a higher precedence than ::/0.

To undo it, set DisabledComponents back to its default of 0x00 and restart. Microsoft adds some sharp warnings. Values other than 0 or 32 cause the Routing and Remote Access service to fail. The full-disable value is 0xFF. Mistakenly using 0xffffffff adds a five-second delay at startup. The DisabledComponents value also doesn't change the IPv6 checkbox in each adapter's Networking tab, so that checkbox isn't a reliable way to see what state you're in.

One legacy tunnel still matters. According to the same article, Windows enables 6to4 by default when an interface gets a public IPv4 address (anything outside 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16). ISATAP and Teredo are off by default. Admins who don't want 6to4 can set DisabledComponents to 0x01, or disable 6to4, ISATAP and Teredo under Computer Configuration\Administrative Templates\Network\TCPIP Settings\IPv6 Transition Technologies in Group Policy.

Thread and Matter make IPv6 the smart-home default​

How-To Geek's strongest example of IPv6 "winning" at home is the smart home, and it holds up. The Thread Group describes Thread as an IPv6-based, low-power mesh network, which is why How-To Geek says it "was built around IPv6 from the start." Locks, bulbs, sensors and switches on Thread talk to each other over that IPv6 mesh. To reach the rest of your network they go through a Thread Border Router, which routes packets between the Thread mesh and your Wi-Fi or Ethernet devices.

Matter needs more careful wording. It is an IP-based smart-home standard, and the Thread Group says it can run over Ethernet, Wi-Fi or Thread. Thread suits low-power battery devices, while Wi-Fi and Ethernet serve devices with other needs. So "Matter device" doesn't automatically mean "Thread device." What is accurate is that Matter-over-Thread devices run on Thread's IPv6 foundation, and that the Thread Group's Thread 1.3.0 white paper describes border routers connecting Thread devices to existing home IP infrastructure, including service discovery across the Wi-Fi and Ethernet links.

This backs up How-To Geek's larger claim. For large numbers of small devices, IPv6's automatic addressing and huge address space fix what IPv4 can only work around with NAT. The comparison is also a bit lopsided, though. A Thread mesh depends on a working border router, not on whether your ISP offers IPv6. Your smart-home devices can talk IPv6 inside the house even if your internet connection is IPv4-only behind CGNAT.

What this means for you: keep IPv6 on and troubleshoot the right layer​

Most Windows users should do nothing at all. IPv6 is already configured, Windows already prefers it where it works, and your router and devices sort out addressing automatically. The people who need to act are the ones who have disabled IPv6 as a reflex fix, or who manage servers, domain controllers or clusters where Microsoft documents specific failures when IPv6 is removed.

  • Leave IPv6 enabled on Windows. Microsoft calls it mandatory since Windows Vista and warns that disabling it or unbinding it from adapters can break Windows components.
  • If an app works better over IPv4, set DisabledComponents to 0x20 to prefer IPv4, restart, and check with ping bing.com and netsh interface ipv6 show prefixpolicies.
  • An fe80:: address only shows the IPv6 stack is active on your local network. Working IPv6 internet also needs a global address from your ISP and router.
  • Treat Google's 50.1% reading from March 28, 2026 as a one-day, Google-specific measurement. Other trackers, including the Internet Society's roughly 43% multi-source average, still show IPv4 carrying most traffic.
  • For Matter-over-Thread problems, check the Thread Border Router and the local network before blaming your ISP. Thread runs IPv6 inside the home whether or not your internet connection does.

IPv4 will be around for a long time on corporate networks, in countries that lag on deployment, and behind every CGNAT gateway. The Internet Society won't even guess when all of its data sources will show an IPv6 majority. Inside the home, the switch is already well along: Windows has preferred IPv6 since Vista, and every Thread lock and sensor on a shelf today depends on it. For Windows admins, the practical outcome is that the old habit of unticking the IPv6 box has become a support liability, and Microsoft's own documentation says so.

 

Click to expand...
You must log in or register to reply here.