-
-
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
Bug: NSIS Installer fails to check if app is running #7413
Comments
Nice find, that's quite some odd behavior. |
This would be possible https://stackoverflow.com/a/56577365 |
Great callout for using I've created this patch via
Honestly, I have no idea if |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue was closed because it has been stalled for 5 days with no activity. |
Which version of electron-builder are you using?
Which version of node are you using?
Which version of electron are you using?
For which target are you building for?
The issue occurs with the following config for NSIS installer:
Before the NSIS Installer/Uninstaller does any modifications, it will check, if the app is currently running. After this change #6472 the installer will only check for running app with the same user (which is currently logged in), not for the whole system.
This line of code checks for running app with "tasklist" and then filtering with "find" in case there is some unexpected output or an error.
Here comes the problem: If the name of the .exe file is too long, it will get cut off by windows with the "tasklist" command. If that is the case, "find" will not find the whole app .exe name anymore, and therefore assumes, that no app is currently running.
Here I attach an picuture of an example why this "find" breaks the logic:
The text was updated successfully, but these errors were encountered: