Everything Causes Reboot!

If you are experiencing problems with "Everything", post here for assistance.
Post Reply
driz
Posts: 3
Joined: Thu Apr 10, 2025 6:39 pm

Everything Causes Reboot!

Post by driz »

Second time this has happened, so not a fluke. When I double-click on Everything, my Win 11 desktop PC (MSI Pro B760 - 2023) immediately reboots itself! All open apps / work is lost. I've probably used Everything 20-30 times, but it's only happened twice, which is enough to warrant a forum post.
void
Developer
Posts: 19839
Joined: Fri Oct 16, 2009 11:31 pm

Re: Everything Causes Reboot!

Post by void »

Sounds like a hardware issue.

Please try running a CPU and RAM stress test.



Options in Everything which might help:

Disable multi-threading:
Copy and paste the following into your Everything search box:
/max_threads=1

Press ENTER in your Everything search box.
If successful, max_threads=1 is shown in the status bar for a few seconds.

This will limit Everything to one CPU, which will make your searches slower, but might help with system stability.



Disable icon shell extensions in Everything:

Copy and paste the following into your Everything search box:
/icon_shell_extensions=0

Press ENTER in your Everything search box.
If successful, icon_shell_extensions=0 is shown in the status bar for a few seconds.



Move your Everything.db to another hard drive

Only an option if you have multiple drives:
  • In Everything, from the Tools menu, click Options.
  • Click the Indexes tab on the left.
  • To the right of Database location, Click Browse...
  • Select a drive that is different to your C: drive and click OK.
  • Click OK.


Please check your C: drive for errors:
  • Please backup anything important on your drive before checking it for errors.
  • In Windows Explorer, right click your C: drive and click Properties.
  • Click the Tools tab.
  • Click Check now...
  • Click Start
  • If prompted to schedule a scan on the next restart, click Yes.


Check the Event Viewer (Start -> eventvwr) under Windows Logs -> System for a possible reboot reason.
Post Reply