{"id":54335,"date":"2026-07-26T18:36:29","date_gmt":"2026-07-26T21:36:29","guid":{"rendered":"https:\/\/mastertrend.info\/?p=54335"},"modified":"2026-07-26T18:36:29","modified_gmt":"2026-07-26T21:36:29","slug":"update-powershell-on-windows","status":"publish","type":"post","link":"https:\/\/mastertrend.info\/en\/actualizar-powershell-en-windows\/","title":{"rendered":"Updating PowerShell on Windows: all methods"},"content":{"rendered":"
\n

Updating PowerShell on Windows: A practical guide and official methods<\/h2>\n

Update PowerShell in Windows<\/strong> It is necessary to distinguish between two different products. Windows PowerShell 5.1 is part of the operating system and only receives security patches through Windows Update. PowerShell 7 is installed separately and uses the executable. pwsh.exe<\/code> and can be updated with WinGet, Microsoft Store, an MSI package, a ZIP file, or the .NET global tool.<\/p>\n

\n

Quick response<\/p>\n

And PowerShell 7 is already installed, open Windows<\/a> Terminal and run:<\/p>\n

winget upgrade --id Microsoft.PowerShell --exact --source winget<\/code><\/pre>\n
If it's not already installed, replace upgrade<\/code> by install<\/code>For administration, remoting, or installation for all users, the MSI is more complete than the default MSIX package.<\/p>\n<\/div>\n
\n
Updating does not fix all errors<\/p>\n
If PowerShell is slow to open, crashes, or displays errors, the cause could also be related to the startup profile, an incompatible module, a corporate policy, antivirus software, environment variables, or corrupted files. Updating may provide fixes, but it shouldn't be considered a solution for every problem.<\/p>\n<\/div>\n
Windows PowerShell 5.1 and PowerShell 7 are not the same application<\/h2>\n
\n\n\n\n\n\n\n\n\n\n
Feature<\/th>\nWindows PowerShell 5.1<\/th>\nPowerShell 7<\/th>\n<\/tr>\n<\/thead>\n
Executable<\/strong><\/td>\npowershell.exe<\/code><\/td>\npwsh.exe<\/code><\/td>\n<\/tr>\n
Motor<\/strong><\/td>\n.NET Framework 4.x<\/td>\nModern and cross-platform .NET<\/td>\n<\/tr>\n
Update<\/strong><\/td>\nWindows Update; security maintenance<\/a><\/td>\nWinGet, Store\/MSIX, MSI, ZIP o .NET<\/td>\n<\/tr>\n
Usual route<\/strong><\/td>\nC:\\Windows\\System32\\WindowsPowerShell\\v1.0<\/code><\/td>\nC:\\Program Files\\PowerShell\\7<\/code><\/td>\n<\/tr>\n
State<\/strong><\/td>\nIncluded for compatibility; no new features<\/td>\nAsset development and support<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
Installing PowerShell 7 does not replace or uninstall Windows PowerShell 5.1. Both can coexist because they use different executables, folders, profiles, and module paths. This separation allows you to retain older tools that are still needed. Windows PowerShell while using the features<\/a> modern versions of PowerShell 7.<\/p>\n
Versions in effect as of July 2026<\/h3>\n