SAPIEN Technologies

All of them. Since you don't really know what happened, hard to point at one specific log. If or when Windows Explorer crashed will for sure not be in a PowerShell log.

Since you didn't provide any additional information, I can only give you a few guesses. It is almost impossible for an application that runs non-privileged to affect Windows Explorer and Task manager unless it uses up a huge amount of CPU cycles, which you state it doesn't. PowerShell Studio and an ...

[Topic moved by moderator] Just my 2 cents here. If all you want to do is to is to describe the traffic light states of the check marks, this is what I would do: - Change the red one from a check mark to an x in a red circle, illustrating the no-go state - Change the yellow icon to an exclamation ...

In the meantime, you can go here: https://www.sapien.com/software
and download the PrimalSQL trial installer. Which will download and install PrimalSQL 2025.

Thank you for letting us know. No clue yet as to why that is. I uploaded the file to virustotal.com (again). The file is flagged by three somewhat obscure virus scanners, which is pretty usual. The three show different 'afflictions' which is generally a sign of a false positive. Google's virus ...

Let me ask a few questions about this delay: - Does the application also show this delay when launched un-packaged from PowerShell Studio? - What is the CPU and network activity of the process during these 15 minutes? - I am assuming, but not certain that packaging with 7.4.5 did not show this delay ...

Can you please attach the actual image you used so we can see if there are any differences to what we use for testing? Thanks!

Generally a 1603 error can be a lot of things. Most of which are not under our control. Please see here: https://learn.microsoft.com/en-us/troubleshoot/windows-server/application-management/msi-installation-error-1603 Here are some other observations: - Our installers include all but one required ...

Packaging scripts is, among other purposes, intent to keep prying eyes from the code. While this is not an absolutely unbreakable mechanism (we never claimed that), it keeps the casual observer from messing with code. Including 'unpackaging' in the product would allow just anyone to look anyway ...

On your SAPIEN account page you will find a link for "Code Recovery" on the bottom of the left hand menu.
Please click there and proceed according to the instructions.