If WSL2 GPU and NPU passthrough has stopped working on your AI laptop, the frustration is familiar: everything else on the machine seems fine, yet the one feature you rely on refuses to cooperate. It is easy to assume the hardware is at fault or that the laptop itself is broken, but in most cases the cause is far more ordinary and far easier to fix than it first appears.

Before you reinstall anything, it helps to understand what usually goes wrong. Passthrough only works when Windows virtualization, the right GPU driver package, and the WSL kernel all agree, so a single outdated component can leave Linux tools running on the CPU alone. A similar pattern shows up in our guide to Fix Lenovo ThinkPad T14s AI camera not working , where the same driver and settings checks often point to the answer, and working through those checks first can save you a long and unnecessary reinstall.

This guide walks through the causes first, then the fixes in the order you should try them, starting with the quick checks and moving to deeper repairs only if you need them. You can stop as soon as WSL2 GPU and NPU passthrough works again. Readers dealing with a related fault may also find our guides to Fix Phone Link AI photo search not working and Live captions auto translate language missing fix useful, since they cover several of the same settings, drivers, and troubleshooting steps.

Why this happens

  • A setting was switched off or reset: A Windows or app update can reset the relevant setting without telling you, and when the switch behind WSL2 GPU and NPU passthrough flips off, the feature simply stops or disappears.
  • An outdated app, system build, or driver: WSL2 GPU and NPU passthrough depends on the app, Windows, and the device driver agreeing with each other, and when one of them falls behind, the feature may fail, crash, or return empty results.
  • A corrupted cache, profile, or app package: A failed update, a forced shutdown, or a damaged user profile can corrupt the files WSL2 GPU and NPU passthrough relies on, while the rest of the app keeps opening normally.
  • An account, licence, or policy check failing: Many features verify your Microsoft account, licence, or organisation policy before they run, and if sign-in lapses or a policy blocks the feature, it stays hidden or disabled.
  • A hardware or acceleration conflict: The NPU, GPU, sensor, or adapter path may be busy, misconfigured, or claimed by another app, and features that need real-time processing are the first to show this as lag, freezing, or failure.
  • A network, region, or content restriction: Cloud-assisted features need a stable connection and regional availability, and a blocked network call or an unsupported file type can look exactly like a broken feature.

How to fix it

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

Fix 1: Confirm sign-in, licence, and extension state

Many reports turn out to be an account or recognition problem rather than a fault, so start here before changing drivers or reinstalling anything. When WSL2 GPU and NPU passthrough cannot verify who you are, or Windows cannot see the device properly, the feature fails in exactly the confusing way described above, and a clean sign-in or reconnection often restores it in minutes.

  1. Sign out of the tool and sign back in with the correct account.
  2. Check the extension or subscription panel for errors or expiry warnings.
  3. Disable other extensions temporarily to rule out a conflict.
  4. Restart the tool and test the feature in a small sample project.

Fix 2: Update the tool, Windows, and your drivers

Updates fix a large share of these problems, because Microsoft, app makers, and laptop makers regularly repair the drivers and services these features rely on. If any one layer falls behind, the feature can fail while everything else looks normal, so bring Windows, the app, and the drivers up to date together rather than updating only one of them. Guidance for keeping Windows current is available from Microsoft Windows support .

  1. Open Settings, then Windows Update, and install every available update.
  2. Update the tool and its extensions to their latest versions.
  3. Install the latest chipset and graphics drivers from your laptop maker.
  4. Restart the laptop, then test the feature again.

Fix 3: Check virtualization and system requirements

When the basic checks pass, the next suspect is how the feature is configured on this machine. A wrong compute device, a disabled adapter, or an aggressive power setting can quietly block the feature even though the app itself opens normally, so work through the settings below methodically and test after each change instead of changing several things at once.

  1. Open Task Manager, then Performance, and confirm virtualization is enabled.
  2. Enable the required Windows features under Turn Windows features on or off.
  3. Check the tool’s requirements page for ARM64 support and memory minimums.
  4. Restart the laptop after changing any virtualization setting.

Fix 4: Clear caches and reset tool settings

If settings look right, corrupted cached data is a common culprit. A failed update, a forced shutdown, or a stale configuration can leave the tool pointing at files that no longer match the installed version, and clearing or resetting that data forces a clean rebuild without losing your documents or projects.

  1. Close the tool and any background agents or daemons it runs.
  2. Clear the tool’s cache and temporary folders from its settings.
  3. Reset the tool’s settings to defaults, keeping a backup of your config.
  4. Reopen the tool and test the feature in a minimal project.

Fix 5: Test with a minimal project and correct architecture

Isolating the problem is the fastest way to stop guessing. A minimal test tells you whether the fault lives in your file, project, network, or device, or in the laptop itself, and that distinction decides whether the remaining fixes are worth trying or whether you should repair the original item instead.

  1. Create a fresh, minimal project instead of the failing one.
  2. Confirm you are using an ARM64 image, SDK, or package where one exists.
  3. Remove third-party packages or plug-ins and re-add them one by one.
  4. If the minimal project works, migrate the real project in stages.

Fix 6: Reinstall the tool cleanly as a last resort

Only reach this step after the earlier fixes have failed, because a clean reinstall costs time and resets your custom settings. Done properly, though, it removes broken package files, stale drivers, and conflicting add-ons in one pass, and it gives you a known-good baseline to test against before you restore anything.

  1. Export your settings, keymaps, and project templates first.
  2. Uninstall the tool and remove leftover configuration folders.
  3. Download the latest ARM64 installer from the official site.
  4. Install, sign in, and test before restoring extensions and plug-ins.

Closing

Most cases of WSL2 GPU and NPU passthrough failing come down to a setting, a driver, or an account check rather than a hardware fault, so work through the fixes above in order and test after each one. If the feature returns, keep Windows, the app, and your drivers updated together, since that combination is what keeps AI features stable on an ARM laptop. If nothing here resolves it, take your notes on the symptoms and the steps you tried to your laptop maker support team, and they will be able to pick up exactly where this guide leaves off.

Frequently asked questions

Why did WSL2 GPU and NPU passthrough stop working suddenly?
Most often a Windows update, a driver update, or a settings change is responsible. Check what changed on the laptop in the last few days, then work through the driver and settings fixes in this guide before assuming a hardware fault.
Do I need a Copilot+ PC for WSL2 GPU and NPU passthrough?
Some features require a Copilot+ PC with an NPU, while others work on any Windows 11 laptop. Check the feature requirements inside the app and in Windows Settings; if your hardware is not eligible, the feature may stay hidden even when everything else is correct.
Will repairing or resetting the app delete my files?
Repair keeps your files and settings. Reset clears the app cached data and settings but not your documents or projects. Back up anything important before a reset, just to be safe.
When should I contact support about WSL2 GPU and NPU passthrough?
If every fix in this guide fails, the hardware is not detected in Device Manager, or the problem appeared right after physical damage, contact your laptop maker support team. Note the exact symptoms and the steps you already tried.