Until today, I was using 1403a alpha build, and I always had an active file filter that filtered out system files and anything located on the Windows drive (C:), so I could search among files on other drives. Whenever I opened the software window using a shortcut, the searchable files would appear immediately, with the filter applied, and with no delay or lag.
However, after updating today to the beta build (version 1413), I noticed that every time I open the software window — with the filter to exclude system files, folders, and the entire Windows drive already set — there is a 1-second lag or pause each time the window is invoked. During this pause, nothing is displayed, and the status bar shows the word "querying." After the 1-second delay, the file list appears and becomes ready for searching. This happens repeatedly, exactly the same way every single time I invoke the window with the shortcut.
I would like to know what is causing this lag and delay, whether this is a known issue, and if there is any solution ?
Repeated and persistent lag/delay when displaying search window
Repeated and persistent lag/delay when displaying search window
Last edited by chivo on Thu May 28, 2026 9:24 am, edited 1 time in total.
Re: Repeated and persistent lag/delay when displaying search window
Please send a debug log:
- In Everything, from the Tools menu, under the Debug submenu, click Start Debug Logging...
- Close the Everything window.
- Reopen the Everything window.
- From the Tools menu, under the Debug submenu, click Stop Debug Logging...
This will open your %TEMP%\Everything Debug Log.txt in your text editor. - Please upload this file in a bug report.
Re: Repeated and persistent lag/delay when displaying search window
I checked, and the last version I was using before this was 1403a. It wasn't the latest alpha build either — I had updated version 1403a to the latest alpha build (1409a). Currently, I have two versions of the software installed and running simultaneously on my system: both version 1409a (alpha) and version 1413 (beta). Both exhibit the same delay when displaying and loading the window and the search list. Both builds have the delay. I have uploaded the debug files for both versions.void wrote: Thu May 28, 2026 8:35 am Please send a debug log:
- In Everything, from the Tools menu, under the Debug submenu, click Start Debug Logging...
- Close the Everything window.
- Reopen the Everything window.
- From the Tools menu, under the Debug submenu, click Stop Debug Logging...
This will open your %TEMP%\Everything Debug Log.txt in your text editor.- Please upload this file in a bug report.
Re: Repeated and persistent lag/delay when displaying search window
Thank you for the logs.
This search is expensive and will likely match nothing.
What are you trying to match here?
Please replace your old filter search:
with:
ancestor-name:
*.\\$recycle.bin\*This search is expensive and will likely match nothing.
What are you trying to match here?
Please replace your old filter search:
Code: Select all
!C:\ !path:$recycle.bin\* !path:$recycle.bin\* !path:*.\\$recycle.bin\*
Code: Select all
!C:\ !whole:ancestor-name:$recycle.bin
Re: Repeated and persistent lag/delay when displaying search window
And, was included in there twice.
Does Everything recognize that & disregard the second instance of it?
(I know on [multiple file] renames, in the set of files to be renamed, it does not rename a name that does not need to be renamed - like when you have differing case of file with otherwise the same name.)
Oh, & in my $recycle.bin excludes, I typically use as that seems to be sufficient.
!path:$recycle.bin\*Does Everything recognize that & disregard the second instance of it?
(I know on [multiple file] renames, in the set of files to be renamed, it does not rename a name that does not need to be renamed - like when you have differing case of file with otherwise the same name.)
Oh, & in my $recycle.bin excludes, I typically use
\$recycle.binRe: Repeated and persistent lag/delay when displaying search window
Normally Everything will remove duplicated terms.Does Everything recognize that & disregard the second instance of it?
In this case it doesn't because they are NOT-ed.
I'll look into optimizing duplicated NOT-ed terms out and I'm working on optimizing $recycle.bin\** => whole:ancestor-name:$recycle.bin
This is fine, the recommend (and most efficient way) is to just excludeOh, & in my $recycle.bin excludes, I typically use
\$recycle.bin
as that seems to be sufficient.
$recycle.binRe: Repeated and persistent lag/delay when displaying search window
I'm using the settings from this post:void wrote: Fri May 29, 2026 2:24 am This is fine, the recommend (and most efficient way) is to just exclude$recycle.bin
?:\$RECYCLE.BINvoid wrote: Mon Feb 06, 2023 11:08 am The following filter will match the recycle bin folder on any drive:
?:\$recycle.bin
?:\$recycle.bin matches c:\$recycle.bin, d:\$recycle.bin, e:\$recycle.bin, etc...