How to Fix Wi-Fi Connected but No Internet on Windows 10 and 11

Introduction

The frustrating scenario of seeing your Wi-Fi icon showing full bars yet receiving no internet access is one of the most common networking complaints on Windows 10 and Windows 11. Your device is successfully connected to the local router or access point, but data cannot reach the outside world. This guide covers How to Fix Wi-Fi Connected but No Internet on Windows 10 and 11 in practical, step-by-step detail, suitable for complete beginners and experienced IT administrators who need a reliable reference document.

The problem typically originates from one of five layers: the physical modem or router, the local IP configuration, the DNS resolver, the wireless driver, or Windows network stack corruption. Because the symptom looks identical regardless of root cause, you must work through a structured diagnostic sequence rather than guessing. By the end of this article you will have a repeatable methodology, a set of command-line tools, and clear decision points for escalation.

Before changing any settings, confirm whether other devices on the same Wi-Fi network have internet access. If a phone or tablet also shows “Connected, no internet,” the fault lies with the router or your internet service provider, not Windows. If only the Windows machine fails, continue with the steps below.

Prerequisites

Gather these items and permissions before you begin. Missing prerequisites are the most common reason a fix appears not to work.

• Administrative access to the Windows 10 or Windows 11 device. Standard user accounts cannot reset the network stack.
• A second working internet connection if possible — a mobile hotspot or Ethernet cable is ideal for downloading drivers.
• The make and model of your Wi-Fi adapter, found in Device Manager under Network adapters.
• Your Wi-Fi network password and, for router checks, the router admin credentials.
• At least 30 minutes of uninterrupted time for the full procedure.

Software compatibility with your hardware architecture matters at every stage. Always verify software compatibility with your hardware architecture (ARM64 vs x86). Windows 11 runs on both ARM64 devices such as Surface Pro X and traditional x86/x64 machines. A driver or utility package built for x64 will not install correctly on ARM64, and forcing it can break your wireless stack further. Check Settings > System > About and note the System type field before downloading anything.

Additionally, keeping your operating system updated before installation prevents dependency conflicts. Run Windows Update to completion, including optional driver updates, so that any network component you later install sits on a current servicing baseline.

Preparation

Preparation reduces the risk of losing connectivity mid-repair. Follow these actions in order.

• Create a System Restore point. Search “Create a restore point,” select your system drive, and click Create. If a fix makes things worse, you can roll back in minutes.
• Document your current IP configuration. Open Command Prompt as administrator and run ipconfig /all. Save the output to a text file on a USB drive or in cloud storage.
• Note any static IP addresses, custom DNS servers, or VPN clients currently installed. VPN software frequently causes the exact “connected but no internet” symptom and must be temporarily disabled during testing.
• Disable third-party firewalls and antivirus network shields temporarily. Re-enable them after each successful test.
• Confirm you know how to reconnect to Wi-Fi if you forget a network, because some steps remove saved profiles.

IT administrators managing multiple endpoints should also confirm group policy settings are not overriding network configuration. A domain policy that enforces a proxy server can produce identical symptoms on every managed machine.

Installation Steps

The following six steps form the core repair sequence. They are ordered from lowest risk to highest impact. Stop as soon as internet access is restored and verify with a browser and ping command.

Step 1: Review prerequisites and compatibility

Re-read the prerequisites section and confirm your Windows build. Press Windows key + R, type winver, and press Enter. Write down the version and OS build. For driver downloads, visit the laptop or motherboard manufacturer’s support page rather than relying on generic chipset sites. Verify that any driver package lists Windows 10 22H2 or Windows 11 23H2 (or later) and matches your architecture. If the download page offers only x64 and your device is ARM64, do not install it; look for the OEM-specific package instead.

Step 2: Prepare the environment

Before touching network settings, isolate the fault. Disconnect the VPN, quit any virtual machine software, and turn off mobile hotspots. Restart the router and modem: unplug both, wait 30 seconds, plug the modem in first, wait for its lights to stabilize, then plug in the router. This clears the most common external cause. On the Windows machine, forget and rejoin the Wi-Fi network by going to Settings > Network & internet > Wi-Fi > Manage known networks, selecting your SSID, and choosing Forget. Reconnect and test. If internet works, you are done.

Step 3: Configure core settings

If the problem persists, confirm the adapter is obtaining an address automatically. Open Settings > Network & internet > Wi-Fi > Hardware properties and set IP assignment and DNS server assignment to Automatic (DHCP). Then open Command Prompt as administrator and run these commands one at a time, pressing Enter after each:

• ipconfig /release — drops the current lease
• ipconfig /renew — requests a fresh address from the router
• ipconfig /flushdns — clears the local DNS resolver cache
• netsh winsock reset — resets the Windows sockets catalog
• netsh int ip reset — rewrites the TCP/IP stack registry entries

Restart the computer after the last command. These five commands resolve the majority of software-side causes. Next, temporarily set your DNS to a public resolver: Settings > Network & internet > Wi-Fi > Hardware properties > DNS server assignment > Edit, choose Manual, enable IPv4, and enter 8.8.8.8 and 1.1.1.1. Test again.

Step 4: Run the main installation procedure

This step addresses driver and protocol corruption. Open Device Manager, expand Network adapters, right-click your Wi-Fi adapter, and choose Uninstall device. Check “Attempt to remove the driver for this device” if offered, then restart. Windows will reinstall a clean driver on boot. If internet still fails, download the latest driver from the manufacturer on another device, transfer it via USB, and install it. Verify the installer matches your architecture — an ARM64 device needs an ARM64 driver package. For administrators, the equivalent command-line approach is pnputil /delete-driver oem##.inf /uninstall, where oem## is identified via pnputil /enum-drivers. After driver installation, run sfc /scannow and then DISM /Online /Cleanup-Image /RestoreHealth to repair corrupted system files that can interfere with network services.

Step 5: Verify the installation

Verification must go beyond opening a browser. Run these checks in order:

• ping 127.0.0.1 — confirms the TCP/IP stack is alive.
• ping 192.168.1.1 or your default gateway — confirms local network reachability.
• ping 8.8.8.8 — confirms routing to the internet without DNS.
• nslookup microsoft.com — confirms DNS resolution works.

If ping to 8.8.8.8 succeeds but nslookup fails, the problem is purely DNS; return to Step 3. If the gateway ping fails, the issue is local — check the router or wireless channel interference. If all four pass, open a browser and load two or three different sites to confirm the fix is stable.

Step 6: Configure post-install options

Re-enable any security software you disabled and test again. Restore your original DNS settings if you prefer your ISP or corporate resolver. Reconnect your VPN and confirm it does not reintroduce the fault. For administrators, reapply group policy with gpupdate /force and confirm the machine still reaches the internet after policy refresh. Finally, run Windows Update once more to pick up any driver revisions published after your manual fix.

Post-Installation

After a successful repair, take these steps to prevent recurrence and to document what worked.

• Re-enable all firewalls and antivirus network protection. Confirm browsing still works after each is switched on.
• Record the exact sequence of commands that resolved the issue in your team knowledge base or personal notes.
• Set the Wi-Fi adapter’s power management to not turn off the device to save power, under Device Manager > adapter > Power Management.
• If you use a static IP for work, reapply it only after confirming DHCP works, and document the address, subnet, gateway, and DNS values.
• Schedule a monthly check for driver and firmware updates for both the router and the wireless adapter.

Users who applied a public DNS fix should be aware that some corporate networks block external resolvers. If you later connect to a managed network and lose access, switch DNS back to Automatic.

Troubleshooting

If the six steps above did not restore connectivity, work through these specific failure modes.

How long does it take to complete How to Fix Wi-Fi Connected but No Internet on Windows 10 and 11?

For most users, the core sequence takes 20 to 40 minutes, including reboots. If a driver download is required on a slow connection or you must locate OEM-specific packages for an ARM64 device, allow up to 90 minutes. Administrators pushing fixes via script across multiple machines can resolve each endpoint in under 10 minutes after the script is validated.

Do I need prior Linux experience?

No. Every step in this guide uses native Windows tools: Command Prompt, PowerShell, Device Manager, and Settings. No Linux shell, WSL, or third-party boot environment is required. If a forum suggests using iwconfig or nmcli, that advice does not apply to Windows 10 or 11.

What if an installation step fails?

If netsh or ipconfig returns an error, confirm you opened Command Prompt as administrator. “Access is denied” means the window is not elevated. If driver installation fails with error 0x80070103 or similar, the package architecture likely does not match your device; download the correct ARM64 or.