Copilot is a cloud creature — but on Copilot+ PCs, parts of it can run locally on the NPU when you’re offline: on-device search and local processing features Microsoft has moved onto the neural hardware. When offline mode doesn’t work, the app either refuses to start without a connection or claims offline features are unavailable on hardware that should support them.

The confusion starts with expectations. “Offline mode” doesn’t mean “full Copilot without internet” — it’s a defined set of local capabilities, only on NPU-equipped laptops with the local models actually downloaded. Most reports are one of three things: the laptop doesn’t qualify, the models never downloaded, or the NPU isn’t healthy. This guide sorts out which one you’re dealing with.

If Copilot won’t respond even online, Copilot not responding is the right starting point. If the app won’t launch at all, see Copilot app not opening on Windows 11 . Required companion reads for this batch: NPU DPC latency stutter fix and Click to Do with Teams chat .

Why this happens

  • Non-NPU hardware: Offline processing needs a Copilot+ PC NPU — on older laptops the feature legitimately doesn’t exist.
  • NPU driver broken or missing: The NPU must be visible and healthy in Device Manager for local models to run.
  • Local models never downloaded: Offline features need multi-gigabyte downloads that fail silently on full disks or metered connections.
  • Expectation mismatch: Only a subset of Copilot’s features works locally; the full assistant needs the cloud.
  • Offline toggles disabled: Settings for local or on-device processing may simply be off.
  • Corrupted model cache: Partially downloaded models leave offline features in a broken half-state.

How to fix it

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

Fix 1: Confirm your laptop qualifies

Offline Copilot features require a Copilot+ PC — a laptop with an NPU meeting Microsoft’s threshold — on a current Windows 11 build. On anything else, “offline mode unavailable” is correct behavior, not a bug. A minute in Task Manager and Settings prevents a long wild-goose chase.

  1. Open Task Manager > Performance and look for an NPU entry.
  2. Check Settings > System > About to confirm a recent Windows 11 build.
  3. Verify on your maker’s site that the laptop is marketed as a Copilot+ PC.
  4. No NPU means no local AI features — use Copilot online instead.
  5. If the NPU exists but shows errors, continue to Fix 2 first.

Fix 2: Get the NPU healthy

Local models run on the NPU — if its driver is broken or missing in Device Manager, every offline feature fails with it. Update the NPU driver from your laptop maker’s support page and confirm the NPU shows clean in Device Manager and appears in Task Manager > Performance.

  1. In Device Manager, find the NPU (under System devices or Neural processors).
  2. If it shows a warning, update the driver, or uninstall and restart for a fresh install.
  3. Get the latest NPU driver from your laptop maker’s support page.
  4. For Intel and AMD platforms, the Intel driver assistant and AMD driver downloads carry the latest NPU packages.
  5. Confirm the NPU is clean in Device Manager before continuing.

Fix 3: Download the local models

Offline features depend on multi-gigabyte local AI models that Windows fetches in the background. A full disk, a metered connection, or an interrupted download means the models never arrive — with no clear error. Free space and a clean, unmetered connection usually fix it.

  1. Free up at least 10 GB on your system drive.
  2. Connect to unmetered Wi-Fi; metered connections pause large background downloads.
  3. Install all pending Windows updates, then leave the laptop on and connected for an hour.
  4. Check Settings > Apps > Installed apps for AI model packages showing download status.
  5. Restart and retest offline features after the waiting period.

Fix 4: Enable the local processing toggles

Even with a healthy NPU and downloaded models, offline features stay dark if their toggles are off — in Copilot’s settings, in Windows AI component settings, or in privacy settings gating on-device processing. These don’t always default to on, especially after major updates.

  1. In the Copilot app’s settings, enable any offline, local, or on-device processing options.
  2. Check Settings > Privacy & security for AI or on-device processing permissions.
  3. Look in the AI components section of Settings for local model toggles.
  4. Restart the Copilot app so it re-detects local capabilities.
  5. Test with Wi-Fi off — disconnect and try the features documented to work locally.

Fix 5: Clear the corrupted model cache

If offline features worked before and broke after an update, or downloads keep stalling, the model cache is likely corrupted — partial files the system treats as complete. Clearing it forces a clean re-download.

  1. In Settings > System > Storage > Temporary files, clear AI model and delivery optimization files.
  2. In Copilot’s Advanced options (Settings > Apps > Installed apps), use Repair, then Reset if needed.
  3. Restart, connect to unmetered Wi-Fi, and let the models re-download.
  4. Watch disk space during the download to catch space problems early.
  5. Test offline features with Wi-Fi disabled once the download completes.

Fix 6: Update Windows to a local-AI-capable build

Local AI frameworks in Windows 11 are still evolving — the NPU APIs and model-delivery plumbing arrived in recent builds. A laptop behind on feature updates can have a healthy NPU and still lack the OS support offline Copilot needs.

  1. Install all pending updates in Settings > Windows Update, including optional drivers.
  2. Compare your build against the current release via the Windows 11 download page .
  3. After updating, revisit Fix 3 — new builds often trigger fresh model downloads.
  4. Re-check the Copilot app for offline toggles the update may have added.
  5. Test by disconnecting from the network entirely and launching Copilot.

Closing

Offline mode fails for unglamorous reasons: no NPU, a broken NPU driver, models that never downloaded, or a toggle sitting off somewhere. Work the chain — qualify the hardware, heal the NPU, download the models, enable the toggles — and test by actually disconnecting. Keep expectations honest too: offline Copilot is a useful subset of the cloud experience, not a replacement. When the local pieces are in place, that subset works exactly where you need it — on the plane, in the dead zone, anywhere the cloud can’t reach.

Frequently asked questions

Does Copilot really work without internet?
Only partially. Copilot’s offline mode handles on-device tasks through local models on your NPU — things like local file search and some assistant features. Full conversational AI still needs the cloud. If you expected the complete Copilot experience offline, that expectation is the issue, not a bug.
Why does Copilot say offline mode is unavailable on my laptop?
Offline features require a Copilot+ PC with a working NPU and the downloaded local models. On non-NPU laptops, or when the NPU driver is broken, offline mode simply isn’t offered.
How much disk space do Copilot's offline models need?
Local AI models are large — expect several gigabytes. If your system drive is nearly full, model downloads fail silently and offline mode never activates. Free up space and retry the download.
Can I force Copilot to stay offline for privacy?
You can disable cloud features where the app offers the toggle, but Copilot is fundamentally a cloud service with offline augmentation — not an offline-first app. For fully offline AI, look at dedicated local-model tools instead.