Windows Terminal FAQ

The settings file can be found in the following location:

• Windows Terminal (Stable): %localappdata%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\settings.json
• Windows Terminal (Preview): %localappdata%\Packages\Microsoft.WindowsTerminalPreview_8wekyb3d8bbwe\LocalState\settings.json
• Windows Terminal (Canary): %localappdata%\Packages\Microsoft.WindowsTerminalCanary_8wekyb3d8bbwe\LocalState\settings.json
• Unpackaged distribution: %localappdata%\Microsoft\Windows Terminal\settings.json

To run Windows Terminal with elevated administrator permission (admin mode), right-click on the Windows Terminal icon, then again on the Windows Terminal title that displays, then select "Run as administrator".

Alternatively, you can open the Windows Quick Access menu using the shortcut, ⊞ Windows key + X, and then selecting Windows Terminal (Admin).

No, mixing administrator-level permission tabbed shells with those that do not have elevated administrator permission is not supported due to security concerns.

No, Visual Studio Code is xtermjs and written in TypeScript while Windows Terminal is native code.

Windows Terminal will support any command line or shell that you have on your machine, including those that are included with Windows like PowerShell or Windows Command Prompt (cmd.exe), as well as any Linux distribution that can be installed with WSL, Azure Cloud Shell, Git Bash, etc. The terminal will automatically detect when you've installed a Linux distribution with WSL and create a profile for you. It can also save your Azure credentials, so you can quickly log in quickly to Azure Cloud Shell.

Windows Terminal is basically a host that enables you to run multiple command-line apps or shells side-by-side in customizable environment using tabs or window panes. Examples of "shell" applications include cmd.exe (the traditional Windows Command Prompt), powershell, or zsh. These are text-only applications that provide streams of characters and don't care about how they are rendered to the user. They are also sometimes referred to as "command-line client" applications. On the other hand, "terminal" applications, like Windows Terminal, gnome-terminal, xterm, iterm2, or hyper, are all graphical applications that can be used to render the output of command-line clients, customizing things like font, text size, colors, etc. On Windows, if you run cmd.exe, the operating system will create an instance of conhost.exe as the "terminal" for displaying the cmd.exe command-line client. The same thing happens for PowerShell, the system creates a new conhost window for any client not already connected to a terminal of some kind. Any terminal can run any command-line client application, so Windows Terminal can run any shell you prefer, such as Bash using Windows Subsystem for Linux (WSL).

In your settings.json file, you can create or modify profiles that run any command-line executable. In the settings.json file, set "commandline" to whatever you want. For example, powershell --> "pwsh.exe". You can also add a profile using the terminal settings ui by scrolling to the bottom of your profiles list and selecting "+ Add a new profile".

Sounds like you're in focus mode. Focus mode will hide the tabs and title bar.

To exit focus mode, which hides the tabs and title bar on Windows Terminal, open the terminal command palette (Ctrl+Shift+P), find "toggle focus mode", then hit enter.

You may also want to ensure that your launch mode is not set to "focus" in the Startup settings.

Windows Terminal is the stable public release and receives regular updates that have been tested and debugged in the preview release. The recommended way to install is via the Microsoft Store, which will provide automatic updates whenever they are released. Windows Terminal Preview is a release for those interested in trying the latest features as they are being developed, tested for bugs, and becoming stable enough to be added to the main terminal release. Features from this release are documented with the (Preview) tag.

While we recommend installing Windows Terminal using the Microsoft Store, you can also install using Windows Package Manager, GitHub, Chocolatey, or Scoop.

Yes. You first need to go to the Profiles section of your settings.json file. Using the "commandline": property, you can specify any batch file, command, ssh connection, or executable that you want to run as a profile in Windows Terminal. You just need to enter the path to the file that you want to run.

This example shows an example of a terminal profile set up based on a "demo" batch file.

{
"commandline": "%USERPROFILE%/OneDrive/demo.bat",
"name": "Batch Profile"
}

This can also be done in the Settings UI. Select "+ Add a new profile" > "+ New empty profile". Browse to the starting directory where your batch file (or SSH connection, executable, command file, etc) is located. Give the profile a name and save.

There have been a wide variety of contributions to Windows Terminal, including bug fixes, identifying and discussing issues, contributing to this documentation, but a few of our favorite features that have come from community contributions have included support for background images and gifs, retro effects, and tab coloring, just to name a few. Learn more about how to contribute.

The Windows Console host, conhost.exe, is Windows' original command-line user experience. It also hosts Windows' command-line infrastructure and the Windows Console API server, input engine, rendering engine, user preferences, etc. A primary goal of Windows Console is to maintain backward compatibility, thus adding new features became prohibitive and led to the creation of the Windows Terminal. Learn more in the Windows Terminal open-source repo and in the WIndows Console docs.

Yes! As of Windows Terminal Preview v1.12.2922.0, you can now save window pane layouts upon closing a terminal session with the firstWindowPreference global setting.

Windows Terminal is under very active development. You can view the team's plans on the Terminal 2.0 Roadmap document in the open-source terminal repo. New features go into Windows Terminal Preview first, then typically a month after they've been in Preview, those features move into Windows Terminal.

You can contribute feature Requests or ideas, as well as bug reports, security vulnerabilities, or documentation issues by filing an issue in the terminal repo.

The PSReadLine module is responsible for setting the colors and behavior of your PowerShell command line. You can set colors for specific attributes of your PowerShell prompt by using the Set-PSReadLineOption, see Example 4: Set multiple color options.

No. For more technical details, refer to this spec and this doc.

The system theme in Windows 11 defaults to the Light theme appearance unless changed by the user. Windows Terminal appearance color scheme, however, is Dark by default. Many users won't change the appearance themes and will just see the default themes. The goal of aligning Windows Terminal appearance with the colors of the Windows operating system (OS) titlebar leaves these options: 1) Do nothing (This is the Terminal default before v1.16). In the default setup, the result is a visually unappealing contrast between black terminal content with a light titlebar. 2) Default the color scheme of the terminal to match the OS theme and leave the app theme set to "system". In the default setup, this will result in the terminal appearing as black text on a white background. 3) Change the default theme of Windows Terminal to Dark, regardless of OS theme. In the default setup, this will result in the terminal appearing as white text on a black background, with a dark titlebar. Option 3 presented the optimum balance of the least surprise to users on the default settings, with the most aesthetically pleasing results. Windows Terminal v1.16 also introduced new toggles for customizing the appearance of the window, including: Customizing the title bar color, the tab color (including auto-matching the background), and enabling different colors for focused or unfocused windows. Windows Terminal 1.17 introduces additional flexibility with the ability to sync the Terminal theme to the OS theme and sync the color scheme to the OS theme. The Terminal is already 99% white text on a black background, these changes just line the title bar up with that.

Add "theme": "system" to your settings.json, or you can change the Theme on the "Appearance" page of the Windows Terminal Settings.

This is a side effect of the Theme changes introduced in v1.16. The default themes in v1.16 and later will always use the Terminal background color as the default color for each tab. By default on a black terminal window, you will get a black tab. With a blue color scheme (like Campbell PowerShell), you'll get a blue tab. This is to give the Terminal a "seamless" feel. In Light mode, that creates a case where a black tab will appear on a white tab row. However, with v1.16 and later, you can customize the theme of the terminal. For example:

"theme": "White Tabs",
"themes":
[
    {
        "name": "White Tabs",
        "tab":
        {
            "background": "#ffffffff",
        },
        "window":
        {
            "applicationTheme": "light"
        }
    },
]

Alternatively, if you're using an OS Light theme and want to set the terminal color scheme to a white background, v1.17 enables setting different color schemes based on the theme of the window. For example, to change the background color based on the window.applicationTheme of Windows Terminal, you can do this:

"colorScheme":
{
    "light": "One Half Light",
    "dark": "One Half Dark",
},