How to install Terminal on Windows Server 2022

Windows Server 2022 doesn't include the Terminal command console, but you can use these instructions to install it.

Windows Server install Terminal
  • Install Windows Terminal on Windows Server 2022 without the Microsoft Store or winget.
  • Download and install the required VCLibs runtime before adding the Terminal package.
  • Use the latest .msixbundle release from GitHub instead of an outdated download link.
  • The same process also works to manually update Windows Terminal on Windows Server.

On Windows Server 2022, you can install the Windows Terminal, but because the operating system doesn’t include the Microsoft Store app or the Windows Package Manager (winget), you will need a workaround.

The Windows Terminal is the console application that Microsoft has built as the new command experience for running Command Prompt, PowerShell, and Linux commands. The command-line console was primarily designed for Windows 11 and 10, but you can also install it on Windows Server 2022. The application supports tabs and a range of customization settings, including the ability to create custom profiles for different applications.

This guide will teach you how to install the Windows Terminal console on Windows Server 2022 and older versions. Windows Server 2025 includes the terminal by default, but if you can’t find it, you can also use these steps to add it to your server.

Install Windows Terminal on Windows Server

To install the Windows Terminal console on Windows Server, use these steps:

  1. Open Start on Windows Server 2022.

  2. Search for PowerShell, right-click the top result, and select Run as administrator.

  3. Type the following command to download the runtime libraries and press Enter:

    Invoke-WebRequest -Uri https://aka.ms/Microsoft.VCLibs.x64.14.00.Desktop.appx -outfile Microsoft.VCLibs.x86.14.00.Desktop.appx

    PowerShell download VClibs

  4. Type the following command to install the “.appx” package and press Enter:

    Add-AppxPackage Microsoft.VCLibs.x86.14.00.Desktop.appx
  5. Type the following command to download the latest version of the Windows Terminal and press Enter:

    Invoke-WebRequest -Uri https://github.com/microsoft/terminal/releases/download/v1.16.10261.0/Microsoft.WindowsTerminal_Win10_1.16.10261.0_8wekyb3d8bbwe.msixbundle -outfile Microsoft.WindowsTerminal_Win10_1.16.10261.0_8wekyb3d8bbwe.msixbundle

    PowerShell download Terminal

    Quick note: You must change the download link to the latest Windows Terminal version. You can find this information on the GitHub page. Under the “Assets” section, right-click the latest “.msixbundle” link and copy the path.
  6. Type the following command to install the Windows Terminal application and press Enter:

    Add-AppxPackage Microsoft.WindowsTerminal_Win10_1.16.10261.0_8wekyb3d8bbwe.msixbundle

Once you complete the steps, the terminal will install on Windows Server. 

You can also use the same instructions to upgrade to a new version of the command console. However, you will need to use the legacy PowerShell console to complete the process because you cannot upgrade the terminal while the application is running.

Server Decode’s Take

I always install Windows Terminal on my Windows Server systems because it’s simply a better command-line experience than juggling separate Command Prompt and PowerShell shells. The only downside is that Microsoft never made the process as straightforward on Server 2022 as it is on Windows 11, where you can install or update it in just a few clicks. On Windows Server, you’re still relying on manual downloads and PowerShell commands, which feel outdated in 2026.

That said, I don’t see this as a deal-breaker. Once Windows Terminal is installed, it becomes one of those tools you use every day without thinking. If you regularly manage servers, I think it’s worth taking a few extra minutes to set it up. Just remember to download the latest release instead of relying on older package links, since Microsoft updates the app frequently.

Do you use Windows Terminal on your Windows Server systems, or do you still prefer the classic PowerShell or Command Prompt? Let me know in the comments.