Skip to content
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

Installer unable to restart application on Windows 11 #270

Open
jim-counter opened this issue Aug 7, 2024 · 2 comments
Open

Installer unable to restart application on Windows 11 #270

jim-counter opened this issue Aug 7, 2024 · 2 comments
Labels
bug Something isn't working help wanted Extra attention is needed packaging Related to packaging/installer Windows Windows-specific

Comments

@jim-counter
Copy link
Member

When running the installer while Space Acres is already running a problem with closing and restarting the application is reported. If the user ignores the warning and continues with the installation it can leave them in a state where the old version continues running.

Note that the following is written to the application log:

Application 'C:\Program Files\Space Acres\bin\gdbus.exe' (pid 18852) cannot be restarted - Application SID does not match Conductor SID..

Application 'C:\Program Files\Space Acres\bin\space-acres.exe' (pid 18560) cannot be restarted - Application SID does not match Conductor SID..

Application 'C:\Program Files\Space Acres\bin\space-acres-modern.exe' (pid 18672) cannot be restarted - Application SID does not match Conductor SID..

image (5)
image (6)

@nazar-pc nazar-pc added bug Something isn't working help wanted Extra attention is needed Windows Windows-specific packaging Related to packaging/installer labels Aug 7, 2024
@nazar-pc
Copy link
Member

nazar-pc commented Aug 8, 2024

This is likely caused by the fact that software is installed globally under elevated privileges, while application is running under current user instead.

Looks like it is possible to create an installer that will not require elevated privileges at all and will instead install an app just for current user, this can be done with following change (didn't test though):

-InstallScope='perMachine'
+InstallScope='perUser'

Though I don't think there will be a nice upgrade path from here, user will likely have to remove their existing installation and install a new version instead.

If this seems like a reasonable tradeoff I can try to make a corresponding change and test it.

@jim-counter
Copy link
Member Author

This sounds like a worthy change to make. We can make sure there is clear messaging around the release when it is made.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed packaging Related to packaging/installer Windows Windows-specific
Projects
Status: No status
Development

No branches or pull requests

2 participants