Installer Issue with 1.3 Unstable

Description

Hello,
thank you for your great work so far and your effort developing such a software for years.

I currently have the following problem. My plan is to automate the installation of the Unstable Version. For this, I am using a user with admin rights. The installation process seems to run relatively quickly and successfully, but I am experiencing some problems afterwards.

This is how I do this:
I call the EXE
"Greenshot-INSTALLER-1.3.274-UNSTABLE.exe" /VERYSILENT /NORESTART

I have also tested the following:
"Greenshot-INSTALLER-1.3.274-UNSTABLE.exe" /SUPPRESSMSGBOXES /ALLUSERS /NOCANCEL /NORESTART /FORCECLOSEAPPLICATIONS /SILENT

(Source: jrsoftware.org/ishelp/index.php?topic=setupcmdline as mentioned at /? )

I noticed that Greenshot is still installed under "Appdata" of the user where I started the install process, even though the "ALLUSERS" switch was used.

Additionally, it does not appear in the list of installed programs because it is likely user-specific.
However, if the installer is installed in the context of "SYSTEM", Greenshot ends up under "C:\Program Files\Greenshot". Despite this, the start menu entry and the entry in the installed programs are missing. At least Greenshot is correctly written to the autostart under "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run".

The problematic aspect is that Greenshot is no longer found by the software management once there is no program entry left. It also makes no difference whether I use the switches.
Perhaps my Workaround will be creating the missing entries under “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Greenshot” myself. It seems that my software distribution can detect it.

perhaps this is something you want to fix in future versions.

Have a nice day and greetings from “Nürnberger Land” 👋🤘.

Greets Christian

Environment

I am using Windows 10 22H2 on my test system and trying to automatically install Greenshot Unstable 1.3.274 silently.

Activity

Details

Assignee

Reporter

Affects versions

Components

Priority

Created June 14, 2023 at 1:55 PM
Updated June 14, 2023 at 1:55 PM

Flag notifications