Deploy applications no longer work on Windows 7 machines

[aflynn93@live.com]

Product, version and build: PowerShell Studio 2018, Version 5.5.152
32 or 64 bit version of product: 64 bit
Operating system: Windows 10
32 or 64 bit OS: 64 bit

*** Please add details and screenshots as needed below. ***

We were able to build applications using PowerShell Studio on Windows 10 that would also work on Windows 7 machines until around February 2018. We built an application in September 2017 that worked on Windows 7, but sometime between September and February, there must have been an update that caused future deployments of applications to no longer work on Windows 7 machines. We have deployed on multiple Windows 10 computers and tested on multiple Windows 7 computers with failure every time, even with the simplest of applications.

When the application is opened on Windows 7, nothing comes up except for an error message (below). Please help! Thanks!

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: <Application Name>.exe
Problem Signature 02: 1.0.0.49
Problem Signature 03: 5a7e7e4a
Problem Signature 04: PoshExeHostWinV5
Problem Signature 05: 1.0.0.49
Problem Signature 06: 5a7e7e4a
Problem Signature 07: c9
Problem Signature 08: 87
Problem Signature 09: System.IO.FileNotFoundException
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1033
Additional Information 1: e6e6
Additional Information 2: e6e6c208b90db2aa028f8f653cabbf23
Additional Information 3: 6a3b
Additional Information 4: 6a3b28b85bc1a77ff6f810aaa659e71e

[davidc]

I have a few questions for you before I can help you further:

1. Are you using the "Run As" option?
2. Are you including the generated .config file when deploying the executable?
3. Does the Windows 7 machines have PowerShell V5 installed?
4. Does the original executable still work? (If you still have it)
5. If you can, please upload the psbuild file here:

https://www.sapien.com/support/upload

[davidc]

Are your .NET runtimes up to date? Do you have .NET 4.5.2 installed on those machines?

[aflynn93@live.com]

I uploaded the psbuild file as requested, though I replaced some semi-sensitive info with "***<generic name>***" strings.

1. Are you using the "Run As" option?
[*]We have tried both ways - Open and Run As Administrator.
2. Are you including the generated .config file when deploying the executable?
[*]Tried both ways - with and without .config file.
3. Does the Windows 7 machines have PowerShell V5 installed?
[*]They have V2 installed, but we have deployed using V2 as well with the same results.
4. Does the original executable still work? (If you still have it)
[*]The original executable does still work, and it was deployed using V5.

[aflynn93@live.com]

.Net 4.5.2 is installed on the Windows 7 machines.

[davidc]

If you are using Run As, you have to make sure the application is not ran from a user specific folder, otherwise you will get a "File Not Found" error. This happens because when the executable runs under the run as user and the run as user will not have access to the current user's folder. The same thing can happen if you run the executable from a mapped drive.

As for V5 engines, if the target machine only has V2 installed, then the executable will fail to run. You should select the V2 engine instead.

[aflynn93@live.com]

As noted, we have tried using V2 without the "Run As" option and it still failed. There seems to have been a bug introduced in a PSS update between September and February that causes deployment issues.

[aflynn93@live.com]

Anyone else have any ideas as to what's going on? Is there a way to downgrade PowerShell Studio to a previous version?

[davidc]

We are attempting to recreate the issue on our end and I will post an update as soon as I have more information.

[davidc]

You can download older build from your registered products page:

https://www.sapien.com/account/products

Just click on the Archives link next to the product.