Windows Terminal is Microsoft's command-line host for PowerShell, Command Prompt, and WSL environments, combining tabs, split panes, and configurable profiles to organize development, administration, and scripting sessions.
Windows Terminal is Microsoft's desktop application for running command-line shells in a shared interface with tabs and split panes. It hosts environments such as PowerShell, Command Prompt, and Linux shells available through Windows Subsystem for Linux. Developers can keep build commands beside application output, while administrators can organize separate sessions for maintenance and troubleshooting. Profiles provide distinct launch settings and appearances for different environments, making the active shell easier to recognize. The application handles input, text display, and window organization; the selected shell still interprets commands. This separation lets you improve your command-line workspace without adopting a new scripting language.
Windows Terminal requires Windows 10 version 2004, build 19041, or later, including Windows 11. Microsoft offers Store installation with automatic updates, while manually downloaded packages require you to maintain updates yourself. The supplied MSIX bundle is the packaged release rather than a standalone shell or Linux distribution. PowerToys complements this command-line workspace with desktop window management and keyboard utilities, helping organize terminal windows alongside editors and documentation. Shells, developer tools, and remote connection clients must still be available separately when a workflow requires them. Profile configuration controls how sessions start, but it does not install their dependencies or grant additional operating system permissions.
Windows Terminal helps you maintain context when a task spans several command-line sessions. Keeping related work together makes it easier to follow a build, inspect its output, and run a corrective command without repeatedly searching through separate windows. Distinct profile names and colors provide visual cues about the environment receiving your input, supporting more deliberate work when similar prompts are open. Reusable launch configurations reduce the setup needed for recurring projects, while adjustable text and shortcuts help accommodate different screens and working preferences. These controls are useful when moving between local Windows tools and Linux environments, because the interface remains familiar even though command syntax differs. The practical benefit comes from organizing access to your existing tools rather than changing their behavior. Teams can also share configuration examples to make documented workflows easier to reproduce, provided each person has the required shells, paths, and applications installed.
Key capabilities and highlights.
Windows Terminal groups multiple command-line sessions into tabs within one window. Keep a project shell, a maintenance session, and another working directory accessible without opening a separate application window for each. Switching tabs changes the active session while allowing the others to remain available for their own commands and output.
Split panes display multiple sessions beside or above one another inside a tab. You can watch application output while entering commands in a neighboring shell, or compare results from different environments. Each pane hosts its own session, so arranging them together does not combine their commands or working directories.
Profiles in Windows Terminal define how different command-line environments launch and appear. Configure a shell's command line, starting directory, and visual settings for a particular workflow. Separate profiles help distinguish similar sessions and reduce repeated setup when switching between installed PowerShell versions, Command Prompt, or available Linux distributions.
Tab tearout lets you drag a session into a new window or move tabs into an existing window. Reorganize your workspace when a task needs more screen space or should sit beside another application. This provides flexibility after sessions are already open, without requiring every task to share one layout.
Windows Terminal lets you assign keyboard shortcuts to actions such as opening tabs, switching sessions, and copying text. Adapt frequently used controls to your keyboard and working habits. Review potential overlaps with shell shortcuts so that a terminal action does not unexpectedly intercept input intended for a command-line application.
Appearance settings let you adjust fonts, color schemes, and backgrounds for individual profiles. Use readable contrast for extended sessions or distinct colors to identify different environments at a glance. Background images are also supported, although a restrained configuration can make dense command output easier to read during troubleshooting.
Windows Terminal supports Unicode and UTF-8 text and uses GPU acceleration for rendering. This accommodates multilingual output and supported symbols within command-line sessions. Correct display still depends on the selected font and the application's encoding, so terminal support alone cannot repair incorrectly encoded text produced by another program.
The wt command accepts arguments that select profiles, starting directories, tabs, and split panes when launching a workspace. Build a reusable launch command for a recurring project instead of arranging every session manually. The referenced shells and directories must exist, and launched applications retain their normal permissions and requirements.
Browse historical releases and previous builds.
Common questions about Windows Terminal.
Yes. Microsoft distributes it as free, open-source software under the MIT license. Commercial use is permitted; redistribution must retain the required copyright and license notices.
No. It provides the interface that displays output and accepts input. PowerShell remains the shell that interprets PowerShell commands and scripts. Command Prompt and WSL shells can run in separate sessions within the same application.
Double-click the MSIX bundle to open Windows App Installer and follow the installation prompts. Microsoft also documents installation through Add-AppxPackage in PowerShell. If installation reports a missing framework dependency, resolve that dependency before retrying.
Yes, through an installed WSL distribution or another suitable environment. Installing the terminal does not itself install Linux. Commands, packages, and filesystem behavior depend on the environment running in the selected session.
This maintenance release fixes issues involving tab dragging, URL detection after scrolling, text export, and font rendering. It also improves screen-reader announcements in Settings and preserves zoomed font sizes when settings reload.
Windows Terminal is Microsoft's command-line host for PowerShell, Command Prompt, and WSL environments, combining tabs, split panes, and configurable profiles to organize development, administration, and scripting sessions.
IIS Service Monitor is the Windows entrypoint process for IIS inside Windows Server containers, watching the w3svc service and promoting container environment variables into the application pool.
Azure Monitor Agent is Microsoft's unified telemetry agent for Windows and Linux machines, collecting logs and performance data and routing it to Azure Monitor through centrally managed data collection rules.
Power Automate for desktop is Microsoft's robotic process automation app for Windows. It builds low-code desktop flows that automate repetitive work across applications, websites, files, and email, and Power Automate for desktop can start from a button, a schedule, or an event.
Remote Desktop is the Microsoft client for connecting to remote PCs, cloud desktops, and published applications over the Remote Desktop Protocol. It lets people work in a full desktop environment from another device, with local printers, drives, and audio available during the session.
Comments