SearchMyFiles now uses an internal wildcard parser instead of basing the search result on the wildcard parser of Windows. This change solves an annoying bug caused by Windows wildcard parser: In previous versions, SearchMyFiles sometimes returned incorrect results, because Windows also matches the wildcard with the short filename (8.3 DOS format).
Notice: The new wildcard parser may cause some compatibility issues, for example: When you scanned using *.* wildcard with Windows parser, it returned all files, including files without extension. With the new SearchMyFiles wildcard parser, *.* returns only files with extension. In order to return all files, you should use * instead of *.*
When loading old config files, SearchMyFiles automatically converts all *.* wildcards to *
The new wildcard parser has some advantages, for example: if you search for *.*.*.*, you'll get all files with 3 dot characters or more. With Windows wildcard parser in previous versions, you simply got the list of all files.
You can now exclude files by using wildcards list. You have to select this option from the combo-box, because the default option is to exclude files by extension.
You can now specify environment strings in the 'Base Folders' and 'Excluded Folders' fields (For example: %AppData% )