SAPIEN Technologies

Yes, this is generally how MSI installers work. The specified install folder is created if it does not exist.
If you are not familiar with Windows Installers and MSI files, this would be a good starting point:
https://docs.microsoft.com/en-us/window ... ler-portal

Depends on where you install it, there may be an easier way. Usually you would install a default.xml with your app. Once launched, it looks if a config.xml exists. If not, it will create it by copying default.xml to config.xml. If it does, it just loads it. Your installer only overwrites the default...

The output is normal. The tool stops when it finds the indicated version. That was the only change in the installer that could have caused a new behavior.
Since it produced the expected output it is not the cause of this.
I am glad to hear you are all set.

Please run the exe in the attached zip file from a command prompt as follows:

NeedDesktopFramework.exe 5.0.0 /DIAG

And see if that hangs. If it produces output, please send it.

Please go here:
C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App
and tell us exactly what folders and files you have in that directory.
Thanks!

Its failing when preparing for the prerequisites dialog.
Can you successfully install other software in this machine?
Can you give the PrimalScript trial a try? Just to see if it is a general MSI issue or related to the specific installer.

Reboot your computer to get rid of any hanging MSI processes.
Start the setup from a command line prompt with these parameters:
"<PowerShellStudio Installer>.exe" /L*V "installer.log"
If it hangs again examine the logs for any clues as to where it might hang.

Yes, thank you. We are aware. Microsoft for some reason does not allow installation of a previous runtime, even though it leaves it in place if a later version is installed. It also to just fail silently and do nothing when a newer version is detected. We have devised our own check which will do its...

It's a good practice to always check if the path is correct. if (!(Test-Path $PathToFile)) { Write-Warning "$PathToFile not found" } else { $result = & $PathToFile -Variable1 $var1 -Variable2 $var2 } If you are running a script from an admin console, elevated, some personal folders may not exist or ...

It seems to download the correct version. Maybe a fluke? Can you please try again?