Questions

Letter L + space - Windows 7 bug

Tags:
+
0 Votes

Letter L + space - Windows 7 bug

infradium
Last week while we were trying to solve a problem presented by a user we found ourselves in this situation.

When we tried to do a fast search (using the search bar located in the folder windows, (Win 7) we found that all the files that started with the letter L and a space were not included in the results of the search.

For example, the user has a folder were the files names are set this way: L 20887, L 25321, L 54851. Trying a search looking for a file through the identifying number (Eg: 20887) the search result doesn’t show any files. If we change the L for any other letter (we tried them all) and do the same search the result is correct.

We thought it might be a problem with the fileserver where those files are allocated but when we tried the same locally we found practically the same result with a small difference: The search results don’t highlight the file that start with L but it shows at the end of the search list. If there’s only one file in the folder starting with L and followed by a space and numbers the search result doesn’t show any files.

Thank you.

Member Answers

    • +
      1 Votes
      robo_dev

      Are you using indexing services? Shut that off.

      Turn indexing off for "\Users" indexing. Indexing Options>Modify and uncheck "\Users" indexing box.

      Although indexing is supposed to speed searching, if it misses files (which it does), then perhaps folks would want to trade accuracy for speed.

      The free FileSearchEx app works very well as a search tool.

      +
      1 Votes
      gechurch

      Perhaps it's fixed in an update, because it works as expected for me (locally, Win7 Pro 64-bit, SP1) when using the folder names you gave (they show up at the top of the list).

      +
      0 Votes
      Charles Bundy

      Me too, so it would seem the default works...

      +
      0 Votes
      Charles Bundy

      I'm thinking natural language search might be a culprit. Or anything that interprets your query. Default should work fine, unless what you think is a space is something else in the filename.

      ADDENDUM: I like [robo_dev]'s suggestion and would try that first.

      +
      0 Votes
      markp24

      has anyone used that? wondering if thats any good, i have sen it recommended.

      +
      0 Votes
      infradium

      I did it, but it doesnt work.

      +
      0 Votes
      pcunite

      We've moved all our users to something called FileSearchEX. No retraining and does not require admin rights (after installed) so it is secure. For this specific question you would need to quote the space ... so search for "L ".

      +
      0 Votes

      bug

      infradium

      So do you think the same as me, it is a bug from W7, W8...?

      Turning off indexing services for “\Users” gives the same result when typing the last part of the file name in the search box.
      What we noticed is that when a file starts with L(space) windows skips the rest of the file name from the search.

      +
      0 Votes
      Charles Bundy

      OK I just tried something for you -

      Created a file called "L 28830.TXT". Typed 28830 in search bar. Worked like a charm. Renamed file by removing the space "L28830.TXT". Doesn't show up anymore in search with 28830. Typed in *28830 in search bar and "L28830" was returned.

      Hypothesis is what you think is a space is not ACSII 0x20. It is probably unprintable like a TAB 0x09 and being treated as a regular ASCII character in the search. Did a program or a person name these files?

      +
      0 Votes

      bug

      infradium

      it is a script which name the files

      I think that the best solution is change it (the script), I don't think that MS will do it first.

      thank you for your support!

    • +
      1 Votes
      robo_dev

      Are you using indexing services? Shut that off.

      Turn indexing off for "\Users" indexing. Indexing Options>Modify and uncheck "\Users" indexing box.

      Although indexing is supposed to speed searching, if it misses files (which it does), then perhaps folks would want to trade accuracy for speed.

      The free FileSearchEx app works very well as a search tool.

      +
      1 Votes
      gechurch

      Perhaps it's fixed in an update, because it works as expected for me (locally, Win7 Pro 64-bit, SP1) when using the folder names you gave (they show up at the top of the list).

      +
      0 Votes
      Charles Bundy

      Me too, so it would seem the default works...

      +
      0 Votes
      Charles Bundy

      I'm thinking natural language search might be a culprit. Or anything that interprets your query. Default should work fine, unless what you think is a space is something else in the filename.

      ADDENDUM: I like [robo_dev]'s suggestion and would try that first.

      +
      0 Votes
      markp24

      has anyone used that? wondering if thats any good, i have sen it recommended.

      +
      0 Votes
      infradium

      I did it, but it doesnt work.

      +
      0 Votes
      pcunite

      We've moved all our users to something called FileSearchEX. No retraining and does not require admin rights (after installed) so it is secure. For this specific question you would need to quote the space ... so search for "L ".

      +
      0 Votes

      bug

      infradium

      So do you think the same as me, it is a bug from W7, W8...?

      Turning off indexing services for “\Users” gives the same result when typing the last part of the file name in the search box.
      What we noticed is that when a file starts with L(space) windows skips the rest of the file name from the search.

      +
      0 Votes
      Charles Bundy

      OK I just tried something for you -

      Created a file called "L 28830.TXT". Typed 28830 in search bar. Worked like a charm. Renamed file by removing the space "L28830.TXT". Doesn't show up anymore in search with 28830. Typed in *28830 in search bar and "L28830" was returned.

      Hypothesis is what you think is a space is not ACSII 0x20. It is probably unprintable like a TAB 0x09 and being treated as a regular ASCII character in the search. Did a program or a person name these files?

      +
      0 Votes

      bug

      infradium

      it is a script which name the files

      I think that the best solution is change it (the script), I don't think that MS will do it first.

      thank you for your support!