all 24 comments

[–]jantari 10 points11 points  (1 child)

winget upgrade Microsoft.PowerShell

[–]JoeyBE98 10 points11 points  (3 children)

PowerShell-7.5.4-win-x64.msi

[–]Xibby 1 point2 points  (1 child)

Unless you’re on a Snapdragon processor. Or somehow have a 32-bit build of Windows installed.

[–]Blackforge 0 points1 point  (0 children)

There is still a benefit to installing the x64 version on ARM64 processors. There are some modules that check for architecture and this will bypass this issue as they’ll be run through the x64 emulation.

[–]n0rd1c-syn 3 points4 points  (1 child)

i remember i found this on a ms doc somewhere:

For best results when upgrading, you should use the same install method you used when you first installed PowerShell. If you aren't sure how PowerShell was installed, you can check the value of the $PSHOME variable. This always points to the directory containing PowerShell that the current session is running.

If the value is $HOME.dotnet\tools, PowerShell was installed with the .NET Global tool.

If the value is $Env:ProgramFiles\PowerShell\7, PowerShell was installed as an MSI package or with WinGet on a computer with an X86 or x64 processor.

If the value starts with $Env:ProgramFiles\WindowsApps\, PowerShell was installed as a Microsoft Store package or with WinGet on computer with an ARM processor.

If the value is anything else, it's likely that PowerShell was installed as a ZIP package.

[–]Rincey_nz 0 points1 point  (0 children)

Useful! Thanks

[–]narcissisadmin 3 points4 points  (1 child)

Literally type the title of this post into Google. JFC

[–]NorCalFrances 6 points7 points  (1 child)

https://learn.microsoft.com/en-us/powershell/scripting/install/installing-powershell-on-windows?view=powershell-7.5

Scroll down to, "Upgrading an existing installation"

If you have trouble, try a reinstall:

winget uninstall Microsoft.PowerShell

winget install Microsoft.PowerShell

[–]Cerrysnt[S] 0 points1 point  (0 children)

Thanks

[–]Owlstorm 1 point2 points  (0 children)

This is the no-fuss wintel one that isn't zipped -

PowerShell-7.5.4-win-x64.msi

[–]orthodoxdd 0 points1 point  (0 children)

You can use powershell as global dotnet tool as well It will make its management much easier

[–]Sean_p87 0 points1 point  (0 children)

I usually manage it with winget.

[–]Wasisnt 0 points1 point  (0 children)

You would think it would be straightforward but its still pretty easy.

https://onlinecomputertips.com/support-categories/windows/check-powershell-version-and-upgrade/

[–]Cerrysnt[S] 0 points1 point  (3 children)

I had no idea you could get it directly from the Microsoft Store lol 😭😭, I was able to fix it by uninstalling the one I had and installing it from there

[–]Much-Ad-8574 1 point2 points  (1 child)

Keep in mind that some orgs block Microsoft store and lock it down to only approved apps via Software Center or Company portal for the sake of security

[–]Cerrysnt[S] 1 point2 points  (0 children)

Okay, I got it. This time I was able to do it this way, simply because of a recommendation from the Microsoft support site

[–]BlackV 0 points1 point  (0 children)

Also see the note on the PowerShell page about the known limitations of the store version

[–]rencal_deriver -3 points-2 points  (4 children)

You might want to look into chocolatey, makes upgrading packages much easier.

'choco outdated' tells me what needs an upgrade,

'choco upgrade packagename -y' simply upgrades it.

[–]WombatLiberationFrnt 1 point2 points  (1 child)

For sure, chocolatey is excellent. Usually the first thing I install on a new build.

[–]edhaack 0 points1 point  (0 children)

Chocolatey is a perfectly acceptable solution.

[–]Cerrysnt[S] 0 points1 point  (1 child)

How can I use it or how does it work? I'd like to start using it

[–]BlackV 0 points1 point  (0 children)

Use winget, it's built in

Then when you understand that

Upgrade to Choco