The yellow exclamation mark on your Wi-Fi icon means your device is connected to the router but cannot reach the internet. You're in a network limbo — associated with your Wi-Fi, assigned an IP address, but actual web traffic is going nowhere. The error message is vague; the cause usually is not.
What the Yellow Triangle Actually Means
Windows determines internet connectivity by periodically pinging Microsoft's connectivity check servers (msftconnecttest.com). If those requests fail, Windows marks the connection as "No internet access" even if your network is otherwise functional. This means the error appears when: your actual internet is down, DNS is failing, your IP configuration is incorrect, a VPN is intercepting traffic, or (in public networks) a captive portal is waiting for you to authenticate.
Fix 1 – Proper Router and PC Restart
Power off your modem and router. Wait 30 seconds. Plug in the modem first, wait for it to fully sync (60–90 seconds), then plug in the router. Restart your PC. This clears most network state issues — DHCP lease problems, DNS cache in the router, and temporary outages that look permanent.
Fix 2 – Release and Renew Your IP Address
If your device doesn't receive a valid IP address from the router's DHCP server, it assigns itself an "APIPA" address (starting with 169.254...), which cannot route to the internet. Open Command Prompt as Administrator:
After running, check the output of ipconfig. Your IPv4 address should start with
192.168.x.x or 10.x.x.x — your router's local network range. If you still see 169.254.x.x, the
router isn't assigning addresses correctly — restart it and try again.
Fix 3 – Switch to a Public DNS Server
If your IP is fine but internet still doesn't work, DNS is likely the failure point. Go to Settings → Network andInternet → Wi-Fi → Hardware Properties and set DNS servers manually: preferred 1.1.1.1 (Cloudflare), alternate 8.8.8.8 (Google). Save and open a browser to test immediately. If pages load, your ISP's DNS servers were the problem.
Fix 4 – Reset the TCP/IP Stack
Corrupted network stack configuration causes traffic to be routed incorrectly even when hardware connectivity is fine. Run these in an elevated Command Prompt:
Restart your PC after running all three. This resets the Windows networking stack to factory defaults — safe to run and frequently effective for persistent connectivity issues.
Fix 5 – Check for a Captive Portal (Public Networks)
On hotel, coffee shop, or campus Wi-Fi networks, the "No Internet Access" error usually means a captive portal is waiting for authentication. Open a browser and try to navigate to any HTTP (non-HTTPS) site — try http://example.com. The portal redirect only works on HTTP; if you navigate to an HTTPS site the redirect is blocked by the browser's security checks and you see an error instead. Once you complete the portal authentication, full internet access restores.
Fix 6 – Disable VPN or Proxy Settings
A VPN that has lost connection to its server can enter a "kill switch" state that blocks all traffic while appearing connected to Wi-Fi. Disconnect and disable your VPN completely, then test internet access. Also check Settings → Network and Internet → Proxy — if a proxy server is configured that no longer exists, all traffic fails. Set proxy to Automatic or Off unless you're intentionally using one.
On a home network: Fix 1 (restart router properly) + Fix 2 (IP release/renew) solves it most of the time. On a public network: Fix 5 (captive portal) is almost always the cause. Knowing which environment you're in cuts your troubleshooting time in half.