Windows Terminal (wt): How It Works, Features, Benefits, Setup, and Troubleshooting

QUICK ANSWER

Windows Terminal is Microsoft’s modern host application for command-line environments such as PowerShell, Command Prompt and Linux shells installed through Windows Subsystem for Linux (WSL). It provides tabs, split panes, profiles, Unicode support, searchable output, customizable shortcuts and GPU-accelerated text rendering. It does not replace or change the commands supported by those shells.

wt is the command-line alias for wt.exe, the Windows Terminal launcher. Running wt opens Terminal, while options such as -p, -d, new-tab and split-pane control which profiles, directories, tabs and panes it opens.

 

What Is Windows Terminal?

Windows Terminal is a graphical terminal application developed by Microsoft. It hosts command-line programs and shells, including:

• Windows PowerShell
• PowerShell 7 (pwsh.exe)
• Command Prompt (cmd.exe)
• WSL distributions such as Ubuntu
• Azure Cloud Shell
• SSH clients and other command-line applications

Windows Terminal is the window and user interface around these programs. PowerShell, Command Prompt and Bash are shells that interpret commands.

Windows Terminal supports multiple profiles, tabs, panes, UTF-8 and Unicode characters, themes, configurable shortcuts and GPU-accelerated text rendering. Microsoft Learn

How Windows Terminal Works

When you open a profile, Windows Terminal starts the profile’s configured command-line program. It captures keyboard input, passes it to the hosted command-line session and renders the resulting text in the Terminal window.

Windows Terminal uses Windows pseudoconsole technology, commonly called ConPTY, to host character-mode applications. ConPTY provides the communication layer between the terminal interface and the command-line application. Windows Console

The basic flow is:

1. Windows Terminal reads the selected profile.
2. It starts the configured shell, such as powershell.exe, pwsh.exe, cmd.exe or wsl.exe.
3. The shell interprets commands and starts other programs.
4. Terminal displays their output, including supported colors, cursor movement and formatting.
5. Each tab or pane maintains its own command-line session.

Closing a tab normally ends the process running in that tab. Unsaved shell output or running tasks may be lost, so check active commands before closing it.

What Does the wt Command Do?

wt is the execution alias for wt.exe. It launches Windows Terminal and accepts arguments that define the initial layout. Microsoft Learn

Running the following command opens Windows Terminal:

wt

Open a specific profile

wt -p "Command Prompt"

Replace Command Prompt with the exact name shown in Terminal’s profile list, such as PowerShell or the name of a WSL distribution.

Open Terminal in a specific directory

wt -d "C:\Projects"

The directory must exist, and the selected shell must be able to use it.

Add a tab to the most recently used Terminal window

wt -w 0 new-tab

The -w 0 option targets the most recently used Terminal window. Without a window target, wt may create a new window depending on Terminal’s windowing configuration.

Open multiple profiles from Command Prompt

wt -p "Command Prompt" ; new-tab -p "Windows PowerShell"

Open multiple profiles from PowerShell

PowerShell also treats semicolons as command separators. Escape the semicolon with a backtick when passing multiple commands to wt:

wt -p "Command Prompt" `; new-tab -p "Windows PowerShell"

Create split panes from PowerShell

wt -p "Command Prompt" `; split-pane -p "Windows PowerShell"

A more complex example can open Command Prompt, PowerShell and WSL in separate panes:

wt -p "Command Prompt" `; split-pane -p "Windows PowerShell" `; split-pane -H wsl.exe

Profile names depend on what is installed. A command fails or falls back to another configuration if it references a missing or incorrectly named profile.

The wt execution alias is not directly available inside WSL distributions. From a WSL shell, Microsoft documents launching it through Command Prompt:

cmd.exe /c "wt.exe"

Requirements and Installation

The current Windows Terminal project requires Windows 10 version 2004, build 19041, or later. Windows 11 is also supported. GitHub

Important: Microsoft ended standard support for Windows 10 on October 14, 2025. Although Terminal can run on supported Windows 10 builds, an unsupported operating system should not be used for security-sensitive work without an applicable Microsoft support option.

Install from Microsoft Store

Microsoft recommends the Store distribution because it receives automatic application updates. Open Microsoft Store, search for Windows Terminal, confirm that Microsoft is the publisher and select Install. GitHub

Install with WinGet

Open PowerShell or Command Prompt and run:

winget install --id Microsoft.WindowsTerminal -e

The -e option requires an exact package identifier match.

To request an update later:

winget upgrade --id Microsoft.WindowsTerminal -e

Installation normally does not require manually building the application. Organization policies may block Microsoft Store, WinGet or MSIX packages; in that case, contact the organization’s administrator.

Other distributions

Microsoft also publishes signed release packages on the official Windows Terminal GitHub repository. Portable and unpackaged distributions are available for specialized scenarios, but administrators must manage updates and dependencies themselves.

Windows Terminal Preview and Canary builds are intended for testing upcoming changes. Canary is the least stable release channel and should not normally be the standard terminal on production or support systems. GitHub

Verify That Windows Terminal Is Installed

Launch it directly

Press Windows+R, enter:

wt

Then press Enter.

Check the installed package with PowerShell

Get-AppxPackage Microsoft.WindowsTerminal

A successful result shows package information. No result normally means the packaged stable edition is not installed for the current user.

Check with WinGet

winget list --id Microsoft.WindowsTerminal -e

This displays the detected package and version when WinGet recognizes the installation.

If wt is not recognized but Terminal is installed, see the troubleshooting section below.

Initial Configuration

Choose the default profile

1. Open Windows Terminal.
2. Select the arrow beside the new-tab button.
3. Select Settings.
4. Open Startup.
5. Select a shell under Default profile.
6. Select Save.

New installations normally start with PowerShell as the default profile. Terminal automatically generates profiles for detected WSL distributions and installed PowerShell versions. Microsoft Learn

Make Windows Terminal the default terminal application

On compatible Windows versions:

1. Open Windows Terminal > Settings > Startup.
2. Set Default terminal application to Windows Terminal.
3. Save the setting.

This causes supported console applications to open through Windows Terminal. The option is available in Windows 11 and in Windows 10 22H2 after the May 23, 2023 update. Microsoft Learn

The default terminal application and default Terminal profile are different settings:

• Default terminal application selects which host displays console programs.
• Default profile selects which shell opens in a new Terminal tab.

Profiles Explained

A profile defines how Terminal starts a particular command-line environment. It can specify:

• Profile name and icon
• Command-line executable
• Starting directory
• Font and font size
• Color scheme
• Background
• Cursor style
• Tab title
• Whether the profile is hidden
• Whether it requests administrator elevation

To add a profile:

1. Open Settings.
2. Select Add a new profile.
3. Duplicate an existing profile or create an empty one.
4. Enter a name and valid command line.
5. Save the configuration.

For example, a profile for PowerShell 7 typically uses:

pwsh.exe

The executable must already be installed. Adding a profile does not install PowerShell, WSL, a Linux distribution or any other shell. Microsoft supports adding command-line executables through either the Settings interface or settings.json. Microsoft Learn

Tabs, Panes and Windows

Tabs

Each tab contains at least one command-line session. Use tabs to separate tasks such as local administration, log monitoring and a remote SSH session.

The default shortcut for a new tab is:

Ctrl+Shift+T

Use Ctrl+Tab to move between tabs.

Panes

Panes divide one tab into multiple command-line sessions. They are useful when two commands must remain visible simultaneously—for example, a server process and its log output.

Shortcuts can vary after customization. Use Ctrl+Shift+P to open the command palette and search for split, move or resize actions.

Tab tear-out

Tabs can be dragged out to create separate windows or moved into other Terminal windows. This is useful when arranging sessions across multiple monitors. Microsoft Learn

Search, Copy and Command Palette

Search output

Press:

Ctrl+Shift+F

Enter a word or phrase to search the current terminal buffer. Search operates on retained output; content that has already left the scrollback buffer cannot be recovered. learn.microsoft.com

Copy and paste

Common defaults include:

Ctrl+Shift+C    Copy
Ctrl+Shift+V    Paste

Ctrl+C is often sent to the running command as an interrupt signal, so it is not always the copy shortcut.

Security warning: Review copied commands before pasting them into a shell, especially an administrator session. Pasted text may contain multiple commands, destructive operations or hidden line breaks. Windows Terminal does not validate whether a command is safe.

Command palette

Press:

Ctrl+Shift+P

The command palette provides searchable access to Terminal actions and configured commands. It is particularly useful after shortcuts have been customized. learn.microsoft.com

Customizing Windows Terminal

Most settings can be changed safely through Settings. Available options include:

• Default profile and startup behavior
• Fonts, colors and cursor appearance
• Background images and opacity
• Tab and window behavior
• Keyboard shortcuts and custom actions
• Scrollback history
• Copy-and-paste behavior
• Bell notifications
• Profile-specific starting directories

Editing settings.json

For advanced settings:

1. Open Settings.
2. Select Open JSON file.
3. Back up the file before making extensive changes.
4. Edit only documented properties.
5. Save the file and review Terminal for configuration warnings.

A minimal profile-defaults section can look like this:

{
    "profiles": {
        "defaults": {
            "font": {
                "face": "Cascadia Mono",
                "size": 11
            }
        },
        "list": []
    }
}

Do not replace an existing settings file with this fragment. Merge required properties into the existing structure because Terminal-generated profiles and other settings may already be present.

Settings applied under profiles.defaults affect all profiles unless a profile overrides them. learn.microsoft.com

Administrator Use and Security

Windows Terminal does not automatically grant administrator privileges. A normal Terminal window runs with the permissions of the signed-in user.

To start an elevated session:

1. Search for Windows Terminal.
2. Right-click it.
3. Select Run as administrator.
4. Approve the User Account Control prompt.

Windows 11 may also offer Terminal (Admin) from the Windows+X menu. learn.microsoft.com

Use elevated sessions only when required. Every tab and process in an elevated Terminal window can potentially perform administrative actions.

Additional security points include:

• Terminal is not a security sandbox.
• A profile launches programs with the user’s current permissions unless elevation is requested.
• SSH security depends on the SSH client, keys, host verification and remote system—not on Terminal’s appearance.
• WSL security and isolation depend on WSL and its distribution configuration.
• Themes, fonts and backgrounds do not change command privileges.
• Do not store passwords, tokens or private keys directly in settings.json or profile command lines.
• Download Terminal only from Microsoft-controlled sources or approved organizational repositories.
• Keep Terminal, Windows, shells, WSL distributions and command-line tools updated.

Enterprise administrators can use Windows Terminal Administrative Templates and Group Policy to control certain functionality. Availability depends on the Terminal version and the organization’s management configuration. learn.microsoft.com

Benefits of Windows Terminal

Consolidated command-line work

PowerShell, Command Prompt, WSL and other tools can run in one application instead of separate console windows.

Better session organization

Tabs, panes, tab titles and colors make it easier to distinguish local, test, production and administrative sessions.

Improved text handling

Unicode and UTF-8 support improves the display of international characters, symbols and modern command-line applications.

Efficient rendering

GPU-accelerated text rendering can provide smoother output for large or rapidly updating terminal displays. Actual performance still depends on the shell, application, graphics driver and computer.

Repeatable workspaces

wt arguments can launch predefined collections of profiles, directories, tabs and panes. This is useful for developers and administrators who repeatedly open the same working environment.

Extensive customization

Profiles allow different shells to use distinct fonts, color schemes, directories and behavior. Custom actions and keyboard shortcuts can reduce repetitive navigation.

Open-source development

Windows Terminal’s source code and issue tracking are publicly available in Microsoft’s official GitHub repository. This improves transparency and provides a documented channel for reporting reproducible problems.

Important Limitations

Windows Terminal is not:

• A replacement for PowerShell, Command Prompt, WSL or Bash
• A programming language or scripting engine
• An SSH server
• A Linux environment by itself
• A privilege or security boundary
• A guarantee that old command-line applications will support modern formatting
• Available for Windows versions earlier than its stated minimum requirement

Commands are interpreted by the active shell. A PowerShell command may not work in Command Prompt, while Linux commands require WSL or another compatible environment.

Terminal also cannot restore output that has left its scrollback buffer, recover commands interrupted by closing a tab or make an unavailable executable work merely by adding a profile for it.

Troubleshooting Windows Terminal

wt is not recognized

1. Confirm that Windows Terminal is installed.
2. Close and reopen the calling shell.
3. Open Settings > Apps > Advanced app settings > App execution aliases.
4. Verify that the Windows Terminal wt.exe alias is enabled.
5. Repair or reinstall Terminal from an official Microsoft source if necessary.

Inside WSL, use:

cmd.exe /c "wt.exe"

The normal Windows execution alias is not directly available as a Linux command. Microsoft Learn

A profile is missing

• Verify that the shell or WSL distribution is installed.
• Restart Terminal so dynamic profiles can be rediscovered.
• Open Settings and check whether the profile is hidden.
• Add a manual profile only after confirming the correct executable path.

A profile opens and immediately closes

The configured executable may be missing, the command line may be invalid or the process may be exiting normally.

Test the executable from another working profile:

Get-Command pwsh.exe
Get-Command cmd.exe
Get-Command wsl.exe

Use only the command relevant to the missing profile.

Terminal opens in the wrong directory

Check the profile’s Starting directory setting. A command passed with wt -d can override the configured directory for that launch.

Opening a new pane in the current shell directory may require shell integration because Terminal does not always know when the shell changes directories. Microsoft documents shell-specific configuration for reporting the current working directory. Windows

Settings changes cause errors

• Use the Settings interface to correct invalid values.
• Check settings.json for missing commas, unmatched braces or unsupported properties.
• Restore the backup made before editing.
• Avoid copying entire settings files from old articles because property names and schemas can change.

Keyboard shortcuts do not match documentation

Shortcuts may have been customized or changed by configuration. Open the command palette with Ctrl+Shift+P, or inspect Settings > Actions.

Text, symbols or icons display incorrectly

• Select a font containing the required characters.
• Confirm that the command-line application outputs Unicode or UTF-8 correctly.
• Install a compatible font if a customized prompt requires special glyphs.
• Remember that Terminal cannot display characters absent from the selected font.

Administrator commands still fail

Confirm that the current window was explicitly started with elevation and that the account has the required rights. Organizational policy, file permissions and service permissions may still block an operation even in an elevated window.

FAQ

Frequently Asked Questions

Is Windows Terminal the same as PowerShell?

No. Windows Terminal is a host interface. PowerShell is a shell and scripting environment that can run inside it.

What is the difference between wt and cmd?

wt launches or controls Windows Terminal. cmd starts Command Prompt, which interprets traditional CMD commands and batch files. Command Prompt can run inside a Windows Terminal profile.

Does Windows Terminal replace Command Prompt?

No. It can become the default host for console applications, but Command Prompt remains a separate command interpreter and can run inside Terminal.

Is Windows Terminal free?

Yes. Microsoft distributes Windows Terminal without a separate purchase, and its source code is available through Microsoft’s public GitHub repository.

Can Windows Terminal run Linux commands?

Only when a Linux environment such as WSL is installed. Windows Terminal displays and hosts the WSL shell; it does not provide Linux by itself.

Can Windows Terminal connect to remote servers?

Yes, by running an appropriate client such as Windows OpenSSH ssh.exe, PowerShell remoting tools or a third-party command-line client. Terminal itself is the host interface, not the network protocol or server.

Does Windows Terminal require administrator rights?

Normal use does not. Administrator rights may be needed to install software, change protected system settings or run administrative commands. Elevate Terminal only for those tasks.

Where are Windows Terminal settings stored?

The location depends on the distribution type. The safest method is to open Terminal Settings and select Open JSON file. Portable mode stores settings in a settings directory beside the application after a .portable marker is enabled. Microsoft Learn

Can I use Windows Terminal on Windows Server?

Compatibility depends on the Windows Server version, build, application packaging support and organizational policy. Verify the environment against Microsoft’s current Windows Terminal requirements before deployment.

FINAL RECOMMENDATION / CONCLUSION

Use Windows Terminal as the primary command-line host on supported Windows systems when you work with PowerShell, Command Prompt, WSL or several command-line tools. Start with the stable Microsoft Store or WinGet release, choose an appropriate default profile and learn tabs, panes, search and the command palette before making extensive JSON customizations.

For secure administration, keep normal and elevated work separate, verify commands before pasting them, protect credentials and private keys, and remember that Windows Terminal does not add security boundaries or capabilities to the shell it hosts. IT teams should test upgrades and centrally manage relevant settings where consistency or access control is required.

 

#WindowsTerminal #WT #WTCommand #PowerShell #CommandPrompt #Windows11 #Windows10 #WSL #CommandLine #TerminalProfiles #SplitPanes #TerminalTabs #WindowsAdministration #ITProfessionals #SystemAdministration #WinGet #ConPTY #TerminalCustomization #Troubleshooting #Microsoft

SOURCES

• Microsoft Learn — Windows Terminal overview Microsoft Learn
• Microsoft Learn — Install and get started with Windows Terminal Microsoft Learn
• Microsoft Learn — Windows Terminal command-line arguments Microsoft Learn
• Microsoft Learn — Windows Terminal FAQ Microsoft Learn
• Microsoft Learn — Windows Terminal troubleshooting Microsoft Learn
• Microsoft Learn — Windows Terminal distribution types Microsoft Learn
• Microsoft Learn — Creating a pseudoconsole session Windows Console
• Microsoft Learn — Group Policy for Windows Terminal learn.microsoft.com
• Microsoft GitHub — Windows Terminal repository GitHub