How do I fix empty search results on mapped network shares in Windows 11 25H2?

Why is Windows Explorer not finding files on network drives after December 2025 updates?

Network Search Failures in Windows 10 and 11: December 2025 Advisory

System administrators are reporting a critical issue affecting Windows 10 and 11 clients within domain environments. As of December 2025, Windows Explorer fails to return results when searching mapped network drives. This behavior differs from previous slowdowns; the search function now yields zero files despite correct indexing on the file server.

Affected Environments and Symptoms

The issue primarily impacts clients running Windows 11 Pro (versions 24H2 and 25H2) and Windows 10 (version 22H2). These clients typically connect to Windows Server 2022 Acting as the Primary Domain Controller.

Key Symptoms:

• Zero Results: Queries on network shares return no files immediately.
• Search Lag: In some instances, the search bar freezes or hangs indefinitely.
• Scope: The problem occurs on mapped network drives despite the “Windows Search” service running correctly on the host server.

Diagnosis: Update Rollouts and Patches

Understanding the patch history is vital for troubleshooting.

1. The Trigger (November 2025): Update KB5068861 introduced significant latency to file server searches.
2. The Proposed Fix (December 2025): Microsoft released Preview Update KB5070311 (also included in the December security rollout) to address the latency.

While KB5070311 resolved the speed issue for some, it has not fixed the “zero results” error for all configurations. If you have deployed the December security update and still face issues, the patch alone is insufficient.

Recommended Troubleshooting Steps

Execute these solutions in order of complexity.

Reset Search Components via PowerShell

Corrupted local search packages often cause Explorer interface failures. Run the following commands in an elevated PowerShell window (Run as Administrator) to reset the client web experience and search components.

Get-AppxPackage -AllUsers MicrosoftWindows.Client.WebExperience | Reset-AppxPackage
Get-AppxPackage -AllUsers MicrosoftWindows.Client.CBS | Reset-AppxPackage
Restart-Service WSearch

Rebuild the Search Index

Although often unsuccessful for this specific bug, you must rule out index corruption.

1. Navigate to Control Panel > Indexing Options.
2. Click Advanced.
3. Select Rebuild under the Troubleshooting section.

Verify SMB Protocols (NAS Configurations)

If your environment uses Synology or QNAP NAS devices rather than Windows Server, protocol mismatches may block file enumeration.

• Symptom: Windows 11 25H2 may block access to files entirely.
• Temporary Workaround: Test enabling SMB 1.0 in Windows Features.
• Note: Keep the NAS configured for SMB2/SMB3. If enabling SMB 1.0 on the client restores search, the issue lies in the SMB handshake negotiation introduced in 25H2.

Audit for Duplicate SIDs

Recent reports indicate that duplicate Security Identifiers (SIDs) cause NTLM and Kerberos authentication failures. This prevents the search service from authenticating against the share to read the file list.

• Scenario: This frequently occurs in environments where machines were cloned without proper Sysprep.
• Solution: Run a diagnostic tool like SIDCHG64 to verify unique SIDs. If duplicates exist, regenerate the SID to restore proper SMB authentication and search functionality.