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:orcontent:), 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.CBSpackage and clearing theLocalStatecache.
- Disabling SMB Signing/Encryption via GPO and Registry (
- 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