Why won’t my wifi adapter connect to my network?

Wifi
1

My wifi adapter suddenly stopped connecting to my home network, even though other devices work fine. I’ve tried rebooting the router, reinstalling drivers, and switching USB ports, but nothing fixes it. I need help figuring out if this is a settings issue, driver problem, or if the adapter is just dead so I know what to replace or change next.

2

This smells like a config issue on the adapter or the router, not hardware dying, since other devices still work.

Run through these in order:

  1. Forget and re-add the network
    • In Windows: Settings → Network & Internet → Wi-Fi → Manage known networks.
    • Remove your home SSID.
    • Reconnect and re-enter the password by hand.
    Typos in saved creds or corrupt profile cause weird stuff like this.

  2. Check band and channel
    • Some USB adapters choke on 5 GHz with certain channels.
    • Log in to your router.
    • Temporarily set Wi-Fi to 2.4 GHz only.
    • Use channel 1, 6, or 11 for 2.4 GHz.
    If it starts working on 2.4 but not 5, your adapter or its driver hates your current 5 GHz setup.

  3. Security mode mismatch
    • Set Wi-Fi security to WPA2‑PSK (AES) only.
    • Avoid mixed WPA2/WPA3 for testing.
    • Avoid TKIP.
    Older or buggy adapters fail to connect with WPA3 or mixed modes.

  4. MAC address filter or access control
    • Check if your router has MAC filtering or parental controls.
    • If enabled, add the adapter MAC to the allowed list.
    • Or disable filtering to test.
    You find the adapter MAC in Windows with:
    Command Prompt →
    ipconfig /all
    Look for Physical Address under the Wi-Fi adapter.

  5. Check if it connects to any other network
    • Phone hotspot, neighbor guest Wi-Fi, public Wi-Fi.
    • If it connects there, problem is in your router config.
    • If it fails everywhere, problem is on the adapter or OS.

  6. Full driver clean install
    • Device Manager → Network adapters → Right click your USB Wi-Fi → Uninstall device.
    • Tick “Delete the driver software” if that option shows.
    • Unplug the adapter.
    • Reboot.
    • Download the latest driver from the chipset vendor, not Windows Update.
    Look for Realtek, Intel, or Mediatek drivers on their own sites.
    • Plug adapter back in and install.

  7. Power saving and USB issues
    • Control Panel → Power Options → Change plan settings → Advanced.
    • Turn off “USB selective suspend”.
    • In Device Manager, under USB controllers and under the Wi-Fi adapter → Properties → Power Management → Uncheck “Allow the computer to turn off this device to save power”.
    USB Wi-Fi sticks often drop or fail to reconnect after sleep due to power settings.

  8. Network stack reset in Windows
    Run Command Prompt as admin and run these one by one:
    netsh winsock reset
    netsh int ip reset
    ipconfig /release
    ipconfig /renew
    ipconfig /flushdns
    Then reboot.

  9. Check for IP conflict or DHCP issues
    • On the PC, after trying to connect, run:
    ipconfig
    • If you see 169.254.x.x on Wi-Fi, DHCP failed.
    • Try setting a static IP in the same range as other devices.
    For example, if your phone has 192.168.1.25 and gateway 192.168.1.1, set:
    IP: 192.168.1.50
    Mask: 255.255.255.0
    Gateway: 192.168.1.1
    DNS: 1.1.1.1 or 8.8.8.8
    If static works and DHCP does not, router DHCP is flaky.

  10. Interference and signal analysis
    If you are in a crowded apartment with tons of overlapping networks, your adapter might struggle more than your other devices.
    Install a Wi-Fi analyzer. A solid option is NetSpot Wi-Fi survey and troubleshooting.
    Use it to:
    • See which channels are overloaded.
    • Check signal strength at your PC.
    • Pick a cleaner channel in your router settings.

  11. Try a different USB port type and cable
    • If you used a front panel USB, move it to a rear port directly on the motherboard.
    • If the adapter heats a lot, use a short USB extension to move it away from the case.
    Some ports have weak power or interference.

  12. Quick Linux live test
    • Boot a Linux live USB (Ubuntu etc) without installing.
    • Try to connect with the same adapter.
    • If it works in Linux but not Windows, your Windows stack or drivers are broken.
    • If it fails in both, the adapter or router config is the culprit.

If you post:
• Adapter brand and exact model.
• Router model.
• OS version.
• Whether you see the network but fail to connect, or it does not show at all.

People here can narrow it down a lot more.

3

Sounds like your adapter and router suddenly decided to hate each other, even though everything else is fine. Since you already tried the obvious stuff and @sternenwanderer covered a ton of the usual suspects, I’ll hit some angles they didn’t dig into as much and disagree a bit on one point.

1. Check what exactly “won’t connect” means

Before anything, nail down the failure point:

  • Do you still see your SSID in the list?
  • When you click it:
    • Does it say “Can’t connect to this network” instantly?
    • Does it hang on “Checking network requirements” forever?
    • Does it connect but with “No Internet” and a yellow triangle?

Each of those points to something different:

  • Instant “can’t connect” = handshake or security issue
  • Hangs forever = often driver or USB / power flakiness
  • Connects but “No Internet” = IP/DHCP or routing problem

This matters more than people think; it’s not just “Wi‑Fi broken.”

2. Don’t fully trust “reinstalling drivers”

I slightly disagree with the idea that a normal driver reinstall is enough. Windows loves to keep old junk around.

What I’d do differently:

  1. Note the adapter’s exact chipset

    • In Device Manager → Properties → Details tab → Hardware Ids
    • You’ll likely see something like USB\VID_0BDA&PID_... which screams Realtek, or Intel, or Mediatek.

  2. Grab the chipset driver, not the “brand” driver

    • Many dongle brands just repackage Realtek drivers and ship ancient versions.

  3. Remove hidden ghost adapters:

    • Command Prompt as admin:
      • set devmgr_show_nonpresent_devices=1
      • devmgmt.msc
    • In Device Manager: View → Show hidden devices
    • Under Network adapters, uninstall every greyed-out Wi‑Fi instance of that device.

  4. Then reinstall the fresh chipset driver.

That can fix weird “it used to work yesterday” issues where a partial update borked something.

3. Check if the SSID itself is the problem

Odd one, but I’ve seen this too many times:

  • Special characters in SSID or password, like ! @ # $ % or super long passwords
  • Some crappy drivers choke on them after a firmware or Windows update

Try this:

  • Temporarily change your Wi‑Fi name to something simple, like Test24 and Test5G
  • Set a short test password: testwifi1234
  • WPA2‑PSK (AES) only, like @sternenwanderer said, but with the simple name + pass

If your adapter suddenly connects to “Test24” but not your old SSID, you found your culprit.

4. Hidden network issues & saved profiles

If you ever used the “Hidden network” option or renamed stuff a few times, Windows can hang on to zombie profiles.

Run these in an admin Command Prompt:

netsh wlan show profiles

Then remove anything related to your home network:

netsh wlan delete profile name='YourOldSSID'

Do this even if you already “forgot” the network in Settings. The GUI sometimes misses leftovers.

5. Try turning off only 802.11n or 802.11ax briefly

On some older or cheap adapters, a half-broken 802.11n or ax implementation can cause exactly what you’re seeing.

In your router’s Wi‑Fi settings, temporarily:

  • Force the 2.4 GHz band to “802.11g only”
  • Or the 5 GHz band to “802.11ac only” (no ax / Wi‑Fi 6)

If it suddenly works, the adapter driver and the router’s newer Wi‑Fi standard are not playing nice.

6. Test with super close distance & minimal interference

Yeah, interference is a thing, but more specifically: badly shielded USB adapters hate being behind a metal PC case.

Try:

  • Plugging the adapter into a rear port with a short USB extension cable
  • Put the adapter somewhere above or away from the metal case
  • Stand near the router for one test

If it suddenly comes alive, it was actually working the whole time but at such a bad SNR it could not complete the handshake.

To see exactly what’s going on with signal and channels, grab something like NetSpot. It lets you scan networks around you, check your signal strength, and find cleaner channels. Their site is here: analyzing and troubleshooting your Wi‑Fi network. It’s way less guesswork than just “try channel 1/6/11 and pray.”

7. Check if Windows updates broke it

Look at:

  • Settings → Windows Update → Update history
  • Note any driver or cumulative updates from around the time it broke

If timing lines up perfectly:

  • Roll back the Wi‑Fi adapter driver in Device Manager (Properties → Driver → Roll Back)
  • Or temporarily uninstall the latest cumulative update and see if the adapter starts working again

This happens more often than anyone wants to admit.

8. OS‑level corruption check

If it fails on your home network and a phone hotspot, and you’re sure the adapter isn’t dead, check for OS rot:

  • Admin Command Prompt:

    sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

Sometimes the network stack fixes @sternenwanderer mentioned are not enough if core system files are damaged.

9. When to suspect the adapter is actually dying

You said other devices work fine. That usually means:

  • Router mostly OK
  • Either:
    • Windows / driver is confused
    • Or the adapter is half-dead

Signs the adapter is on its way out:

  • It randomly disappears from Device Manager until you replug it
  • LED on the adapter behaves differently than it used to
  • Works for a minute, then fully drops, not just “No Internet”

If it also fails in a Linux live session and also cannot connect to any other Wi‑Fi (hotspot etc), at that point I’d stop debugging and replace the thing.

Cleaner, search‑friendly description of what you’re dealing with

Why won’t my Wi‑Fi adapter connect to my home network? My USB Wi‑Fi adapter suddenly stopped connecting to my home Wi‑Fi, even though my phone, laptop, and other devices still connect with no problem. I’ve already tried restarting the router, reinstalling the Wi‑Fi drivers, and switching the adapter between different USB ports on my PC, but nothing has fixed the issue. I need help figuring out whether this is a router configuration problem, a Windows network issue, or a failing USB Wi‑Fi adapter, and what specific troubleshooting steps I should try next to get the connection working again.

4

Since you already hit the “standard” stuff and both @sognonotturno and @sternenwanderer covered a lot, I’d look at angles that explain why your specific adapter and router suddenly dislike each other while everything else is fine.

1. Check if the adapter is being rate-limited or blocked by the router’s “smart” features

Some routers silently apply device isolation, QoS tiers, or “security” auto-block rules:

  • Look for features like:
    • Smart Connect / band steering
    • Access control that is not pure MAC filtering (some routers label it as “Device Management” or “Security events”)
    • AP isolation / “Guest-like” mode for a specific client

Sometimes the router will partially block a device after it repeatedly fails authentication. It might still show in the client list but not be allowed to fully join. Clear any “blocked devices,” disable band steering temporarily, then try again.

I slightly disagree with the idea that this is only a config mismatch. These smart features can behave like a silent firewall between the adapter and the LAN, which feels like a broken adapter when it is really the router being “helpful.”

2. Try a completely different SSID and subnet combo

The others mentioned changing SSID / security, but I’d go one step further and change the subnet too, because some flaky drivers cache assumptions.

For a test:

  1. Create a new temporary WiFi network:

    • New SSID: something clean like TempHome
    • WPA2 AES only
    • 2.4 GHz only at first
    • Router LAN IP: change from 192.168.0.x or 192.168.1.x to something like 192.168.10.1

  2. Reboot the router after the LAN change.

If the adapter suddenly joins TempHome with a new subnet, you know the problem is in the previous combo of SSID + encryption + addressing. That helps narrow whether your old config has some odd cached state or DHCP quirk just for this device.

3. Watch the handshake with a second device

If you have another machine with WiFi that supports monitor mode (Linux laptop, for example), you can watch what happens during the connect attempt:

  • Capture around the time you try to connect
  • Look for repeated authentication attempts or association failures

This is overkill for basic home issues, but since simple steps failed, it can show if your adapter is not finishing the handshake at all or is failing right after.

If you do not want to go that deep, at least check your router’s system log around each failed connect. You may see entries like:

  • Incorrect password
  • Unsupported auth mode
  • Deauthenticated, reason code X

Those reason codes matter.

4. IPv6 and weird DHCP interactions

This part rarely gets mentioned, and I have seen it break only specific adapters:

  • Some drivers freak out if the router is doing:
    • IPv6 with SLAAC along with DHCPv4
    • Or uses unusual DHCP options

Try:

  • Temporarily disable IPv6 on the router
  • Or on Windows: in adapter properties, uncheck “Internet Protocol Version 6 (TCP/IPv6)” just for a test

If the adapter suddenly starts behaving, then your IPv6 or DHCP option set is interacting badly with the driver.

5. Compare behavior with another USB WiFi on the same PC

Since other devices work, the big unknown is: is it Windows on this PC, or this adapter specifically?

  • Borrow a different USB WiFi stick, plug into the same PC, same port
  • Connect to your existing home network with the same settings

Result matrix:

  • Other USB stick works: your old adapter or its driver is the problem, not Windows
  • Other USB stick fails the same way: your Windows network stack or some PC-level security suite is messing with the association or DHCP

At that point, consider security software:

  • Temporarily disable or uninstall third-party firewall / AV
    Some suites hook the network stack in a way that breaks one adapter and not another type.

6. OS-level isolation and profiles in conflict

Windows can get into a strange state if:

  • You had Ethernet and WiFi bridged once
  • Or used Internet Connection Sharing
  • Or have a VPN client that created virtual adapters

Check:

  • In “Network Connections,” verify:
    • No bridges
    • No ICS enabled on the WiFi adapter
    • VPN or virtual adapters are not forcing policy that blocks this physical adapter

Even if this sounds unrelated, virtual NICs plus a flaky driver can produce exactly “can’t connect to this specific network” symptoms.

7. Quick word on NetSpot and why it might help here

NetSpot was mentioned already as a WiFi analyzer. In your case it is useful for more than just “channel crowding”:

Pros:

  • Shows exact signal strength and noise for your network and neighbors
  • Lets you see if your adapter sees a much weaker or unstable signal than your phone in the same spot
  • Helps verify that when you change channels, bandwidth, or band (2.4 vs 5 GHz), the adapter is really seeing those changes

Cons:

  • It will not directly tell you “your driver is broken” or “router security mode mismatch”
  • Free versions tend to be limited if you want advanced surveying or long-term monitoring
  • Requires a bit of interpretation, so it is not as simple as a one-click “fix” app

Used along with router logs, it lets you rule out pure RF problems. If NetSpot shows your adapter has a solid signal and clean channel yet you still cannot stay associated, you can stop chasing interference and focus strictly on config or driver issues.

There are other approaches described by @sognonotturno and @sternenwanderer that target classic misconfigurations and Windows resets. They are good baselines. What you are doing here is the next layer: validating router smart features, IPv6, subnet quirks, and Windows’ more obscure networking features.

If you can post:

  • Exact adapter model and chipset
  • Router model
  • What the router log says when the adapter tries to join

then you can usually go straight to “this is a compatibility bug, just replace the adapter or turn off feature X” instead of endlessly reinstalling drivers.