The command sends the specified lines to the standard output device.5 It is similar to the find command. However, while the find command supports UTF-16, findstr does not. On the other hand, findstr supports regular expressions, which find does not. The findstr program was first released as part of the Windows 2000 Resource Kit under the name qgrep.6
findstr cannot search for null bytes commonly found in Unicode computer files.7
Arguments:
Flags:
Note: Following command displays the detailed help about this command:
Save your running services into file _services.txt and search in this file for lines containing word "network" - case insensitive:
output would be:
Microsoft WinXP documentation for findstr https://technet.microsoft.com/en-us/library/bb490907.aspx ↩
Microsoft Server 2012/2016 documentation for findstr https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/findstr ↩
"Reactos/Reactos". GitHub. 16 October 2021. https://github.com/reactos/reactos/blob/master/base/applications/findstr/findstr.c ↩
MS-DOS and Windows command line findstr command https://www.computerhope.com/findstr.htm ↩
Excellent documentation on usage of findstr https://stackoverflow.com/questions/8844868/what-are-the-undocumented-features-and-limitations-of-the-windows-findstr-comman#8844873 ↩
History of Findstr from Raymond Chen https://devblogs.microsoft.com/oldnewthing/20121128-00/?p=5963 ↩
Findstr - Search for strings - Windows CMD - SS64.com https://ss64.com/nt/findstr.html ↩