"Everything writing database to disk" blocks windows restart / shutdown

[Christian.Ziegelt]

Hi everyone,

does anybody know a way to disable saving the database to disk or to specify what is written ?
It feels as if the content index is written and it takes forever.

Currently my everything index takes 89 GB of RAM - and I allready tried to single down what to content index.

Any idea could help - I can't restart windows now without having a hang.

[horst.epp]

Hi everyone,

does anybody know a way to disable saving the database to disk or to specify what is written ?
It feels as if the content index is written and it takes forever.

Currently my everything index takes 89 GB of RAM - and I allready tried to single down what to content index.

Any idea could help - I can't restart windows now without having a hang.

Everything is not designed to make content indexing with such amount of data.
You should split your indexing.
Make the bulk of it with Windows indexing and about 1GB with Everything.
You can still query the Windows part with Everything's si:

[Christian.Ziegelt]

Thx for the feedback - but this doesn't help me here.

The indexing of content works well for me - the machine has enough RAM so I don't care too much on the usage in everyday live.

The windows indexing is a crap-like-hell thing I would never rely on in any circumstance. I would simply be lost.

The only thing I realy care for is, how to disable the write back or how to limit what is written back to disk when closing down Everything.

I'm fine when the "normal" - Index is written without content stuff.

[tuska]

The indexing of content works well for me - the machine has enough RAM ...

Hi,

Just out of curiosity:
How much RAM do you have that you can use without any problems when Everything uses 89 GB RAM?

I'm interested in this because I want to upgrade the RAM in my next PC and
I'm trying to relate that to my data...

- “Everything” uses about 2 GB of RAM on my system, though content indexing alone recently required 1.6 GB
  There are approximately 550,000 files.
- Installed RAM: 32 GB; available physical memory: 22.5 GB
- My RAM usage (Task Manager: Physical memory used by active processes)
  is currently between 29% and 35% (taking into account various other programs that are also running).

I’d appreciate your response.

_______________________________________________________________________________
'Everything' 1.5.0.1418b (x64) - "Portable on system drive C:"
Windows 11 Pro (x64) Version 25H2 (OS build 26200.8894) - 2026-07-18
Windows Feature Experience Pack 1000.26100.334.0
Processor: Intel(R) Core(TM) i5-12600K 12th Gen, 3.70 GHz, 10 Cores, 16 Logical Processors

[Christian.Ziegelt]

The indexing of content works well for me - the machine has enough RAM ...

Hi,

Just out of curiosity:
How much RAM do you have that you can use without any problems when Everything uses 89 GB RAM?

I'm interested in this because I want to upgrade the RAM in my next PC and
I'm trying to relate that to my data...

- “Everything” uses about 2 GB of RAM on my system, though content indexing alone recently required 1.6 GB
  There are approximately 550,000 files.
- Installed RAM: 32 GB; available physical memory: 22.5 GB
- My RAM usage (Task Manager: Physical memory used by active processes)
  is currently between 29% and 35% (taking into account various other programs that are also running).

I’d appreciate your response.

_______________________________________________________________________________
'Everything' 1.5.0.1418b (x64) - "Portable on system drive C:"
Windows 11 Pro (x64) Version 25H2 (OS build 26200.8894) - 2026-07-18
Windows Feature Experience Pack 1000.26100.334.0
Processor: Intel(R) Core(TM) i5-12600K 12th Gen, 3.70 GHz, 10 Cores, 16 Logical Processors

Sure,

Its a Threadripper workstation with 256 GB of ram - bought well before the price explosion.

I could give you some more details on the files size etc the best days when wiring at the pc.

I’m using it for software development and photo organization mainly.

[tuska]

2Christian.Ziegelt
Thank you for your prompt reply!

Its a Threadripper workstation with 256 GB of ram - bought well before the price explosion.

I'll probably never need that much storage and a workstation

I could give you some more details on the files size etc the best days when wiring at the pc.

Thanks, but the information you provided about RAM and workstation is more than enough for me.

[void]

Everything is not designed for indexing over 1GB of data.



To disable saving the index to disk on exit and windows shutdown:

• In Everything 1.5, from the Tools menu, click Options.
• Click the Advanced tab on the left.
• To the right of Show settings containing, search for:
  save
• Select: db_save_on_exit
• Set the value to: false
• Click OK.

db_save_on_exit



To specify when Everything saves the index to disk:

• In Everything 1.5, from the Tools menu, click Options.
• Click the Advanced tab on the left.
• To the right of Show settings containing, search for:
  save
• Set db_auto_save_at_hour and db_auto_save_at_minute
• db_auto_save_type to Daily.
• Click OK.

db_auto_save_at_hour
db_auto_save_at_minute
db_auto_save_type

[Herkules97]

Did Void's reply help?

You could make an lnk with -exit-now in it I think, or just write /exit-now in the search bar or force-exit via Task Manager, Process Explorer, Process Lasso or whatever else you might have.

I was focused on saving because surely you'd want to save so you don't lose what you've indexed..But maybe yours is rather static so force-exiting most of the time is fine.

Curious..What does it take when you add new stuff? When I add to my monolthic instance it can go from 25GB to 45-48GB.
89GB base..Is that nearing 200GB?

[Christian.Ziegelt]

Hey void and herkules,

Thanks for your replies.
Haven’t been on the pc again since.

I’ll give both approaches a try next week.
Most likely, i don’t need to save at all.
Reading doesn’t do harm to the ssds and content is only index from ssd drives.

The content index is also very very helpful for claude sessions.

Regarding “when adding new stuff” - i did not get the question maybe you could give me a bit more detail.

Best

[Herkules97]

When adding new monitors or changing property settings, it will cause a rebuild. Same if using NTFS and there are too many changes since you last ran the instance.

At least that's what I'd expect. If you don't even need to save after every run maybe it barely changes so you never get a rebuild.