Support Forums

The problem is not with the ampersand characters in your code. You selected a PowerShell engine to execute VBscript code. Obviously the PowerShell engine would not know what to do with VBScript code. It interprets the code as PowerShell and thus complains about these characters. For what you seem to...

Generally, if you have that much output, it would be best to write the output to a file and load that afterwards. It will also speed up your script I would assume. It will also make it easier to view and verify information.
I will look into what we can do to make this easier.

The component is typically installed here: C:\Program Files\Common Files\SAPIEN Common The PrimalScript installer registers the component correctly (usually) but manually running regasm version can screw things up. I am assuming your Windows install is 64 bit, but I cannot be sure. The error code is...

Like I said, usually a failure to create an object produces an error code. That code is really important to determine what happened.

That component has always been part of PrimalScript. I haven't looked at it in some time but it should still work. If it fails to create, most likely you didn't register the COM object or your don't have a prerequisite installed for it to register properly. Hard to tell without any actual error code...

Believe it or not, that is a good thing. There is a major advantage to a platform having stability rather than having everyone apply their "good ideas" to it
We are of course following PowerShell Core development. But at the moment that is basically an alpha version.

Make sure you actually have PowerShell 5 on your machine. If you installed V5 after installing PrimalScript you may have to uninstall/re-install it.
If that does not help, you may be missing some components. But try that first.

Glad you were able to fix it. And yes, Windows Installer error message usually point in the wrong direction

PowerShell Core will not ever support any kind of UI library. At least that is what Microsoft states now. It wouldn't make any sense anyway, as PowerShell Core is meant to be run cross platform on things like router and and other UI-less device. I have to point out that no one here at SAPIEN works f...

The wizard comes up when the Windows signing component does not know what you want to do. Most likely you left the old signature in your certificate store. Now you have two signature with the same name.
Delete the old signature from your certificate store.