If a PCIe Wi‑Fi card only drops after sleep or resume, the problem is usually in Windows power management, the driver, or the motherboard’s PCIe wake settings, not the router. The fastest fix path is to check whether the adapter disappears, comes back slowly, or stays present but disabled. Then test the Windows power options first, followed by the driver and BIOS. If those don’t change anything, reseat the card, try another slot, and treat the card as suspect if the same failure follows it everywhere.
What it usually means when Wi‑Fi breaks only after sleep
The symptom matters more than the headline. If the adapter vanishes from Windows after sleep and comes back after a restart, that usually points to a sleep-resume problem, a driver issue, or a motherboard setting that keeps the card from waking cleanly. If the adapter is still listed but won’t reconnect, that leans more toward power management or driver behavior than a failed radio.
A third pattern is a slow return. The PC wakes, but Wi‑Fi takes a long time to reattach or shows “limited” or no internet until you disable and re-enable the adapter. That often means Windows woke the device, but the card did not finish reconnecting cleanly. Reports in Windows 11 describe the adapter disappearing from Device Manager after sleep and returning only after a restart. That pattern is worth separating early from a simple connection drop.
The practical clue is simple: if a cold boot fixes it every time, but sleep breaks it again, the fault is tied to sleep resume. That narrows the search fast and keeps you from chasing router settings that were never the real problem.
Before you start
- Work on the Windows PC that has the PCIe Wi‑Fi card, and make sure you can get back into Windows after each test.
- Use the same sleep or resume path each time so you are comparing the same behavior.
- Change one thing at a time.
- If a change makes the adapter behave worse, put it back before moving on.
- If the adapter disappears completely, note whether it is gone from the taskbar, Device Manager, or both.
- If you plan to reseat or move the card, shut the PC down fully and disconnect power first.
If the issue only happens after sleep and not after a normal restart, focus on sleep, wake, and power settings first. If it happens after shutdown too, Fast Startup belongs in the test plan as well.
Check the Windows power settings that most often cause this
Start in Device Manager, because this is the quickest safe check. Open the Wi‑Fi adapter’s properties and look at the Power Management tab first. If you see “Allow the computer to turn off this device to save power,” uncheck it and test sleep again. That’s a common first fix when the adapter goes missing after sleep.
Then open the adapter’s Advanced tab if it has power-saving or sleep-related options. Different drivers label these differently, but the goal is the same: stop Windows from putting the wireless card into a deeper power state than it can reliably resume from. If you change one setting and the problem gets worse, put it back before trying the next one.
Next, check the sleep-related settings in Power Options for the plan you actually use. Fast Startup matters here because it changes how Windows behaves around shutdown-like power states, which can make shutdown and sleep problems look connected when they are not. If the issue happens after a normal shutdown as well as sleep, disable Fast Startup and retest. If the problem happens only after sleep, keep the focus on sleep and resume behavior first.
Then separate driver problems from BIOS and motherboard wake issues
A bad or buggy driver usually affects how the adapter resumes, while a BIOS or motherboard setting usually affects whether the PCIe device wakes at all. That difference shows up in Device Manager. If the card is still there but behaves badly, think driver or Windows power policy first. If it disappears or shows up inconsistently, BIOS, UEFI, or the slot itself moves higher on the list.
Driver rollback is worth trying when the newest driver changed sleep-state handling rather than radio performance. That’s a common pattern with wireless adapters: the card works fine while awake, but resume breaks after an update. If Windows Update installed the newest driver and the problem began right after that, a rollback or a vendor driver from the card maker is a sensible test.
BIOS and UEFI settings matter when the motherboard controls PCIe wake behavior. Look for settings tied to PCIe power management, wake from PCIe devices, ErP/low-power mode, or deep sleep. The exact names vary by board, so check the motherboard manual or the vendor’s current support page before changing anything. If you change a wake-related option and the adapter starts returning reliably after sleep, that points away from the card itself and toward firmware behavior.
Sleep, hibernation, and Fast Startup do not behave the same way. A card that fails after sleep may still work after hibernation, or the reverse. That is why I would test one power state at a time instead of assuming one fix covers all of them. If the card fails in every resume path, the problem is broader than one Windows setting.
Reseat the card, check antennas, and try another slot
Once the Windows and BIOS checks are out of the way, move to the hardware that can be touched safely. Reseat the card if it might be loose, then check the antenna leads and external antennas for a poor connection. A slightly loose card can work all day and then fail after the system cools and wakes again.
The order matters. Power the PC down fully, unplug it, and wait for the board to discharge according to the system manual before touching the card. Then remove and reinstall the PCIe Wi‑Fi card, making sure it is fully seated and screwed down. Reattach the antennas firmly. A loose antenna lead can look like a sleep problem because the signal issue shows up only after the system resumes.
If the card supports another PCIe slot and the board manual allows it, try a different slot. That helps separate a bad slot from a bad card. A move to another slot is especially useful when the adapter disappears after sleep, because that can mean the board is failing to wake that lane cleanly rather than the Wi‑Fi radio itself failing.
After the move, test the same sleep cycle you use normally. If the issue vanishes in the new slot, the old slot or its power/wake behavior is the likely problem. If nothing changes, the card or its driver remains the stronger suspect.
How to tell whether the problem follows the card, the PC, or the router
Use one known-good comparison at a time. If another Wi‑Fi adapter works in the same PC after the same sleep routine, the original card moves to the top of the suspect list. If the same card fails in one PC but works normally in another, that points back to the motherboard, BIOS, or slot behavior rather than the Wi‑Fi card itself.
A router problem usually does not make only one desktop adapter disappear after sleep while other devices stay online. If other devices remain connected and the issue appears only on this PCIe card after resume, the router is probably not the root cause. The useful test here is not a long checklist of router tweaks; it is whether the failure follows the card, the machine, or neither.
If you do need to compare across devices, keep the test simple: one sleep cycle, one resume, one result. A clean pass or fail is more useful than trying to judge weak signal, crowded channels, or unrelated network changes at the same time.
When the card is probably failing and needs replacement
Treat the card as likely faulty when the same symptom follows the adapter across settings and slots. If you’ve already checked Device Manager power options, tried a different driver, disabled the most suspicious wake-related BIOS settings, reseated the card, and tested another PCIe slot, but the adapter still disappears or refuses to reconnect after sleep, replacement starts to make more sense than another tweak.
The clearest sign is repeatability. If the PC works normally after a cold boot, then fails after every sleep cycle no matter which slot or driver you use, the fault is following the card or its wake circuitry. If another Wi‑Fi adapter works in the same machine after the same sleep routine, that also points back to the original card.
At that point, I would stop spending time on the router and treat the card as the thing to replace or RMA. You’ve already isolated the obvious software and wake settings, so the remaining time is better spent proving the hardware fault than hunting for a fifth workaround.
Verify the fix
Put the PC through the same sleep-and-resume path that used to fail. If the adapter stays visible in Device Manager, reconnects on its own, and keeps working after resume, you’ve likely found the right fix.
If it only works after one change, test it again after a full shutdown and a fresh boot. That helps you tell whether you fixed sleep resume itself or only masked part of the problem. If the symptom comes back, undo the last change and move to the next branch in the sequence instead of stacking more tweaks on top of it.