You type “photos from the beach trip” into File Explorer’s search box and get nothing — even though the photos are right there in your Pictures folder with sensible names. Exact filenames still find files, so search is not broken exactly. It is just dumb. The smart part, the part your Copilot+ PC was advertised for, refuses to work.

Natural language file search is one of the signature Copilot+ features: instead of matching characters in filenames, an on-device AI model interprets what you mean and searches file content, metadata, and context. It runs on the NPU, needs a downloaded language model, and depends on the same Windows Search index that classic search uses. When descriptions fail but filenames succeed, the keyword machinery is healthy and the AI layer is the patient.

This guide gives you six fixes in order: confirm the index is healthy, verify the NPU and AI components, check region and language gates, re-register the search components, tune the search settings, and rule out a profile problem. Test a descriptive query — not a filename — after each fix. The same NPU-dependent AI stack shows up in other failures, like Procyon AI benchmark NPU errors , so a fix here can help there too.

Why this happens

  • On-device AI model never downloaded: The semantic search model arrives as a background download after setup. Until it completes, descriptive queries silently fall back to keyword matching and find nothing.
  • Broken or generic NPU driver: Semantic search executes on the NPU. A missing or broken driver means the AI layer errors out instead of interpreting your query.
  • Unsupported region or display language: Windows AI features are gated by region and language. An unsupported combination disables semantic search even on perfect hardware.
  • Search index missing file content: If the index only catalogs filenames and not file contents, the AI layer has nothing semantic to match against for documents and photos.
  • Search components need re-registration: The File Explorer search integration can lose its registration after updates, breaking the handoff between the search box and the AI backend.
  • Damaged user profile search data: Per-user search settings and caches can corrupt, killing semantic search for one account while another works.
  • Third-party shell extensions interfering: Explorer extensions and “search enhancer” utilities can intercept queries before the AI layer ever sees them.

How to fix it

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

Fix 1: Confirm classic search and indexing are healthy

Semantic search builds on the regular index, so rule out foundation problems first. If the index does not even contain your files’ contents, no AI model can find them by description.

  1. Open File Explorer and search for an exact filename you know exists — if that fails, the problem is the index, not the AI layer.
  2. Go to Settings > Privacy & security > Searching Windows and confirm the folders you search are included in indexed locations.
  3. Click Advanced indexing options > Advanced > File Types and verify common types (docx, pdf, jpg) are set to Index Properties and File Contents.
  4. If you changed anything, click Rebuild under Troubleshooting and let the index rebuild while plugged in.
  5. Retest with a filename, then with a descriptive phrase. If filenames work and descriptions still fail, the index is fine — continue to the AI layer. Index health is also the root of many Wi-Fi 7 router compatibility quirks on AI laptops , where background services stall the same way.

Fix 2: Verify the NPU and the AI model download

Semantic search needs two things from the hardware side: a working NPU and the downloaded language model. Check both, because Windows will not always tell you which one is missing — it just returns no results.

  1. Open Device Manager > Neural processors and confirm the NPU shows without a warning icon.
  2. If flagged, reinstall the NPU driver from your laptop maker’s support page (Dell, HP, or Lenovo) — do not rely on the generic Windows driver.
  3. Open Settings > Windows Update and install all updates including optional drivers; the Copilot+ AI components often arrive this way.
  4. Leave the PC plugged in, on Wi-Fi, and idle for 30–60 minutes so the on-device model can download in the background.
  5. Test again with “find the document about the project budget” or similar. Microsoft’s Windows support pages list which AI features require the downloaded models.

Fix 3: Check region, language, and AI feature eligibility

Windows gates its AI features by region and display language, and semantic search quietly disables itself outside the supported set. This is a common trap for laptops set up with a non-US region during initial setup.

  1. Open Settings > Time & language > Language & region.
  2. Set Windows display language to English (United States) and Country or region to United States.
  3. Sign out and back in so the change fully applies.
  4. Confirm your PC is actually a Copilot+ PC in Settings > System > About — non-Copilot+ hardware does not get semantic File Explorer search at all, and no setting can enable it.
  5. Retest a descriptive query. On a genuine Copilot+ PC with a supported region, the feature should now respond. Accessibility-related AI features share these same gates, as seen with accessibility AI features not working .

Fix 4: Re-register the Windows Search components

If the hardware and model are fine, the software handoff between File Explorer’s search box and the AI backend may be broken — usually after a feature update. Re-registering the search app packages restores the plumbing.

  1. Right-click Start and open Terminal (Admin).
  2. Run: Get-AppXPackage -AllUsers Microsoft.Windows.Search | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}.
  3. Restart the Windows Search service in services.msc after the command completes.
  4. Restart the laptop.
  5. Test a descriptive query in File Explorer. If semantic search returns now, the registration was the break.

Fix 5: Tune search settings and clear the search history

Sometimes the feature works but your settings or a poisoned search cache get in the way — for example, cloud content settings or a stuck suggestion cache returning stale empty results for new queries.

  1. In Settings > Privacy & security > Searching Windows, toggle Cloud content search off and back on, then test.
  2. Scroll to History and click Clear device search history.
  3. In Advanced indexing options, confirm Index encrypted files matches your actual setup — mismatches here silently exclude files.
  4. Try the descriptive query in a different folder (Documents vs. Pictures) to see if the failure is location-specific.
  5. If one folder works and another does not, remove and re-add the failing folder under Add an excluded folder (add it, then remove it) to force a re-crawl of just that location.

Fix 6: Rule out a damaged user profile

Search caches, AI model permissions, and per-user settings all live in your profile. A five-minute test with a fresh local account tells you definitively whether the problem is your profile or the system.

  1. Go to Settings > Accounts > Other users > Add account.
  2. Create a local account without a Microsoft account and sign in to it.
  3. Open File Explorer there and try the same descriptive query on the same files (copy a test file to the Public folder so both accounts can see it).
  4. If semantic search works in the new profile, migrate your data — your old profile’s search state is damaged.
  5. If it fails in the new profile too, run an in-place upgrade repair from the Windows 11 download page , keeping files and apps; that restores system components the earlier fixes cannot.

Closing

Natural language file search fails when the AI layer is missing rather than when search itself is broken — the on-device model, the NPU driver, or the region gate is almost always the story. Filenames working while descriptions fail is the diagnostic clue that points you straight at Fixes 2 and 3. Once the model is downloaded and the driver is healthy, descriptive queries start answering, and File Explorer finally searches the way the Copilot+ marketing promised.

Frequently asked questions

What is natural language search in File Explorer?
It is the Copilot+ PC feature that lets you describe a file in plain words — like “budget spreadsheet from last month” — instead of typing an exact filename. The query is interpreted by an on-device AI model running on the NPU, which matches meaning rather than just keywords.
Why does it work for filenames but not for descriptions?
That split means classic keyword search is fine but the semantic AI layer is not running. The usual causes are a missing on-device AI model, a broken NPU driver, or an unsupported region or display language blocking the AI features from activating.
Does natural language file search send my files to the cloud?
No. On Copilot+ PCs the semantic matching happens entirely on-device using the NPU — your file contents and queries are not uploaded. It works offline once the model has downloaded, which is exactly why the NPU driver matters so much.
Do I need to be signed in with a Microsoft account for it to work?
Semantic search in File Explorer does not require a Microsoft account — it is a local, on-device feature. A local account works fine. If someone told you to sign in to fix it, that applies to cloud Copilot features, not to File Explorer search.