Path MTU Discovery Windows Fix – Complete (2026)

Path MTU Discovery Windows fix is essential for anyone experiencing partial connectivity issues where small packets work but large transfers fail. Path MTU Discovery (PMTUD) is the mechanism TCP/IP uses to find the largest packet size that can travel across the entire network path without fragmentation[reference:0]. According to Microsoft documentation, when PMTUD fails, it can cause websites to load partially, downloads to hang, VPN connections to stall, and general network performance to degrade. This comprehensive Path MTU Discovery Windows fix guide covers everything from understanding PMTUD to diagnosing and fixing black hole router issues.

When you search for a Path MTU Discovery Windows fix, you are likely experiencing the classic MTU problem pattern: pings work, web browsing partially works, HTTPS pages load but large downloads hang, SSH connects but hangs after the banner, and VPN tunnels work for small packets but not large transfers[reference:1]. This happens when PMTUD ICMP messages are blocked, breaking the discovery process. In IPv4, this is ICMP “Fragmentation Needed” (Destination Unreachable, Type 3 Code 4); in IPv6, it is ICMPv6 “Packet Too Big”[reference:2]. This Path MTU Discovery Windows fix guide walks you through every step needed to diagnose and resolve these issues.

1. Understanding Path MTU Discovery and Why It Fails

Path MTU Discovery (PMTUD) is the mechanism TCP/IP uses to discover the largest packet size that can travel from your computer to a remote server without being fragmented[reference:3]. MTU stands for Maximum Transmission Unit. On standard Ethernet, the usual MTU is 1500 bytes. On PPPoE DSL links, it is often 1492 bytes. VPNs, tunnels, and some ISP networks may require even smaller packet sizes[reference:4].

PMTUD works by setting the “Don’t Fragment” (DF) bit in the IP header. When a router along the path cannot forward a packet because it is too large and the DF bit is set, it should send back an ICMP “Fragmentation Needed” message (Type 3 Code 4)[reference:5]. However, some routers and firewalls block these ICMP messages. These routers are called “PMTU black hole routers”[reference:6].

Common symptoms of PMTUD failure include:

• Partial connectivity: Small packets work, but large transfers fail[reference:7].
• Websites loading halfway: Some requests hang or time out[reference:8].
• VPN stalling: File transfers freeze or lock up the system[reference:9].
• SSH hanging: Connects but hangs after the banner[reference:10].
• DSLReports Tweak Test showing PMTUD as “off”[reference:11].

According to a Microsoft Q&A discussion, when the effective MTU is reduced (such as over VPN), large file transfers can stall or freeze the system if Path MTU Discovery fails[reference:12]. Understanding these root causes is the first step in any Path MTU Discovery Windows fix guide.

2. Path MTU Discovery Windows Fix: Diagnose with Ping Test

The ping test is the most reliable way to diagnose PMTUD issues. This Path MTU Discovery Windows fix guide starts with this essential diagnostic step.

Step 1: Open Command Prompt as Administrator
- Press Win + R, type "cmd", right-click and select "Run as administrator"

Step 2: Run the ping test with -f (Don't Fragment) flag
- ping -f -l 1472 8.8.8.8
- The -f flag sets the Don't Fragment bit
- The -l flag specifies the data size (1472 + 28 byte header = 1500 total)

Step 3: Interpret the results
- If you get a successful reply, PMTUD is working for this packet size
- If you get "Packet needs to be fragmented but DF set", PMTUD is failing

Step 4: Find the maximum packet size
- Reduce the packet size by 8 or 10 bytes until you get a successful reply
- Example: try 1464, then 1456, 1448, etc.
- The largest successful size + 28 = your path MTU

According to Microsoft’s documentation, the ping command’s size parameter specifies just the size of the ICMP Echo Request data to send, not including the IP and ICMP headers. The ICMP Echo Request header is 8 bytes, and the IP header is normally 20 bytes[reference:13]. So the total packet size is the ping data size plus 28 bytes.

Outcome: The ping test reveals whether PMTUD is working and what your actual path MTU is.

3. Check Current PMTUD Status in Windows

Before applying any Path MTU Discovery Windows fix, it’s helpful to check your current PMTUD and MTU settings.

Check current MTU for all interfaces:
1. Open Command Prompt as Administrator
2. Type: netsh interface ipv4 show subinterfaces
3. Look for your active network interface (Ethernet, Wi-Fi, etc.)
4. Note the MTU value in the output

Check current PMTUD registry setting:
1. Open Registry Editor (regedit) as Administrator
2. Navigate to: HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
3. Look for EnablePMTUDiscovery (REG_DWORD)
4. Default value is 1 (enabled) if present
5. If not present, PMTUD is enabled by default

Check for black hole detection:
1. In the same registry key, look for EnablePMTUBHDetect (REG_DWORD)
2. Default value is 0 (disabled) if present
3. If not present, black hole detection is disabled by default

According to Microsoft’s documentation, the EnablePMTUDiscovery registry entry determines whether TCP uses a fixed, default MTU or attempts to detect the actual MTU[reference:14]. By default, this entry applies to all interfaces and is enabled when present[reference:15].

Outcome: Checking current settings provides a baseline for your PMTUD troubleshooting.

4. Enable PMTUD via Registry (EnablePMTUDiscovery)

If PMTUD is disabled on your system, you can enable it through the registry. This is a critical Path MTU Discovery Windows fix method.

Step 1: Open Registry Editor as Administrator
- Press Win + R, type "regedit", and press Enter

Step 2: Navigate to the TCP/IP parameters key
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

Step 3: Check if EnablePMTUDiscovery exists
- Look for EnablePMTUDiscovery (REG_DWORD)
- If it doesn't exist, create it: Right-click → New → DWORD (32-bit) Value
- Name it: EnablePMTUDiscovery

Step 4: Set the value
- Double-click EnablePMTUDiscovery
- Set to 1 (enabled) or 0 (disabled)
- 1 = TCP attempts to discover the MTU of the path to a remote host[reference:16]
- 0 = TCP uses an MTU of 576 bytes for all connections outside the local subnet[reference:17]

Step 5: Restart your PC for changes to take effect

According to Microsoft’s documentation, by discovering the Path MTU and limiting TCP segments to this size, TCP can eliminate fragmentation at routers connecting networks with different MTUs[reference:18]. Fragmentation reduces TCP throughput and increases network congestion[reference:19].

Warning: Registry editing carries risks. Always back up the registry key before making changes.

Outcome: Enabling PMTUD via registry allows TCP to dynamically discover the optimal packet size.

5. Enable Black Hole Router Detection (EnablePMTUBHDetect)

If you have PMTUD enabled but still experience issues, you may be dealing with a black hole router. Enabling black hole detection is an essential Path MTU Discovery Windows fix for these scenarios.

Step 1: Open Registry Editor as Administrator

Step 2: Navigate to the TCP/IP parameters key
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

Step 3: Create or modify EnablePMTUBHDetect
- Look for EnablePMTUBHDetect (REG_DWORD)
- If it doesn't exist, create it: Right-click → New → DWORD (32-bit) Value
- Name it: EnablePMTUBHDetect

Step 4: Set the value
- Double-click EnablePMTUBHDetect
- Set to 1 (enabled) or 0 (disabled)
- 1 = TCP tries to detect black hole routers[reference:20]
- 0 = Black hole detection is disabled[reference:21]

Step 5: Restart your PC for changes to take effect

According to Microsoft’s documentation, to respond effectively to black hole routers, you must enable the Path MTUBH Detect feature of TCP/IP[reference:22]. Path MTUBH Detect recognizes repeated unacknowledged transmissions and responds by turning off the Don’t Fragment bit[reference:23]. After a datagram is transmitted successfully, it reduces the maximum segment size and turns the Don’t Fragment bit on again[reference:24].

This entry is used only when the Path MTU discovery process is performed, that is, when the value of the EnablePMTUDiscovery entry is 1[reference:25].

Outcome: Enabling black hole detection allows Windows to adapt when routers block ICMP messages.

6. Fix PMTUD by Lowering Interface MTU with netsh

If registry changes don’t resolve the issue, lowering the interface MTU is a reliable Path MTU Discovery Windows fix. According to OneUptime’s guide, you can fix PMTUD issues by lowering the MTU on the interface[reference:26].

Step 1: Open Command Prompt as Administrator

Step 2: Find your interface name
- netsh interface ipv4 show subinterfaces
- Note the name of your active interface (e.g., "Ethernet", "Wi-Fi", "Ethernet 2")

Step 3: Lower the MTU value
- netsh interface ipv4 set subinterface "Ethernet" mtu=1450 store=persistent
- Replace "Ethernet" with your actual interface name
- Replace 1450 with your desired MTU value (based on your ping test results)
- Common values: 1492 (PPPoE), 1480 (VPNs), 1450 (general troubleshooting)

Step 4: Verify the change
- netsh interface ipv4 show subinterfaces
- Your new MTU should appear in the output

Step 5: Test with ping -f -l to confirm the issue is resolved

According to Microsoft Q&A, for VPN connections, you should lower the MTU on the VPN adapter, typically to 1400 or 1350[reference:27]. You can set this using netsh interface ipv4 set subinterface "<VPN Adapter Name>" mtu=1400 store=persistent[reference:28].

Outcome: Lowering the interface MTU prevents fragmentation and resolves PMTUD failures.

7. Fix PMTUD Black Hole with TCP MSS Clamping

When ICMP “Fragmentation Needed” packets are blocked and you cannot change firewall rules, TCP MSS clamping provides a workaround. According to OneUptime’s guide, MSS clamping is used when ICMP fragmentation needed packets are blocked[reference:29].

What is MSS Clamping?
- MSS = MTU - 40 (20 bytes IP header + 20 bytes TCP header)[reference:30]
- MSS clamping forces TCP segments to a smaller size at network edges
- This prevents TCP segments from hitting the MTU ceiling and fragmenting[reference:31]

How to apply MSS clamping:
1. This is typically done at the router level, not on Windows
2. Look for "MSS Clamping" or "MSS Fix" in your router's advanced settings
3. Set the MSS value based on your path MTU
4. Example: For MTU 1450, set MSS to 1410 (1450 - 40)

Alternative: Lower interface MTU
- If you cannot configure MSS clamping on your router, lower the interface MTU on Windows
- This effectively achieves the same result at the client level

According to VPN.how’s guide, MSS clamping is a safety net — it doesn’t fix the road but reduces crash risk[reference:32]. It is particularly effective for VPN tunnels where ICMP messages are often blocked[reference:33].

Outcome: MSS clamping prevents fragmentation when ICMP messages are blocked.

8. Ensure ICMP Messages Are Not Blocked by Firewalls

The root cause of PMTUD failure is almost always either a firewall blocking ICMP Type 3 Code 4 messages or an MTU mismatch in VPN/tunnel configurations[reference:34]. This Path MTU Discovery Windows fix guide recommends checking your firewall settings.

Check Windows Firewall:
1. Open Windows Security → Firewall & network protection
2. Click "Allow an app through firewall"
3. Ensure "File and Printer Sharing" (which includes ICMP) is checked
4. If not, click "Change settings" and enable it

Check third-party firewalls:
- Look for ICMP or ping settings in your security software
- Ensure ICMP Type 3 Code 4 (Destination Unreachable - Fragmentation Needed) is allowed
- For IPv6, ensure ICMPv6 Type 2 (Packet Too Big) is allowed[reference:35]

Check router/firewall settings:
- Log in to your router's web interface
- Look for ICMP or firewall settings
- Enable ICMP messages if they are being blocked
- Some routers have a "Block ICMP" or "Respond to Ping" option

According to Oracle’s documentation, when PMTUD is in use, the sending hosts receive a special ICMP message if they send packets that are too large for the connection[reference:36]. If these messages are blocked, PMTUD fails.

According to Positioniseverything, fixing PMTUD usually means confirming that Windows has PMTUD enabled, checking that routers and security software are not blocking required ICMP messages, and verifying that MTU values match your connection type[reference:37].

Outcome: Allowing ICMP messages restores PMTUD functionality.

9. Fix PMTUD for VPN Connections

VPN connections are particularly susceptible to PMTUD issues because they add encapsulation overhead. According to a Microsoft Q&A discussion, when the VPN is established, the effective MTU is reduced, and large file transfers can stall or freeze the system if Path MTU Discovery fails[reference:38].

Step 1: Identify your VPN adapter name
- netsh interface ipv4 show subinterfaces
- Look for your VPN adapter (e.g., "WireGuard Tunnel", "OpenVPN TAP", etc.)

Step 2: Lower the MTU on the VPN adapter
- netsh interface ipv4 set subinterface "VPN Adapter Name" mtu=1400 store=persistent
- Common VPN MTU values: 1420 (WireGuard)[reference:39], 1400 (general), 1350 (troubleshooting)

Step 3: If the issue persists, try even lower values
- Try 1380, 1360, or 1350[reference:40]
- Test with ping -f -l to confirm

Step 4: Disable offloading features
- Open Device Manager → Network adapters → Properties → Advanced
- Disable Large Send Offload (LSO) and Checksum Offload[reference:41]
- These often conflict with encrypted tunnels[reference:42]

Step 5: Check VPN client logs
- Look for errors like Event ID 20227 or Error 809[reference:43]
- These indicate tunnel instability

According to VPN.how’s guide, WireGuard often recommends MTU around 1420[reference:44]. But if your ISP cuts MTU to 1472 and you’re using VLAN or PPPoE on top, your effective MTU might drop to 1380-1400[reference:45]. The fix is to recalculate and explicitly set the interface MTU[reference:46].

Outcome: Optimizing VPN MTU settings resolves PMTUD-related VPN issues.

10. Frequently Asked Questions

What is Path MTU Discovery (PMTUD)?

Path MTU Discovery (PMTUD) is the mechanism TCP/IP uses to find the largest packet size that can travel from your computer to a remote server without being fragmented[reference:47]. It works by setting the “Don’t Fragment” bit and listening for ICMP “Fragmentation Needed” messages.

How do I test if PMTUD is working on Windows?

Run a ping test with the -f flag: ping -f -l 1472 8.8.8.8. If you get a successful reply, PMTUD is working for that packet size. If you get “Packet needs to be fragmented but DF set,” PMTUD is failing.

What causes PMTUD to fail?

PMTUD fails when ICMP “Fragmentation Needed” messages (Type 3 Code 4) are blocked by firewalls or routers[reference:48]. These routers are called “PMTU black hole routers”[reference:49].

How do I enable PMTUD in Windows?

Open Registry Editor, navigate to HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters, create or modify EnablePMTUDiscovery (REG_DWORD), and set it to 1[reference:50]. Restart your PC for changes to take effect.

What is a black hole router?

A black hole router is a router that drops packets instead of sending ICMP “Fragmentation Needed” messages when it cannot forward a packet[reference:51]. This breaks PMTUD because the sending host never learns that it needs to reduce packet size[reference:52].

How do I enable black hole router detection in Windows?

Open Registry Editor, navigate to HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters, create EnablePMTUBHDetect (REG_DWORD), and set it to 1[reference:53]. This allows TCP to detect and work around black hole routers[reference:54].

What MTU should I use for VPN connections?

For WireGuard, try 1420[reference:55]. For OpenVPN, try 1400 or 1350[reference:56]. For general VPN troubleshooting, start with 1400 and lower if needed[reference:57].

What is TCP MSS clamping?

MSS (Maximum Segment Size) clamping is a technique that forces TCP segments to a smaller size at network edges, preventing them from hitting the MTU ceiling and fragmenting[reference:58]. It is a workaround when ICMP messages are blocked[reference:59].

How do I check my current MTU in Windows?

Open Command Prompt and type netsh interface ipv4 show subinterfaces. Look for your active network interface and note the MTU value[reference:60].

Where can I find more PMTUD troubleshooting help?

Explore our Network Troubleshooting Hub and guides on changing MTU in Windows 11, finding optimal MTU, and packet loss optimization.

11. Conclusion

Path MTU Discovery Windows fix covers everything you need to diagnose and resolve PMTUD issues on Windows 11. From understanding how PMTUD works to enabling it via registry, fixing black hole routers, lowering interface MTU, and optimizing VPN connections, this guide provides all proven methods. According to Microsoft’s documentation, an optimal PMTUD configuration can significantly improve network performance and reliability.

Start with the ping test to diagnose the issue, then apply the appropriate fix based on your findings. For more network optimization, explore our Network Troubleshooting Hub and guides on changing MTU in Windows 11, finding optimal MTU, and packet loss optimization. With the right approach from this Path MTU Discovery Windows fix guide, you can eliminate packet fragmentation, resolve black hole router issues, and keep your network running at peak performance.

For more Windows networking troubleshooting, explore our Windows 11 Troubleshooting Hub and guides on how to update network drivers, DHCP not enabled, and how to change Wi‑Fi channel Windows 11. With the right approach, you can resolve any Path MTU Discovery issues and keep your network running optimally.