Confirm the drops in Event Viewer
Open **Event Viewer** and navigate to **Applications and Services Logs > Microsoft > Windows > WLAN-Autoconfig > Operational**. Look for Event ID 4001 or 8002 around the times your Wi-Fi dropped.
eventvwr.msc
Wi-Fi drops after 25H2 are usually caused by aggressive power management or a generic driver. Fix it in five steps.
The 25H2 update resets **Wi-Fi adapter power settings** and can install a generic driver that drops connections. Disable power saving and roll back the driver to fix it.
Open **Event Viewer** and navigate to **Applications and Services Logs > Microsoft > Windows > WLAN-Autoconfig > Operational**. Look for Event ID 4001 or 8002 around the times your Wi-Fi dropped.
eventvwr.msc
Open **Device Manager**, expand **Network adapters**, right-click your Wi-Fi adapter and select **Properties**. On the **Power Management** tab, uncheck **Allow the computer to turn off this device to save power**.
devmgmt.msc
In the same adapter **Properties** window, go to the **Driver** tab. Click **Roll Back Driver** if available. If not, download the latest driver from your laptop or motherboard manufacturer's support page.
Open **Terminal** as administrator and run the reset commands below. Restart your PC after both commands complete.
netsh winsock reset
netsh int ip reset
ipconfig /flushdns
Leave your PC idle for 30 minutes and check **Event Viewer** again for new WLAN-Autoconfig warnings. Run a continuous ping to your router to confirm zero packet loss.
ping -t 192.168.1.1
The 25H2 update removed your adapter driver. Download the Wi-Fi driver from your laptop manufacturer's support page using a wired connection or phone hotspot, then install it manually.
Run the DNS flush command from step 4 and restart. If it persists, set your DNS to 1.1.1.1 or 8.8.8.8 in adapter properties.
Yes, a USB adapter uses its own driver and is not affected by the 25H2 power management bug on internal adapters.
No. The power management fix in step 2 resolves the issue without rolling back the OS.
No. The bug is specific to Wi-Fi adapter power states.
Re-enable the power saving checkbox in **Device Manager > Network adapters > your adapter > Power Management**. Re-run `netsh winsock reset` and restart to restore the original network stack.
Free · no account needed · tracks your progress