Fix 5GHz Wi-Fi Not Showing Up in Windows 11
I got called out to a friend's place a while back for exactly this: brand-new mesh router, laptop only three years old, and the 5GHz network simply wasn't in the list. Not weak, not slow —absent. She'd already tried the obvious things: restarting the laptop, forgetting the network, moving closer to the router. None of it touched the actual cause, because the actual cause wasn't on her end at all. It was the router's 5GHz radio sitting on a DFS channel that her adapter's driver silently skipped during every scan. This is a more common failure mode than people expect, and it's almost never covered in the generic "restart everything" advice you'll find first.
First, confirm your adapter can even do 5GHz
Before touching router settings, rule out the simplest explanation: some Wi-Fi adapters, especially in older or budget laptops, only support 2.4GHz. Open an elevated Command Prompt or PowerShell and run:
netsh wlan show driversLook at the "Radio types supported" line. If it lists 802.11a alongside 802.11g and 802.11n (or you see modern standards like 802.11ac or 802.11ax), your adapter supports 5GHz. If it lists only 802.11b, 802.11g, and 802.11n without an 802.11a/ac/ax entry, your hardware is 2.4GHz-only and no amount of driver or router tweaking will add 5GHz support you'd need an external USB Wi-Fi adapter that explicitly lists 5GHz or Wi-Fi 5/6 support. This step takes thirty seconds and eliminates an entire category of wasted troubleshooting.
If your adapter does support it, the next most common cause isn't your PC at all. It's how the router's radio negotiated its channel.
DFS channels: the cause almost nobody checks
The 5GHz band spans a wide range of channels, and a chunk of them roughly channels 52 through 144, depending on region fall under Dynamic Frequency Selection (DFS). These channels are shared with weather and military radar, and by regulation, a router has to scan for radar activity before it's allowed to use them and immediately vacate if it detects any. That scan, called a Channel Availability Check, can take anywhere from one to ten minutes on boot, and during that window the 5GHz radio is genuinely not broadcasting the 2.4GHz band keeps working the whole time, which is exactly why it looks like "5GHz vanished" rather than "5GHz hasn't started yet."
Beyond the startup delay, some older Wi-Fi adapter drivers don't scan DFS channels at all during a normal network search, even once the router is broadcasting on one. If your router auto-selected a DFS channel and your adapter's driver just doesn't include those channels in its scan list, you'll never see the network, on any device using that chipset, no matter how many times you restart it.
The reliable fix here isn't chasing driver updates it's moving the router off a DFS channel entirely. Log into your router's admin page, go to the wireless or Wi-Fi settings for the 5GHz band, and manually set the channel to 36, 40, 44, or 48. These sit in the UNII-1 range, aren't subject to DFS, and every 5GHz-capable device made in the last decade can see them without exception.
This one change resolves a surprising share of "5GHz not showing up" cases that otherwise look identical to a driver problem, and I've seen people burn hours reinstalling drivers on three different laptops before finding out the router itself was the variable.
Regulatory domain mismatches are rarer, but nastier when they happen
There's a related but distinct problem: routers and Wi-Fi adapters both operate under a regulatory domain setting (essentially, "which country's spectrum rules apply here"), and that setting determines which 5GHz channels are legally usable. Routers bought in one country and used in another sometimes broadcast on channels that are valid where they were made but restricted where they're actually being used, and depending on the adapter and driver, Windows may simply refuse to show or connect to those channels rather than throwing a clear error about it.
This is the case that's genuinely hard to fix as an end user, and I won't pretend otherwise. There's no supported Windows setting that lets you override your Wi-Fi adapter's regulatory domain the way you can on Linux with tools like iw reg set Windows determines this from a combination of the installed driver and, on many chipsets, information from the system's ACPI tables, and it isn't user-configurable through the interface. If you've confirmed your adapter supports 5GHz, ruled out DFS channels by moving the router to channel 36-48, and you're still not seeing the network while every other device in the house connects fine, a regulatory domain mismatch on that specific adapter is worth suspecting particularly if the laptop or its Wi-Fi card was purchased or replaced from outside your country. At that point you're mostly limited to trying a different driver version from the chipset vendor (Intel, Qualcomm, MediaTek) rather than the Windows Update-supplied one, since regulatory domain handling can differ meaningfully between driver builds.
Symptom, confirming check, and fix
| What you're seeing | How to confirm it | Fix |
|---|---|---|
| No 5GHz network ever appears, on any router | netsh wlan show drivers shows no 802.11a/ac/ax in Radio types supported | Adapter is 2.4GHz-only; use an external USB adapter with confirmed 5GHz/Wi-Fi 5+ support |
| 5GHz appears a few minutes after the router reboots, not immediately | Router admin page shows the 5GHz channel as one of 52-144 | This is normal DFS Channel Availability Check behavior; wait it out, or move the channel to 36-48 to skip it |
| 5GHz never appears no matter how long you wait, other devices also can't see it after a firmware update or router reset | Router's 5GHz radio setting is toggled off entirely in Wireless settings | Enable the 5GHz radio explicitly in router admin; some routers reset this to off after a factory reset |
| 5GHz visible on phones and other laptops, invisible only on this one PC | Router channel is in the 52-144 DFS range and this PC uses an older or budget Wi-Fi chipset | Move the router to channel 36, 40, 44, or 48 (non-DFS) |
| 5GHz visible on this PC in another country/network, invisible on your home network only, adapter confirmed 5GHz-capable | Router or adapter was purchased/imported from a different regulatory region | Try the chipset vendor's own driver instead of the Windows Update version; check router's Country/Regulatory Domain setting matches your actual location |
| 5GHz was working, disappeared after a Windows update | Device Manager shows the Wi-Fi adapter with no warning icon | Update the driver directly from the chipset vendor's site (Intel, Qualcomm, MediaTek, Realtek), not just via Windows Update |
What I would not do
- Don't force "Preferred Band: 5GHz only" in the adapter's advanced properties as a first move. If the network isn't showing up at all, forcing a band preference does nothing there's nothing to prefer. This setting only matters once both bands are already visible and you want to stop Windows from defaulting to 2.4GHz.
- Don't reset the entire TCP/IP stack for a network that isn't even appearing in the scan list. A missing SSID is a radio/scanning problem, not a connectivity or IP configuration problem;
netsh winsock resetand similar commands fix a different category of issue and won't make an invisible network visible. - Don't buy a new router assuming yours is defective before you've checked its channel and Country/Regulatory setting. I've seen this exact purchase made and the replacement router hit the identical DFS-channel default a week later.
- Don't disable and re-enable the network adapter over and over hoping repetition helps. It's a legitimate one-time step to clear a stuck adapter state, not a fix you improve by repeating five times in a row.
The verdict
If I had to bet on the single most likely cause of "5GHz just isn't there" on a Windows 11 machine that used to see it fine, I'd bet on a DFS channel before I'd bet on a driver bug. Move the 5GHz band to channel 36, 40, 44, or 48 in your router's settings, give it a minute to restart the radio, and check again before you touch anything on the Windows side. It's the fix that actually addresses why the network is invisible, rather than the fix that just happens to be first in most troubleshooting lists.