-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
auto-updater on windows: reboot during update install leaves incomplete installation [nsis] #3798
Comments
[2019-06-18 18:27:03.030] [info] Update installer has already been triggered. Quitting application. I have same question. |
"electron-updater": "^4.0.6", |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@develar, I believe this is still a bug (but the stale bot closed it). Do you consider it an NSIS issue? |
One solution (for certain use cases) might be to configure electron-updater to only trigger the install manually (i.e. not on close). https://www.electron.build/auto-update#appupdater-eventemitter Set |
We're experiencing a proper error condition when using auto-updater: Our application is run by our customers from boot to shutdown (I'd even say "from dawn to dusk" :p). This means that the auto-updater finds an update and marks it for installation on exit - fine.
Now, the user's work day ends, they want to run home. They shut down the app (the update installer starts), and immediately shut down windows.
Now, windows at some point kills the update installer NSIS process, leaving behind an incompletely installed app! 💥
The question is now for me: is this a fixable bug or should we rather "move" the update installation to another point in time? I could think of rearrange stuff so that the update is installed on launch - essentially slowing down the launch due to the pending update...
What is the official stance on this issue? Did anybody else experience (and solve) this?
The text was updated successfully, but these errors were encountered: