You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
After interrogating Greenshot-INSTALLER-1.3.270-UNSTABLE.exe for command-line installation parameters using /?. no combination of /VERYSILENT /CLOSEAPPLICATIONS or /VERYSILENT /FORCECLOSEAPPLICATIONS would result in GreenShot being forcibly closed so that an unattended install would commence. Instead, the user receives an interactive prompt to confirm closure. If deployed as SYSTEM using a deployment tool such as Microsoft SCCM/MECM, Intune, or Ivanti EPM, this would run as SYSTEM and produce a hang owing to the popup, which would be hidden from users due to Windows session isolation.
To Reproduce
Perform a capture and ensure a GreenShot edit window is open, not just the systray icon.
Attempt a command-line install the CMD prompt and parameters /VERYSILENT /CLOSEAPPLICATIONS or /VERYSILENT /FORCECLOSEAPPLICATIONS.
Observe that in both cases the installer will visibly prompt the user to close GreenShot despite the silent parameter in use, rather than silently and forcibly close Greenshot.
Expected behavior
These install parameters should work as advertised or should be removed from the parameter list when /? is used.
Versions (please complete the following information):
Running Greenshot-RELEASE-1.2.10.6
Attempting to deploy upgrade to 1.3.270-UNSTABLE due to CVE-2023-34634.
The text was updated successfully, but these errors were encountered:
middletonk
changed the title
/CLOSEAPPLICATIONS and /FORCECLOSEAPPLICATIONS both produce an interactive prompt on install
/CLOSEAPPLICATIONS and /FORCECLOSEAPPLICATIONS both produce an interactive prompt on a /VERYSILENT install
Sep 7, 2023
Describe the bug
After interrogating Greenshot-INSTALLER-1.3.270-UNSTABLE.exe for command-line installation parameters using /?. no combination of /VERYSILENT /CLOSEAPPLICATIONS or /VERYSILENT /FORCECLOSEAPPLICATIONS would result in GreenShot being forcibly closed so that an unattended install would commence. Instead, the user receives an interactive prompt to confirm closure. If deployed as SYSTEM using a deployment tool such as Microsoft SCCM/MECM, Intune, or Ivanti EPM, this would run as SYSTEM and produce a hang owing to the popup, which would be hidden from users due to Windows session isolation.
To Reproduce
Expected behavior
These install parameters should work as advertised or should be removed from the parameter list when /? is used.
Versions (please complete the following information):
The text was updated successfully, but these errors were encountered: