Solved findstr : Why not found?
- Thread starter anyname
- Start date
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!) .
FINDSTR does not support UTF-16 files, but FIND does.
Code:
findstr /R /C:"M.o.d.e.=" desktop.ini
find /C "Mode=" desktop.iniFINDSTR does not support UTF-16 files, but FIND does.
Last edited:
My Computer
System One
-
- OS
- Windows 11 23H2
- Computer type
- PC/Desktop
- Manufacturer/Model
- custom
- CPU
- intel i7-8700 (non-K)
- Motherboard
- Asus Z370 TUF Gaming
- Memory
- 32Gb
- Graphics Card(s)
- On-board Intel iGPU
- Sound Card
- On-board Realtek
- Hard Drives
- Samsung_SSD_850_EVO
- PSU
- Corsair Rm850X
- Cooling
- All air
or
type desktop.ini | findstr /c:"Mode="
Last edited:
My Computers
System One System Two
-
- OS
- Windows 11 Pro 24H2
- Computer type
- PC/Desktop
- Manufacturer/Model
- Intel NUC12WSHi7
- CPU
- 12th Gen Intel Core i7-1260P, 2100 MHz
- Motherboard
- NUC12WSBi7
- Memory
- 64 GB
- Graphics Card(s)
- Intel Iris Xe
- Sound Card
- built-in Realtek HD audio
- Monitor(s) Displays
- Dell U3219Q
- Screen Resolution
- 3840x2160 @ 60Hz
- Hard Drives
- Samsung SSD 990 PRO 1TB
- Keyboard
- CODE 104-Key Mechanical with Cherry MX Clears
- Antivirus
- Microsoft Defender
-
- Operating System
- Linux Mint 21.2 (Cinnamon)
- Computer type
- PC/Desktop
- Manufacturer/Model
- Intel NUC8i5BEH
- CPU
- Intel Core i5-8259U CPU @ 2.30GHz
- Memory
- 32 GB
- Graphics card(s)
- Iris Plus 655
- Keyboard
- CODE 104-Key Mechanical with Cherry MX Clears
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).
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).
Last edited:
My Computer
System One
-
- OS
- Win11 Pro 23H2
Yeah I was actually looking for a different string to test it and changed it to More/Mode when I pasted it here. :)
My Computers
System One System Two
-
- OS
- Windows 11 Pro 24H2
- Computer type
- PC/Desktop
- Manufacturer/Model
- Intel NUC12WSHi7
- CPU
- 12th Gen Intel Core i7-1260P, 2100 MHz
- Motherboard
- NUC12WSBi7
- Memory
- 64 GB
- Graphics Card(s)
- Intel Iris Xe
- Sound Card
- built-in Realtek HD audio
- Monitor(s) Displays
- Dell U3219Q
- Screen Resolution
- 3840x2160 @ 60Hz
- Hard Drives
- Samsung SSD 990 PRO 1TB
- Keyboard
- CODE 104-Key Mechanical with Cherry MX Clears
- Antivirus
- Microsoft Defender
-
- Operating System
- Linux Mint 21.2 (Cinnamon)
- Computer type
- PC/Desktop
- Manufacturer/Model
- Intel NUC8i5BEH
- CPU
- Intel Core i5-8259U CPU @ 2.30GHz
- Memory
- 32 GB
- Graphics card(s)
- Iris Plus 655
- Keyboard
- CODE 104-Key Mechanical with Cherry MX Clears
Similar threads
Latest Tutorials
-
Apps Use Copilot Vision in Microsoft Edge and Copilot app on Windows 11- Started by Brink
- Replies: 0
-
Privacy and Security Check Search Indexing Status in Windows 11- Started by Brink
- Replies: 0
-
Privacy and Security Enable or Disable Search Cloud Content from Apps in Windows 11- Started by Brink
- Replies: 0
-
Accessibility Add Word to Dictionary in Voice Access in Windows 11- Started by Brink
- Replies: 0
-
Time and Language Add or Remove Time in Notification Center in Windows 11- Started by Brink
- Replies: 0