Samsung’s Galaxy Book5 family spans Intel Lunar Lake and Snapdragon variants, all marketed hard on AI — Galaxy AI features, Copilot+ experiences, on-device intelligence. When the NPU driver misbehaves on a Book5, the symptoms are familiar: no Neural processors in Device Manager, AI features grayed out, or Intel AI Boost failing to install.
Samsung’s wrinkle is its dual update system: Samsung Update (model-aware, sometimes slow) versus Windows Update (fast, sometimes wrong for Samsung hardware). The NPU driver lives inside chipset/graphics packages on both channels, and version fights between them are the top cause of Book5 NPU trouble. This guide navigates Samsung’s specific maze. For the general NPU detection diagnosis that applies to every brand, see NPU not detected in Windows 11 . For Microsoft’s own AI hardware with similar symptoms, see Microsoft Surface Pro NPU not detected ; for Acer’s AI laptop, Acer Swift 14 AI Copilot problems .
If the Book5 runs hot while the NPU struggles, AI PC running hot fix covers thermals.
Why this happens
- NPU driver bundled invisibly: Samsung doesn’t ship a standalone “NPU driver” — it’s inside chipset/MEI and graphics packages, so owners install the wrong thing or nothing.
- Samsung Update vs Windows Update fights: The two channels overwrite each other’s NPU driver versions, breaking initialization.
- BIOS version gaps: Early Book5 BIOS releases had NPU enumeration and power issues fixed in later updates.
- Model confusion: Book5, Book5 Pro, Book5 360, Book5 Pro 360 — similar names, different driver packs. Wrong-model drivers cause subtle failures.
- Interrupted multi-part installs: The Intel AI Boost stack installs in stages; interruption corrupts it.
- Ecosystem service noise: Samsung’s background services complicate diagnosis by adding load that mimics NPU-related slowness.
How to fix it
Work through these in order — Samsung’s channel first, with exact model numbers.
Fix 1: Update via Samsung Update completely
Samsung Update knows your exact Book5 sub-model — let it lead.
- Open Samsung Update (preinstalled; Microsoft Store if missing).
- Run a full check and install everything, especially BIOS/firmware, chipset, and graphics.
- Keep AC power connected throughout BIOS updates.
- Reboot as prompted — some Samsung updates need two reboots to settle.
- Check Device Manager for the Neural processors category afterward.
Fix 2: Confirm your exact model and processor
“Galaxy Book5” isn’t precise enough — Samsung’s lineup has overlapping names with different silicon.
- Find your exact model: Settings > System > About, plus the sticker on the bottom (e.g., NP940XHA vs NP950QHA).
- Note the processor: Intel Core Ultra 7 258V (Lunar Lake, Intel AI Boost) vs Snapdragon X Elite (Qualcomm Hexagon) — different driver stacks.
- On Samsung’s support site, search the full model number, not just “Book5.”
- Download the chipset and graphics drivers for YOUR model only.
- If you previously installed another Book5 variant’s drivers, that’s a likely culprit — proceed to Fix 3.
Fix 3: Clean-install the NPU driver stack
When channels have fought, clean-slate the driver stack in the right order.
- In Device Manager, uninstall the NPU device if present (check “delete the driver software”).
- Uninstall related chipset/MEI entries showing warnings.
- Reboot; temporarily pause Windows Update driver installs to prevent interference.
- Install Samsung’s chipset/MEI package first, reboot, then the graphics package, reboot.
- Verify: Neural processors present without warnings; Task Manager > Performance shows the NPU graph.
Fix 4: Update BIOS and check firmware settings
Samsung BIOS updates carry NPU initialization fixes — and occasionally reset relevant settings.
- Install the latest BIOS via Samsung Update (preferred) or Samsung’s support site.
- Reboot into BIOS (F2 on Samsung) and look for NPU/AI device options.
- Ensure any NPU toggle is Enabled; confirm the iGPU isn’t disabled.
- Save, boot to Windows, and re-check Device Manager.
- If a BIOS update caused the problem (regression), Samsung support can advise on rollback options.
Fix 5: Rule out software interference
Samsung’s ecosystem apps are usually innocent, but verify rather than assume.
- Task Manager > Startup: disable Samsung ecosystem apps temporarily (Phone Link helpers, Quick Share).
- Reboot and test NPU-dependent features.
- If nothing changes, re-enable them — they weren’t the cause.
- Also check third-party antivirus: some suites’ kernel drivers conflict with NPU drivers (temporarily test with Defender only).
- Keep notes on what you disabled for easy reversal.
Fix 6: Escalate to Samsung with model precision
Samsung support runs on exact model numbers — bring them.
- Document: full model number, BIOS version, driver versions, Device Manager screenshots.
- Run Samsung’s built-in diagnostics (Samsung Update or BIOS diagnostics) and save results.
- Contact Samsung support with the evidence — mention the clean reinstall already done.
- Under warranty, NPU failures surviving BIOS + clean drivers warrant mainboard service (the NPU is in the SoC).
- Out of warranty: Samsung service centers can diagnose definitively.
Closing
Galaxy Book5 NPU driver issues are almost always channel fights (Samsung Update vs Windows Update) or wrong-model packages — not dead silicon. Lead with Samsung Update on your exact model number, clean-install the chipset-then-graphics stack when versions have tangled, and keep BIOS current. The NPU appears in Device Manager in the large majority of cases after this sequence. What doesn’t appear — with current BIOS and clean Samsung drivers on the right model — is firmware or hardware, and Samsung service with your documentation is the efficient next step.
