-
-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not possible to update to 2.10.17 under WIN10 #8149
Comments
I'm in the same boat. Can't upgrade to 2.10.17 with "Joplin cannot be closed" message. Windows 10 |
Upstream issue: electron-userland/electron-builder#6865 |
If you're having this issue please could you try the latest version? https://github.com/laurent22/joplin/releases/tag/v2.10.18 |
Tnx. |
Now (2.10.18) installation process does not consider running joplin and gives the appearance that the process has been finished correctly. But the running joplin shows the old version, even after a restart. Stopping joplin and restarting the update with no running joplin helps to finaly update joplin. |
Version 2.12.18 and I still have this issue under Windows 10. The previous installer also had this issue. Nothing helps except restarting the PC (or waiting about 5 minutes after fully killing the process). I'm surprised nobody talks about it anymore? The problem is caused by NSIS installer. There's more info here: electron-userland/electron-builder#6865 Edit: Still the same as of 2.13.8. |
Environment
Joplin version: 2.10.17
Platform: Windows
OS specifics: WIN10
Steps to reproduce
Error message (in German): 'Joplin kann nicht geschlossen werden. Schließ es bitte manuell und klicke auf Wiederholen um fortzufahren'
Restarted PC to prevent a hidden joplin process
taskmanager is clean, no joplin process is running
Joplin will not be autostarted!
Describe what you expected to happen
expected correct detection of running joplin in background.
Logfile
don't have a log file from installation process, only screenshot
The text was updated successfully, but these errors were encountered: