You open Settings, type “display” in the search box, and get nothing back — a blank list where results should be. The setting definitely exists, you have seen it before, and the mouse still works, so you end up clicking through every page by hand. On a Copilot+ PC this feels especially wrong, because the machine is supposed to have smarter search, not dumber search.

Settings search sits on top of the Windows Search service and its index. On Copilot+ hardware there is an extra layer: Microsoft’s semantic search, which runs on-device AI models through the NPU so you can type phrases like “change my screen brightness” instead of exact setting names. When any piece of that chain breaks — the service stalls, the index goes stale, the Settings app package loses registration, or the AI model never downloads — the search box either returns nothing or returns garbage.

This guide walks you through six fixes in technician order: restart the search plumbing, rebuild the index, run the official troubleshooter, re-register the Settings app, check the Copilot+ AI layer, and finally test whether your user profile itself is the problem. Similar search weirdness on the same machines can share a root cause with Wi-Fi 7 drops on Windows 11 , where a background service silently stalls after a driver update.

Why this happens

  • Windows Search service stalled: The service that feeds results to the Settings search box can hang after updates or sleep cycles, leaving queries to time out with zero results.
  • Corrupted or stale search index: If the index database is damaged or was never rebuilt after a major update, Settings entries are missing from it and keyword matches come back empty.
  • Settings app package lost registration: The Settings app is a modern app package; a failed update or interrupted Store sync can break its registration, which also breaks its search integration.
  • Copilot+ semantic AI model not downloaded: The on-device search model downloads in the background after setup. Until it arrives, natural-language queries fail and even keyword search can behave oddly.
  • Broken NPU driver: Semantic search calls the NPU. A generic or broken NPU driver means the AI search layer errors out instead of falling back cleanly to classic search.
  • Damaged user profile search data: Search personalization and cached results live in your profile. A damaged profile can break Settings search for your account while another account works fine.
  • Conflicting third-party search tools: Utilities that hook into Windows Search or replace the shell search experience can intercept and swallow Settings queries.

How to fix it

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

Fix 1: Restart the Windows Search service

Most sudden failures are a stalled service, not a broken system. Restarting it flushes hung query handlers and is the fastest possible fix, so it belongs first even though it looks too simple to matter.

  1. Press Win + R, type services.msc, and press Enter to open the Services console.
  2. Scroll to Windows Search, right-click it, and choose Restart.
  3. While you are there, confirm the Startup type is set to Automatic (Delayed Start).
  4. Open Settings and type a query in the search box — test something simple like “brightness”.
  5. If results return, you are done; if the service immediately shows as “Stopping” again, move on to the index rebuild. A service that will not stay running usually points at the same class of stuck background process that breaks Narrator natural voices .

Fix 2: Rebuild the search index

A damaged index is the most common persistent cause. Rebuilding forces Windows to re-catalog every Settings entry from scratch, which clears out the stale or missing records that make the search box return nothing.

  1. Open Settings > Privacy & security > Searching Windows and scroll to the bottom.
  2. Click Advanced indexing options, then click the Advanced button in the dialog.
  3. Under Troubleshooting, click Rebuild and confirm the warning dialog.
  4. Leave the laptop plugged in and idle — a full rebuild takes 30 minutes to a few hours depending on disk size.
  5. After indexing completes, test the Settings search box again with two or three different queries. Microsoft’s Windows support pages document what the index covers and how long rebuilds take.

Fix 3: Run the Search and Indexing troubleshooter

Before doing surgery on the app itself, let the built-in troubleshooter check the plumbing — service permissions, index locations, and group policy states it can repair automatically. It catches the configuration problems a restart cannot.

  1. Open Settings > System > Troubleshoot > Other troubleshooters.
  2. Find Search and Indexing and click Run.
  3. Select every symptom that applies (for example “Files, folders, apps, or settings don’t appear in results”) and click Next.
  4. Apply every fix the troubleshooter offers and let it finish.
  5. Re-test the Settings search box; if the troubleshooter reports it could not identify the problem, continue to the app re-registration below.

Fix 4: Re-register the Settings app package

When the index is healthy but Settings search still returns nothing, the app’s registration with the search system is broken. Re-registering re-links the Settings package to the search APIs without touching your data or settings.

  1. Right-click the Start button and choose Terminal (Admin).
  2. Run this command to re-register all inbox app packages, including Settings: Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}.
  3. Wait for the command to finish — it takes several minutes and may show red text that is safe to ignore.
  4. Restart the laptop so the re-registration fully takes effect.
  5. Open Settings and search again. If results now appear, the package registration was the culprit.

Fix 5: Check the Copilot+ semantic search layer

On Copilot+ PCs, search inside Settings is supposed to understand intent, not just keywords. If keyword search works but natural-language queries fail — or both fail — the on-device AI layer may never have come online. This is where the AI-PC hardware specifically enters the picture.

  1. Open Device Manager > Neural processors and confirm your NPU appears with no warning icon; a broken NPU driver kills semantic search. Related AI failures across apps share this root with OneNote Copilot problems .
  2. Open Settings > Windows Update and install every pending update, including optional driver updates — the Copilot+ AI components often arrive as separate downloads.
  3. Leave the PC plugged in on Wi-Fi for 30–60 minutes; the semantic search model downloads silently in the background after setup or major updates.
  4. Test with a natural-language query like “make text bigger” — if it now returns Display settings, the AI layer is alive.
  5. If only keyword search works and semantic search never arrives, check that your region and display language are supported for Windows AI features, then re-run Windows Update.

Fix 6: Test with a fresh user profile

Search caches and per-user registrations live in your profile, so a damaged profile can break Settings search for you while the machine itself is fine. A quick test with a new local account proves or rules this out in minutes.

  1. Open Settings > Accounts > Other users and click Add account.
  2. Choose I don’t have this person’s sign-in information, then Add a user without a Microsoft account, and create a local account.
  3. Sign out of your main account and sign in to the new one.
  4. Open Settings and type a query in the search box.
  5. If search works in the new profile, your old profile’s search data is damaged — migrate your files to the new account rather than fighting the corruption. If it fails there too, the problem is system-wide, and an in-place upgrade repair (keeping files and apps) is the honest next step, available from the Windows 11 download page .

Closing

Settings search breaks at one of six places: a stalled service, a stale index, a failed troubleshooter-level configuration, a deregistered app package, a Copilot+ AI model that never downloaded, or a damaged user profile. The order above moves from fastest to most invasive on purpose, and nearly every case resolves by Fix 4. Once the box answers again, give the index an hour of idle time to settle so results stay fast and complete.

Frequently asked questions

Why does typing in the Settings search box return no results?
The Settings app relies on the Windows Search index and its own app registration to return results. When the index is stale, the Windows Search service is stuck, or the Settings app package is corrupted, queries return nothing. Rebuilding the index and restarting the service fix most cases.
Does Copilot+ AI change how Settings search works on these laptops?
Yes, partially. Copilot+ PCs add semantic, natural-language search to Windows — including inside Settings — powered by on-device AI models on the NPU. If those AI components are not downloaded or the NPU driver is broken, semantic search falls back to plain keyword matching or fails silently.
Should I reinstall Windows if Settings search is completely broken?
No, that is almost never necessary. Reinstalling is a last resort that wipes your setup for a problem that lives in a service, an index, or an app package. Work through the service, index, and re-registration fixes below first — they resolve nearly every case.
Can my search highlights setting affect the Settings search box?
No, search highlights only control the rotating content in the taskbar search panel, not results inside the Settings app. If both are misbehaving at once, though, they share the same underlying Windows Search infrastructure, which points you at a service or index problem.