“Limited connectivity” — the yellow triangle on the Wi-Fi icon — is Windows saying “you’re connected to the network but I can’t reach the internet.” The connection to the router is established. It’s what happens after that’s broken. You’ll find the complete rundown in our Complete Guide to Fixing Windows, Browser, and Software Errors.
First, spend 10 seconds ruling out the most obvious cause: is it just this machine, or everything? Check your phone or another device. If those also have no internet, restart the router — unplug it completely for 60 seconds, plug it back in, wait two minutes. If the phone has internet while your PC shows limited connectivity, the problem is specific to Windows.
From there: open Command Prompt as administrator and run these four commands, then restart:
netsh winsock reset
netsh int ip reset
ipconfig /flushdns
ipconfig /renewThis resolves a large share of limited connectivity cases — they work because the TCP/IP stack or Winsock configuration has accumulated corrupted state that prevents proper routing. After restarting, check whether the yellow triangle is gone.
What the Yellow Triangle Actually Means
Windows tests internet connectivity by sending a request to a Microsoft endpoint at www.msftconnecttest.com/connecttest.txt. If this succeeds, the icon shows connected. If it fails — even though the internet may be working for other purposes — Windows shows “limited connectivity.”
This matters because some situations produce the warning even when everything is fine:
- Captive portals (hotel Wi-Fi, coffee shop networks) — The network is intercepting the connectivity test. Open a browser and complete the login page. The triangle usually disappears within 30–60 seconds of successful login.
- Corporate networks with content filtering — IT’s proxy intercepts the connectivity test and returns an incorrect response. The network works but Windows permanently shows limited connectivity. This is cosmetic — the network is functioning — and resolving it requires IT changing the proxy configuration.
Fix 1: Check the IP Address
Limited connectivity often traces to the machine not getting a valid IP address from the router. When DHCP fails — because the router didn’t respond in time, its pool is exhausted, or the machine had a corrupted lease — Windows assigns itself a fallback address in the 169.254.x.x range. This address can’t reach the internet.
Check: open Command Prompt → ipconfig /all → look at the IPv4 Address for your network adapter. If it starts with 169.254, DHCP failed. Run ipconfig /release then ipconfig /renew to get a fresh address from the router. If the address still shows 169.254 after renewal, restart the router — it may have run out of DHCP addresses to assign.
Fix 2: Change the DNS Server
Limited connectivity where the connection icon shows yellow but pinging the router succeeds (ping 192.168.1.1 from Command Prompt) means the physical connection is fine but DNS is failing. The router is reachable; the wider internet isn’t being translated correctly.
Settings → Network and internet → your active connection → DNS server assignment → Edit → Manual → IPv4 → Preferred DNS: 1.1.1.1 → Alternate: 8.8.8.8 → Save. Switching from the ISP-provided DNS to Cloudflare or Google bypasses whatever DNS problem was occurring upstream. This resolves limited connectivity caused by ISP DNS outages immediately.
Fix 3: Update or Roll Back the Network Adapter Driver
Limited connectivity that started after a Windows Update often traces to the update replacing the working network adapter driver with an incompatible version. Device Manager → Network Adapters → right-click the adapter → Properties → Driver → Roll Back Driver. If Roll Back is greyed out, download the previous driver from the manufacturer’s support page.
For the opposite case — an outdated driver causing the issue — download the current driver from the laptop or motherboard manufacturer’s support page rather than using Windows Update’s version.
Fix 4: Run the Network Troubleshooter
Settings → System → Troubleshoot → Other troubleshooters → Internet Connections → Run. The troubleshooter catches specific categories of limited connectivity: stopped DNS client service, incorrect adapter configuration, and basic driver issues. It takes two minutes and occasionally resolves what the manual commands above missed. Apply any recommended fixes and restart.
Fix 5: TCP/IP and Winsock Deep Reset
When the four commands above didn’t work, a more thorough network reset reinstalls all network adapters from scratch: Settings → Network and internet → Advanced network settings → Network reset → Reset now → confirm. This is the most thorough non-destructive network fix available. It removes VPN adapters and clears saved Wi-Fi passwords — have passwords ready beforehand.
Fix 6: Check Power Management on the Adapter
Windows sometimes powers down network adapters to save energy, and they don’t wake correctly when needed — producing limited connectivity that appears after the machine wakes from sleep. Device Manager → Network Adapters → right-click adapter → Properties → Power Management → uncheck “Allow the computer to turn off this device to save power.” Also check the adapter’s Advanced tab for power-related settings (Energy Efficient Ethernet, Power Save Mode) and disable them.
Fix 7: Check for IPv6 Conflicts
IPv6 configuration problems cause limited connectivity on networks that have partial or broken IPv6 support. Windows may attempt IPv6 routing, get incorrect or no response, and show limited connectivity even though IPv4 is working. Test: Settings → Network and internet → Advanced network settings → More network adapter options → right-click your adapter → Properties → uncheck “Internet Protocol Version 6 (TCP/IPv6)” → OK → test connectivity. If the triangle disappears, IPv6 was the problem on this network.
When Limited Connectivity Appeared After Changing Networks
Machines that move between networks frequently — offices, coffee shops, home — sometimes accumulate network profiles that conflict with the current network. Forgetting the current network and reconnecting creates a fresh profile: Wi-Fi icon → arrow next to network name → Forget → reconnect and enter the password. This resolves cases where an old profile’s cached settings are conflicting with the current network’s configuration.
Our guide on Wi-Fi not working on Windows 11 covers the more severe connection failures where no connection is established at all — sharing several of the driver and stack fixes that also apply here. For DNS-specific failures where the adapter has a valid IP but can’t resolve names, our DNS troubleshooting guide covers the resolver and DNS client service in detail. Microsoft’s connectivity troubleshooting documentation covers the NCA probe mechanism, the specific registry settings that control which endpoint Windows uses to test internet access, and the Group Policy settings for corporate environments where the default connectivity test endpoint is blocked.
Metered Connection Affecting Connectivity
Windows 11 allows marking network connections as “metered” — intended for mobile hotspots and data-capped connections to prevent large background downloads. When a metered connection setting is applied to a standard broadband connection (sometimes applied by Windows automatically after a network change), background services including Windows Update and Microsoft connectivity tests may be restricted in ways that produce the limited connectivity warning.
Check: Settings → Network and internet → your active connection type → look for “Metered connection” toggle. If it’s On for a broadband Wi-Fi or Ethernet connection, toggle it Off. After turning off metered mode, Windows resumes normal background connectivity testing and the icon may resolve within a minute.
DHCP Server Address Exhaustion
Home routers typically come configured with a pool of 50–254 DHCP addresses available for devices. On homes with many connected devices — multiple computers, phones, tablets, smart home devices, gaming consoles, streaming sticks — the DHCP pool can run out of available addresses. New devices that try to connect receive no valid IP and show limited connectivity.
Check whether this applies: router admin panel (usually 192.168.1.1) → DHCP settings → look at how many addresses are assigned vs how many remain in the pool. If the pool is nearly exhausted: increase the DHCP pool range in the router settings (changing the ending address from 192.168.1.150 to 192.168.1.254 adds 104 more addresses). Alternatively, assign static IP addresses to devices you control (computers, printers) so they don’t consume DHCP leases, leaving more for devices that require DHCP.
Limited Connectivity on VPN Networks
When a VPN is active, “limited connectivity” takes on a different meaning. The network adapter may show connected to the local network with limited connectivity because the VPN is handling all internet traffic through its tunnel — the local network adapter’s internet test fails because internet traffic isn’t supposed to go through it. This is expected VPN behaviour, not a fault.
Distinguish this: click the limited connectivity icon → check whether a VPN connection is listed as active. If so, internet access through the VPN tunnel is the intended path. Check that the VPN connection itself shows as connected and try accessing websites — if sites load, the “limited connectivity” on the underlying adapter is cosmetic and the VPN is working correctly. If sites don’t load and the VPN is active, the VPN connection is the problem rather than the local network adapter — see our VPN not connecting guide for that diagnostic path.
Static IP Configuration Conflicts
If the machine was manually configured with a static IP address that’s outside the current router’s DHCP range, or that conflicts with another device on the network, limited connectivity results — the machine has an IP address but it’s not correctly routable on the current network.
Check: Settings → Network and internet → your connection → IP settings. If “Manual” is shown rather than “Automatic (DHCP),” a static IP is configured. Temporarily switch to Automatic and test whether internet access restores. If it does, the static IP configuration needs to be updated to match the current network’s addressing scheme before switching back to manual. For home networks, DHCP automatic assignment is almost always the right configuration — static IPs for home PCs are only useful in very specific scenarios.
Windows Defender Firewall Blocking Connectivity Tests
Windows Defender Firewall can block the outbound requests that Windows uses to test internet connectivity. When the firewall blocks the msftconnecttest.com request, Windows perpetually shows limited connectivity even when the internet is fully accessible for all actual browsing and application use.
Quick test: temporarily disable Windows Defender Firewall (Settings → Windows Security → Firewall → your active network → toggle off) and check whether the limited connectivity warning disappears. If it does, the firewall was blocking the connectivity test. Re-enable the firewall immediately after the test. Rather than leaving the firewall disabled, add an outbound rule that allows connections to msftconnecttest.com — the Microsoft documentation covers the specific IPs and domains used for connectivity testing that need to be in the allowlist for the icon to show correctly.
Large Frame Size and Jumbo Frames
Jumbo frames — large MTU (Maximum Transmission Unit) settings above the standard 1500 bytes — are used in some high-performance network setups. When an adapter is configured for jumbo frames (4088, 9000, or 9014 bytes are common settings) on a network that doesn’t support them, certain connectivity tests fail even though most traffic works. The limited connectivity indicator is often triggered by a small test packet that works while larger actual packets are dropped by the network’s MTU limitation.
Check: Device Manager → Network Adapters → right-click adapter → Properties → Advanced tab → look for “Jumbo Frame,” “Jumbo Packet,” or “MTU” settings. If the value is above 1500, change it to 1514 (standard Ethernet + VLAN tag overhead) or disabled. This is a rare cause but worth checking on machines configured by IT for specific network requirements that may not apply on the current connection.
Router Firmware and Limited Connectivity
Outdated router firmware sometimes causes DHCP lease issues, NAT table problems, or DNS relay failures that produce limited connectivity on specific devices. If the limited connectivity issue affects multiple devices on the network (not just one Windows PC) and resetting the network stack on individual machines doesn’t help, the router itself is the problem.
Update the router firmware: access the router admin panel → find the firmware update section (usually under Administration or Advanced) → check for and install any available updates. Many consumer routers have a one-click update option that downloads and installs the latest firmware automatically. A router firmware update resolves persistent DHCP and routing issues that client-side fixes can’t address because the fault is in the router’s own software rather than any connected device.
One practical observation: limited connectivity that only appears for 30–60 seconds after waking from sleep — and then clears on its own — is not a problem worth troubleshooting. It’s Windows checking connectivity after wake before the network adapter has fully reconnected to the router. The yellow triangle is accurate during that window; the adapter genuinely doesn’t have full connectivity yet. Only persistent limited connectivity (lasting more than 2–3 minutes after a stable wake) or limited connectivity that appeared and hasn’t cleared in days warrants investigation.
