This is an automated archive.
The original was posted on /r/sysadmin by /u/PizzaCatLover on 2023-07-17 18:40:07+00:00.
Okay so here's a weird one that may not have a solution...
My employees work with design files and diagrams that are listed as part numbers on a network share. They often want to use File Explorer's search function to see what all files exist for a part, with revisions and such. The problem is, they aren't getting consistent results. Check this out...
There are about 60 files in a given folder that start with "1116-". Of those, 40 or so start with "1116-A". There are three that start with "1116-A0003_".
Typing "1116-" in the search box comes up with full results as expected. But putting "1116-A", it only shows one result instead of the 40 that there should be matched to that string. Continue entering characters up to "1116-A00" and there is no change, it only shows one result. When you get to "1116-A000" by putting in the third zero, the only result you had disappears and you get "No items match your search". Adding a 3, still nothing. Punch one more character in for "1116-A0003_" and poof - all three results show up. as they should. Interestingly, in the results box, it's only highlighting the "1116" part in the results, but all three files that should show are now showing.
We've also figured out that if you put a leading wildcard asterisk, like "*1116-A", it works completely as expected and all the files show up when and how they should(though still only highlighting 1116 and not the full string).
I've replicated this behavior on several Windows 11 and Windows 10 boxes, as well as on Server 2019. To rule out a problem with the network fileshare, I copied all these files to a local path on my workstation, and it works exactly the same way.
Surely there is some bug with Windows search here? Has anyone else discovered a fix for this? Alternatively, is there an application similar to Everything that could be used as a workaround for these employees?
Thanks!