Cannot upgrade to 5.8.186

[hmiller10]

Here is my install information minus SPS2021.

Operating System: Windows 10 Pro 2009
OS build: 19042.804
32 or 64 bit OS: 64 bit
Screen Resolutions: DISPLAY1: 3840 x 2160 with scale factor 250%
PowerShell Core: 7.1.1.0
PowerShell Core (x86): No PowerShell Core (x86) version detected
.NET Core Framework: 1.0.13, 1.1.10, 2.1.13, 2.1.24, 2.1.25, 3.1.11, 3.1.12, 3.1.3, 5.0.0, 5.0.2, 5.0.3
.NET Core Framework (x86): 3.1.11, 3.1.12, 5.0.2, 5.0.3
.NET Core Desktop: 3.1.11, 3.1.12, 3.1.3, 5.0.0, 5.0.2, 5.0.3
.NET Core Desktop (x86): 3.1.11, 3.1.12, 5.0.2, 5.0.3
PowerShell cache:
PowerShell 2: 32 Bit, 64 Bit
PowerShell 5: 32 Bit, 64 Bit
PowerShell 7: 64 Bit
SAPIEN Software:
Document Explorer 2020: 3.1.91.0,
PowerShell HelpWriter 2021: 2.3.49.0,
SAPIEN Updates: 1.1.38.0,
ScriptMerge 2021: 1.4.84.0
.NET Framework runtime: 4.8 or later
Visual Studio runtime: 14.0: v14.24.28127.04

I tried to upgrade from version 5.8.185 to 5.8.186 using the normal upgrade GUI. My upgrade gets stuck at the splash screen (See attachment). I let it run for hours and it is still at the splash screen.

I removed the 5.8.185 install from Add/Remove Programs. I get the same result trying to re-install the software.

Please advise what I need to do. I have work I need to get done and my project is now halted.

[Alexander Riedel]

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.

[hmiller10]

It hung again. I cannot see anything in the log that looks as if it would halt the installation. See attached. Next steps?

[Alexander Riedel]

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.

[hmiller10]

I was able to successfully install PowerShell Help Writer 2.3.49 and PowerShell Studio 2021 5.8.183. I downloaded PrimalScript 2021. It hangs on the splash screen as well. I also cannot upgrade from PS Studio 2021 from 5.8.183 to 5.8.186.

The PrimalScript 2021 installation was attempted after a reboot. I checked for any pending reboots and there are none. It appears there may be something with whatever installer was used to package up the latest releases. Next ideas?

[Alexander Riedel]

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!

[Alexander Riedel]

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.

[hmiller10]

Upon doing some digging and using past experience with Anti-Virus/Anti-Malware software I observed my Anti-Malware software Spyhunter 5.10.9.232 had system guard enabled. What started me down this path was a Spyhunter prompt to allow the SPS21... package to execute.

[hmiller10]

NeedDesktopFramework.exe 5.0.0 /Diag yielded the following:
.
..
3.1.11
3.1.12
3.1.3

A review of "Microsoft.WindowsDesktop.App" yielded this result:
3.1.11
3.1.12
5.0.2
5.0.3

Not to overstate the obvious but there is a definite discrepancy. Running NeedDesktopFramwork.exe 5.0.3 yielded:
3.1.11
3.1.12
3.1.3
5.0.0
5.0.2

I opened the Spyhunter software, clicked on the System Guard tab, and disabled the guard. It was not more than 3 minutes, after disabling the Guard, before I saw the SPS21... software icons update. I opened PowerShell Studio 2021 and found that version 5.8.186 finally installed.

While the upgrade was successful I would like to know if there is a .NET issue or if disabling the Guard fixed the issue.

[Alexander Riedel]

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.