I'm experiencing a frustrating problem with Windows 11 version 25H2 where File Explorer isn't using the server-side search index for SMB shares. I've tried a few different setups, and here's what I've found:
- On Windows 11 version 22H2, network content searches work perfectly, utilizing the server index.
- The same goes for version 24H2, which also functions as expected.
- However, with 25H2, whether it's an upgrade from 24H2 or a fresh install, I can't get any content results, just filenames.
I've tested this against both Windows Server 2012 and Windows Server 2022, and the Windows Search Service is enabled with indexing on the shares. Clients running 22H2 and 24H2 can access instant content results from the server index without issues.
It seems like 25H2 may have broken the remote indexed search over SMB due to a potential change in the search protocol, security settings, or possibly a regression. I noticed things like "RemoteIndexedSearch" not operating anymore, and the option to "Include in Library" has gone missing when I right-click on network folders, suggesting that Windows thinks these locations aren't indexable.
Has anyone else encountered this issue? Is there any known workaround, or could there be a registry/GPO fix for it? I've also reported this through the Feedback Hub, and it's gathering some traction. Any insights would be appreciated!
1 Answer
This might be tied to the same update that disabled file previews. It makes sense that if the files can’t be previewed, they can't be indexed either. Check if the files have the Mark of the Web and consider adding the source domain to your trusted sites zone for proper indexing. There's some support documentation on this too!
I’m looking for the right registry key to adjust for shares to avoid always unlocking via PowerShell. Got any ideas?