How to fix Wi-Fi problems on Windows 11 by symptom
Wi-Fi problems on Windows 11 break down into distinct failure patterns, and the fix for each one is different. If your Windows 11 Wi-Fi is not working, the fastest path to a solution depends on matching the symptom to the right repair. Running the wrong fix wastes time and occasionally makes things worse. This guide walks you through identifying your specific symptom first, then applying the targeted fix.
Before anything else, two checks:
- Confirm airplane mode is off: open the Action Center (Win + A) and verify the Wi-Fi tile is active
- Test another device on the same router. If nothing on the network has internet, the problem is your router or ISP, not Windows 11. Restart the router, wait 60 seconds, and retest before continuing
Jump to your symptom:
| Symptom | Likely cause | Go to |
|---|---|---|
| No Wi-Fi toggle / no networks visible | Adapter, service, or driver | Step 1 |
| Connected but no internet ("No Internet, Secured") | DHCP, DNS, proxy, or Winsock | Step 2 |
| Wi-Fi drops intermittently | Driver, power management, or roaming | Step 3 |
| Problem started after Windows Update | Bad update or swapped driver | Step 4 |
| Nothing has worked | Full stack reset | Step 5 |
Prerequisites: Local administrator access is required for command-line steps. Have a phone or second device available some commands temporarily drop the network connection.
Step 1: Windows 11 can't detect Wi-Fi networks, or adapter appears dead
If the Wi-Fi toggle is absent from Settings, no SSIDs appear in the network list, or Device Manager shows the adapter with an error, the problem is at the adapter layer before IP addressing even enters the picture.
1a. Check the WLAN AutoConfig service
The Wi-Fi stack in Windows 11 depends on a background service called WLAN AutoConfig. If it's stopped or disabled, the Wi-Fi toggle disappears entirely. Open an elevated Command Prompt and run:
sc query WlanSvc
If the state shows anything other than RUNNING, start it:
sc start WlanSvc
Then confirm it's set to start automatically: open Services (search "services.msc"), find WLAN AutoConfig, double-click it, and set Startup type to Automatic. Helpdesk Hero includes this as a foundational check before any other wireless diagnostic.
1b. Check Device Manager for adapter errors
Open Device Manager (right-click the Start button, select Device Manager) and expand Network adapters. A yellow warning icon on your Wi-Fi adapter means the driver has an error or conflict; no entry at all means Windows isn't detecting the hardware.
If the adapter shows an error, right-click it, select Disable device, wait five seconds, then right-click and select Enable device. If the adapter is missing entirely, click Action, then Scan for hardware changes. If it still doesn't appear, the adapter may be disabled in BIOS, or a Windows Update cycle may have removed the driver. That last scenario is especially common on Windows 11 24H2, where several driver-breaking updates shipped in late 2025, per Helpdesk Hero.
1c. Run a quick connection snapshot
Once the adapter is visible and active, run this in an elevated Command Prompt:
netsh wlan show interfaces
This single command shows the connected SSID, signal strength, radio type, channel, and authentication type, immediately confirming whether the adapter is associating with a network or visible to Windows but not connecting to anything, as Helpdesk Hero explains. If you can see networks now but had none before re-enabling the adapter or starting the service, you're done. If networks appear but the connection fails, continue to Step 2.
Step 2: Fix Windows 11 "No Internet, Secured" Wi-Fi
The "No Internet, Secured" message is one of the most common Windows 11 Wi-Fi complaints. Understanding what it actually means saves a lot of unnecessary router restarts.
"Secured" confirms the WPA2 or WPA3 cryptographic handshake between your adapter and the router completed successfully the wireless link is up, per 404andmore. "No Internet" fires when Windows's internal connectivity probe fails, which can happen because of a corrupted DNS cache, a dead proxy left by uninstalled software, or a broken network stack. None of those involve the router.
2a. Read your IP address to classify the problem
Open an elevated Command Prompt and run ipconfig. Look at the IPv4 address under your Wi-Fi adapter.
- Starts with 169.254: DHCP failed. Windows never received an address from the router and self-assigned a placeholder, according to Reboot Doctor. Restart your router first. If the 169.254 address returns after reconnecting, the router's DHCP pool may be exhausted. Consumer routers often default to 32 or 64 address slots, and a household with 20 or more devices can genuinely run out. Log into your router (usually at 192.168.1.1) and either expand the pool or reduce the lease time to two hours so stale devices release addresses. This is a router problem, not a Windows problem.
- Looks normal (192.168.x.x): The connection itself is fine. The problem is DNS, a leftover proxy, or the network stack. Continue below.
2b. Run the four-command stack reset
Open an elevated Command Prompt and run these in order:
ipconfig /release
ipconfig /flushdns
ipconfig /renew
netsh winsock reset
Restart after the last command. Reboot Doctor puts this sequence at roughly 40% effectiveness for "connected but no internet" cases, with a stale DNS cache or corrupted Winsock catalog as the usual culprit.
The key command is netsh winsock reset. Winsock is the interface that routes all application network requests. VPN clients, antivirus tools, and bandwidth monitors inject custom filters called Layered Service Providers into this layer, and they can break internet access even after the software is uninstalled. The reset strips every one of those hooks and restores Microsoft's default socket configuration, as 404andmore explains in detail.
⚠️ Warning: Don't run these commands over a remote desktop or screen-sharing session. ipconfig /release kills the connection the instant it runs. You need physical keyboard access to continue.
2c. Switch your DNS servers
If the flush didn't resolve it, set DNS manually. Go to Settings, Network & internet, Wi-Fi, Hardware properties, DNS server assignment, Edit, switch to Manual, and enter 1.1.1.1 (Cloudflare) as primary and 8.8.8.8 (Google) as secondary. ISP-assigned DNS is frequently the first thing to fail, per Reboot Doctor.
2d. Check for leftover proxy settings and VPN remnants
Go to Settings, Network & internet, Proxy. If "Use a proxy server" is toggled on and you didn't set it intentionally, turn it off. An uninstalled VPN can leave a dead proxy pointing at a local port that no longer exists, so every outbound HTTP request hits a wall Reboot Doctor describes this as a recurring scenario. Also check Device Manager under Network adapters for any leftover TAP-Windows or TUN adapters from old VPN software; right-click and uninstall them.
2e. Check MAC address randomization
Windows 11 randomizes your adapter's hardware address by default on some networks. If your router uses MAC filtering, it may complete the authentication handshake but then block all outbound traffic because the randomized address isn't on its approved list, per Reboot Doctor and 404andmore. It's an edge case, but worth a look if nothing else has worked. Go to Settings, Network & internet, Wi-Fi, click your network name, Random hardware addresses and set it to Off.
Step 3: Wi-Fi keeps disconnecting
Intermittent disconnects on Windows 11 almost always trace to one of three causes: a driver silently replaced by Windows Update with a generic version, a power management setting that cuts the adapter to save battery, or a chipset with known compatibility issues on 24H2. Helpdesk Hero identifies Windows 11 24H2 as having introduced driver compatibility changes that cause intermittent disconnections specifically on Intel AX200/AX201/AX210/AX211 and MediaTek MT7921/MT7922 chipsets.
3a. Identify your adapter and driver version
Run this in an elevated Command Prompt:
netsh wlan show drivers
Note the adapter name, driver version, and driver date. Then check your manufacturer's current release. If the date is more than a few months old and your problems started recently, a driver mismatch is the likely explanation.
3b. Disable Wi-Fi power management
Open Device Manager, find your Wi-Fi adapter under Network adapters, right-click, select Properties, go to the Power Management tab, and uncheck "Allow the computer to turn off this device to save power." This single change is one of the highest-yield fixes for disconnect issues, per Helpdesk Hero.
3c. Intel adapters: adjust roaming aggressiveness and update the driver
Intel AX200, AX201, AX210, and AX211 adapters drop connections because their default roaming aggressiveness causes the adapter to constantly scan for a stronger access point, often disconnecting mid-session. In Device Manager, open your adapter's Properties, go to the Advanced tab, find "Roaming Aggressiveness," and set it to Medium or Low, per Reboot Doctor.
Download the driver directly from Intel's website, not through Windows Update. Helpdesk Hero specifies that Intel driver version 23.80.x and later resolves most disconnection issues introduced by the 24H2 compatibility changes.
3d. Realtek RTL8821CE: use the OEM driver
The RTL8821CE has a documented track record of instability on Windows 11, particularly on 24H2 and 25H2 builds. Random disconnects, DNS errors, and poor throughput appear even with the latest generic Realtek driver, per HP Support Community. For HP machines specifically, the thread identifies version 2024.10.230.600 (SoftPaq sp162860) as the stable release for the HP 14s-dq2027nf. That version number is specific to that machine check your own manufacturer's support page for the equivalent OEM package. Uninstall the current driver, reboot, then install the OEM package. Set roaming aggressiveness to Medium-Low in the Advanced tab, and if 5 GHz instability persists, force 2.4 GHz only.
⚠️ Hardware note: If none of these steps stabilize an RTL8821CE, the adapter may simply be unreliable on current Windows 11 builds. A USB Wi-Fi dongle from Intel or TP-Link is an inexpensive way out of the problem, per HP Support Community.
Step 4: Repair network connection after Windows 11 update
If Wi-Fi broke immediately after Windows Update ran, treat that timing as a strong diagnostic signal. Act on it before attempting anything else in this guide.
A thread on Microsoft Tech Community documents a case where update KB5086672 caused complete loss of both Wi-Fi and Ethernet no networks visible, no Ethernet connection, while every other device on the same router worked fine. The network troubleshooter and network reset both failed to restore connectivity. Rolling back the update immediately fixed it. Helpdesk Hero confirms that several driver-breaking updates shipped for Windows 11 24H2 in late 2025, so this pattern isn't limited to a single update.
4a. Uninstall the update
Go to Settings, Windows Update, Update history, Uninstall updates. Find the most recently installed update, uninstall it, and restart. If Wi-Fi returns, that update was the cause.
4b. Reinstall the correct driver
Windows Update routinely swaps a working OEM driver for Microsoft's generic Wi-Fi driver during update cycles, per Reboot Doctor. After rolling back the update, go to your device or adapter manufacturer's support page and download the driver directly. If Windows Update immediately reinstalls the generic version again, pause updates under Settings, Windows Update, Pause updates while you confirm the connection is stable.
4c. If you can't access the internet to download a driver
Use your phone as a USB hotspot, or download the driver on a second machine and transfer it via USB drive. The KB5086672 case shows the issue can knock out both Wi-Fi and Ethernet simultaneously, so a wired fallback may not be available either.
After resolving the update-specific breakage, return to Step 2 or Step 3 if the underlying symptom persists.
Step 5: Full network reset last resort only
A full network reset reinstalls all network adapters, erases every saved Wi-Fi network and password, removes VPN configurations, resets firewall rules to default, and clears network-related registry entries, per Tech Ilu. Files and applications are untouched. Microsoft's own documentation positions this as a late-stage step, after targeted fixes have failed, Tech Ilu notes.
Before proceeding: Write down all Wi-Fi passwords and any VPN configuration details. You will need them after the restart.
- Open Settings (Win + I)
- Click Network & internet
- Scroll down and click Advanced network settings
- Under "More settings," click Network reset
- Click Reset now, then Yes to confirm
- Windows restarts automatically
- Reconnect to your Wi-Fi network and re-enter your password
After the restart, recheck connectivity. If the problem returns even after this, the next section explains where to look.
When the problem is probably not Windows
If you've worked through the relevant steps and nothing has stuck, further Windows-side changes are unlikely to help. A few diagnostics will tell you where the fault actually lives.
Run the following in an elevated Command Prompt:
netsh wlan show wlanreport
This generates an HTML report at C:\ProgramData\Microsoft\Windows\WlanReport\wlan-report-latest.html covering the past three days of wireless activity, including every disconnect event and its reason code, per Helpdesk Hero. If the report shows repeated signal drops or low RSSI values rather than authentication or driver errors, the issue is physical distance, interference, or antenna degradation.
Stop troubleshooting Windows when:
- Multiple devices on the same network also lose internet or show instability
- The WLAN report consistently shows signal strength below usable levels
- The adapter is absent from Device Manager and reinstalling drivers doesn't change that
- Rolling back updates and resetting the network stack both failed to restore connectivity
Helpdesk Hero frames Windows 11 Wi-Fi failures as falling into four categories: adapter/driver, authentication, infrastructure, and RF/signal. The last two are outside what any Windows setting can fix. At that point, the candidates are the router, the physical environment (walls, interference, channel congestion), or the Wi-Fi adapter hardware itself.
Comments
Be the first, drop a comment!