Solved findstr : Why not found?

das10 · Mar 30, 2025

Is it possible that the second file might be encoded using UTF-16, in which case findstr won't work with it? Instead, you could try "find" which appears to detect the presence/absence of "Mode=", or findtsr using regex also appears to work on UTF-16 files (with awkward string input & output!) .

Code:

findstr /R /C:"M.o.d.e.=" desktop.ini
find /C "Mode=" desktop.ini

FINDSTR does not support UTF-16 files, but FIND does.

Findstr - Search for strings command - Windows CMD

ss64.com

pseymour · Mar 30, 2025

or type desktop.ini | findstr /c:"Mode="

anyname · Mar 30, 2025

The mystery is solved.

I thank you both.

Apparently pseymour's solution (ignoring the typo) works because the output of command "type" is not UTF-16.

Command "find" works if you omit the /C. Its output adds line containing file name (undesirable in my use).

pseymour · Mar 30, 2025

Yeah I was actually looking for a different string to test it and changed it to More/Mode when I pasted it here. :)

Search

Solved findstr : Why not found?

anyname

Banned

My Computer

At a glance

das10

Well-known member

Findstr - Search for strings command - Windows CMD

My Computer

At a glance

pseymour

tell me again what you think about OneDrive

My Computer

At a glance

anyname

Banned

My Computer

At a glance

pseymour

tell me again what you think about OneDrive

My Computer

At a glance

Similar threads

Latest Support Threads

Latest Tutorials

Solved findstr : Why not found?

Banned

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

tell me again what you think about OneDrive

My Computer My Computer

At a glance

Banned

My Computer My Computer

At a glance

tell me again what you think about OneDrive

My Computer My Computer

At a glance

Similar threads

My Computer

My Computer

My Computer

My Computer

My Computer