A peculiar and frustrating symptom: after the Windows 11 24H2 update, your laptop connects to Wi-Fi fine — but only on the slow 2.4GHz band. The 5GHz network either does not appear in the list, appears but refuses to connect, or connects and immediately drops. Everything else about wireless works, which sends most people down the wrong path: rebooting the router, calling the ISP, blaming the walls.
The 2.4GHz-works/5GHz-doesn’t pattern is diagnostic gold. It means the radio hardware is alive, the router is broadcasting, and Windows’ wireless stack functions — the failure is specifically in 5GHz band handling, which lives in the Wi-Fi driver and its advanced settings. And 24H2 is notorious for disturbing exactly that: driver migration, reset band preferences, and new power behavior. Work through the fixes in order.
Why this happens
- Driver migration broke 5GHz negotiation: 24H2’s upgrade installed a Wi-Fi driver build whose 5GHz (VHT/HE) handshake fails with your router.
- Preferred band reset: the adapter’s “Preferred Band” advanced setting reverted to 2.4GHz or “No preference” with broken steering.
- VHT/802.11ac mode disabled: the driver’s 5GHz mode toggle got switched off during migration.
- Aggressive power saving: 24H2’s power defaults let the adapter drop power-hungry 5GHz associations while keeping 2.4GHz.
- Channel compatibility: the router’s 5GHz channel (especially DFS channels) is one the new driver build handles poorly.
- Outdated router firmware vs. new driver: the 24H2-era driver expects behaviors the router’s old firmware does not provide.
- Corrupted wireless profile: the saved 5GHz network profile cached pre-24H2 security parameters that no longer match.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Forget the network and reconnect fresh
Start by clearing the cached wireless profile. 24H2 migrations corrupt saved profiles just often enough that this two-minute step deserves to go first.
- Open Settings > Network & internet > Wi-Fi > Manage known networks.
- Select your 5GHz network (or the combined SSID) and click Forget.
- Restart the Wi-Fi adapter: Settings > Network & internet > Advanced network settings, disable Wi-Fi, wait 10 seconds, re-enable.
- Reconnect to the 5GHz network, carefully re-entering the password.
- If it connects and holds, the profile was corrupt — if your router uses one SSID for both bands, consider temporarily splitting them (see FAQ) to verify the 5GHz band specifically.
Fix 2: Set the preferred band and VHT mode in adapter properties
The driver’s advanced settings directly control band behavior. 24H2 resets these to defaults that deprioritize 5GHz on some adapters.
- Open Device Manager, expand Network adapters, right-click your Wi-Fi adapter, and open Properties > Advanced.
- Find Preferred Band and set it to 5GHz (or “Prefer 5GHz band”).
- Find VHT Mode (or “802.11a/b/g Wireless Mode”) and ensure 5GHz-capable modes are enabled — set to VHT or 802.11ac/ax as available.
- Find Roaming Aggressiveness and set it to a middle value — extremes can cause band-flapping.
- Click OK, disable and re-enable the adapter, and attempt the 5GHz connection.
Fix 3: Install the manufacturer’s 24H2-validated Wi-Fi driver
The core fix for 24H2 5GHz regressions: replace the migrated driver with the manufacturer’s 24H2-validated wireless package for your exact model.
- Identify your Wi-Fi chip in Device Manager (e.g., Intel AX211, MediaTek MT7922, Realtek 8852BE).
- Download the latest Wi-Fi driver from your laptop manufacturer’s support page — look for 24H2-era releases.
- For Intel cards, Intel’s driver detection tool provides the newest validated package.
- Uninstall the current Wi-Fi driver (ticking driver removal), install the downloaded package, then full shutdown and cold boot.
- Recheck the Advanced tab settings from Fix 2 — reinstalls reset them — then test 5GHz.
Fix 4: Disable power saving on the wireless adapter
5GHz operation draws more power than 2.4GHz, and 24H2’s power defaults can sacrifice the 5GHz association to save battery — producing the connects-then-drops pattern.
- In Device Manager, open the Wi-Fi adapter’s Properties > Power Management and uncheck “Allow the computer to turn off this device to save power.”
- In the Advanced tab, set Power Saving Mode (or “Transmit Power”) to Maximum Performance.
- In Power Options > Advanced settings, set Wireless Adapter Settings > Power Saving Mode to Maximum Performance for both battery and plugged-in.
- Test the 5GHz connection on AC power first to isolate battery-policy effects.
- If 5GHz stabilizes, the diagnosis is confirmed — keep maximum performance while plugged in, as with the radio power fixes in our Bluetooth power-management guide .
Fix 5: Change the router’s 5GHz channel
Some 24H2 driver builds handle certain 5GHz channels poorly — particularly DFS channels (52–144) that require radar detection. Moving to a clean non-DFS channel sidesteps the incompatibility.
- Log into your router’s admin page and find the 5GHz wireless settings.
- Change the channel from Auto to a fixed non-DFS channel: 36, 40, 44, or 48.
- Set channel width to 80MHz (or 40MHz for testing) rather than 160MHz — narrower widths negotiate more reliably.
- Save, let the router restart its radio, and attempt the 5GHz connection from the laptop.
- If it connects solidly, the driver/channel combination was the issue — check for router firmware updates as the long-term fix.
Fix 6: Update router firmware and check 24H2 cumulative updates
Both ends of the handshake matter. An old router firmware plus a new 24H2 driver is a classic mismatch; meanwhile, Microsoft shipped 24H2 wireless fixes in cumulative updates.
- Install all pending Windows updates (Settings > Windows Update) — note the build number before and after.
- Check your router manufacturer’s site for firmware updates and install them.
- After both updates, forget the network once more (Fix 1) and reconnect fresh.
- Test 5GHz stability for a day of normal use before declaring victory.
- If problems persist, check Microsoft’s support hub for documented 24H2 wireless regressions affecting your adapter — and see our 24H2 Bluetooth guide for the same update’s parallel wireless-stack issues.
Fix 7: Reset the network stack and test the hardware
If driver, settings, channel, and firmware all check out, reset Windows’ network stack wholesale — then verify the radio hardware with a live USB.
- In an elevated Command Prompt, run
netsh winsock resetandnetsh int ip reset, then restart. - Go to Settings > Network & internet > Advanced network settings > Network reset and reset.
- Reconnect to the 5GHz network fresh after the reset.
- Boot an Ubuntu live USB and test 5GHz there — if Linux connects fine, the Windows driver stack is the fault; try an older manufacturer driver version.
- If Linux also fails on 5GHz while 2.4GHz works, the radio’s 5GHz chain has a hardware fault — the M.2 wireless card is replaceable on most laptops; as a workaround, a USB Wi-Fi 6 adapter restores full 5GHz immediately.
Closing
The 2.4GHz-works/5GHz-doesn’t pattern after 24H2 is a driver-and-settings problem wearing a router-problem costume. Forget the cached profile, set the preferred band and VHT mode explicitly, install the manufacturer’s 24H2-validated Wi-Fi driver, tame the power settings, and check the router’s channel — in that order. One of those layers is where 24H2 broke your 5GHz, and the fix at that layer is permanent. And once 5GHz is stable, lock the working driver against Windows Update; the next “helpful” generic driver is how this whole story started.
