How to Fix No Internet Connection

No internet connection on Windows most often results from a router or modem fault rather than a problem with the computer. Other frequent causes include an internet service provider outage, a dropped Wi-Fi or Ethernet link, an expired or wrong IP address from DHCP, a DNS lookup failure, a corrupted network stack, an outdated network adapter driver, an IP address conflict, and a VPN or firewall that blocks traffic. This article first lists the specific causes of a lost connection, then gives step-by-step fixes ordered from the fastest checks to a full network reset.

Each fix names the exact Windows tool to use, including the Network troubleshooter, ipconfig, netsh, and Device Manager. Apply the fixes in order and test the connection after each one, because a single fault usually accounts for the whole outage. The goal is a restored connection without contacting support or replacing hardware.

What Causes No Internet Connection?

No internet connection is caused by a break at one point along the path from the computer to the internet service provider. The causes below are ranked from most to least common on Windows.

• An ISP or router outage. A service provider fault or a frozen router stops every device on the network from reaching the internet.
• A dropped Wi-Fi or Ethernet link. A disconnected wireless network or an unplugged cable breaks the physical path before any data leaves the computer.
• A wrong or expired IP address. A failed DHCP lease leaves the adapter with no valid address or an automatic 169.254 address that cannot route.
• A DNS lookup failure. A broken DNS server lets the connection reach the network but blocks every website name from resolving to an address.
• A corrupted network stack. Damaged Winsock or TCP/IP settings stop Windows from sending and receiving traffic correctly.
• An outdated network driver. An old or faulty adapter driver causes the connection to drop or never form.
• An IP address conflict. Two devices assigned the same address cause one to lose access until a new lease is issued.
• A VPN or firewall block. A stalled VPN tunnel or a strict firewall rule blocks all outbound traffic from the computer.

Confirm Whether Other Devices Have Internet

Checking a second device first tells whether the fault is on the computer or across the whole network, which decides every step that follows. A phone or tablet on the same network gives an instant comparison.

1. Open a website on a phone or tablet connected to the same Wi-Fi network.
2. Switch the phone off Wi-Fi onto mobile data to confirm the site loads elsewhere.
3. Note whether the failure affects one device or every device on the network.
4. Treat a network-wide outage as a router or provider fault and start with a power cycle.
5. Treat a single-device failure as a Windows network problem and continue with the steps below.

A failure on every device points to the router, the modem, or the internet service provider. A failure on only the computer points to the adapter, the driver, or the network settings in Windows.

Power-Cycle the Modem and Router

Restarting the modem and router clears a frozen connection and forces a fresh link to the internet service provider, which fixes most network-wide outages. A full power cycle differs from a quick restart because it drains stored state.

1. Unplug the power cable from both the modem and the router.
2. Wait 60 seconds so the devices fully discharge and the provider clears the old session.
3. Plug the modem back in first and wait for its internet light to turn solid.
4. Plug the router back in and wait for its Wi-Fi and internet lights to stabilize.
5. Reconnect a device and load a website to confirm the connection returned.

A combined modem-router unit needs a single power cycle. Check the provider status page or app from mobile data when the internet light stays off or red after the restart.

Run the Windows Network Troubleshooter

The Windows Network troubleshooter detects and repairs common adapter, IP, and DNS faults automatically, which resolves many single-device outages without manual commands. The tool resets the adapter and renews settings as needed.

1. Open Settings, then System, then Troubleshoot, then Other troubleshooters.
2. Find Network and Internet or Internet Connections in the list.
3. Click Run and let the troubleshooter test the adapter, gateway, and DNS.
4. Apply any repair the troubleshooter offers, such as resetting the adapter.
5. Test the connection after the troubleshooter reports its result.

Right-click the network icon in the taskbar and select Diagnose network problems on older Windows builds to reach the same tool. The troubleshooter names the exact stage that failed when it cannot repair the fault.

Renew the IP Address and Flush the DNS Cache

Releasing and renewing the IP address fixes a failed DHCP lease, and flushing the DNS cache clears stale records that block websites from loading. Both run in an elevated Command Prompt with three commands.

1. Type cmd in Windows Search, right-click Command Prompt, and select Run as administrator.
2. Run ipconfig /release to drop the current IP address lease.
3. Run ipconfig /renew to request a fresh address from the router DHCP server.
4. Run ipconfig /flushdns to clear the stored DNS records.
5. Run ipconfig /all to confirm the adapter shows a valid IPv4 address and a default gateway.

An address that starts with 169.254 after a renew means the adapter never reached the DHCP server, which points back to the router or the cable. A valid private address such as 192.168.x.x with a matching gateway confirms the lease succeeded.

Reset the Network Stack with Netsh

Resetting Winsock and the TCP/IP stack repairs corrupted network components that no longer send or receive traffic, which clears outages that survive an IP renewal. The reset returns the network configuration to its default state.

1. Open Command Prompt as administrator.
2. Run netsh winsock reset to rebuild the Winsock catalog.
3. Run netsh int ip reset to restore the TCP/IP stack defaults.
4. Run ipconfig /flushdns to clear the resolver cache again.
5. Restart the computer so the reset takes effect.

A restart is required after the netsh commands, because Windows applies the rebuilt catalog at boot. Reconfigure any static IP or proxy settings afterward, since the reset returns the adapter to automatic configuration.

Update or Reinstall the Network Adapter Driver

Updating or reinstalling the network adapter driver replaces faulty code that prevents the connection from forming or holding. Device Manager lists the wireless and wired adapters under Network adapters.

1. Right-click the Start button and select Device Manager.
2. Expand Network adapters and find the Wi-Fi or Ethernet adapter.
3. Right-click the adapter and select Update driver, then Search automatically for drivers.
4. Select Uninstall device when an update finds nothing, then restart to reinstall the driver.
5. Download the latest driver from the PC or adapter maker when Windows keeps an old version.

Windows reinstalls a default driver automatically after a restart when the adapter is uninstalled. A driver downloaded from the manufacturer site resolves faults that the built-in driver does not, especially on newer Wi-Fi 6 and Wi-Fi 6E adapters.

Change the DNS Server Address

Setting a reliable public DNS server fixes outages where the connection is active but no website name resolves, which a failing provider DNS causes. Cloudflare at 1.1.1.1 and Google at 8.8.8.8 are two public resolvers.

1. Open Settings, then Network and Internet, then select the active Wi-Fi or Ethernet network.
2. Find DNS server assignment and click Edit.
3. Switch from Automatic to Manual and turn on IPv4.
4. Enter 1.1.1.1 as the preferred DNS and 8.8.8.8 as the alternate DNS.
5. Save the change and run ipconfig /flushdns, then load a website to confirm names resolve.

A connection that pings 8.8.8.8 by number but fails to open websites by name confirms a DNS fault. The manual public DNS entries override the provider resolver for every lookup.

Disable the VPN and Check the Firewall

Disabling a VPN and reviewing the firewall restores access when a stalled tunnel or a strict rule blocks all outbound traffic from the computer. A VPN that fails to connect can leave the adapter unable to route.

• Disconnect the VPN. Close the VPN client fully and test the connection with the tunnel down.
• Disable the TAP adapter. Turn off any VPN virtual adapter in Network Connections when the client leaves a dead tunnel behind.
• Reset the firewall. Open Windows Security, Firewall and network protection, and select Restore firewalls to default to clear a blocking rule.
• Confirm proxy settings. Open Settings, Network and Internet, Proxy, and turn off any manual proxy a VPN or tool left enabled.

No Internet Connection Symptoms and Likely Causes

Key Takeaways

• Test a second device first. A network-wide outage points to the router or provider, not the computer.
• Power-cycle before commands. A full modem and router restart clears most whole-network failures.
• Renew the IP address. Releasing and renewing fixes a failed DHCP lease that leaves no valid address.
• Reset the stack when nothing else works. The netsh winsock and TCP/IP reset repairs a corrupted network configuration.
• Rule out DNS and the VPN. A connection with no website access often traces to DNS or a stalled VPN tunnel.

Last Thoughts on No Internet Connection

No internet connection is resolved by working from the fastest checks to a full network reset and testing after each step. Confirming a second device, power-cycling the modem and router, running the Network troubleshooter, and renewing the IP address fix most outages within minutes. When the connection drops repeatedly rather than failing once, the steps to fix Wi-Fi that keeps disconnecting address intermittent wireless faults, and a dead wired link is covered in the guide to fix Ethernet not working.

The hub page listing common PC problems connects every troubleshooting topic. Readers new to the underlying concepts can review how the global network operates in the explanation of what the internet is and how name resolution works in the guide to what DNS is.