Support for all customers who have purchased a PrimalScript product license. This forum does not offer a response time guarantee.

Forum rulesDO NOT POST SUBSCRIPTION NUMBERS, LICENSE KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.

Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.

1. Product, version and build (e.g. Product: PrimalScript 2014, Version & Build: 7.0.46. Version and build information can be found in the product's About box accessed by clicking the blue icon with the 'i' in the upper right hand corner of the ribbon.)
2. Specify if you are running a 32 or 64 bit version
3. Specify your operating system and if it is 32 or 64 bit.
4. Attach a screenshot if your issue can be seen on the screen
5. Attach a zip file if you have multiple files (crash reports, log entries, etc.) related to your issue.

If not, please take a moment to edit your original post or reply to this one.

What you see is the output from the PowerShell engine, not something that PrimalScript generates.
Unfortunately we cannot change what any given PowerShell engine outputs as error. Only Microsoft can do that.

Notice the difference? You run this in V2 mode on a machine with PowerShell V4 and you get the original message.
You run it on a machine with a TRUE V2 installation you get a different message.

Microsoft never allows side-by-side installation of powershell versions.
So once you have V3,V4 or V5 installed, anything V2 is just a different mode of the same engine. It is not the same as using a real V2 engine.

Again, we do not generate, alter, modify, shorten or otherwise influence PowerShell error messages. What you see in the output window is what Powershell returns. We know it is inconsistent across versions and platforms. Please feel free to tell Microsoft about it.

Again, PrimalScript does not fail to capture anything. You seem to imply that we intentionally withhold error information. We do not.
PrimalScript does not have some magical V2 mode that withholds errors. It just runs the installed Powershell engine in V2 mode. Same as if you start the console in V2 mode.

Run this on that machine where PrimalScript is installed in a V2 console.
If you compare the output from a V2 only machine to a V4 machine you will get different results, of course.