Now, when rebooting without exiting the program, the client takes a long time to check the databases.
It’s unclear why and takes a lot of time. It is advisable to eliminate this process
1 Like
Definitely not advisable.
Because the application wasn’t closed correctly, the database was left in a condition where data has not yet been written back to the files, and may have errors as well. On start we need to recombine the files, and check for errors. If we don’t, you won’t be able to load the database at all. Instead you will need to delete it, and start with a blank database, adding your accounts and reconfiguring your preferences.
1 Like
viernes 23 febrero 2024 :: 1037hrs (UTC +0100)
What you say is not completely clear to me; anyway if you do not shut down / exit eMC separately before system reboot or shutdown eMC will, as a precaution run a database check and attempt, usually with success, to identify & repair any corruption on restart.
In any event it is not a good idea to rely upon the OS to correctly close any running Apps during the reboot & shutdown process.
skybat
¡Buena suerte!
¡Los mejores desde Valencia y mantente a salvo!
Hablo español, luego portugués, inglés, francés y alemán
con conocimiento de varios otros idiomas.
That’s right. But I forget to log out before rebooting. I think I’m not alone.
It is not clear to me why the client cannot exit correctly if the system tells it to reboot. All programs understand, but the client does not?
2 Likes
I too, would really like eM Client to respond properly to WM_QUERYENDSESSION and WM_ENDSESSION messages as issued by Windows at shutdown. There is a protocol on how to respond to these two messages and would prevent this problem in most situations.
1 Like
So I’m not alone in my delusions 
ALL programs respond. We need to improve