Database Error and unable to launch app after installing V1.10.0

[Predeactor]

Hello everyone.
As I’ve ran into the issue myself, I also find a better workaround, following @dgiakoum’s advice, so all thank to him.
This method will not erase your data, settings, themes, etc… so you’re safe to read this guide.
I would also like to mention that the developers of Mailspring are working ASAP on the issue, hopefully a hotfix will arrive soon!

Killing Mailspring Instance

First of all, it is important to “kill” Mailspring, because it is probably running in the background, as such, please do this first:

1. Open the task manager by doing Ctrl+Shift+Esc (Or Ctrl+Shift+Del → Task manager)
2. You should see a simular windows, if not, click on Name at the top:
   
3. Click on Mailspring
4. Click on End task at the bottom right.

You can now close the task manager and go on.

Uninstalling 1.10.0

1. Go to %LocalAppData%\Mailspring (Windows+R)
2. Delete the folder app-1.10.0

We’re not exactly done yet…

Suspending updates

Until the developers push an update, we need to block the update, because it will automatically install at every exit, reload, etc…

1. Go to %LocalAppData%\Mailspring (Windows+R)
2. Rename Update.exe to Update.exe.old

Congratulation, you just saved your Mailspring instance!

This is how I fixed the Mailspring’s 1.10.0 issue, I cannot tell if this will work for you, many peoples were helped by my guide, many were not, as such, if you are unable to rollback your Mailspring instance to 1.9, consider reinstalling Mailspring entirely, I’ve made another post about this, you can read this here:

Error with the local database during update

Hello @andreacoyotzi, I apologize that this happened when trying my solution I suggest a complete reinstall of Mailspring at this point… However, here’s a slight word of caution Yes, I’ve tried uninstalling Mailspring by myself to see if the uninstalling solution I gave you will work, of course, it worked for me without loosing your data, but again, this is my solution, it worked for me, on my computer, and I hope it will work for you too, but if not, I’ll be sorry to …

I suggest to rename Update.exe.old back to Update.exe when the developers of Mailspring will fix the issue.

I hope this solution will work for you, if not, I hope my second post will, and, if not, keep fingers crossed and hopefully, a hotfix will arrive soon!
Have a good day