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

Description

After uninstalling the stable running V1.9.2 I tried to install V1.10.0 The installation process ended with an error dialog box ‘… better_sqlite3.node is not a valid Win32 application’. The error dialog box appears infinitely again regardless of the action taken – hitting ‘okay’ or closing the window. I also tried cleaning any remaining Mailspring files from the system after a second uninstall try and before a new install approach. The same behavior occurs. The same behavior occurs when the mainspring task is killed via task-manager and then manually started again.

Workaround

For a Workaround, until this is resolved, please see: Database Error and unable to launch app after installing V1.10.0 - #11 by Predeactor

To Reproduce…

Steps to reproduce the behavior:

  1. Uninstall existing Mailspring app via Settings > Apps > Apps & Features
  2. Install V1.10.0 MailspringSetup.exe
  3. Receiving error
  4. Perform ‘any action’ with the dialog box
  5. Receiving error again

Expected Behavior

I expected to (a) have a functioning Mailspring app again, maybe with the need of reconnecting accounts. Or (b) after clean re-install to have a functioning app which needs to be completely set up again.

Screenshots

image
Headline translated: ‘We have detected a problem with your local email database. We will now try to rebuild it.’

Setup

  • OS and Version: Windows 11 Pro (10.0.22000 Build 22000)
  • Mailspring Version: 1.10.0

Additional Context

Each time, after the install attempt ended with an error, the app again can be found as an installed app within the system ‘Apps & Features’ overview.

I found someone who might experience the same issue

Installing V1.9.2 however works fine and as expected.

Yes, this looks identical to what I’m experiencing. Thanks for the higher quality report (and finding the right tag/category, which I failed at).

I suppose it’s good that this bug that is reproducible. Of course, that is also a downside…

2 Likes

I have this same issue with v1.10

1 Like

I have the same issue. Using Windows 10.

I’m having same error.
Process:
Uninstalled version: 1.9.2
Installed: 1.10.0

OS Details:
OS: Windows 10 Pro
Version: 21H2
OS Build: 19044.1526

Same here. I love mailspring but between the constant reconnecting mailboxes and reinstalling updating fails this is hardly a solution, Not ungrateful just annoyed since now every morning i have to uninstall… Reinstall. reconnect 4 mailboxes before actual mail. It takes the “spring” out of mailspring

1 Like

I have the same issue, it’s driving me nuts? Any solution people please ?

I have the same problem :frowning:
I can not download 1.9.2 version. Put this version somewhere please!

Same issue here. On version 1.10.0 (upgraded into it) on Windows 10.
Manually launching Mailspring\app-1.9.2\mailspring.exe works as a workaround.

3 Likes

Hi,
Do You have version 1.9.2 ?

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:

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!
:slight_smile: Have a good day

13 Likes

If you visit their repository page on github you will find all their previous releases here: Releases

Here a shortcut to release page of V 1.9.2 with all installers: V1.9.2

1 Like

Nice. Very straightforward to avoid reinstallation.

1 Like

My app automatically installed the 1.10.0 update this morning. Tried this workaround and it worked fine – reinstallation avoided.

1 Like

This worked for me! Thank you.
If it tells you that folder is used by another process, you need to shut down mailspring from task manager

1 Like

no, both deleting the folder and uninstalling doesn’t work for me. The app is totally fucked up on my Windows 11 now. I don’t see how an update can make this happen.

1 Like

I freported this too, then realized that I actually had TWO errors, and forgot to screenshot the first (which marked better_sql3.node as “not a Win32 application”). This error went away, but the broken DB stood.

And this is where I am now. You know, I am trying to apply for a job - kinda hard without an email client… ^^;
Going to try and install something before 1.10… x.x

The minute I saw this message… I knew I shouldn’t click the “Install” button but it’s just too tempting for me. Being a returning user after a couple of years, I knew from the past that Mailspring’s updates are risky. Half the time, it breaks everything. I even checked the release notes before and I saw the big jump (and I said “Not looking good…” in my head – especially with the Electron stuff) but I tried nonetheless…

image

Of course, everything was broken after the update. Deleting the folder did the trick, THANK YOU.

2 Likes

For those “fixing” the problem by deleting the folder app-1.10.0 - check to see what version you’re actually using. I think deleting that folder actually deletes the update and you’re back to the previous version. Deleting the folder did not help me. I can only use version 1.9.2.

Hi there, my version of Mailspring is apparently 1.9.2 too, as such I think that 1.9.2 is the actual “stable” version of Mailspring
As you can see, this is my version:
image
I personally think that yes, it delete the update, and make you go back to the previous version, but if it does not help you, I’m out of luck here, and you’ll be on your own :confused: All I can suggest is a complete uninstall + reinstall…
This is my solution after all, worked for me, can’t work for everyone, after all, it’s a temporary solution until a new update comes out, hopefully!

Edit: Now thinking about it, it also could be something regarding the cache in %AppData%/Mailspring, but I would disregard this opinion, I would prefer to not touch this folder because it contain settings/config, everything you have set, etc…