Few things sting like finishing a major Windows update and discovering your laptop can no longer see a single wireless network. After the 24H2 update, forum threads filled up with exactly this complaint: Wi-Fi adapters vanished from Device Manager, networks showed “no networks found,” or connections dropped every few minutes. The community has been hammering on this problem long enough that the effective fixes are well mapped.

This guide collects the fixes that real users report actually working, ordered from safest to most aggressive. You do not need to try exotic registry surgery first; start with the driver rollback that resolves most cases and escalate only if your adapter stays dark.

Before starting, confirm the scope: is Wi-Fi broken for all networks or just yours, and does the adapter appear in Device Manager at all? An adapter missing from Device Manager points at drivers or hardware, while an adapter present but unable to connect points at configuration. Knowing which saves you from trying fixes for the wrong problem.

Why this happens

  • Incompatible driver pushed by the update: 24H2 installs a newer Wi-Fi driver that your adapter firmware cannot handle.
  • Adapter disabled by power management: The update resets power settings so Windows powers down the radio.
  • Corrupted network stack: The upgrade process can leave Winsock or TCP/IP configuration in a broken state.
  • Fast Startup conflicts: Hybrid shutdown holds stale driver state across the update.
  • BIOS/UEFI interaction: Some adapters need a firmware-level reset the update never triggers.
  • VPN or filter drivers: Old virtual adapters from VPN software block the real adapter after the upgrade.
  • Hardware actually failing: Rare, but the update’s timing can coincide with a dying card.
  • Driver signature enforcement quirks: 24H2’s stricter driver validation rejecting older signed drivers.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Roll back the Wi-Fi driver

  1. Press Win + X and open Device Manager, then expand Network adapters.
  2. Right-click your Wi-Fi adapter, choose Properties, and open the Driver tab.
  3. Click Roll Back Driver if it is available and pick any reason; this restores the pre-24H2 driver.
  4. Restart and test. This single step fixes the majority of post-24H2 Wi-Fi failures, because the pushed driver is usually the culprit.
  5. If Roll Back is greyed out, Windows has no previous driver stored — proceed to Fix 2 instead.
  6. After rolling back, open the driver’s Properties again to confirm the version actually changed.

Fix 2: Install the manufacturer’s driver directly

  1. Identify your adapter model in Device Manager (Intel AX200, Realtek 8852, MediaTek, and so on).
  2. On another device, download the latest driver from the adapter maker’s site — Intel’s Driver and Support Assistant automates this for Intel cards.
  3. Transfer the installer by USB and run it on the laptop, choosing a clean install if offered.
  4. Restart and confirm networks appear. Manufacturer drivers are consistently more reliable than the ones Windows Update selects.
  5. During installation, choose a clean install option if offered to remove the bad driver’s remnants.
  6. After installing, disable automatic driver updates for the adapter so Windows Update does not reinstall the broken version.

Fix 3: Disable power management on the adapter

  1. In Device Manager, right-click the Wi-Fi adapter and open Properties, then the Power Management tab.
  2. Uncheck Allow the computer to turn off this device to save power.
  3. Also go to Settings > System > Power & battery and set the Wi-Fi power saving options to maximum performance.
  4. Test for a full day. Adapters that drop every few minutes are usually victims of aggressive power saving.
  5. In Device Manager’s Advanced tab, disable any power-saving or sleep-on-idle properties for the adapter.
  6. Test with the laptop plugged in versus on battery — differing behavior confirms a power cause.

Fix 4: Reset the network stack

  1. Open an elevated Command Prompt.
  2. Run these in order: netsh winsock reset, netsh int ip reset, ipconfig /release, ipconfig /renew, ipconfig /flushdns.
  3. Restart the laptop; do not skip the restart, as the reset only completes on boot.
  4. If wireless still fails, use Settings > Network & internet > Advanced network settings > Network reset as the heavier alternative. Related stuck-update issues are covered in our guide on updates that freeze while downloading .
  5. After the network reset, you will need to re-enter Wi-Fi passwords — have them handy before you begin.
  6. Reinstall VPN clients after the reset, since it removes their virtual adapters.

Fix 5: Disable Fast Startup

  1. Open Control Panel > Power Options > Choose what the power buttons do.
  2. Click Change settings that are currently unavailable.
  3. Uncheck Turn on fast startup and save changes, then do a full Shut down (not Restart).
  4. Power on fresh. Fast Startup preserves driver state across reboots, which can lock a broken adapter state in place.
  5. After disabling Fast Startup, perform two full shutdown-and-power-on cycles to fully clear the stale state.
  6. Leave Fast Startup off permanently if the problem recurs — the boot-time cost is minor.

Fix 6: Remove stale VPN and filter drivers

  1. In Device Manager, enable View > Show hidden devices.
  2. Expand Network adapters and uninstall greyed-out entries and old VPN virtual adapters (TAP, WAN Miniport leftovers).
  3. Do not uninstall your physical Wi-Fi adapter unless you have its driver ready to reinstall.
  4. Restart. Orphaned filter drivers are a well-documented post-upgrade Wi-Fi killer.
  5. Note which VPN or filter you removed; update it to a 24H2-compatible version before reinstalling.
  6. If Wi-Fi works with filters removed, reinstall them one at a time to identify the offender.

Fix 7: Reset BIOS and reseat the card (last resort)

  1. Restart into BIOS/UEFI and choose Load optimized defaults, then save and exit.
  2. If the adapter still misbehaves and your laptop allows it, power off, unplug, and reseat the M.2 Wi-Fi card.
  3. Check the antenna wires are firmly attached to the card’s terminals.
  4. If nothing revives it, the card may have genuinely failed; a replacement Intel AX210 card is inexpensive and widely compatible.
  5. Before buying a replacement card, test with a USB Wi-Fi adapter to confirm the internal card is the problem.
  6. When replacing, match the card’s form factor (usually M.2 2230) and antenna connector count.

Closing

Post-24H2 Wi-Fi failures look catastrophic but are almost always a driver mismatch the community has already solved. Roll back, install the manufacturer’s driver, and tame power management before you touch anything drastic. Once you are back online, pause driver updates in Windows Update so the bad driver does not return. And if the update process itself is misbehaving, see our guide on 24H2 update problems more broadly . Document which fix worked — if 24H2’s successor does the same thing, you will know exactly where to start. Community wisdom is cumulative; consider sharing your result in the threads that helped you.

Frequently asked questions

Why does Wi-Fi stop working after the 24H2 update?
The 24H2 update replaces your Wi-Fi driver with a version from Windows Update that may be incompatible with your adapter, or it resets network stack settings your old driver depended on. In some cases the update also changes power management behavior, letting Windows turn the adapter off. All three failure modes are reversible without reinstalling Windows.
Should I trust Reddit fixes for Wi-Fi problems?
Community fixes are valuable because they are tested on real hardware combinations Microsoft never validated, but apply them with judgment. Driver rollbacks and network resets are safe. Registry edits from random threads deserve caution: back up the key first and verify the advice appears in multiple independent threads before applying it.
Will rolling back the Wi-Fi driver break anything else?
No. Rolling back only affects the wireless adapter driver and does not touch the rest of the system. Your other drivers, settings, and files are unaffected. If the rollback does not help, you can update the driver again to return to the newer version.
How do I get online if Wi-Fi is completely dead?
Use a USB Ethernet adapter, a phone tethered over USB, or download the driver on another device and transfer it by USB stick. You need some connection to fetch a fixed driver, so solve the connectivity problem first with whatever alternative you have available.