Everything freezes when typing words

[toriatama]

Everything was working fine, then I installed new programs on my PC, uninstalled other and change some drivers, and now everything freezes when I am searching/typing a word in the search bar.

I was using the latest stable version, I've udpated with the latest night build (1.4.1.965.x64), but it continues to freeze...

What can I do?

Thank for your support and this great software (cannot live without it...)!

[void]

There might be a program making many changes to your file system?

Please try sorting by date modified in Everything and monitor your system for file changes:

• In Everything, click the Date Modified column header to sort by date modified.
• Are the results constantly changing? -How often and how many? Usually one or two a second is OK.

Everything likes to keep the database up-to-date.
File system changes are processed before searches.
If there are thousands of changes to process it can cause a search to be unrepsonsive.



Is there a program using 100% CPU?

• Press Ctrl + Shift + ESC to launch the Task Manager.
• Click the Details tab.
• Sort by CPU.
• Are there any programs using 100% CPU?

If there is a program using 100% CPU, Everything may not get enough CPU cycles to complete a search.

Try increasing the processing priority of Everything (not recommended):

• Press Ctrl + Shift + ESC to launch the Task Manager.
• Click the Details tab.
• Select the Everything.exe process (If there is two or more, do the following for all Everything.exe processes).
  • Right click the Everything.exe process and click Set Priority -> High.

There might be a low memory condition? Everything could be paging to and from disk.

• Press Ctrl + Shift + ESC to launch the Task Manager.
• Click the Performance tab.
• How much memory is being used?

[therube]

> I installed new programs
> uninstalled other and change some drivers

Such as?

[dfleiss]

This behavior started suddenly on my Windows 10 machine (v 1909, build 18363.657) yesterday when I upgraded from v 1.4.1.935 to v 1.4.1.965 (both x64). I tried reinstalling the older version but the behavior has persisted. I raised the priority, as suggested, but the behavior has persisted. I rebuilt the database, thinking that maybe it had become corrupted, but the behavior has persisted.

I'm on the verge of uninstalling Everything completely and performing a fresh install.

[void]

Try forcing Everything to build a fresh index:

• In Everything, from the File menu, click Exit.
• In Windows Explorer, navigate to: %LOCALAPPDATA%\Everything
• Delete your Everything.db
• Restart Everything.

Please try reducing the number of threads Everything uses:

• In Everything, type in the following search and press ENTER:
  /max_threads=3
• If successful, you should see max_threads=3 in the status bar for a few seconds.

Experiment with different values, I'm using 3 above, assuming you have at least 4 logical CPUs.
0 = unlimited threads (limited to total logical CPU count)
1 = single threaded
Try setting to any number less than your current total logical CPU count. Closer to 1 will make your Everything searches slow and make the system more responsive. Closer to your total logical CPU count will make your Everything searches faster and system less responsive.

[dfleiss]

I gave that a try and so far, it seems to be working. Thank you!

[toriatama]

Thank you for your support and sorry for the delayed reply:

Is there a program using 100% CPU?
No

There might be a low memory condition? Everything could be paging to and from disk.
No

Note: I have a lot of files on my HHD... files accumulated for 15 years, including many unicode names (asian + russian file names), but Everything was alway performing well, except some random crashes. The index size is 65Mo.

Delete your Everything.db and Restart Everything
Tried. It was working for a while again but then the issue came back

Please try reducing the number of threads Everything uses:
The command "/max_threads=3" is working.
I've tried several values, 1, 2, 3, 4, 5 (I have 8 logical CPU) but the issues is always here.

Are the results constantly changing? -How often and how many? Usually one or two a second is OK.
Results are not constantly changing

There might be a program making many changes to your file system?
I cannot say what program would do that.
What I've done in case:
I added Everything as an exclusion to my antivirus, antimalware (Eset Internet Security, MalwareBytes Premium, SpyShelter Firewall)
But everything goes on crashing.

For my observations, what I can tell:
I noticed that now, Everything does not display correctly the icons of the files names in the results. All icons are white/generic. When Everything cannot show properly icons, I know that it's going to crash... and it crashes after a few searches, very quickly, 2-10 seconds later. Sometimes, after deleting/rebuilding the index, rebooting, etc. Everything works again for a while and very quickly the issue comes back.

My system: Win10 Pro version 1909
8 Go RAM, Processeur Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz, 4001 MHz

What I did not really try yet:
- reverting / downgrading to an older version of Everything.
- deleting and reinstalling totally Everything but I guess it will not change anything
- disabling Everything service and using the program only with admin rights

How I'll be able to fix it!!
Thank you again!

[void]

I noticed that now, Everything does not display correctly the icons of the files names in the results.

This can be caused by a shell extension that doesn't handle really long path names.

Please try the latest version of Everything and enable shell max path:

• In Everything, type in the following search and press ENTER:
  /shell_max_path=1
• If successful, you should see shell_max_path=1 in the status bar for a few seconds.

[toriatama]

First, I just had downgraded to version 1.4.1.877 64bits, and used it a couple of days without bug.

I've now installed the latest 1.4.1.965 (for x64) following your advice, and typed "/shell_max_path=1" successfully, I can see it in the status bar for a few seconds.

I will go on using 1.4.1.965 and will report if the issue occurs again.

Thank you for your kind support.