How to Disable IPv6: Windows Network Settings vs Router-Level Configuration

September 30, 2026
Written By Digital Crafter Team

 

Disable IPv6 in Windows if the problem affects one computer; disable it on the router only if you need a network wide policy. For most home users, changing the Windows network adapter setting is safer, easier to undo, and less likely to break other devices. Router level changes should be handled with more care because they affect phones, laptops, smart TVs, printers, and anything else using that connection.

TLDR: If one Windows PC has VPN, DNS, or app connection issues, turn off IPv6 only on that PC first. For example, in a 25 device small office, disabling IPv6 on one failing workstation may fix the issue without risking the other 24 devices. Router level IPv6 disabling makes sense when your ISP, firewall rules, or monitoring policy requires IPv4 only across the whole network. Test before and after with sites such as test ipv6 tools and keep notes so you can reverse the change fast.

Why people disable IPv6 at all

IPv6 is not “bad.” It is the modern IP standard built to replace IPv4 and solve address exhaustion. Many networks run IPv4 and IPv6 together in dual stack mode. That setup is common and usually works fine.

The trouble starts when part of the chain handles IPv6 poorly. A VPN may leak IPv6 traffic. A DNS server may answer slowly over IPv6. An older firewall may apply strict rules to IPv4 but weak rules to IPv6. Some ISP routers also expose confusing IPv6 options with names that feel half finished. Honestly, it feels like some router menus were written by three teams that never spoke to each other.

Common reasons to disable IPv6 include:

  • VPN compatibility: Some VPN clients route IPv4 well but mishandle IPv6.
  • DNS delays: Browsers may try IPv6 first, wait, then fall back to IPv4.
  • Security policy: A company may want one protocol family to simplify firewall rules.
  • Troubleshooting: Turning IPv6 off briefly can confirm whether it is part of the fault.
  • Legacy software: Old applications may bind to the wrong address type.

Option 1: Disable IPv6 in Windows network settings

This is the best first step for most users. It changes only one computer. If something breaks, you can turn IPv6 back on in under a minute.

On Windows 10 or Windows 11, use this path:

  1. Open Settings.
  2. Go to Network and Internet.
  3. Open Advanced network settings.
  4. Select More network adapter options or open the adapter properties from the classic Control Panel.
  5. Right click your active adapter, such as Wi Fi or Ethernet.
  6. Choose Properties.
  7. Clear the box for Internet Protocol Version 6 TCP/IPv6.
  8. Click OK, then reconnect the network or restart the PC.

This method is simple, visible, and easy to audit. It also avoids changing the behavior of the whole network. That matters if your phone, work laptop, or streaming device works fine with IPv6.

Best use case: One Windows PC has slow website loading, VPN drops, failed remote desktop access, or odd DNS behavior. Disable IPv6 on that machine, test for 10 to 15 minutes, and compare the result.

Main downside: Windows updates and adapter driver changes can sometimes reset network settings. It drives me crazy that a driver update can quietly bring back a setting you thought was settled. Keep a short record of what you changed.

Option 2: Disable IPv6 at the router level

Router level configuration applies to the entire local network. If the router stops offering IPv6, connected devices usually fall back to IPv4. This is cleaner from a policy view, but it carries more risk.

The exact menu depends on the router brand. You may see IPv6 settings under:

  • Internet
  • WAN
  • Advanced settings
  • LAN
  • Firewall
  • ISP protocol

Typical options include Enable IPv6, IPv6 mode, Native, Passthrough, DHCPv6, 6rd, or Prefix delegation. To disable IPv6, you usually turn off the global IPv6 option or set the mode to Disabled. Save the change, reboot the router, then reboot or reconnect client devices.

Best use case: A small business has a firewall policy built around IPv4 only, or a home user confirms that the ISP router is handing out broken IPv6 addresses to every device. In that case, fixing one PC will not solve the broader problem.

Main downside: Every device is affected. A modern phone may behave differently. A game console may change NAT behavior. Some smart home hubs may reconnect slowly. Expect to waste time on device reboots, especially when older printers and cameras decide they need five minutes to “think.”

Windows vs router: which is safer?

Windows level disabling is safer for testing. It limits the blast radius. If the issue is local to one device, there is no good reason to change router behavior for everyone.

Router level disabling is better for consistency. It keeps all devices on the same protocol plan. That can help an IT admin enforce logging, filtering, or VPN rules. It also prevents users from re enabling IPv6 on individual devices without approval.

Factor Windows setting Router setting
Scope One PC Whole network
Risk Low Medium to high
Undo time About 1 minute 5 to 15 minutes, sometimes longer
Best for Troubleshooting one machine Network policy or ISP wide issues

Security concerns

Do not disable IPv6 just because someone says it is unsafe. The real issue is often poor configuration. IPv6 can be secure when firewalls, DNS, VPN software, and endpoint rules all support it correctly.

Still, partial IPv6 support can create blind spots. A firewall may block an IPv4 inbound path but allow an IPv6 path. A VPN may protect IPv4 traffic while IPv6 goes outside the tunnel. That is a serious concern for remote workers and regulated environments.

If privacy is the reason, run a leak test before and after. Check:

  • Your public IPv4 address.
  • Your public IPv6 address, if present.
  • DNS server locations.
  • Whether VPN traffic stays inside the tunnel.

How to verify the change worked

After disabling IPv6, do not trust the checkbox alone. Test it.

  1. Open Command Prompt.
  2. Run ipconfig.
  3. Look for IPv6 addresses under the active adapter.
  4. Visit an IPv6 test website.
  5. Test the original problem, such as VPN login or slow browsing.

If IPv6 is still visible, check for virtual adapters created by VPN clients, Hyper V, VMware, VirtualBox, or security tools. These adapters can keep their own IPv6 settings. Disable IPv6 there only if you understand what that adapter does.

Practical recommendation

Start with the narrowest change. Disable IPv6 on the affected Windows device first. Test carefully. If the issue disappears, you have useful proof without disturbing the rest of the network.

Move to router level configuration only when the evidence points to a network wide fault or when policy demands it. Before changing the router, export the configuration if possible, take screenshots of the original IPv6 settings, and schedule the change when users are not depending on the connection.

The sensible order is simple: test one Windows machine, confirm the result, then decide whether the router needs the same treatment. That keeps the fix controlled, reversible, and easier to explain when someone asks why the Wi Fi printer suddenly went silent.