SAPIEN Technologies

In the current version this looks like this. You do have to make sure your script file is saved
as Unicode (UTF-16-LE) before packaging.
I am not sure if the 2016 had an encoding selector on the status bar already or not, sorry.

What actual packager engine are you using? And what version of what product do you use?

A script packaged as a console application (assuming that is what you did) does not set any font by itself.
It uses the font that is configured on a system for that particular console.

As for your first question, you cannot uninstall a product that is still being installed, no matter how you frame it. You cannot actually run Windows Installer if it is already running for something else. Best you could do, is to schedule it. Start menu items are added via the "Shortcuts" ...

Sorry to hear you are having trouble. All our subscriptions are one year, not two years.
Please contact sales@sapien.com directly if you are still experiencing problems.

All SAPIEN Hosts use a variable $ExitCode to return a value through the host.

$form1.Activate();

in the form load event handler should do it.

For reference, this are the standard MSI actions:
https://learn.microsoft.com/en-us/windo ... -reference

Your custom actions should not have a name already used.

You have a double ]] in "[ProgramFiles]]\[Product]" that's what causes the path to be incorrect. I found the source of your troubles. You use the name of 'RegisterProduct' for the custom action name. The internal actions (according to the MSI log) have one with a name 'RegisterProduct' and...

It's a little strange. Not sure what would be causing this. Let's do this: Create a dummy script "Hello World". Make an installer for it. Add a custom action that runs your trimmed down forms app. Add that and the config to the files installed. Try the MSI on your machine with logging. Ass...