Currently, when deploying Companion App on Windows OS using the MSI, it will not start automatically.

If the MSI is distributed across the organization by the system administrator, if the user is not aware and doesn't reboot the machine afterward, they will still get prompted to install the Companion app upon trying to edit the attachment.

This will result in a new installation of the Companion app on top of the one that is already installed.

The solution for this is to make the Application start automatically after it is installed.

Current scenario:

After user runs the App for the first time, the registry key will be added in the following path

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run

The Workaround

One of our customers came up with a solution to add the registry key automatically in the HKLM during the deployment to ensure that the app is started automatically without having the user to start it manually.