Fix Wi-Fi Speed Drops to a Crawl After a Driver Update on Windows 11
🔍 WiseChecker

Fix Wi-Fi Speed Drops to a Crawl After a Driver Update on Windows 11

Quick fix: Roll back the Wi-Fi driver to the previous version via Device Manager → Network adapters → [Wi-Fi adapter] → Properties → Driver tab → Roll Back Driver. If the rollback button is greyed out, download the previous driver manually from the manufacturer’s site (Intel, Realtek, Qualcomm) and install with Have Disk.

Yesterday your Wi-Fi was fine: 300 Mbps over 802.11ax to a 1 Gbps internet plan. Today after a Windows Update or driver auto-update, speeds collapsed to 20 Mbps. Other devices on the same network are unaffected. The driver update introduced a regression specific to your Wi-Fi chipset, or replaced your vendor driver with Microsoft’s generic one (which lacks vendor-optimized 802.11ax features).

Symptom: Wi-Fi throughput drops dramatically (90%+ slower) after a driver or Windows update; other devices on the same network are unaffected.
Affects: Windows 11 (and Windows 10) with Intel AX2xx, Realtek, Qualcomm, or Broadcom Wi-Fi chipsets.
Fix time: ~10 minutes.

ADVERTISEMENT

What causes this

Windows Update sometimes ships new Wi-Fi drivers automatically through Windows Update. The new driver may have a regression specific to your chipset or your router’s firmware version. Common regressions: dropped support for specific 802.11ax features (OFDMA, MU-MIMO), incorrect band-steering negotiation, or replacing a vendor-optimized driver with Microsoft’s generic Class Driver.

A related cause: a Windows feature update (e.g., 22H2 to 23H2) may have wiped vendor-installed drivers and substituted generic ones. The generic driver works at 5–10% of expected throughput on high-end Wi-Fi 6 chipsets.

Method 1: Roll back the Wi-Fi driver to the previous version

The standard route. Windows keeps one previous driver version for rollback.

  1. Press Win + X, choose Device Manager.
  2. Expand Network adapters. Right-click your Wi-Fi adapter (typically labeled Intel Wi-Fi 6E AX2xx, Realtek 8852, Qualcomm Atheros, etc.). Choose Properties.
  3. Switch to the Driver tab.
  4. Click Roll Back Driver. If greyed out, Windows didn’t keep the previous driver — skip to Method 2.
  5. Choose a reason and click Yes. Windows replaces the current driver with the previous version. Wi-Fi drops briefly during the swap.
  6. Test speed: use fast.com or a speedtest app. You should see your usual full speed.
  7. Prevent re-update: open Settings → Windows Update → Advanced options → Pause updates for 5 weeks. Or pin the rolled-back driver via Group Policy: gpedit.msc → Computer Configuration → Administrative Templates → Windows Components → Windows Update → Manage updates offered from Windows Update → Do not include drivers with Windows Updates → Enable.

This is the right approach when a recent Microsoft-pushed driver is the culprit.

ADVERTISEMENT

Method 2: Install vendor driver manually

For when the Roll Back button is unavailable, or you want a newer driver than Microsoft ships.

  1. Identify your Wi-Fi chipset: in Device Manager, right-click the adapter → Properties → Details tab → Property: Hardware Ids. The first entry shows PCI\VEN_XXXX&DEV_XXXX&.... Vendor ID 8086 = Intel, 10EC = Realtek, 14E4 = Broadcom.
  2. Download the driver directly from the chipset vendor’s site (Intel Download Center, Realtek Drivers section, etc.) — not from Microsoft’s catalog. Pick the one matching your chipset model.
  3. Run the installer. If it’s an EXE, just install. If it’s INF-only: in Device Manager, right-click the adapter → Update driver → Browse my computer → Let me pick from a list → Have Disk → browse to the INF file.
  4. After install, reboot. Wi-Fi disconnects briefly during driver swap.
  5. Verify: Device Manager → right-click the adapter → Properties → Driver tab. Provider should now be Intel / Realtek / Qualcomm (not Microsoft).
  6. Test speed.

Vendor drivers usually have more aggressive band-steering, full 802.11ax feature support, and faster connection times than Microsoft’s generic equivalents.

Method 3: Reset network stack and reconfigure Wi-Fi

For when a driver swap doesn’t restore speeds — indicates corrupted Wi-Fi configuration.

  1. Open Terminal (Admin).
  2. Reset the network stack:
    netsh int ip reset
    netsh winsock reset
    ipconfig /flushdns
    ipconfig /registerdns
    ipconfig /release
    ipconfig /renew
  3. Reboot.
  4. After reboot, “Forget” the Wi-Fi network: Settings → Network & internet → Wi-Fi → Manage known networks → [your network] → Forget.
  5. Reconnect from scratch — enter the password again.
  6. Check the connection details: Settings → Network & internet → Wi-Fi → Properties. Verify Wireless standard shows Wi-Fi 6 (802.11ax) or Wi-Fi 5 (802.11ac) as expected, and Network band shows 5 GHz or 6 GHz, not 2.4 GHz.
  7. If band is stuck on 2.4 GHz: open Device Manager → adapter properties → Advanced tab. Find Preferred Band setting — set to Prefer 5 GHz band.

This handles the case where the driver is correct but the connection settings are wrong.

How to verify the fix worked

  • Run a speed test (fast.com, speedtest.net). Speeds should match what other devices on the same network see.
  • In Settings → Network & internet → Wi-Fi → Properties, the Link speed (Receive/Transmit) should be hundreds of Mbps, not single-digit or low-tens.
  • Run netsh wlan show interfaces. Verify Receive rate and Transmit rate are in the 300+ Mbps range (or higher for Wi-Fi 6/6E).

If none of these work

If Wi-Fi speeds remain low after driver rollback and network reset, the cause may be router-side. Connect a different Wi-Fi device (phone, tablet) to the same router at the same spot — if its speeds are also low, the router or your ISP is the bottleneck. If only your PC is slow, the issue is PC-specific. Check router-side: log into router admin, disable any “client steering” or “band steering” features that may be misbehaving with your laptop’s driver. Disable WPA3 if your card’s driver doesn’t handle it well — use WPA2-AES instead. As a last resort, an external USB Wi-Fi adapter (TP-Link Archer T4U Plus, Asus USB-AX56) bypasses the internal card entirely and uses its own driver. Cheap insurance against a flaky internal card.

Bottom line: A bad Wi-Fi driver from Windows Update is the most common cause — roll back via Device Manager, or install the vendor driver directly. Pause driver updates to prevent recurrence.

ADVERTISEMENT