Update

docs/SETUP_ANALYZER.md

@@ -36,6 +36,14 @@ Version 0.5.5.77 can also create a persistent AssetManager software package dire
 
 Software-package jobs transfer only the files required for the selected action through MeshCentral, run the generated PowerShell wrapper, and use the normal AssetManager callback/status/retry infrastructure.
 
+## Post-install application start
+
+A package can optionally start an application after a successful install or reinstall. The launch happens only after the package detection rule confirms that the software is installed. Because deployment jobs execute as SYSTEM, AssetManager uses the active interactive Windows session and the logged-on user's session token to create the configured application there.
+
+If no interactive user session is active and **Start only when an interactive user is logged on** is enabled, the application start is skipped without failing the installation job. Application launch is also skipped when the installer reports that a reboot is required.
+
+For known packages, Setup Analyzer can prefill the application path. Greenshot uses `C:\Program Files\Greenshot\Greenshot.exe`.
+
 ## Installer process handling
 
 Generated installation scripts no longer use `Start-Process -Wait` for the installer. They start the installer process, wait only for that specific PID with a configurable timeout, and then evaluate its exit code. This prevents a browser or another long-running child process launched by the installer from keeping the PowerShell script open indefinitely.

docs/version-history/README.md

@@ -1,3 +1,5 @@
+- [0.5.5.83](UPDATE-0.5.5.83.md) - fix Windows PowerShell compatibility for post-install application start.
+- [0.5.5.82](UPDATE-0.5.5.82.md) - add optional post-install application launch in the active interactive user session.
 - [0.5.5.81](UPDATE-0.5.5.81.md) - fix generated PowerShell process-control syntax for software jobs.
 - [0.5.5.80](UPDATE-0.5.5.80.md) - add configurable process control before install/uninstall and improve Inno application closing.
 - [0.5.5.79](UPDATE-0.5.5.79.md) - fix Greenshot SYSTEM deployment and add software-package deletion.
@@ -17,7 +19,7 @@
 
 Release notes are stored outside the project root to keep the repository overview compact.
 
-The current release is **0.5.5.81**.
+The current release is **0.5.5.83**.
 
 Older notes are concise English summaries migrated from the original release documents. Git history remains authoritative for exact implementation details.
 

docs/version-history/UPDATE-0.5.5.82.md

@@ -0,0 +1,16 @@
+# Update 0.5.5.82
+
+## Added
+
+- Optional application start after successful install and reinstall software-package jobs.
+- Per-package executable path and optional application arguments.
+- Interactive-session launch from SYSTEM jobs using the logged-on user's Windows session token.
+- Optional behavior for machines without an active interactive user session.
+- Optional job failure when a configured post-install application cannot be started.
+- Setup Analyzer suggestions for the post-install application of known packages such as Greenshot.
+
+## Behavior
+
+Application launch occurs only after the installation command has completed and the package detection rule reports the software as installed. If the installer reports that a reboot is required, application launch is skipped.
+
+Software jobs themselves continue to run as SYSTEM. The optional application is created in the active interactive Windows session of the logged-on user.

docs/version-history/UPDATE-0.5.5.83.md

@@ -0,0 +1,13 @@
+# Update 0.5.5.83
+
+## Fixed
+
+- Replaced the incompatible `Split-Path -LiteralPath ... -Parent` call in the generated post-install launcher.
+- Uses `System.IO.Path.GetDirectoryName()` for the application working directory.
+- Uses `System.IO.File.Exists()` for the post-install executable check.
+- The complete optional application-start call is now protected by error handling.
+- A start failure no longer changes a successful installation into a failed software job unless `fail_job_on_error` is explicitly enabled.
+
+## Result
+
+The install/reinstall result is determined by installer exit code and package detection. Optional application start is handled separately and logged.