"Updating database" even when service is running

[zespri]

If this is a faq, please feel free to point me to appropriate resources.

I thought that the point of Everything Windows Service is to maintain the database so that the UI does not have to. Yet, when I open the UI for the first time after reboot I'm waiting several minutes watch "Updating database". Note, that it do not mean straigh after reboot, it could be several hours after reboot so that the Windows Service had plenty of time to catch up.

Did I misunderstand what Windows Service is for? Is this initial several minutes load delay inevitable?

[void]

The Everything Service does not maintain your Everything database.

The database is maintained by the Everything Search Client.
The Everything Service merely allows the Everything Search Client to read the USN Journal on your NTFS volumes.

The long update occurs when there are many changes to your file systems between Everything sessions.
To avoid the long update keep the Everything Search Client running.

Alternatively, delete your Everything.db before starting Everything:
del %LOCALAPPDATA%\Everything\Everything.db
"C:\Program Files\Everything\Everything.exe"

or, run Everything with the -nodb command line option:
"C:\Program Files\Everything\Everything.exe" -nodb

This will force Everything to rebuild the index from scratch which might be faster for you.

[zespri]

Thank you.