Windows 10 behaviour doesn't match Windows 8.1

[HarryStottle]

might be just me but I can't get the basic search syntax to work under Win 10.

Ferinstance I have a file whose name contains "enemy at the gates". Under Win 8.1, the search: enemy gates
would home in on it instantly.

Under 10, enemy finds 182 matches, but as soon as I type the letter g, the results disappear and the query reports 0 objects

and none of the Regex searches work (and yes, it's enabled. regex: doesn't work either)

I'm using v 1.3.4.686 (64)

Is this a known Win 10 issue?
Suggestions?

[gcrawdad]

I just tried a similar type of search and it seems to work ok on mine. Also have Windows 10.

[void]

Under 10, enemy finds 182 matches, but as soon as I type the letter g, the results disappear and the query reports 0 objects

Maybe Match Whole Word is enabled from the Search menu?
What is search options are displayed in the bottom right of the status bar?

If you are using Regex, spaces must match, you might need to search for:

Code: Select all

enemy.*g

[HarryStottle]

right, well that's my first dumb ass mistake of the year out of the way.

Didn't realise that when you enable regex, that's the ONLY search it will do. As soon as I disabled it, "enemy gates" found the file like it did under 8.1 (where I must have been running with regex disabled)

However, it reveals that I must still be getting the regex searching wrong because they still don't find anything. I'm intrigued by your example which looks like:
CODE: SELECT ALL
enemy. *g

which appears on two lines in a form I can't seem to emulate. What am I missing?

[void]

Ignore the Code: Select All

Please try searching for:
enemy.*g

[HarryStottle]

Bingo!

That worked.

Cheers