Greenshot

For unattended Greenshot deployment, quote Windows paths and use the Inno Setup switches exposed by the official installer. A practical machine-install pattern is Greenshot-INSTALLER-x.x.x.x-RELEASE.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART /SP- /LOG="C:\Windows\Logs\Software\Greenshot-Install.log".

For enterprise configuration, seed greenshot-defaults.ini or greenshot-fixed.ini in the install folder, for example C:\Program Files\Greenshot. Defaults give users starting values, while fixed settings are useful when you need to enforce items such as output paths or plugin behavior.

Close Greenshot before managed upgrades. Both the standard and User-x64 Greenshot packages can return 0x87D00705 if the tray application is open during update, so configure Greenshot.exe as a conflicting process in Intune, ConfigMgr, or PSADT instead of relying on installer retries while the app is still running.

Official source: Greenshot downloads.

For managed Greenshot updates, close Greenshot before setup starts. Standard and per-user Greenshot packages can report 0x87D00705 when the app is open during update, so add a Greenshot-specific pre-close or user-deferral step before retrying detection. Official source: Greenshot Windows/download documentation.