Windows Search Non Functional on NPU Machines

Marc Gunn 5 Reputation points
2026-02-16T20:41:37.83+00:00

I currently have two Dell PA13250 machines, both fully patched to 25H2 (Build 26200.7840). These devices will not return any results from SMB shares on a Windows 2019 Server. I have multiple other machines on the same network, same domain, that have zero problems with Windows Search, and easily access the network shares.

I believe that the problem is that the Dell PA13250 machines have the "Copilot AI" neuro processors installed, where none of the other machines have such processors. The Indexer Version of the problem machines is 10.60502.60502. Working Machines use version 9.60502.60502. I believe that the "upgraded" version of the indexer is due to the AI processor - but I cannot confirm this to be true.

The Server is running all required roles, and has Windows Search Service enabled and running. I have confirmed that if I create a "new" network share, but don't include the shared location in the server index, then I can search that location by file name. As soon as the network share is added to the server index, I am no longer able to search for files and search results immediately return "No items match your search". This behavior only happens with Shares from the 2019 Server, as files on a NAS can be searched without issue.I and Gemini have become close these past several weeks, and I have tried every "fix" Gemini and Copilot have been able to generate: registry keys, reindexing (server and client), resetting search host packages, etc.

I believe the issue may be related to the fact that 25H2 is blocking the "handshake" required to see Server 2019 results. Despite adding registry keys to "force" recognition of the server index, I still have the same problem.

I am willing to upgrade my Server to 2025, as having search is critical to workflow. However, I have seen that even with Server 2025 there appear to be similar issues with "AI" machines. Are there any suggested work arounds or "fixes" to this ongoing problem?

Windows for business | Windows Client for IT Pros | Networking | Network connectivity and file sharing

1 answer

Sort by: Oldest
  1. Marc Gunn 5 Reputation points
    2026-02-20T00:00:24.7+00:00

    Not generally a fan of commenting on my own posts, but perhaps more information would be helpful if someone else has this problem. Here is a technical summary of what has still not worked:

    I appear to be experiencing an ongoing specific regression between Windows 11 Build 26200.7840 (25H2) and Windows Server 2019 search indexing.

    Technical Summary: Remote SMB Search Regression

    • Environment:
      • Client: Windows 11 Pro/Enterprise (Build 26200.7840, Version 25H2) on NPU-equipped hardware (Dell/Intel Core Ultra).
      • Server: Windows Server 2019 (File Server Role with Windows Search Service).
      • Connection: SMB 3.1.1 (FQDN-mapped drives and UNC paths).
    • The Issue: General keyword searches on network shares return 0 results instantly, even when the server index is fully built and healthy. Results only appear when using explicit property filters (e.g., filename: or content:), which triggers a slow, non-indexed "Greedy Search" (live directory crawl).
    • Root Cause Analysis: The Remote Search Broker (the background "Named Pipe" over SMB) fails to handshake between the new NPU-integrated AI Shell (Client.CBS) and legacy Server 2019 indices.
      • Protocol Failure: The client enforces SMB Signing (Signed: True) for FQDN/Kerberos connections. The search broker fails to authenticate over this signed pipe on Build 26200, causing a silent fallback to local search (which has 0 results for remote paths).
      • NPU Interception: The Windows Semantic Indexer (WUISearch.exe) intercepts general queries but currently lacks the "Trust" or logic to ingest remote index data from Server 2019 on this specific build.
    • Attempted Fixes (Unsuccessful):
      • Disabling SMB Signing/Encryption via GPO and Registry (AllowRemoteIndexing, PreventRemoteQueries, DisableSemanticSearch).
      • Updating Dell NPU Drivers to 32.0.100.4512 and applying KB5077181 (Feb 2026).
      • Resetting the Client.CBS package and clearing the LocalState cache.
    • Current Somewhat Functional Workaround: Creating a Symbolic Link (mklink /D C:\NetworkShare \\Server\Share) and adding it to a Library. This tricks the OS into using the Local Search Provider, which successfully bypasses the broken Remote Search Broker but results in slower "non-indexed" performance.

    If anyone has any insight, that would be appreciated


    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.