You open Windows Security > Device security > Core isolation and find Memory Integrity switched off with a warning that an incompatible driver is blocking it — and the named driver belongs to your NPU. Turn Memory Integrity on and the NPU stops working; leave it off and you lose a key security protection. It feels like a forced choice between security and the AI hardware you paid for.

On Copilot+ PCs, Memory Integrity (Hypervisor-Protected Code Integrity, HVCI) requires every kernel driver to meet modern compatibility standards. Many early NPU drivers shipped before those standards were enforced, so HVCI flags them as incompatible and refuses to load them — or refuses to enable itself. The conflict is a driver-age problem, not a hardware problem: the NPU is fine, the driver just predates the requirement.

This guide gives you six fixes in technician order: identify the exact blocking driver, replace it with a compliant version, and verify both Memory Integrity and the NPU are healthy afterward. The goal is both protections on and the NPU accelerating — never one at the expense of the other.

Why this happens

  • NPU driver predates HVCI compatibility: Early Copilot+ NPU drivers were built before Microsoft enforced HVCI-compatible signing and memory practices; the driver works but Memory Integrity will not load it.
  • Windows Update installed an older driver: Update catalogs sometimes offer a stale NPU driver that overwrites a newer compliant one, reintroducing the block after it was already fixed.
  • OEM driver bundle partially updated: Updating only the graphics driver while the NPU driver stays on its launch version leaves a mixed set where the old NPU component trips HVCI.
  • Third-party AI or tuning utilities install their own drivers: Some NPU utilities and overclocking tools ship helper drivers that are not HVCI-compatible and get flagged alongside — or instead of — the real NPU driver.
  • Firmware and driver versions mismatched: Newer platform firmware can expose NPU capabilities the old driver does not declare properly, and HVCI treats the mismatch as a blocked load.
  • Leftover driver from a previous install: Incomplete uninstalls leave an old NPU driver file that HVCI scans and flags even though Device Manager shows the new one as active.

How to fix it

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

Fix 1: Identify the exact blocking driver

Memory Integrity names the offender — do not guess. Get the precise driver filename before changing anything, because the fix targets that specific file.

  1. Open Windows Security > Device security > Core isolation > Memory integrity and click Review incompatible drivers (or the warning link) to see the flagged driver name, e.g. a .sys file.
  2. Note the full filename and the published name — you will match it against Device Manager and installer packages.
  3. In Device Manager, enable View > Show hidden devices, then check the NPU/AI accelerator entry’s Driver > Driver Details to confirm the flagged file belongs to it.
  4. Take a screenshot or write down the driver version currently installed — you need the “before” number to confirm the update actually replaced it.
  5. Do not disable Memory Integrity yet; leave it off (as found) while you work, and treat any urge to leave it off permanently as a red flag.

Fix 2: Install the latest OEM NPU driver package

The maker’s current driver bundle contains the HVCI-compatible NPU driver. This single update resolves the conflict on most Copilot+ PCs — the same driver hygiene that fixes SSD firmware update problems on ARM laptops applies here: the OEM bundle is the source of truth.

  1. Find your exact model in Settings > System > About, then go to your maker’s support page — Dell , HP , or Lenovo — and download the latest NPU/AI or chipset driver package for Windows 11 on ARM (or x64 for Intel/AMD AI PCs).
  2. For Intel AI PCs you can also check Intel’s driver detection tool ; for AMD, the AMD driver page .
  3. Run the installer as administrator with Memory Integrity still off, and let it complete without sleep or interruption.
  4. Restart when prompted, then recheck the driver version in Device Manager against your “before” number.
  5. Return to Core isolation and try enabling Memory Integrity — if the incompatible-driver warning is gone, toggle it on and restart.

Fix 3: Clean out the old driver if the block persists

When the new installer does not fully replace the flagged file, HVCI keeps seeing the old one. A manual removal clears the stale file so only the compliant driver remains.

  1. In Device Manager, right-click the NPU device and choose Uninstall device, checking Attempt to remove the driver for this device.
  2. Open Settings > Apps > Installed apps and remove any standalone NPU/AI utility packages from the chip vendor or a third-party tool.
  3. Restart — Windows will load a basic driver or none at all; that is expected and temporary.
  4. Reinstall the OEM NPU driver package from Fix 2 cleanly on top of the cleared state.
  5. Restart again, then check Review incompatible drivers — the flagged filename should no longer appear. If a different file is now flagged, repeat this fix for that driver; conflicts sometimes come in pairs.

Fix 4: Verify the NPU actually works with Memory Integrity on

A green toggle is not proof — confirm the NPU loads, is visible to the OS, and actually accelerates work. A blocked driver can fail silently even with HVCI enabled.

  1. With Memory Integrity on and the laptop restarted, open Task Manager > Performance and confirm the NPU tile appears and shows 0% at idle (present, not errored).
  2. Run a quick AI workload — Windows Studio Effects in the Camera app, or Recall/Cocreator if enabled — and watch NPU utilization rise.
  3. If Task Manager shows no NPU tile, check Device Manager for a warning icon on the NPU device; a Code 48 or similar means the driver is still being blocked at load.
  4. For a quantitative check, run an AI benchmark and compare against expectations — abnormally low Geekbench AI NPU scores after this fix suggest the NPU is present but throttled or falling back to another processor.
  5. Check Event Viewer > Windows Logs > System for driver-block events referencing the NPU filename; zero new events across two restarts means the conflict is truly resolved.

Fix 5: Stop Windows Update from reinstalling the bad driver

The cruelest version of this conflict is the one that fixes itself and then returns: Windows Update re-delivers the older incompatible NPU driver. Pin the good driver in place.

  1. After confirming the working driver version, open Settings > Windows Update > Advanced options > Optional updates and look for any pending NPU/driver updates — hide or decline older ones.
  2. Check Microsoft’s Windows support pages for the supported “show or hide updates” troubleshooter to block the specific older NPU driver version.
  3. In Device Manager > NPU device > Properties > Driver, use Roll Back Driver only as a diagnostic — the durable fix is blocking the bad version, not rolling back the good one.
  4. If your maker offers a driver-update utility, prefer it over Windows Update for NPU drivers going forward; vendor tools track HVCI-compatible releases faster.
  5. Recheck Memory Integrity after the next Patch Tuesday — a two-minute verification beats discovering the regression weeks later.

Fix 6: Audit third-party drivers and consider a clean baseline

If HVCI still flags something after the NPU driver is current, the blocker may be a helper driver from tuning software, not the NPU driver itself. Audit the whole driver set before giving up on Memory Integrity.

  1. Reopen Review incompatible drivers and identify every flagged file — note which belong to the NPU and which belong to utilities.
  2. Uninstall AI tuning tools, RGB controllers, and system “optimizers” one at a time, restarting and rechecking HVCI after each — aggressive debloat guides for Copilot+ PCs sometimes recommend tools that install their own incompatible drivers.
  3. For any remaining flagged driver with no newer version, contact that vendor — not Microsoft — since only the driver author can make it HVCI-compatible.
  4. As a temporary diagnostic only, you may disable Memory Integrity to confirm the NPU works without it; re-enable it immediately after the test regardless of the result.
  5. If the system shipped with the conflict and no driver update exists yet, file feedback via the Feedback Hub referencing the driver filename — and check the maker’s support page monthly, since compliant drivers typically follow within a quarter.

Closing

The Memory Integrity versus NPU driver conflict is a versioning problem, not a hardware flaw: an old NPU driver that predates HVCI requirements. Identify the flagged file, install the maker’s current NPU driver package, clean out stale copies, and verify both the toggle and the NPU are healthy. Keep Memory Integrity on — a compliant driver gives you the security and the AI acceleration together.

Frequently asked questions

Why does Memory Integrity say an NPU driver is incompatible?
Memory Integrity (HVCI) blocks drivers that are not HVCI-compatible — usually older NPU or AI-accelerator drivers built before the requirement. Updating to the maker’s latest NPU driver package almost always provides a compliant version.
Should I just turn off Memory Integrity to use my NPU?
No. Disabling Memory Integrity removes a core virtualization-based security protection from the whole system. Update the NPU driver first; turning HVCI off is a temporary diagnostic step, not a fix.
Can Windows Update install an incompatible NPU driver?
Yes — Windows Update occasionally delivers an older NPU driver that predates HVCI compatibility, which then trips the Memory Integrity block. Installing the newer driver from your laptop maker or chip vendor resolves it.
Will this conflict slow down AI features?
If Memory Integrity blocks the NPU driver, AI features fall back to CPU or GPU, which is slower and drains more battery. Fixing the driver conflict restores NPU acceleration and its efficiency advantage.