You close the lid, the laptop hibernates, and when you wake it the NPU is gone. Device Manager shows no neural processor, Copilot+ features report that AI hardware is unavailable, and only a full restart brings the NPU back — until the next hibernation, when it vanishes again.

Hibernation is the hardest resume path Windows has. The whole system state is written to disk and restored, and any driver or firmware step that mishandles that restore can leave the NPU unenumerated. The hardware is fine; Windows simply never re-discovers it during resume.

This guide gives you six fixes in order: prove the pattern, fix power and resume settings, then repair the driver and firmware so hibernation works reliably.

Why this happens

  • Faulty NPU driver resume path: The driver may initialise correctly at cold boot but fail to reinitialise when Windows restores the hibernation file.
  • Fast Startup preserving bad state: Fast Startup reuses a hibernation-style file, so a resume fault can appear even on a normal shutdown and boot.
  • BIOS firmware resume bug: An old BIOS may not re-expose the NPU to Windows during resume, even though cold boot enumeration works perfectly.
  • Power management turning the NPU off: Aggressive power settings can allow Windows to power down the NPU during hibernation and then fail to power it back up.
  • Corrupted hibernation file: A damaged or oversized hibernation file can restore an inconsistent device state, leaving some devices missing after every resume.
  • Chipset driver mismatch: The NPU depends on the chipset driver during resume, so an outdated chipset package can break NPU detection even when the NPU driver itself is current. A device that is present but flagged in Device Manager needs a different approach, as with an NPU showing a yellow triangle .

How to fix it

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

Fix 1: Confirm the pattern and test a cold boot

Before changing settings, prove hibernation is the trigger. That distinction saves you from chasing a general detection fault when the real problem is resume-only.

  1. With the NPU working, put the laptop into hibernation manually from the Start menu power options.
  2. Resume it and immediately check Device Manager for the NPU entry.
  3. If it is missing, restart fully and confirm it returns — that confirms a resume fault, not a dead device.
  4. Repeat the test once more to rule out a one-off glitch; a fault that repeats twice is systematic.
  5. Note whether sleep causes the same problem, since a sleep-only fault points more strongly at power management than at the hibernation file.

Fix 2: Turn off Fast Startup and test hibernation again

Fast Startup is the cheapest variable to eliminate. It shares hibernation machinery, and disabling it often restores reliable NPU detection without losing hibernation itself.

  1. Open Control Panel > Power Options > Choose what the power buttons do.
  2. Click Change settings that are currently unavailable and uncheck Turn on fast startup.
  3. Save the change, then shut down fully and power on to clear any saved state.
  4. Hibernate and resume again, then check Device Manager for the NPU.
  5. If the NPU now survives hibernation, leave Fast Startup off — the small boot-time cost is worth reliable AI hardware.

Fix 3: Stop Windows powering down the NPU

Windows may power down the NPU to save battery and then fail to wake it. Removing that permission forces the device to stay in a state Windows can always rediscover.

  1. Open Device Manager and find the NPU under Neural processors or System devices.
  2. Right-click it, choose Properties, and open the Power Management tab if one is present.
  3. Uncheck Allow the computer to turn off this device to save power.
  4. In Settings > System > Power & battery, set the power mode to Balanced rather than Best power efficiency for testing.
  5. Hibernate, resume, and check whether the NPU is now detected every time.

Fix 4: Reinstall the NPU and chipset drivers from your maker

Resume faults are often fixed by a driver version that handles hibernation correctly. Your laptop maker’s validated pair — chipset plus NPU — matters more than the newest generic build.

  1. Download the latest chipset and NPU drivers for your exact model from Dell , HP , or Lenovo support.
  2. In Device Manager, uninstall the NPU driver with driver removal checked, then restart.
  3. Install the chipset driver first, then the NPU driver, each as administrator.
  4. Restart again, hibernate, resume, and check Device Manager twice in a row.
  5. If the fault persists on the maker’s latest drivers, try the previous driver version — newer is not always better for resume handling.

Fix 5: Rebuild the hibernation file and update the BIOS

A corrupted hibernation file restores bad state every time, no matter how good the drivers are. Rebuilding it, plus a BIOS update, covers the firmware side of resume.

  1. Open an elevated terminal and disable hibernation, then restart the PC.
  2. Re-enable hibernation from the same terminal and restart once more, which creates a fresh hibernation file.
  3. Check your BIOS version, then download the BIOS update for your exact model from your maker’s support page.
  4. On AC power, run the BIOS update and let the laptop restart itself without interruption.
  5. Hibernate and resume twice, checking Device Manager each time to confirm the fix holds. The same firmware-first thinking helps with other app faults after resume, including Spotify issues on ARM Windows .

Fix 6: Reset power plans and repair Windows resume components

If the NPU still vanishes, the power plan or Windows resume machinery itself may be damaged. Resetting plans is safe, and system repair is the last software step before hardware service.

  1. Open an elevated terminal and restore the default power plans, then restart.
  2. Set your preferred plan again, keeping Fast Startup off from Fix 2.
  3. Run System File Checker from an elevated terminal and repair any reported damage.
  4. Hibernate, resume, and verify the NPU in Device Manager and in a Copilot+ feature.
  5. If the NPU still disappears after every hibernation on a repaired system, contact your maker’s support with your test notes — a repeatable resume fault is strong evidence for a firmware case. A related dead end to rule out first is a Cocreator prompt producing no image , which can look like missing AI hardware but is usually a service fault.

Closing

An NPU that vanishes after hibernation is a resume fault, not a hardware failure: the driver, BIOS, or hibernation file fails to bring the device back. Prove the pattern, turn off Fast Startup, stop power management from parking the NPU, and reinstall your maker’s chipset and NPU drivers. If those steps do not hold across two hibernation cycles, rebuild the hibernation file and update the BIOS before considering service.

Frequently asked questions

Why does my NPU vanish after hibernation but not after sleep?
Hibernation saves the full system state to disk and restores it later, which stresses driver resume paths far more than sleep. A driver or BIOS fault that sleep hides will often show up only after hibernation.
Is disabling hibernation a real fix?
It is a workaround, not a fix. Disabling hibernation avoids the faulty resume path, but updating the driver and BIOS addresses the cause and lets you keep hibernation if you want it.
Will the NPU come back on its own after hibernation?
Sometimes a later restart restores it, but if it disappears after every hibernation, the resume fault is systematic. Follow the driver and firmware steps in this guide rather than relying on restarts.
Can Fast Startup cause the same problem?
Yes. Fast Startup uses a partial hibernation file, so it can trigger the same resume faults as full hibernation. Turning Fast Startup off is a useful diagnostic step.