What's new – PowerEverything3 (update after 0.1.0)
Everything SDK 3.0.1.12
Updated Everything3_x64.dll from SDK 3.0.0.9 to 3.0.1.12 (multiple sessions support, better waiting on busy pipes)
Tested with Everything 1.5.0.1424b (and 1.5.0.1423b) and PowerShell 7.6.9
Fixes
Find-Files -Extensions returned no results on Everything 1.5. The query was built as (ext:a|ext:b), but Everything does not treat round brackets as grouping. It now builds ext:a;b, and leading dots (.pdf) are accepted
Thanks to andbrai for reporting this and for the patch (issue #1). I did not take over ext:a|b as it means "ext:a OR name contains b" and returned false hits such as docxlist.xml
New
Integration tests (Pester) for Find-Files -Extensions: tests/Integration, own fixture folder in %TEMP%, results compared with the file system
skills/everything-search: a skill for AI coding agents (e.g. Claude Code) with the usage of the module and the search-syntax pitfalls below
Search syntax pitfalls (measured on 1.5.0.1423b and 1.5.0.1424b)
Round brackets do not group: * (ext:pdf) finds nothing. Use < > for grouping
Several extensions: ext:pdf;docx, not ext:pdf|docx
Everything indexes long paths. A path like C:\Users\NAME~1.X\... (8.3 short name, e.g. from %TEMP%) finds nothing
"C:\Folder" counts the folder itself, "C:\Folder\" does not: an empty folder gives 1 hit without and 0 with the trailing backslash
Please note
Find-Files -Extensions needs this update. Before, it silently returned nothing
Everything 1.5.0.1424b removes the old beta instance "1.5a". Connect-Everything -InstanceName '1.5a' now fails with "pipe not found"; the default instance works
Everything 1.5.0.1424b only accepts connections from programs in the same Windows session. A scheduled task running without a logged-on user (session 0) can open a connection, but its first search fails with error 0xE0000003. If you need this, run the script in the user's session or use a normal file system scan instead. I tested only this one case (not RDP sessions)