SAPIEN Technologies

We have been able to replicate it, but have not identified the cause yet. We are investigating.

In September 2018 we added some macro expansion when packaging. It scrolled off the changelog by now. Add: Packager expands macros in code from packaging settings, current status: __PRODUCTVERSION__ __FILEVERSION__ __PRODUCTDESCRIPTION__ __PRODUCTNAME__ __COMPANY__ __COPYRIGHT__ __FILE__ __DATE__ __...

Detecting a virtual machine is not an easy task. It happens that there are false positives. Our apologies if you encountered one of those.
Simply go your SAPIEN account page and get a VM Trial key.
Enter that as activation key along with your SAPIEN username and password and press "Start / Trial"

A folder and files from which you wish to execute code must be readable. If the OS cannot read a file, it cannot execute it. There really is no way around that. You didn't provide a lot of detail here, so there is some guesswork involved here. Renaming a .ps1 file to .xyz it does not make it any les...

I apologize, maybe my original answer was not verbose enough. When you package (it is not a compiler) with a SAPIEN Script Host, there is no script FILE. It is executed from memory. That's the point of it. Because there is no FILE, mechanisms like Get-PSCallStack don't work, because they assume that...

Well, as there is no actual script really that is a little tough. I am not certain at this time if PowerShell can provide a location within a script block.

You can also package using RunAs. That does not imply admin.

Create a starter app that prompts and then run the main process as required. Or create the shortcut on install.
Without knowing more about your getup it's a bit hard to tell.

Please try this: https://www.sevenforums.com/tutorials/1 ... -user.html

Please send the text you wanted to post to websupport@sapien.com
The SPAM plugin is probably overeager and needs to be adjusted.
We apologize for the inconvenience.