Forum Discussion

TheZakiSayed's avatar
TheZakiSayed
Copper Contributor
Aug 02, 2026

Search in File Explorer can't find files with hyphens

All files and folders with the same keywords but using spaces, hyphens, and underscores as word separatorsOnly the first keyword is correctly found.The folder using hyphens was found but not the file when searching for either alphabetical or numerical keywords that didn't appear at the start.Unlike underscores, searching for a single hyphen returns ALL files and folders as if a hyphen is not even recognized as a valid searchable character (like space). However, searching for "--" returns nothing even when a file and folder name had it (no screenshot). Pairing "--" with keywords (either suffix or prefix) produces similar unusual search results like with single hyphen. This makes "--" useless as a special separator for a metadata segment like how "__" (2 underscores) can be used in names like "Project_Proposal__FLAG.docx" to find all files with the flag.Keywords with hyphen as prefix don't find folders with the matching search term.Keywords with hyphen as suffix return similar results (missing files with hyphens) as if the search term didn't have the hyphen as suffix at all.Numerical search terms with hyphens as both suffix and prefix ("-123-") return same results (missing folders with hyphens) as an alphabetical search term with hyphen only as prefix (see screenshot for "-middle").

Search not only fails to find the files with hyphens, the results are inconsistent as well depending on the searched terms.

Remember to not immediately conclude that you don't have the file (if it has hyphens around the search term) when a File Explorer search doesn't show it. Try searching with asterisks like *this* and it will find the file correctly. That said, we can't expect everyone we share files with to know that.

Microsoft REALLY needs to fix search and File Explorer in general.

3 Replies

  • Bonniewest's avatar
    Bonniewest
    Bronze Contributor

    Your point about Microsoft needing to improve search functionality is valid. Many users have reported similar issues, and better search accuracy and reliability would greatly enhance user experience. Until then, employing techniques like wildcard searches can help mitigate these problems.

    • TheZakiSayed's avatar
      TheZakiSayed
      Copper Contributor

      The main reason I made this post is for public awareness as most people (based on my experience) don't have their digital data well organised and rely on memory, visual scanning, or search to find their needle in a haystack.

      Also, files are often shared and majority of people outside the tech circle have no idea of using wildcards. I've even worked with software developers who had no idea they could use * in Windows search. When they search for something and see no results, they conclude that file doesn't exist which is practically data loss -- unless it's mission critical and they have to dig into their messy folders, wasting time.

      I wouldn't frame it like you have as if the current search works fine and fixing the reported issues will "enhance the user experience". Let's not water it down. My post demonstrates the current search functionality is BROKEN.

      If it was an issue with some obscure characters, it would've been acceptable. Hyphen is not some obscure Unicode character, and kebab-case is one of the most common file naming conventions. Being able to find files with exact matching keywords using the absolute baseline A-Z and 0-9 characters beyond the first word is NOT about an enhancement -- it's a basic requirement.

  • Faulk's avatar
    Faulk
    Copper Contributor

    Your point about Microsoft needing to improve search functionality is valid. Many users have reported similar issues, and better search accuracy and reliability would greatly enhance user experience. Until then, employing techniques like wildcard searches can help mitigate these problems.