Download and install PowerShell 7: Updated complete guide for Windows, macOS and Linux

Have you ever wondered how to maximize the potential of PowerShell on your team, without wasting time bouncing from one scattered guide to another? Nowadays, PowerShell 7 has become the benchmark for automating, managing, and getting the most out of systems Windows, Linux and macOSHowever, downloading and installing it may raise some questions due to the variety of methods and alternatives available.

This article is your ultimate guide to downloading, installing, and updating PowerShell 7 on any operating system —and all this without neglecting the details for corporate environments or the tips and tricks for developers or users who get straight to the point. Here you'll find cross-platform advice, step-by-step methods, solutions to the most common errors, and answers to frequently asked questions, all explained in clear and accessible Spanish.. If you stay until the end, you'll learn how to choose the installation method that really suits your needs, avoid headaches when dealing with failures, and understand how to keep your environment updated and secure.

What is PowerShell 7 and why is everyone talking about it?

PowerShell 7 is the direct evolution of Windows PowerShell**. While PowerShell 5.1 was exclusive to Windows And it came pre-installed; the seventh generation makes the leap to cross-platform, allowing its use on macOS and Linux as well. It is developed as an open-source project under the umbrella of Microsoft on GitHubThis ensures constant updates and an active community ready to solve any new challenge.

What makes it stand out from its predecessors?

• Core in .NET Core / .NET 5+: The separation from the .NET Framework translates into greater performance, portability, and flexibility in development and automation..
• Wide compatibility: Works on Windows 10 Windows 11 and popular Linux and macOS distributions (even on ARM64 architectures).
• Scripting and operator news: Introduce the use of ForEach-Object -Parallel for massive parallel operations, modern conditional operators, and improved error handling with Get-Error.
• Parallel installation and coexistence: You can have PowerShell 7 coexisting perfectly with Windows PowerShell 5.1, paving the way for a smooth migration.
• Integration with VS Code and DevOps environments: Its official extension for Visual Studio Code multiplies the efficiency when writing, debugging, and sharing scripts.

For whom it is? While it was traditionally focused on system administrators, PowerShell 7 has become the Swiss Army knife for developers, power users, DevOps, and anyone looking to conveniently automate administrative tasks..

PowerShell 7 versions and lifecycle: which one you need and how to identify it

Before you start installing, it's important that you understand What versions are available and which one should you download?:

• Stable Launches (Stable): These are the recommended versions for almost any user, ready for production, with active support (minimum 18 months) and maximum stability.
• LTS (Long Term Support): Designed for businesses or critical projects, they extend support for up to 3 years and guarantee security patches. For example, PowerShell 7.4.x It is LTS and will be supported until November 2026.
• Preliminaries (Preview/RC): If you're up for it and want to try out the latest features, you can download release candidate versions, although bugs are not out of the question here.

How do I find out which version I have installed? Open any PowerShell console and run:

Get-Host | Select-Object Version

This shows you the exact version number in use. Remember that in Windows You can have several versions installed and choose the one that best suits your environment.

Where to download PowerShell 7 safely and in an up-to-date manner

The official links to download PowerShell 7 are always found at:

• PowerShell GitHub release page: The most reliable site, always updated with the latest versions for WindowsmacOS, Linux, and ARM. Download the package here according to your system and architecture.
• Official Microsoft Documentation: It offers detailed cross-platform instructions and links to each installation method.
• Microsoft Store: If you are in Windows If you want to play it safe (and fast), look for it in the Microsoft Store. It guarantees automatic updates but with some advanced limitations.

Avoid dubious sources: go directly to the links of ecosystem and GitHub It saves you from unpleasant surprises such as corrupted versions, malware injections, or scripts altered without your knowledge.

PowerShell 7 installation methods in Windows

Here are all the valid ways to install PowerShell 7 on Windows (Plus, you can combine them according to your needs):

• MSI Package: The classic "next, next, finish" installer downloaded from the GitHub releases page. It lets you customize the path, add the program to the system PATH, and choose additional features (for example, adding the context menu to Explorer).
• Microsoft Store: Absolute simplicity, ideal for everyday users. You get automatic updates from the Store itself. The only downside? Certain advanced administrative options are unavailable due to restrictions in the Store's system.
• ZIP (portable version): Download, extract, and run pwsh.exe whenever you want, without affecting the rest of your system. Perfect for creating a "portable" version to test new versions or keep your installation independent in a shared environment.
• Winget Package Manager: It tienes Windows 10 or 11, open a console and run winget install --id Microsoft.PowerShell --source winget to have the latest version whenever you want, in automated mode.
• Global .NET Tool: If you regularly use the .NET SDK, you can install PowerShell as a global tool with dotnet tool install --global PowerShellMade for developers and .NET geeks, just add pwsh to your PATH and you're good to go.

How to choose the right method for you?

If you prefer ease and conveniencego to Microsoft Store.
Do you deploy across multiple devices, or do you install on-site at your company? Opt for the MSI package.
Don't you have administrator privileges? Download the ZIP for a portable installation.
Are you a fan of automation and scripting? Usa Winget or the global .NET tool.

Steps for each PowerShell 7 installation in Windows

Installing via MSI

1. Visit GitHub releases and download the appropriate MSI file. Choose x64 (the usual one), x86 (for very few cases) or ARM64 (if you have a Surface Pro X, for example).
2. Double-click the file and follow the wizard (choose to add to PATH and any integrations you need).
3. Finish the process and look for PowerShell 7 in the start menu.

Quick installation with Winget

1. Open PowerShell or Command Prompt as administrator.
2. Install with a single command:
   winget install --id Microsoft.PowerShell --source winget

You can specify the version, for example:
winget install --id Microsoft.PowerShell --version 7.4.6

Install via Microsoft Store

1. Open the Microsoft Store and search for “PowerShell 7”.
2. Click on Install / Get, accept permissions if necessary and wait for the download to finish.
3. PowerShell will be automatically updated from the store.

Portable installation using ZIP

1. Download the ZIP file for your architecture from GitHub releases.
2. Extract the contents to the folder of your choice (make sure it's a path without spaces or limited permissions if you want to be safe).
3. Run directly pwsh.exe from that directory (you can create a shortcut wherever you want or manually add the folder to the PATH to use it from any command window).

Do you want the installation completely isolated from the rest of the users? This method is even recommended in specialized forums and communities when you share a machine with other users and only need PowerShell 7 for yourself.

PowerShell 7 on macOS: installers, Homebrew, and full portability

On Mac, the variety of methods is also present, so let's see which one suits you best:

• Homebrew: It's the ultimate package manager for macOS. Easy, convenient, and updatable with a single command. It installs PowerShell and updates automatically when you request it.
• Signed installer .pkg: If you prefer the traditional visual experience (double-click, next, finish), download the .pkg file from the “Assets” section of the GitHub releases page.
• ZIP / Tarball: Portable option, to install wherever you want or to experiment without affecting the general system configuration.
• Global .NET tool: If you work extensively with the .NET SDK, you can install PowerShell globally in your profile, just like in Windows.

Supported macOS versions

• macOS 15 (Sequoia), 14 (Sonoma), 13 (Ventura) — all on x64/ARM64

Quick steps to install with Homebrew

1. Open Terminal and run:

   brew install --cask powershell

2. For the LTS version:

   brew install --cask powershell-lts

Installation using the .pkg file

1. Download the corresponding .pkg from GitHub releases.
2. Double-click the .pkg file and follow the typical macOS installation wizard.
3. The executable pwsh It is usually accessible in /usr/local/bin/pwsh or similar.

Is the system not finding the pwsh command after installation?

Add the path to your PATH by running this line in your Terminal (adjusting the path if folders have changed):

echo 'export PATH="/usr/local/microsoft/powershell/7:$PATH"' >> ~/.zshrc
source ~/.zshrc

Installing PowerShell 7 on Linux: all distros covered

PowerShell 7 integrates seamlessly with many GNU/Linux distributions. How do I install it correctly?

• APT/DEB For Ubuntu, Debian and derivatives: always use the official Microsoft repository to keep it updated with the rest of the packages.
• YUM/DNF For RHEL, CentOS, Fedora: the same applies; official repositories are added and you receive patches and improvements automatically.
• zipper for Suse and openSUSE.
• Tarball file .tar.gz: Download and manually extract wherever you want (perfect for Alpine Linux or custom architectures).
• Docker containers: Microsoft releases official images ready to be used directly in Docker hub or the Microsoft Container Registry.

Example installation on Ubuntu or Debian

1. Update the system:
   sudo apt-get update
2. Install pre-installation dependencies:
   sudo apt-get install -y wget apt-transport-https software-properties-common
3. Add the GPG key and the official Microsoft repository:
   wget https://packages.microsoft.com/config/ubuntu/22.04/packages-microsoft-prod.deb
sudo dpkg -i packages-microsoft-prod.deb
4. Update again:
   sudo apt-get update
5. Install PowerShell:
   sudo apt-get install -y powershell

Using tar.gz files (portable versions)

1. Download the appropriate tarball from GitHub releases.
2. Extract the contents to ~/powershell or the directory of your choice.
   tar -xvf powershell-7.x.x-linux-x64.tar.gz -C ~/powershell
3. Make the binary executable.
   chmod +x ~/powershell/pwsh
4. Add ~/powershell to your PATH or use the executable directly.

Official Docker Images

To start PowerShell in a Docker container:

docker pull mcr.microsoft.com/powershell:latest
# Para entrar en modo interactivo
docker run -it mcr.microsoft.com/powershell pwsh

ARM Installation and Support

If you have ARM devices (for example, Raspberry Pi, ARM64 servers, etc.), Microsoft publishes compatible binaries and deb/rpm/tarball packages in official releases. Refer to the documentation for specific compatibility details.

Migration from Windows PowerShell 5.1 to PowerShell 7: What you should know?

PowerShell 7 does not replace at once Windows PowerShell 5.1: They can coexist perfectlyThis is crucial in environments where some scripts or modules still depend on "legacy" features.

The main differences and advantages of migrating include:

• Separate installation paths: Windows PowerShell 5.1 resides in %windir%\System32\WindowsPowerShell\v1.0 while PowerShell 7 will %ProgramFiles%\PowerShell\7.
• Different executable names: In version 5.1 and earlier, the executable is powershell.exe; from 6.xy 7.x it is pwsh.exe.
• Differentiated environmental variables: $Env:PSModulePath, $PROFILE and others store scripts and modules in separate paths to avoid conflicts.
• Module compatibility layer: Most of your PowerShell 5.1 modules will work perfectly in PowerShell 7, and you can take advantage of the command Import-Module -UseWindowsPowerShell to load some older modules via implicit remoting.
• Separate profiles: Profile files or boot scripts are also divided by version (see $PROFILE in each environment).
• Extended remote communication: Use both WSMan and SSH to connect systems Windows, macOS or Linux from PowerShell 7.

Upgrading or migrating may be advisable to take advantage of modern capabilities and advanced automation, but maintaining the classic version is also feasible while you migrate your scripts and processes at your own pace.

Different installation scenarios: businesses, developers, home users, and isolated environments

Home users and beginners:

The simplest option is to choose the Microsoft Store (in Windows), Homebrew (on Mac) or apt/yum repositories (on Linux). This ensures automatic updates and maximum simplicity.

Companies and massive deployments:

• MSI Packages: They allow centralized deployment through Active Directory, Group Policy, SCCM, Intune, or automated scripts.
• Full customization: add context menus, define custom paths, exclude PATH according to corporate policy, and allow silent installations (/quiet /norestart).
• Support for updates via Windows Update/Microsoft Update.
• Automate installation on hundreds of computers using batch/powershell scripts.

Isolated environments without direct internet access:

• Manual download and distribution of MSI, PKG, and Tarball files.
• Install synchronously on each device and configure PATH manually.

Developers and advanced users:

• Install portable versions alongside the classic environment to experiment without risking breaking legacy integrations.
• Use scripts to automate installations and regression testing.

PowerShell 7 Update and Maintenance

The update will depend on the method originally used. However, in general:

• From the Microsoft Store or Homebrew: Updates will arrive automatically; just accept the notifications.
• From MSI: Download the latest version and run it; it will automatically overwrite or install alongside the previous one.
• Using package managers like Winget or apt: run winget upgrade --id Microsoft.PowerShell o sudo apt-get upgrade powershell.
• For portable installations (ZIP/Tarball): Download and replace the old folders with the new ones.

Do you want to check how your PowerShell was installed? check out $PSHOMEThe paths will tell you if it was via Store, MSI, ZIP, or portable method.

Typical errors and key solutions during installation and use

Windows

• "The implementation policy prevents the installation": Run Set-ExecutionPolicy RemoteSigned -Scope CurrentUser before installing.
• "Missing .NET requirement": Download and install the latest version of the .NET runtime from the official .NET website.
• "You need to be an administrator": Run the installer with administrator rights (right click > "Run as administrator").
• Corrupt facilities: Download the MSI again from GitHub, verify signatures, and avoid unofficial sources.
• Problems with the PATH: Manually add the PowerShell path to the system if the installer did not do so automatically.

Mac

• "zsh: command not found: pwsh": Add the PowerShell folder to the PATH in your profile (~/.zshrc).
• The .pkg file cannot be mounted: Download again from the official site if there are any errors.
• Unsupported macOS version: PowerShell 7 requires macOS 10.13 or later, update if necessary.
• "Permission denied": Usa sudo to install if there are restricted permissions.

Linux

• "The powershell package could not be located": Add the official repositories according to your distribution (refer to the official documentation).
• Missing dependencies: Install necessary libraries such as libssl o libcurl with your manager.
• "Permission denied when executing pwsh": Check permissions and run chmod +x if required.
• "Package incompatible with the architecture": Download the correct version for your CPU (x64, ARM).

Advanced troubleshooting and security recommendations

• Check the installation logs or system logs for errors if problems arise.
• Always download from sources official such as GitHub, Microsoft, or trusted package managers.
• Keep the routes in the PATH updated after new installations.
• Run with administrator or superuser privileges when necessary.
• To rule out profile errors, run pwsh -NoProfile.
• Back up scripts and profiles before migrating versions.
• In enterprise environments, it automates installations and updates with centralized scripts and policies.

First steps and configuration after installation

To get started with PowerShell 7:

• Launch PowerShell 7 by typing pwsh. In Windows, search for "PowerShell 7" in the start menu.
• Check out the available modules with Get-Module -ListAvailable and the aliases with Get-Alias.
• Add custom functions and scripts to your profile ($PROFILE).
• Connect remote machines using SSH or WSMan from PowerShell 7.
• Use Get-Help [Comando] to access the documentation and examples.

Advanced automation and management with PowerShell 7

From PowerShell you can:

• Automate tasks such as backups, monitoring, and remote configuration.
• Create parallel or batch scripts for repetitive tasks.
• Manage modules and functionalities from PowerShell Gallery using Install-Module.
• Enable secure remoting to manage remote systems via WSMan or SSH.
• Implement scripts in CI/CD pipelines, manage containers, and perform automated audits.

Modules, compatibility, and help for legacy scripts

Module compatibility between versions is constantly increasing.Many modules, such as Azure PowerShell and Active Directory, are already compatible with PowerShell 7. Some legacy modules still depend on the classic environment, but the compatibility layer allows you to run them if needed. $PSVersionTable to check your surroundings and Import-Module -UseWindowsPowerShell to load older modules if necessary.

Routine problem-solving and best practices for management

To fix common errors:

• Make sure you have the correct requirements, internet connection, and appropriate privileges.
• In enterprise environments, review proxy, firewall, and permissions in PowerShell Gallery.
• Check system logs and reinstall if there are persistent errors.
• Sign your scripts to improve security and prevent malicious executions.

Integration with Visual Studio Code and development experience

In VS Code with the PowerShell extension:

• Enjoy IntelliSense, advanced debugging and highlighting.
• Emulate the classic ISE environment if you want a similar experience.
• Automate tests and share snippets with your team.

Frequently Asked Questions about PowerShell 7

How can I find out which version of PowerShell I'm using?

Run Get-Host | Select-Object Version o $PSVersionTable for details.

What differentiates PowerShell 7 from Windows PowerShell?

Cross-platform compatibility, superior performance, advanced error handling, and an open ecosystem make it the modern choice for administration, scripting, and DevOps. Furthermore, its open source nature ensures long-term evolution and security.

Can I uninstall PowerShell if I no longer want to use it?

Yes, if you installed via MSI or Store, you can uninstall it like any other app. Windows PowerShell 5.1 remains on the system as part of the OS, but you can disable it in "Turn features on or off" Windows».

How do I install additional modules after installation?

Usa Install-Module -Name NombreModuloFor example, for Azure:
Install-Module -Name Az -AllowClobber -Scope CurrentUserIn business environments, review internal policies and sign the modules for added security.

Integration with Microsoft Update and automatic version management

PowerShell 7 can be automatically updated through Microsoft Update if it was installed using supported methods (MSI, Winget, Store). Enable automatic updates in Windows to keep it protected and up-to-date.

Essential points to get the most out of PowerShell 7

• PowerShell 7 facilitates administration, automation, and scripting across multiple systems, allowing you to customize the installation to suit your needs (development, enterprise, daily use).
• Its compatibility and modularity allow for risk-free migration, coexisting with Windows PowerShell and taking advantage of new features such as parallel execution and SSH.
• The community and open source code guarantee constant improvements, integration with Visual Studio Code, containers and CI/CD pipelines, as well as robust documentation.
• By following best practices and keeping your environment up to date, you will improve security, efficiency, and reduce future problems in your automation and administration tasks.

Few tools offer the flexibility, support, and community that PowerShell 7 provides. With the right installation method, a streamlined workflow, and regular updates, you can focus on what really matters: automating, managing, and working faster, with fewer errors and greater confidence.