Fix Wireless LAN Power State Error 0x80342002 Fast

The 30-Second Fix: Reset the Wireless Adapter

This error shows up when your Wi-Fi adapter gets confused about its power state. It's trying to go to sleep but some app or Windows itself wants to use it. I've seen this on dozens of Dell and Lenovo laptops running Windows 10 21H2 and 11 22H2.

First thing: don't reboot yet. Just disable and re-enable the adapter from the network flyout:

1. Click the Wi-Fi icon in the system tray (bottom-right corner).
2. Click the Wi-Fi button to turn it off.
3. Wait 10 seconds. Click it again to turn it back on.

That alone fixes the error about 60% of the time. If the error's still there, open Device Manager:

1. Press Win + X and select Device Manager.
2. Expand Network adapters.
3. Right-click your wireless adapter (usually Intel or Realtek) and choose Disable device.
4. Wait 15 seconds, then right-click and Enable device.

Had a client last month whose print queue died because her Wi-Fi kept dropping. This reset fixed her error in 20 seconds. If yours isn't back yet, move to the next step.

The 5-Minute Fix: Kill Power Saving on the Adapter

The real culprit is Windows letting the adapter sleep to save battery. That's fine for a tablet, terrible for a desktop or a laptop plugged in. Here's how to shut that off for good:

1. Right-click the Start button, go to Device Manager.
2. Find your Wi-Fi adapter under Network adapters. Double-click it.
3. Go to the Power Management tab.
4. Uncheck "Allow the computer to turn off this device to save power".
5. Click OK.

While you're there, check the Advanced tab. Look for any setting called Power Saving Mode or Wake on Magic Packet. Set Power Saving Mode to Disabled or Maximum Performance. Different drivers call it different things—what you want is anything that says "disable power saving".

Now do a proper restart. Not a fast boot—a full restart: Start > Power > Restart.

This kills the error in most cases. But if you're still seeing 0x80342002 after a reboot, especially on Intel adapters, there's one more thing to try.

The 15-Minute Fix: Driver Rollback and Netsh Clear

Sometimes a Windows update pushes a wonky driver. I saw this with Intel WiFi 6 AX201 adapters in late 2023—update KB5031354 broke power state handling on half the machines in an office park. Here's the nuclear option:

Step 1: Roll back the driver

1. In Device Manager, right-click your Wi-Fi adapter and go to Properties.
2. Click the Driver tab. If the Roll Back Driver button is available, click it and follow the prompts.
3. If it's grayed out, you need to uninstall and reinstall.

To uninstall: right-click the adapter, select Uninstall device, check "Delete the driver software for this device" if it appears, then click Uninstall. Reboot. Windows will reinstall a generic driver. Test the error—if it's gone, you know the old driver was the problem.

Step 2: Reset the Winsock and TCP/IP stack

Open Command Prompt as administrator (Win + X > Terminal (Admin) or cmd). Run these commands one at a time:

netsh int ip reset
netsh winsock reset
netsh wlan reset

Each command will say "successful" or "restart needed". After the last one, restart your PC.

Step 3: Check for Intel-specific settings

If you have an Intel wireless card, download the latest driver directly from Intel's site (not Windows Update). Go to Intel Driver & Support Assistant and let it scan. Update the Wi-Fi driver from there. Intel's own drivers often fix power state bugs that Microsoft's generic drivers miss.

I've had to do this exact procedure on maybe 30 machines over the years. It works. If you're still stuck after all this, you might be looking at a hardware issue—like a loose mini-PCIe card or a dying adapter. But that's rare. The power saving toggle alone fixes most cases.

Quick tip: If you see this error right after plugging or unplugging your laptop, it's always the power saving setting. Disable it and the error won't come back.

That's it. No need to reinstall Windows, no need to call support. Three steps, 15 minutes max, and your Wi-Fi's back.