Updated to the latest version, and now Windows refuses to open the app, with Smart App Control blocking it, saying it can’t verify who it’s from and they’re not familiar with it. This must be fixed ASAP. I already sent feedback to Microsoft, but I’m not sure they’ll be quick about it.
Is there any update on this issue? I installed Mailspring yesterday without issue but get the same message as Maxolian today. The only option available to the end user is to send feedback to Microsoft.
To me it fixed itself with the update after. It seems really weird. Haven’t updated to the latest one yet though after this incident.
Yeah, it’s working this evening. Very odd!
I updated to the newest just last week, today I’m blocked. Running update.exe shows no change. Any Ideas, uninstall and reinstall with the lastest version from the web. This however, after reading the squirrel update, is timestamped with 10. March same as the installer file, also timestamped 10. March. I’m unsure if there are any changes in that install file which have been addressed since.
Windows Smart App Control requires apps to have a strong reputation signal built up from a large number of downloads of a specific binary hash. Because each Mailspring release is a new binary, new versions occasionally hit this before enough users have downloaded them. This is unfortunately a Microsoft-side reputation system we can’t directly control.
The quickest fix if you’re blocked is to temporarily disable Smart App Control (Settings > Privacy & Security > Windows Security > App & Browser Control > Smart App Control > Off), install Mailspring, then re-enable it. Alternatively, downloading the latest version from getmailspring.com a few days after release usually works because the reputation has had time to accumulate. Sorry for the friction — this has improved with recent releases as we’ve accumulated more download history.
Turning smart app control off, requires a full windows re-install to re-enable it. You cannot turn it on and off whenever you want. Anywyas yes the problem does seem to have become less frequent and it did resolve itself after a few days so it’s fine