windows explorer slows to a crawl after installation

[mtasquared]

Hello,

I love everything but after installing it my windows explorer slows to a crawl, and sometimes takes 2 minutes to open a folder on my desktop.

I am wondering if it is because everything is indexing in the background, or the service is causing this.

I have windows 11. I have a PC with four nvme drives and some 17 million files.

I suspect that if i configured the installation differently I would not have this problem.

Any suggestions, similar experiences or solutions? Please help. Ty

[harryray2]

I run Win 7 on an oldish computer...I do find that indexing does slow things down, sometimes considerably and occasionally freezes the computer completely.

For example, I was experimenting with:
eachline:content:<a b c d e f g h|i j|k l|m|n !o !p !d>

This caused a complete freeze for quite a long time.

[void]

What does the CPU usage for Everything look like?
What does the RAM usage for Everything look like?
What does the CPU usage for Explorer look like?
What does the RAM usage for Explorer look like?


Please make sure Everything is not running as an administrator.

• In Everything, from the Tools menu, click Options.
• Click the General tab on the left.
• Check Store settings and data in %APPDATA%\Everything.
• Uncheck Run as administrator.
• Check Everything Service. (Please make sure this is tick-checked and not square-checked)
• Click OK.
• Exit Everything (right click the Everything tray icon and click Exit).
• Restart Everything.
• If you make any changes above, please restart your PC to ensure no Explorer.exe processes are also running as an admin.

Does the slowness only occur when Everything is indexing?


Please try reducing the number of files indexed.
Does the issue persist?

eachline:content:<a b c d e f g h|i j|k l|m|n !o !p !d>

This caused a complete freeze for quite a long time.

This is expected.
Combine with more filters for the best performance.

[mtasquared]

Thanks for the replies.

When the slowup occurs, the cpu and ram usage for everything and windows explorer is not unusual. That is to say, close to zero.

I was kind of hoping that configuring it differently on install would help.

Such as not installing the service, or disabling indexing. There are also numerous settings which i do not understand. However, won't disabling indexing or the service render the program unable to do its job?

Thanks again guys for the input.

[harryray2]

Would it be possible to have a way of excluding files/folders from property indexing, whilst not excluding the same files/folders from the search?

This would help a lot as the files that I need to be property indexed are a relatively low percentage of all the files, while at the same time the files/folders that I need to search are high.

[hamid56]

Dear David
adding ram-cpu usage by everything.exe process at status bar of Ev1.5 is very beneficial.
please add to TODO list with high periority.

[void]

Are you indexing any properties under Tools -> Options -> Properties?
Are you indexing any content under Tools -> Options -> Content?



I will consider showing the RAM/CPU usage in the status bar.
Thank you for the suggestion hamid56.

[void]

Such as not installing the service, or disabling indexing. There are also numerous settings which i do not understand. However, won't disabling indexing or the service render the program unable to do its job?

Everything will only index once.
Is the initial index causing the system slowness?

I highly recommend installing the "Everything Service" and "Store settings and data in %APPDATA%\Everything"
You can change these settings at any time:

• In Everything, from the Tools menu, click Options.
• Click the General tab on the left.
• Check Store settings and data in %APPDATA%\Everything.
• Uncheck Run as administrator.
• Check Everything Service. (Please make sure this is tick-checked and not square-checked)
• Click OK.
• Exit Everything (right click the Everything tray icon and click Exit).
• Restart Everything.

Without the Everything Service, Everything will be unable to index your NTFS volumes.

Would it be possible to have a way of excluding files/folders from property indexing, whilst not excluding the same files/folders from the search?

Please see: Exclude folders when indexing properties.