The issue has to do specifically with the built-in administrator account on Windows. This is an account that is hidden by default and requires a special command to enable. Most people are not aware of it's existence. The account is not intended for normal use and it is a little bit like the "root" account on Linux.

Anyhow, here is the behaviour that I observe when I run ANY program under the built-in administrator account. If a program's execution level (ANY program) is set to require administrative privileges (e.g. Right-click on the .exe | Properties | Compatibility | Check 'Run As Admin'), the program will not run. To me, this seems to be a Windows bug. Either way, it seems that if the program is set to request elevation AND is run under the built-in administrator account it will not run. We embed a manifest in the Install Manager that sets the execution level to administrator so that's the explanation for why it won't run. And it needs to be run as admin or else it won't work properly, so we don't want to leave it up to the user to configure. There are ways we can get around that, however for now I think it's best if you just run it from a normal account, and we will add an informative message in the installer explaining this in case a user happens to be running under this built-in administrator account. If this does not seem to be the issue you experience, please PM me and we can do some more digging.

Andrew
PG Music Inc.