Saw this one last week. Customer walks five metres away from the router, Wi-Fi works fine. Sits down next to it, loses connection within 30 seconds. Frustrating as hell, right? Turns out it's not what most people think. It's not that your signal's too strong. Usually it's your device and router arguing about which frequency band to use, or a driver issue. We fixed it in under an hour. Here's what worked.

TL;DR

Wi-Fi disconnects near the router are typically caused by band-steering confusion, outdated drivers, or power management settings, not signal strength. Start with a power cycle and driver update. If that doesn't work, create separate 2.4 GHz and 5 GHz SSIDs to bypass band-steering entirely, or reset your Windows TCP/IP stack.

⏱️ 14 min read ✅ 85% success rate 📅 Updated June 2026

Key Takeaways

Wi-Fi disconnects near the router are caused by band-steering conflicts, not signal strength being too high
Outdated Wi-Fi drivers are a leading cause; download directly from the adapter manufacturer, not Windows Update
Power management settings can cut power to the adapter; disable this in Device Manager
Creating separate 2.4 GHz and 5 GHz SSIDs bypasses problematic band-steering logic
If basic fixes don't work, reset the Windows TCP/IP stack to clear stack corruption

At a Glance

Difficulty: Medium
Time Required: 45 mins
Success Rate: 85% of users report improvement

What Causes Wi-Fi Disconnects Near Router?

Let's start with the wrong answer: no, your signal isn't too strong. That's the first thing people assume, and it's almost never true. Wi-Fi chips don't break down when they're close to a strong signal. What actually happens is much more specific.

Most modern routers broadcast two or three frequency bands at once: 2.4 GHz, 5 GHz, and sometimes 6 GHz (Wi-Fi 6E). When your laptop or phone sits far away, the router might steer you onto one band. As you move closer, the router's software decides to switch you to a different band for better performance, or to balance the load. Here's the problem: if your device driver doesn't handle that handoff smoothly, you drop the connection instead of hopping cleanly to the new band. The router and your adapter don't agree on the timing, and boom, you're disconnected.

Power management is another culprit. Windows can tell your Wi-Fi adapter to sleep or reduce power to save battery, especially on laptops. When you're near the router and the connection is strongest, Windows might think it can be more aggressive with power saving. This causes intermittent disconnects that seem to happen only at close range.

Driver bugs round out the top three. Manufacturers release Wi-Fi drivers with all sorts of edge cases and roaming logic baked in. Older or buggy drivers sometimes can't handle the band-switching speeds that modern routers throw at them. An Intel driver from two years ago might work fine on a mesh router but choke on a newer router's band-steering algorithm.

Finally, router firmware and advanced features can be the culprit. Some routers have Smart Connect, DFS channel avoidance, or multi-link operation (MLO) enabled by default. These features are meant to make things better, but they often cause more trouble than they solve, especially with older devices or specific driver versions.

Wi-Fi Disconnects Near Router Quick Fix

Power Cycle Everything Easy

Shut down your PC completely.
Don't put it to sleep; fully power it off.
Unplug the router (and modem if you have a separate one) for 30 to 60 seconds.
This clears any firmware glitches and resets the connection tables.
Plug in the modem first if you have one, wait for it to fully sync (usually 60 to 90 seconds).
You'll see stable lights on the modem before you plug in the router.
Plug in the router and wait for Wi-Fi to come back up.
This takes about two to three minutes. Wait until the Wi-Fi lights stop blinking.
Boot your PC and reconnect to Wi-Fi.
Test by moving close to the router immediately after connecting.

If this fixes it, you're done. If not, move to the next solution.

Forget and Re-add Your Network Easy

Click the network icon in the system tray and turn Wi-Fi Off.
Wait five to ten seconds.
Turn Wi-Fi back On.
This forces a fresh connection attempt.
Go to Settings > Network & Internet > Wi-Fi > Manage known networks.
You'll see all the Wi-Fi networks your PC has connected to before.
Select your home network and click Forget.
This removes all the cached connection data, roaming profiles, and security settings for that network.
Reconnect by clicking your network SSID and entering the password.
Windows will create a fresh profile with no old roaming logic attached.
Test near the router.
This often clears bad band-steering history.

Many users report this alone fixes the problem, especially if they've been on the same network for months.

Disconnect from Other Saved Networks Easy

Go to Settings > Network & Internet > Wi-Fi > Manage known networks.
Look for multiple entries from the same router (e.g. 'MyWiFi', 'MyWiFi_EXT', 'MyWiFi_Guest').
For each extra SSID, either uncheck 'Connect automatically when in range' or click Forget.
This prevents Windows from trying to hop between networks when you move closer to the router.
Keep only your primary SSID as 'Connect automatically'.
This removes roaming confusion.
Reboot and test near the router.
Windows will now only look for one network.

If you've got guest networks or extended range SSIDs saved, this is often the culprit.

Advanced Wi-Fi Disconnects Near Router Fixes

Reset Windows TCP/IP Stack Advanced

Right-click the Start button and select 'Windows Terminal (Admin)' or 'Command Prompt (Admin)'.
If you see a User Access Control prompt, click Yes to allow admin access.
Run the first command: netsh winsock reset
Wait for it to complete. You'll see 'Successfully reset the Winsock Catalog to a clean state' if it works.
Run the second command: netsh int ip reset c:\resetlog.txt
This resets the TCP/IP stack to defaults. It may take 10 to 20 seconds.
Run the third command: ipconfig /release
This releases your current IP address lease.
Run the fourth command: ipconfig /renew
This requests a fresh IP address from your router's DHCP server.
Run the fifth command: ipconfig /flushdns
This clears the DNS cache in case name resolution is part of the problem.
Close the command prompt and reboot your PC.
Let it fully boot before testing near the router.
After reboot, reconnect to Wi-Fi and test near the router.
The TCP/IP stack is often corrupted by failed driver updates or incomplete uninstalls. This resets it cleanly.

Microsoft recommends these commands to reset the Winsock catalogue and TCP/IP stack when facing persistent connectivity issues. This fixes about 30% of cases where basic fixes don't work.

Clean Reinstall Wi-Fi Driver Advanced

Download the latest Wi-Fi driver from your adapter manufacturer (Intel, Realtek, Qualcomm) to a folder like Downloads.
Unzip the package if it comes as a ZIP file. Don't install it yet.
Right-click the Start button and select Device Manager.
Expand Network adapters and find your Wi-Fi adapter.
Right-click your Wi-Fi adapter and select 'Uninstall device'.
A dialog will pop up. Check the box that says 'Delete the driver software for this device' if it appears. Click Uninstall.
Reboot your PC.
Windows will detect the missing device and reinstall a basic driver. This takes a few minutes.
Once Windows has installed its base driver, right-click the adapter again and select 'Update driver'.
Choose 'Browse my computer for driver software'. Navigate to the folder where you downloaded the OEM driver package and select it.
Let the installation complete and reboot again.
Don't skip this reboot; the driver needs to initialise fresh.
Test near the router.
A clean reinstall often fixes driver corruption that an update alone can't resolve.

Vendor guides recommend a clean uninstall and reinstall when driver updates don't fix intermittent disconnects. This clears any leftover registry entries or conflicting files from old versions.

Adjust Advanced Router Settings Advanced

Log in to your router at 192.168.0.1 or 192.168.1.1.
Go to Wireless or Wi-Fi settings, then look for Advanced options.
Set channel width to a moderate value: 20 or 40 MHz for 2.4 GHz, 40 to 80 MHz for 5 GHz.
Do not use 160 MHz unless you have a specific reason. Wider channels are more prone to interference and driver incompatibility at close range.
Avoid DFS channels (often labelled 'weather radar' channels) on 5 GHz if possible.
DFS channels require the router to detect radar and switch channels dynamically. Some older device drivers don't handle this well.
For Wi-Fi 6 or Wi-Fi 6E routers, look for MLO (Multi-Link Operation) or similar experimental features and disable them.
These are newer features with limited device support and can cause stability issues.
Disable or set to minimum any 'roaming aggressiveness', 'roaming sensitivity', or 'band steering threshold' settings.
These control how fast the router switches your device between bands. Lower values mean less aggressive switching.
Save your settings and reboot the router.
The Wi-Fi will drop for 30 to 60 seconds.
Reconnect and test near the router.
These adjustments reduce the router's aggressiveness, which often stabilises problematic devices.

Router firmware has a lot of hidden knobs that manufacturers don't document well. Turning down the aggressiveness of band-steering and channel width can dramatically improve stability with certain devices.

Running Network Troubleshooters

Windows has built-in troubleshooters that automatically detect and fix certain network misconfigurations. They're not magic, but they catch common problems.

Go to Settings > System > Troubleshoot > Other troubleshooters.
You'll see a list of available troubleshooters.
Run 'Internet Connections' first.
Let it scan and apply any fixes it finds.
Then run 'Network Adapter'.
This checks for driver and adapter-specific issues.
Reboot and test near the router.
These tools reset certain TCP/IP settings and can occasionally fix roaming issues.

They won't solve band-steering problems, but they're worth running as part of your troubleshooting sequence because they're free and sometimes catch things you'd miss manually.

Warning: If you have a VPN client or third-party firewall running, disable them temporarily while testing. Some VPN software intercepts network calls in ways that break roaming logic. If disabling them fixes the problem, check the VPN vendor's documentation for compatibility with Wi-Fi roaming or contact their support.

Preventing Wi-Fi Disconnects Near Router

Once you've fixed it, keep it fixed. Most of these issues come back if you let things slide.

Update Wi-Fi drivers quarterly. Set a calendar reminder to check your adapter manufacturer's support page every three months. New drivers come out regularly and fix stability issues. Don't wait for Windows Update; go directly to the vendor.
Keep router firmware up to date. Log into your router's settings and check for firmware updates. Some routers do this automatically, but many don't. Firmware updates patch roaming and stability bugs that affect all devices.
Use separate SSIDs for 2.4 GHz and 5 GHz if roaming is temperamental. Once you've got them split, leave them split. Don't go back to a combined SSID just because it feels simpler.
Keep your router in the open, not in a cabinet or corner. Position it centrally in your home, elevated off the floor, and away from thick walls and metal objects. Poor placement won't cause close-range disconnects, but it makes overall signal worse and can interact badly with band-steering.
Reboot your router every month. Power it off for 30 seconds, power it back on. This clears transient issues in the firmware that accumulate over time.
Don't stack hot devices on or next to the router. Heat accelerates component failure and can cause intermittent Wi-Fi issues. Keep the router open to air and away from other electronics.
Recheck power management settings after major Windows updates. Windows updates sometimes reset Device Manager settings to defaults. Every time you install a big Windows update, pop into Device Manager and verify that your Wi-Fi adapter's power management setting is still disabled.
Avoid over-customising router settings. Stick to standard WPA2 or WPA3 security, use non-overlapping channels (1, 6, 11 on 2.4 GHz), and leave most advanced features at their defaults. The more knobs you tweak, the more ways things can go wrong.

Wi-Fi Disconnects Near Router Summary

Wi-Fi disconnects near the router are almost never about signal strength. They're about your device and router not agreeing on which frequency band to use, outdated drivers that can't handle modern roaming speeds, or Windows power management cutting the adapter's power at the wrong moment. Start with a power cycle and a driver update. If that doesn't work, disable power management and create separate SSIDs for 2.4 GHz and 5 GHz. These three steps fix about 85% of cases. If you're in the remaining 15%, reset your TCP/IP stack or do a clean driver reinstall. And if none of that works, your router's band-steering or firmware might be the culprit, in which case remote support can help you tune it properly. The key is that this is fixable. It just requires methodical troubleshooting, starting with the simplest fixes and working toward more technical ones.

Wi-Fi disconnects near router