Improving the bootstrapper script

[HotCakeX]

Removed the old PowerShell link because PowerShell team don't like updating and providing the MSIXBundle package in their releases. Read more about it here: PowerShell/PowerShell#24872

The old link in the bootstrapper script is useless since it points to an old PowerShell version that isn't even supported by the Harden Windows Security module. Winget is the only reliable way to install PowerShell or any apps in general in Windows and if you can't use it for some reason, then you can go ahead and comment in that issue i raised in the PowerShell repository.

Also removed the -MSIXPath parameter from the AppControl function since MSIXBundle parameter is in use now and it can deploy MSIX files too.

Copilot wasn't able to review any files in this pull request.

Files not reviewed (1)

• Harden-Windows-Security.ps1: Language not supported

[SamErde]

Bummer. I've been curious about that MSIX delay as well. Poked through the PowerShell repo workflows to see for any signs of a skipped or failed step, but I didn't see one there. Will be watching for a response!

On a bit of a tangent, do you have any idea why they stopped releasing per-user MSI installers? I asked a while ago, but haven't gotten an answer regarding that, either. From winget-pkgs/issues/176976:

WinGet is selecting the right version here because you specified --scope user. 7.2.6.0 was the last manifest to have MSIX based i.e., user scoped installers for x64/x86 arch. Every version afterwards had MSI installers (machine scope) for x86 / x64 and only included MSIX for arm/arm64 architecture (to my understanding, even those will get replaced soon with MSI installers). This was a decision that came from the PowerShell team to only include MSI installers that are machine scoped for installing PowerShell through WinGet.

@anamnavi may be able to offer more details on that decision

I wonder now if these things may be related.

OT: Copilot can't review PowerShell PRs yet?!

[HotCakeX]

@SamErde I started using PowerShell with version 7.3.x and as long as i remember non-MSIX installers wrote to the C:\Program Files\PowerShell directory which is Admin protected so that could be the reason, they probably did something different before that.

PowerShell still can be installed with Standard user privileges through Winget, i just needed the MSIXBundle file for environments that blocked Winget or don't have it preinstalled such as Windows Server 2022. (Server 2025 has Winget by default)

[SamErde]

Yep, there are so many good things in Windows Server 2025, but it's hard not to get a little excited about simply having WinGet and Windows Terminal in it. 😎

[PromiseYoung]

This is a excellent notice, good job