SAPIEN Technologies

Yes, this is how MSI works. You must increase your version number for a new build. Please understand that while PrimalScript and PowerShell Studio can generate MSI (Microsoft Installer) file, we do not not provide support or training in regards to Windows features. Please consult with Microsoft docu...

Please see: https://docs.microsoft.com/en-us/window ... ne-options

Please note that we are NOT using PowerShell internally to sign scripts, executable files or MSI installers. We are using the prescribed Windows API calls. I am obviously in no position to tell you what to do, but I would just go with a standard time stamp server and void that trouble altogether. Th...

So the MSI is behaving differently on your machine than on other machines, is that what you are saying? You will need to run the MSI the first and second time with logging. That should probably give you a clue as to what is happening. You can also try to do a manual uninstall and then start at a def...

[Topic moved by moderator]

It's great that it works. I am curious why you are launching signtool.exe through powershell rather than launching it directly? Also, is the any specific reason for using this particular time stamp server? It's only a time stamp, so I am curious why it has to be that particular one. Please let us kn...

To quietly uninstall any MSI use
msiexec.exe /x "C:\Example.msi" /qn

It was emailed back to you on 11/06/19, but the email bounced with "Recipient address rejected: Access denied"

The host version is not the same as the Powershell version. SAPIEN Powershell hosts have their own version numbering, so can other hosts.
The proper way to query for the actual PowerShell version is to use $psversiontable.

This is a normal operation. All created MSIs are configured to uninstall/install if a newer or same version is detected. That way software gets reliably updated or repaired. So what you see is normal. There is an uninstall, followed by a re-install and you still see the software in the "Add / Remove...