The new Windows Terminal and the original Windows console host, all in the same place!

Overview

Welcome to the Windows Terminal, Console and Command-Line repo

This repository contains the source code for:

Related repositories include:

Installing and running Windows Terminal

🔴 Note: Windows Terminal requires Windows 10 1903 (build 18362) or later

Microsoft Store [Recommended]

Install the Windows Terminal from the Microsoft Store. This allows you to always be on the latest version when we release new builds with automatic upgrades.

This is our preferred method.

Other install methods

Via GitHub

For users who are unable to install Windows Terminal from the Microsoft Store, released builds can be manually downloaded from this repository's Releases page.

Download the Microsoft.WindowsTerminal_.msixbundle file from the Assets section. To install the app, you can simply double-click on the .msixbundle file, and the app installer should automatically run. If that fails for any reason, you can try the following command at a PowerShell prompt:

# NOTE: If you are using PowerShell 7+, please run
# Import-Module Appx -UseWindowsPowerShell
# before using Add-AppxPackage.

Add-AppxPackage Microsoft.WindowsTerminal_<versionNumber>.msixbundle

🔴 Note: If you install Terminal manually:

  • Terminal will not auto-update when new builds are released so you will need to regularly install the latest Terminal release to receive all the latest fixes and improvements!

Via Windows Package Manager CLI (aka winget)

winget users can download and install the latest Terminal release by installing the Microsoft.WindowsTerminal package:

winget install --id=Microsoft.WindowsTerminal -e

Via Chocolatey (unofficial)

Chocolatey users can download and install the latest Terminal release by installing the microsoft-windows-terminal package:

choco install microsoft-windows-terminal

To upgrade Windows Terminal using Chocolatey, run the following:

choco upgrade microsoft-windows-terminal

If you have any issues when installing/upgrading the package please go to the Windows Terminal package page and follow the Chocolatey triage process

Via Scoop (unofficial)

Scoop users can download and install the latest Terminal release by installing the windows-terminal package:

scoop bucket add extras
scoop install windows-terminal

To update Windows Terminal using Scoop, run the following:

scoop update windows-terminal

If you have any issues when installing/updating the package, please search for or report the same on the issues page of Scoop Extras bucket repository.


Windows Terminal 2.0 Roadmap

The plan for delivering Windows Terminal 2.0 is described here and will be updated as the project proceeds.

Project Build Status

Project Build Status
Terminal Terminal Build Status
ColorTool Colortool Build Status

Terminal & Console Overview

Please take a few minutes to review the overview below before diving into the code:

Windows Terminal

Windows Terminal is a new, modern, feature-rich, productive terminal application for command-line users. It includes many of the features most frequently requested by the Windows command-line community including support for tabs, rich text, globalization, configurability, theming & styling, and more.

The Terminal will also need to meet our goals and measures to ensure it remains fast and efficient, and doesn't consume vast amounts of memory or power.

The Windows Console Host

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. The console host code in this repository is the actual source from which the conhost.exe in Windows itself is built.

Since taking ownership of the Windows command-line in 2014, the team added several new features to the Console, including background transparency, line-based selection, support for ANSI / Virtual Terminal sequences, 24-bit color, a Pseudoconsole ("ConPTY"), and more.

However, because Windows Console's primary goal is to maintain backward compatibility, we have been unable to add many of the features the community (and the team) have been wanting for the last several years including tabs, unicode text, and emoji.

These limitations led us to create the new Windows Terminal.

You can read more about the evolution of the command-line in general, and the Windows command-line specifically in this accompanying series of blog posts on the Command-Line team's blog.

Shared Components

While overhauling Windows Console, we modernized its codebase considerably, cleanly separating logical entities into modules and classes, introduced some key extensibility points, replaced several old, home-grown collections and containers with safer, more efficient STL containers, and made the code simpler and safer by using Microsoft's Windows Implementation Libraries - WIL.

This overhaul resulted in several of Console's key components being available for re-use in any terminal implementation on Windows. These components include a new DirectWrite-based text layout and rendering engine, a text buffer capable of storing both UTF-16 and UTF-8, a VT parser/emitter, and more.

Creating the new Windows Terminal

When we started planning the new Windows Terminal application, we explored and evaluated several approaches and technology stacks. We ultimately decided that our goals would be best met by continuing our investment in our C++ codebase, which would allow us to reuse several of the aforementioned modernized components in both the existing Console and the new Terminal. Further, we realized that this would allow us to build much of the Terminal's core itself as a reusable UI control that others can incorporate into their own applications.

The result of this work is contained within this repo and delivered as the Windows Terminal application you can download from the Microsoft Store, or directly from this repo's releases.


Resources

For more information about Windows Terminal, you may find some of these resources useful and interesting:


FAQ

I built and ran the new Terminal, but it looks just like the old console

Cause: You're launching the incorrect solution in Visual Studio.

Solution: Make sure you're building & deploying the CascadiaPackage project in Visual Studio.

Note: OpenConsole.exe is just a locally-built conhost.exe, the classic Windows Console that hosts Windows' command-line infrastructure. OpenConsole is used by Windows Terminal to connect to and communicate with command-line applications (via ConPty).


Documentation

All project documentation is located at aka.ms/terminal-docs. If you would like to contribute to the documentation, please submit a pull request on the Windows Terminal Documentation repo.


Contributing

We are excited to work alongside you, our amazing community, to build and enhance Windows Terminal!

BEFORE you start work on a feature/fix, please read & follow our Contributor's Guide to help avoid any wasted or duplicate effort.

Communicating with the Team

The easiest way to communicate with the team is via GitHub issues.

Please file new issues, feature requests and suggestions, but DO search for similar open/closed pre-existing issues before creating a new issue.

If you would like to ask a question that you feel doesn't warrant an issue (yet), please reach out to us via Twitter:

Developer Guidance

Prerequisites

Building the Code

This repository uses git submodules for some of its dependencies. To make sure submodules are restored or updated, be sure to run the following prior to building:

git submodule update --init --recursive

OpenConsole.sln may be built from within Visual Studio or from the command-line using a set of convenience scripts & tools in the /tools directory:

Building in PowerShell

Import-Module .\tools\OpenConsole.psm1
Set-MsBuildDevEnvironment
Invoke-OpenConsoleBuild

Building in Cmd

.\tools\razzle.cmd
bcz

Running & Debugging

To debug the Windows Terminal in VS, right click on CascadiaPackage (in the Solution Explorer) and go to properties. In the Debug menu, change "Application process" and "Background task process" to "Native Only".

You should then be able to build & debug the Terminal project by hitting F5.

👉 You will not be able to launch the Terminal directly by running the WindowsTerminal.exe. For more details on why, see #926, #4043

Coding Guidance

Please review these brief docs below about our coding practices.

👉 If you find something missing from these docs, feel free to contribute to any of our documentation files anywhere in the repository (or write some new ones!)

This is a work in progress as we learn what we'll need to provide people in order to be effective contributors to our project.


Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

Comments
  • Guide for build and installation

    Guide for build and installation

    Tools needed

    1. VS2017 or higher with the following packages ("Workloads" tab in Visual Studio Installer) : 1.1 Desktop Development with C++. 1.2 Universal Windows Platform Development. 1.3 Windows 10 SDK (10.0.18362.0). 1.4 If you're running VS2019, you'll also need to install either v141 Toolset or v142 Toolset.
    2. Git command-line tool.
    3. Nuget.exe (Needed in build step 3, can be found in Terminal/dep/nuget).

    Build Steps

    1. git clone this repository, not download .zip file.
    2. Run git submodule update --init --recursive in Terminal folder.
    3. Run nuget restore OpenConsole.sln (This step can be skipped, then Visual Studio should warn you that there are packages to restore - then restore).
    4. Open OpenConsole.sln with Visual Studio.
    5. Build whole solution(F7) with your platform(x86/x64) and release mode, you may need to fix some build errors: 5.1 C2220 and code page warnings: All errors and warnings are encoding error of unicode characters, a helpful workaround is to modify corresponding file encoding to UTF-8 BOM (Notepad++ is recommended). 5.2 Errors in src/tools/vtpipeterm/main.cpp: In addtion, you should also add u8 prefix before string literals with unicode characters, e.g. line 395, 398, 401 and 404.

    Workaround

    Try build with PR 458 or PR 549, both of them can build successfully.

    Installation

    Unfortunately, the generated .appx doesn't have any certificates, so it cannot be installed via double-click or powershell, the only way to install is to deploy the solution in VS.

    1. Open Windows Settings - Upgrade & Security - For Developers, switch App sources to Developer mode.
    2. Right click on CascadiaPackage project (under Solution/Terminal), select Deploy Solution to install, then you'll find Windows Terminal (Preview) in start menu.

    Settings

    After open the terminal, you can't see any menu buttons.

    Just press Ctrl + T to open a new tab, and you'll see a drop-down button in the tab bar.

    Click it and select Settings, then you can modify the configuration via opened profiles.json.

    Add WSL

    1. Create a new session in profiles, with content copied from profiles/cmd.
    2. Give it a new guid.
    3. Give it a new name, such as WSL.
    4. Specify its commandline to wsl.exe.

    Then you'll find WSL in the drop-down menu of tab bar.

    Here're sample codes:

    {
        "guid": "{09dc5eef-6840-4050-ae69-21e55e6a2e62}",
        "name": "WSL",
        "colorscheme": "Campbell",
        "historySize": 9001,
        "snapOnInput": true,
        "cursorColor": "#FFFFFF",
        "cursorShape": "bar",
        "commandline": "wsl.exe",
        "fontFace": "Consolas",
        "fontSize": 12,
        "acrylicOpacity": 0.75,
        "useAcrylic": true,
        "closeOnExit": false,
        "padding": "0, 0, 0, 0"
    }
    
    Issue-Docs Area-Build Product-Terminal Needs-Tag-Fix 
    opened by ZgblKylin 262
  • Add

    Add "open Windows terminal here" into right-click context menu

    Add "open Windows terminal here" to right-click context menu?

    We know that, for windows 7, by default when we click "shift + right click with mouse" when we enter into a folder without selecting anything, we can see the option "open command window here".

    image

    While for windows 10, by default when we click "shift + right click with mouse", we can see the option "open powershell window here".

    So for Windows 10 (version later than 1903), how can we make the following three options available in right-click context menu?

    • open command window here
    • open powershell window here
    • open Windows terminal here

    Looking forward to your reply, thanks a lot~

    Issue-Feature Resolution-Fix-Committed Help Wanted Area-User Interface Product-Terminal 
    opened by yanglr 235
  • [Question] Configuring Windows Terminal profile to always launch elevated

    [Question] Configuring Windows Terminal profile to always launch elevated

    Hi! Is there a way to configure a profile so that the commandLine it launches always starts with elevated (admin) permissions?

    Currently, you can launch the entire application as Administrator, but then every single commandLine runs as Administrator, which is not ideal.

    Issue-Feature Area-Settings Product-Terminal 
    opened by pingzing 212
  • Feature request: hot key drop down ala quake/guake/tilda

    Feature request: hot key drop down ala quake/guake/tilda

    The petty thing I miss most when I pop into Windows is having a separate hot key terminal for each of my three monitors. The closest i've ever been to believing in god was when I realized that was obtainable and if you could make that happen in Windows I just might have to kiss you.

    Issue-Feature Resolution-Fix-Committed Help Wanted Area-User Interface Product-Terminal Needs-Tag-Fix 
    opened by NOFUNEVER 147
  • AltGR SEQUENCES DO NOT WORK -- Can't type any AltGr combinations in Windows Terminal

    AltGR SEQUENCES DO NOT WORK -- Can't type any AltGr combinations in Windows Terminal

    Your Windows build number: 10.0.18362.86

    What you're doing and what's happening: Trying to enter the @ sign on a Swedish keyboard in a PowerShell console using Alt Gr + 2.
    See animated gif:

    terminal

    What's wrong / what should be happening instead: Windows terminal shows digit-argument instead of outputting the @ sign as expected.

    It's possible this is a PEBKAC error somehow but the problem doesn't show up in the normal PowerShell console... 😓

    Resolution-Fix-Committed Resolution-Fix-Available Help Wanted Issue-Bug Area-TerminalControl Product-Terminal 
    opened by patriksvensson 143
  • No keyboard input

    No keyboard input

    You may experience an issue with Windows Terminal where keyboard input does not work. By and large, we've determined that this is caused by the "Touch Keyboard and Handwriting Service" being disabled.

    If you're hitting this issue, make sure that the "Touch Keyboard and Handwriting Service" is not disabled. Certain "de-bloating" software (and apparently MSI Afterburner) likes to disable it or suppress it in the name of making your machine less understandable and "faster".

    If you're experiencing an input issue that is not helped by exiting MSI Afterburner or re-enabling the "Touch Keyboard and Handwriting Service", please file a new issue.

    Original issue content Latest version of Windows Terminal.

    Tried clean installing multiple times, keyboard input works on everything else (as I am typing with it here ...) yes that includes powershell.exe and cmd.exe.

    What gives?

    Needs-Repro Area-Input Issue-Bug Product-Terminal Priority-2 Tracking-External 
    opened by privacyguy123 131
  • Feature Request: Standard Opacity options like the traditional console.

    Feature Request: Standard Opacity options like the traditional console.

    Perhaps I overlooked it browsing through the json file but i didn't see another means to achieve transparency and i'm not a fan of the acrylic effects blurring factor or the fact that it turns off when the window is not selected. The traditional console provides for a static opacity just like in most nix envs, i'd hope it's just a matter of time before it's implemented here?

    Issue-Feature Resolution-Fix-Committed Area-User Interface Product-Terminal 
    opened by NOFUNEVER 113
  • [Conpty] Add support for mouse input

    [Conpty] Add support for mouse input

    On: Microsoft Windows [Version 10.0.17763.134]

    I have implemented conpty in my terminal emulator: https://github.com/wez/wezterm

    I can successfully run target\debug\wezterm.exe to spawn console applications such as cmd.exe powershell.exe and bash.

    The issue I'm seeing is that when I launch bash, either indirectly via cmd.exe or directly via the bash launcher, conpty seems to swallow the mouse reporting escape sequences; I don't see them being received by my terminal parser, and thus vim has no effective mouse support despite being configured with set mouse=a.

    Running the same WSL install via wsl-terminal does have working mouse support, and wezterm has been my daily driver on Linux for about a year with working mouse support, so we can rule out an obvious misconfiguration with vim and the parser in wezterm.

    I've also tried echo -e "\e[?1000h" to manually enable mouse reporting from the shell; normally (on linux and via wsl-terminal) this causes clicks in the terminal to send data to the shell (which appears as garbage input), but when running my terminal with conpty, these are also swallowed up somewhere.

    Is there something special needed for the apps that I spawn into my pty to be able to work with the mouse?

    In case you want to double check the key portion of the code, the relevant file is: https://github.com/wez/wezterm/blob/master/src/winpty.rs The flow is to CreatePipe a pair of pipes, CreatePseudoConsole, and then pass that to a spawned child via the threadproc attributes, as the samples in the MSDN docs and this repo also do.

    Issue-Feature Area-Interop Product-Conpty Needs-Tag-Fix 
    opened by wez 104
  • Terminal hangs when opening new windows or new tabs on Windows Server 2022

    Terminal hangs when opening new windows or new tabs on Windows Server 2022

    After installing either Terminal 1.10 or Terminal Preview 1.11 (after its dependencies and winget), opening it the first time (or subsequent times) causes the window to hang indefinitely (the process shows as 'Not Responding' in Task Manager). A similar problem happens when clicking the + to open a new tab.

    The problem happens regardless if the default terminal is either Powershell or others (like Command Prompt).

    A partial workaround is to launch a second copy of the app while the instance is hung, then use Task Manager to kill the hung app. Once the hung process closes, the application opens as expected. The workaround does not address the new tab problem, but just the initial window opening.

    If there is any logging or debug that can be enabled, please let me know.

    Resolution-Fix-Committed Issue-Bug Area-TerminalControl Needs-Triage Product-Terminal Severity-Blocking Priority-0 
    opened by wkbrd 75
  • Changing Ubuntu WSL starting directory keeps it set to the defualt

    Changing Ubuntu WSL starting directory keeps it set to the defualt

    When editing the the settings, I have tried to chang the default starting directory for the Ubuntu WSL Terminal profile as follows "startingDirectory": "/mnt/D/Folder/SubFolder/", and while it doesnt cause any issues or causes the Terminal to resort to default configuration, it does not set the default starting directory to the specified path.

    Also it seems that most settings for the profile do literally nothing when changing them, from color, to acrylic or scheme settings.

    Note: changing the setting for power shell, cmd, of Kali-Linux does work and change things respectively

    Resolution-Fix-Committed Issue-Docs Area-Settings Product-Terminal Needs-Tag-Fix 
    opened by AlikanakelaKarwowski 75
  • Title bar buttons aren't working (PowerToys)

    Title bar buttons aren't working (PowerToys)

    Environment

    Windows build number: 10.0.18362.295
    Windows Terminal version (if applicable): 0.6.2951.0
    
    Any other software?
    

    Steps to reproduce

    Open terminal and click on close/minimize/maximize/edit environment.

    Expected behavior

    It should work

    Actual behavior

    It shows weird cursor and doesn't work.

    Printscreen

    Issue-Bug Area-User Interface Needs-Author-Feedback Product-Terminal Tracking-External 
    opened by Ronkiro 74
  • can not run after offline install have no any logs

    can not run after offline install have no any logs

    Windows Terminal version

    1.15.2874.0

    Windows build number

    10.0.19044.1288

    Other Software

    No response

    Steps to reproduce

    offline install by commd add-appxpackage xxxx than run

    Expected Behavior

    run ok

    Actual Behavior

    can not run without any log

    Issue-Bug Needs-Triage 
    opened by KnightBlood 0
  • Automatically copy selection to clipboard is no longer working correctly with tmux

    Automatically copy selection to clipboard is no longer working correctly with tmux

    Windows Terminal version

    1.15.2875.0

    Windows build number

    10.0.22621.819

    Other Software

    tmux

    • 3.3a in Fedora Remix WSL
    • 1.8 when SSHed into CentOS 7
    • 3.2a on Ubuntu 22.04 WSL

    Steps to reproduce

    1. Enable "Automatically copy selection to clipboard" image
        "copyFormatting": "all",
        "copyOnSelect": true,
    
    1. Start tmux
    2. I use the mouse to Scroll. If you need help it's: Ctrl + b then : and type set-window-option -g mouse on and press enter (Unless you are on tmux 1.8 and it's a lot more complicated)
    3. Scroll up in tmux buffer
    4. Press Shift + Left Click and drag on the text you want to Select. Holding Shift is important because this is doing a normal terminal "select" not a fancy Tmux select (which copies to tmuxes internal clipboard, not the real Windows one) image
    5. Scroll back down to the bottom so you can get out of scrolling mode image
    6. Paste in terminal (Shift right click)
    7. Now paste in terminal or any other application, and you will have the wrong text pasted

    In this case it will paste 85, not the 10 I actually selected

    Expected Behavior

    This used to work, it was beautiful, and everything was bearable. The text I selected before scrolling back down was in my clipboard, and it pasted correctly. Now the "selection" was in same physical space but no longer over the text I initially selected, but this never mattered and not something I'd expect to change behavior

    I expect it to paste 10 like it was until very recently

    Actual Behavior

    It pasted 85

    Terminal is deciding to copy again at paste time.

    Step 4 is important. Before step 7, if you paste outside of terminal, you will see that after step 5, the text in the Windows Clipboard is indeed correct, even after step 6. But as soon as I go to paste in Terminal, it "re copies" where the select text is and breaks everything.

    It's also important

    Issue-Bug Needs-Triage 
    opened by andyneff 0
  • Fix a potential deadlock for PtySignal::SetParent

    Fix a potential deadlock for PtySignal::SetParent

    This changeset consists of two parts:

    • Refactor PtySignalInputThread to move more code from _InputThread into the various _Do* handlers. This allows us to precisely control console locking behavior which is the cause of this bug.
    • Add the 1-line fix to _DoSetWindowParent to unlock the console before calling foreign functions (SetWindowLongPtrW in this case).

    This fix is theoretical in nature, based on a memory dump from an affected user and most likely fixes: https://developercommunity.visualstudio.com/t/10199439

    Validation Steps Performed

    • ConPTY tests complete. ✅
    Product-Conpty Issue-Bug Priority-1 Area-Remoting 
    opened by lhecker 0
  • Unable to select text correctly while new lines are printed and history buffer is full

    Unable to select text correctly while new lines are printed and history buffer is full

    Windows Terminal version

    1.15.2875.0

    Windows build number

    10.0.22621.819

    Other Software

    No response

    Steps to reproduce

    See #10319 for the previous report, it was supposedly fixed in v1.11, but I still see this behaviour.

    1. Set "historySize": 100, for the profile.
    2. Run a script that echoes new lines
    3. Try to select text

    Example script to test the issue:

    Do {
    	echo $(Get-Random)
    	sleep 0.1
    }
    while ($true)
    

    https://user-images.githubusercontent.com/613331/204636943-b8f8f4b5-e6da-4fdb-88cd-b59bc8e8ad17.mp4

    Expected Behavior

    Correctly select text. It works when the history buffer is full.

    Actual Behavior

    The selection scrolls away from you, selecting different text.

    Issue-Bug Needs-Triage 
    opened by xPaw 0
  • NULL_CLASS_PTR_READ from PublicTerminalCore.dll!TerminalIsSelectionActive

    NULL_CLASS_PTR_READ from PublicTerminalCore.dll!TerminalIsSelectionActive

    Windows Terminal version

    1.15.2210.6001

    Windows build number

    10.0.19044.2251

    Other Software

    Visual Studio 2022 v.17.5.33103.201

    Steps to reproduce

    Currently unknown, but the dumps show the user selecting some text and Visual Studio crashing due to an AccessViolationException.

    You can find more information in the Watson cabs: https://watsonportal.microsoft.com/Failure?FailureSearchText=32503620-0791-0795-1eff-dc016b5e23e9&MaxRows=100

    Internal bug ticket: Bug 1676887: [Watson] crash64: NULL_CLASS_PTR_READ_c0000005_PublicTerminalCore.dll!TerminalIsSelectionActive

    Version of VS showing this issue: https://devdiv.visualstudio.com/DefaultCollection/DevDiv/_workitems/edit/1639645 (Go to Build and Install tab for download link)

    Expected Behavior

    No response

    Actual Behavior

    Visual Studio crashes when text is selected

    Issue-Bug Needs-Triage 
    opened by javierdlg 0
  • `error 2147942402 (0x80070002)` exception occurs when launching the panel and executing multiple commands

    `error 2147942402 (0x80070002)` exception occurs when launching the panel and executing multiple commands

    Windows Terminal version

    1.15.2874.0

    Windows build number

    10.0.19044.2193

    Other Software

    No response

    Steps to reproduce

    1. wt -p "Git Bash" ssh -i ~/.ssh/id_rsa [email protected] "cd /home/project/feature; yarn -v; node -v"; split-pane -V -p "Git Bash" ssh -i ~/.ssh/id_rsa [email protected] "cd /home/project2; yarn -v; node -v" → Enter
    2. [error 2147942402 (0x80070002) when launching `" node -v"']

    start multiple panels via wt, each panel executing multiple commands.

    Expected Behavior

    Login, enter /home/project/feature, and then run yarn -v, and then run node -v.

    Actual Behavior

    An exception occurs.

    Issue-Bug Needs-Triage Needs-Attention 
    opened by xianghongai 4
Releases(v1.15.2874.0)
  • v1.15.2874.0(Oct 18, 2022)

    v1.15.2874 (Windows 10) and v1.15.2875 (Windows 11) are servicing updates to Windows Terminal Stable v1.15. It is highly recommended that you install this version if you're using Windows 11 22H2 (October Update).

    As a reminder, Terminal 1.12 was the last version of Windows Terminal that supports Windows 19H1 or 19H2. Those versions of Windows went out of support in May, so you really may want to consider upgrading.

    Preinstallation Kit info

    A preinstallation kit is available for system integrators and OEMs interested in prepackaging Windows Terminal with a Windows image. More information is available in the DISM documentation on preinstallation. Users who do not intend to preinstall Windows Terminal should continue using the msixbundle distribution.

    Why are there so many packages? How do I choose? This version of Windows Terminal is distributed in two bundles, one of which works on Windows 10-11 and the other of which only works on Windows 11. The Windows 11 version is much smaller because we no longer need to work around a platform issue related to our dependencies.

    If you intend on using Terminal as an unpackaged application--that is, extracting the msix file--we recommend that you use the Win10 bundle. You will need the Visual C++ runtime redistributable.

    In addition, if you install the packaged version on either Windows 10 or Windows 11, it now depends on the Visual C++ Universal Runtime Package.

    Despite these distributions having different version numbers, they are built from the same code and there is no functional difference between them.

    If you install the Windows 10 version on Windows 11, it will probably automatically upgrade itself to the Windows 11 version.

    This servicing release supersedes the v1.15.2712.0 release (not uploaded to GitHub) and contains the following bug fixes and changes:

    Changes

    • Terminal will now detect the title of a LNK or EXE as the default terminal (backport from 1.16) (#13570)

    Bug Fixes

    Stability and Security

    • Windows Terminal once again works on Windows N (no media) SKUs
    • We've fixed the following issues that could lead to a local denial of service or worse (with many thanks to @dgl for reporting):
      • OSC 9;9 will now reject malformed paths and not further propagate them into wsl --cd (#14093)
      • OSC 8 URIs will be limited to 2MB in length, following iTerm2 (and only 1024 bytes will be displayed in the tooltip) (#14198)
    • We've fixed some lag and deadlocking that would happen when you close a tab (#14041)
    • We will no longer leak OpenConsole processes when they're running a Visual Studio Developer Shell (#14160)
    • An application calling system() on its main thread will no longer deadlock itself and Terminal (when Terminal is set as default) (#14195)
    • We've fixed a potential race condition causing a crash on tab close (#13882)

    Accessibility

    • The WPF control now supports accessibility notifications (#14097)
    • The Settings UI title/breadcrumb bar is now readable by screen readers (#14180)

    Usability

    • You can now duplicate unfocused tabs (#13964) (thanks @JerBast!)
    • The Open in Terminal shell extension should appear more reliably on the Desktop context menu (#14048) (#14211)
    • "Export Text" will no longer suggest illegal filenames (#13693) (thanks @EliaSchiavon!)
    • Alt+Space will now open the system menu in the Settings UI and Command Palette (#14221)
    • intenseTextStyle is now included properly in the JSON schema (whoops) (#14210) (thanks @neersighted!)
    Source code(tar.gz)
    Source code(zip)
    Microsoft.WindowsTerminal_Win10_1.15.2874.0_8wekyb3d8bbwe.msixbundle(36.77 MB)
    Microsoft.WindowsTerminal_Win10_1.15.2874.0_8wekyb3d8bbwe.msixbundle_Windows10_PreinstallKit.zip(65.29 MB)
    Microsoft.WindowsTerminal_Win11_1.15.2875.0_8wekyb3d8bbwe.msixbundle(17.43 MB)
    Microsoft.WindowsTerminal_Win11_1.15.2875.0_8wekyb3d8bbwe.msixbundle_Windows10_PreinstallKit.zip(64.49 MB)
  • v1.16.2641.0(Sep 23, 2022)

    Here on this day of September 2022, we've quashed a number of bugs in the 1.16 preview release and added some new features to boot. Enjoy!

    Changes

    • Terminal now understands the sizes of characters newly-added in Unicode 15.0 (#14001)
    • We've added support for fractional font sizes (surprise! on a point release!) (#14013) (#14040)
      • If you're using the new text rendering engine plus the Terminus TTF font, you can now select a font size that perfectly matches a bitmap strike . . . and it works!

    Bug Fixes

    New Rendering Engine

    • Bitmap fonts should look much better now (#14014)
      • As a side effect, we are now intentionally ignoring the typographic line gap. We have found that monospaced terminal fonts have a line gap of zero, and the ones that don't should.
      • See above. Some bitmap fonts require fractional point sizes . . . so now you can see them in their full glory!
    • On devices that don't support Shader Model 4.0 but do support DirectX 10, we will no longer try to use the glyph atlas (#13994)
      • ... and if we did, we would no longer tell you about the error 10,000 times (#13995) (thanks to @Its-Nevmo and @noinkling for testing!)
    • No longer should there be streaks of cursor left all over the left side of the screen (#14038)
    • If you were to specify \e#3, we might have crashed before, but now we will not (#13966)
    • You can once again use shaders for experimental.pixelShaderPath that are not technically perfect (that is, ones that compile with warnings) (#13998) (thanks @mrange!)
    • Some text (especially that which requires fake italics) should now look less like a RaNsOm nOtE (#14039)
      • It might still look a little bit like a ransom note, sorry. Just less so.

    Reliability

    • Tabs should no longer take up to infinity seconds to close (#14041)
      • If you see any instances of OpenConsole.exe hanging around after you close a tab (or a whole Terminal), please let us know!
    • The "Open in Terminal ..." context menu item should now show up and disappear more reliably (#14048)
    Source code(tar.gz)
    Source code(zip)
    Microsoft.WindowsTerminalPreview_Win10_1.16.2641.0_8wekyb3d8bbwe.msixbundle(37.79 MB)
    Microsoft.WindowsTerminalPreview_Win11_1.16.2642.0_8wekyb3d8bbwe.msixbundle(18.45 MB)
  • v1.16.2523.0(Sep 13, 2022)

    This one almost speaks for itself. Dang. Welcome to Terminal: Really Long Release Notes Edition!

    Features

    • Themes: Terminal now has support for themes! (#12992) (#13049) (#13178) (#13348) (#13465) (#13689) (#13702) (#13871)
      • To celebrate this, we've changed the default theme to Windows Dark. If you are not happy about that, you can change it back to light or anything you like (#13743)
    • New Text Rendering Engine
      • The new text rendering engine is now enabled by default in Preview builds (#13752)
      • We've added support for the experimental.pixelShaderPath and experimental.retroTerminalEffect settings... (#13885)
        • ... with a further optimization: shaders that do not use the time component will not trigger a redraw every frame! (#13903)
      • It now supports...
        • experimental.rendering.software (#13886)
        • intenseTextStyle bold (#13458)
        • underline/overline/hyperlink lines (#13587)
      • Glyphs that have not been used in some time will be aged out and replaced (#13458) (#13607) (#13784) (#13477)
      • Performance over RDP to a machine that has no GPU has been improved (#13816)
        • (at the cost of some fidelity)
        • experimental.rendering.software will enable this fallback mode as a last resort for compatibility
      • Glyphs that do not fit in a cell will be scaled up or down as appropriate (#13549), including "Powerline" glyphs (#13650)
      • We've added a setting in the Rendering section, and promoted useAtlasEngine out of the experimental. compartment (#13939)
      • Fonts whose cell sizes were borderline are now rounded instead of clamped to the next pixel size up (#13833)
      • We've made some other correctness and compatibility fixes, far too minute to name (#13956) (#13496) (#13906) (#13530) (#13608)
      • Somewhat as a side effect of all this, you may notice that you're seeing an inverted cursor where you had not previously seen one!
    • This release marks the triumphant return of the "adjust brightness of indistinguishable colors" feature... (#13343)
      • ...and it's brought friends: you can now enable it for all color pairs (#13512)
      • You can enable it with the profile setting adjustIndistinguishableColors (enum never, indexed, always; default never)
    • We've redesigned the color schemes page (#13269) and made updates all over the settings UI (#13179) (#13390) (#13378) (#13377) (#13391)
      • New in this release: color scheme previews, and an easy-access "Set as default color scheme" button!
    • You can now configure Terminal to hide when it loses focus (#13478) (thanks @davidegiacometti!)
    • You can now close all panes other than the focused one with the closeOtherPanes action! (#13547) (thanks @JerBast!)
    • There's a new option that lets you configure where new tabs appear: next to the current one, or at the end (#13421) (#13602) (#13469) (thanks @serd2011!)
      • JSON setting newTabPosition (enum afterLastTab (default), afterCurrentTab)
    • Tab and Shift+Tab now navigate between hyperlinks in Mark Mode. You can open the selected link with Ctrl+Enter. (#13405) (#13494)
    • You can now expandSelectionToWord, which will... well, you know. (#13765)
    • We will now try to detect the title when Terminal is launched by default from an LNK file (#13570)
    • For the old conhost fans in the room, you can now set experimental.enableColorSelection (global, bool, default false) to add 31 new actions that will highlight search results in the colors of the rainbow (#13429)
      • This conhost feature used to be hidden behind a registry key. If you know about it, I think I'm supposed to say you're "one of the real ones?"

    Changes

    Interaction

    • When in mark mode, its built in key bindings Ctrl+A and the modified arrow keys will take precedence over your key bindings (#13659)
    • We've polished how existing selections interact with mark mode (#13893)
    • @AdamSotak has added quick access buttons for the source code and filing feedback to the About dialog (#13510) (thanks!)
    • When your pane is in a light color scheme, the bell flash will now be dark (#13707) (thanks @Fyrebright!)
    • Inverted cursors (which you might find lying around) will now be slightly modulated to account for accidental color overlaps (#13748) (thanks @alabuzhev!)
    • When you Select All, we'll scroll to the top of the screen (#13656)
    • Multi-line paste will no longer strip newlines if there are other newlines in the content (#13698) (thanks @serd2011!)
      • This is to aid in the pasting (after confirmation, of course!) of multi-line commands.

    UI

    • @dansmor7 figured out that we don't need to draw our caption buttons ourselves; now they look great on all versions of Windows! (#13341) (thanks!)

    Console Compatibility

    • We will now discard empty command histories before discarding LRU non-empty ones (#13869) (thanks @serd2011!)
    • ReadConsoleOutput will no longer return nonsense if you wrote nonsense to the text buffer (API BREAKING CHANGE) (#13321)

    VT Support

    • We now support DECBKM (Backarrow Key Mode) (#13894) (thanks @j4james!)
    • The slow march to soft font support in Terminal continues . . . (#13362) (thanks @j4james!)

    Bug Fixes

    Interaction

    • Terminal will now use the tab's active title for Export Text (#13915) (thanks @serd2011!)
    • The Emoji picker, PinYin IME or any other IME will no longer drift off the bottom of the screen (oops) (#13785)
    • The settings UI will now disable "Always show tabs" when "Hide the title bar" is enabled (#13694) (thanks @leejy12!)
    • We'll no longer helpfully offer to put things like \\ and : in your filenames for Export Text (oops) (#13693) (thanks @EliaSchiavon!)
    • We've fixed command line argument parsing when there was a one-letter argument followed by a ; (#13706) (thanks @serd2011!)
    • In the command palette, the 'go back' button will finally returns to the previously selected action (#13504) (thanks @JerBast!)

    UI

    • No longer is there a 1-pixel gap under inactive tabs (#13897)

    Accessibility

    • The Command Palette has become much chattier, announcing (to a screen reader) the name of the selected item (#13519)
    • Asking for INT_MAX characters via UIA will no longer wig us out or try to send you multiple gigabytes of null bytes (#13779)
      • However, it remains impolite to ask for INT_MAX characters via ITextPattern::GetText.

    Performance

    • Terminal is now 1.2 megabytes smaller on disk (uncompressed) thanks to not using RTTI (#13947) (thanks RTTI!)
    • Updating the jumplist used to happen on every launch. Now it will only happen if you've actually changed your settings (#13692)

    Reliability

    • Fixed a number of crashes, not all of which were common or user-impacting:
      • Attempted a fix for the SignalTextChanged crash (#13876)
      • Attempted another fix, this time for the _refreshSizeUnderLock crash (#13857)
      • Fixed a crash in _WritePseudoWindowCallback (#13777)
      • Fixed a crash on exit with the command palette open (#13778)
      • Fixed a race condition in UpdatePatternLocations (#13859)
      • Fixed two race conditions around pseudo window visibility (#13832)
      • Fixed a crash in NVDA, caused by us considering a specific text range invalid (#13907)
      • Fixed a ControlCore race condition on connection close (#13882)
      • Fixed a crash on settings reload (#13644)
      • Fixed a crash when showTabsInTitlebar:false (#13561)
      • Fixed crash on save in rejuv'd Color Schemes page (#13902)
    • Terminal should now more reliably appear in the context menu
    • We've stopped conhost from buying the farm when it got --headless without --signal (#13950)

    With additional thanks to our documentation and code health contributors @jsoref and @LitoMore.

    Source code(tar.gz)
    Source code(zip)
    Microsoft.WindowsTerminalPreview_Win10_1.16.2523.0_8wekyb3d8bbwe.msixbundle(37.78 MB)
    Microsoft.WindowsTerminalPreview_Win11_1.16.2524.0_8wekyb3d8bbwe.msixbundle(18.44 MB)
  • v1.15.2524.0(Sep 13, 2022)

    This release migrates some awesome features, changes and bug fixes from Terminal 1.15 Preview into the stable channel!

    • Terminal now supports "Mark Mode", a keyboard-first text selection and navigation mode. The name is an homage to the traditional Windows Console Host!
      • It is bound by default to Ctrl+Shift+M

    Please see the following release notes for additional details:

    Note that the new text rendering engine and scrollbar mark feature is not included in this Stable build. Yet.

    IMPORTANT This version was made available to the Dev External flighting ring (Windows Insiders) first, and will be released to general availability one or two weeks later depending on its reliability.

    As a reminder, Terminal 1.12 was the last version of Windows Terminal that supports Windows 19H1 or 19H2. That version of windows is going out of support soon, so you may want to consider upgrading.

    Preinstallation Kit info

    A preinstallation kit is available for system integrators and OEMs interested in prepackaging Windows Terminal with a Windows image. More information is available in the DISM documentation on preinstallation. Users who do not intend to preinstall Windows Terminal should continue using the msixbundle distribution.

    Why are there so many packages? How do I choose? This version of Windows Terminal is distributed in two bundles, one of which works on Windows 10-11 and the other of which only works on Windows 11. The Windows 11 version is much smaller because we no longer need to work around a platform issue related to our dependencies.

    If you intend on using Terminal as an unpackaged application--that is, extracting the msix file--we recommend that you use the Win10 bundle. You will need the Visual C++ runtime redistributable.

    In addition, if you install the packaged version on either Windows 10 or Windows 11, it now depends on the Visual C++ Universal Runtime Package.

    Despite these distributions having different version numbers, they are built from the same code and there is no functional difference between them.

    If you install the Windows 10 version on Windows 11, it will probably automatically upgrade itself to the Windows 11 version. It turns out that it is impossible to have two bundles with the same version number, so it has to be this way.

    In addition to the above, we've backported the following changes and bugfixes from Windows Terminal Preview 1.16:

    Changes

    Interaction

    • When in mark mode, its built in key bindings Ctrl+A and the modified arrow keys will take precedence over your key bindings (#13659)
    • We've polished how existing selections interact with mark mode (#13893)

    UI

    • @dansmor7 figured out that we don't need to draw our caption buttons ourselves; now they look great on all versions of Windows! (#13341) (thanks!)

    Bug Fixes

    Interaction

    • Terminal will now use the tab's active title for Export Text (#13915) (thanks @serd2011!)
    • The Emoji picker, PinYin IME or any other IME will no longer drift off the bottom of the screen (oops) (#13785)

    Accessibility

    • The Command Palette has become much chattier, announcing (to a screen reader) the name of the selected item (#13519)
    • Asking for INT_MAX characters via UIA will no longer wig us out or try to send you multiple gigabytes of null bytes (#13779)
      • However, it remains impolite to ask for INT_MAX characters via ITextPattern::GetText.

    Performance

    • Terminal is now 1.2 megabytes smaller on disk (uncompressed) thanks to not using RTTI (#13947) (thanks RTTI!)

    Reliability

    • Fixed a number of crashes (smaller number than that in Preview), not all of which were common or user-impacting:
      • Attempted a fix for the SignalTextChanged crash (#13876)
      • Attempted another fix, this time for the _refreshSizeUnderLock crash (#13857)
      • Fixed a crash in _WritePseudoWindowCallback (#13777)
      • Fixed a crash on exit with the command palette open (#13778)
      • Fixed a race condition in UpdatePatternLocations (#13859)
      • Fixed two race conditions around pseudo window visibility (#13832)
      • Fixed a crash in NVDA, caused by us considering a specific text range invalid (#13907)
    • Terminal should now more reliably appear in the context menu

    With additional thanks to our documentation and code health contributors @jsoref and @LitoMore.

    Source code(tar.gz)
    Source code(zip)
    Microsoft.WindowsTerminal_Win10_1.15.2524.0_8wekyb3d8bbwe.msixbundle(36.75 MB)
    Microsoft.WindowsTerminal_Win10_1.15.2524.0_8wekyb3d8bbwe.msixbundle_Windows10_PreinstallKit.zip(65.27 MB)
    Microsoft.WindowsTerminal_Win11_1.15.2525.0_8wekyb3d8bbwe.msixbundle(17.41 MB)
    Microsoft.WindowsTerminal_Win11_1.15.2525.0_8wekyb3d8bbwe.msixbundle_Windows10_PreinstallKit.zip(64.48 MB)
  • v1.15.2282.0(Aug 17, 2022)

    This is another servicing release for the Preview channel of Windows Terminal! We fixed that Alt+Tab issue!

    Note People in the Beta channel of the Windows Insider program will receive 1.15 as a Stable channel update while we test out coming features for the next version of Windows. It is roughly equivalent to the build included here, but it does not include the experimental text rendering engine.

    It contains the following other things as well:

    Bug Fixes

    Usability

    • We've restored the ability for Alt+Tab to restore the Terminal after it was minimized with the taskbar icon (#13624)
    • Terminal will no longer replace colored backgrounds with blank spaces on first launch (#13665)
    • We will once again display underlines, hyperlinks, and more to the end of the line instead of getting tired and stopping early (#13661)
    • Sessions handed off from the Windows Console will no longer stick around with an ominous and annoying "process exited with code ..." message, unless you explicitly configure them to.
      • To accomplish this, we've changed the default value of closeOnExit to a new value, automatic. Automatic close-on-exit determines whether to close based on whether the process exited gracefully and whether the process was spawned by Terminal. (#13560) (#13649)
    • Select All and Mark Mode will now trigger scrolling to make sure that one of the selection endpoints is visible. (#13660)
    • SendInput with high unicode characters will no longer fail (#13667)
    • Text input in Japanese, Vietnamese, Korean and Chinese should be more reasonably switch between alphanumeric modes (#13678) (#13677)

    Reliability

    • We've upgraded to XAML 2.7.3 to fix a crash in closing the Settings page (#13761)
    • The "Open Terminal Here" context menu item should show up more reliably (and crash less) (reverted PR #13206)
    • We've solved--or at least, reduced the incidence of--one source of deadlocks in rendering (#13758)
    • We'll try much harder to defibrillate a Terminal session that can't talk to the "primary" Terminal session to improve reliability (#13604)
    • We will now listen to signals the OS sends us telling us that it's taking us down for an update. It's not going to help us stop it form happening, but it puts us in a better position to handle it later (#13614)

    Performance

    • We're preparing to fix an issue with jump list generation that results in a slower-than-expected launch (but we aren't there yet) (#13688)
    • There is now only one tab color picker in the world, and all ~~users~~ terminal tabs now have to share it (to improve performance) (#13736
    Source code(tar.gz)
    Source code(zip)
    Microsoft.WindowsTerminalPreview_Win10_1.15.2282.0_8wekyb3d8bbwe.msixbundle(37.61 MB)
    Microsoft.WindowsTerminalPreview_Win11_1.15.2283.0_8wekyb3d8bbwe.msixbundle(18.28 MB)
  • v1.14.2281.0(Aug 17, 2022)

    This servicing release of Windows Terminal v1.14 originally became available in the Release Preview channel on August 17th

    Preinstallation Kit info

    A preinstallation kit is available for system integrators and OEMs interested in prepackaging Windows Terminal with a Windows image. More information is available in the DISM documentation on preinstallation. Users who do not intend to preinstall Windows Terminal should continue using the msixbundle distribution.

    Why are there so many packages? How do I choose? This version of Windows Terminal is distributed in two bundles, one of which works on Windows 10-11 and the other of which only works on Windows 11. The Windows 11 version is much smaller because we no longer need to work around a platform issue related to our dependencies.

    If you intend on using Terminal as an unpackaged application--that is, extracting the msix file--we recommend that you use the Win10 bundle. You will need the Visual C++ runtime redistributable.

    In addition, if you install the packaged version on either Windows 10 or Windows 11, it now depends on the Visual C++ Universal Runtime Package.

    Despite these distributions having different version numbers, they are built from the same code and there is no functional difference between them.

    If you install the Windows 10 verison on Windows 11, it will probably automatically upgrade itself to the Windows 11 version. It turns out that it is impossible to have two bundles with the same version number, so it has to be this way.

    It contains the following fixes:

    • We've upgraded to XAML 2.7.3 to fix a crash in closing the Settings page (#13761)
    • The "Open Terminal Here" context menu item should show up more reliably (and crash less) (reverted PR #13206)
    • We've solved--or at least, reduced the incidence of--one source of deadlocks in rendering (#13758)
    • Terminal will no longer replace colored backgrounds with blank spaces on first launch (#13665)
    • We will once again display underlines, hyperlinks, and more to the end of the line instead of getting tired and stopping early (#13661)
    • SendInput with high unicode characters will no longer fail (#13667)
    • We've restored the ability for Alt+Tab to restore the Terminal after it was minimized with the taskbar icon (#13624)
    Source code(tar.gz)
    Source code(zip)
    Microsoft.WindowsTerminal_Win10_1.14.2281.0_8wekyb3d8bbwe.msixbundle(37.01 MB)
    Microsoft.WindowsTerminal_Win10_1.14.2281.0_8wekyb3d8bbwe.msixbundle_Windows10_PreinstallKit.zip(65.53 MB)
    Microsoft.WindowsTerminal_Win11_1.14.2282.0_8wekyb3d8bbwe.msixbundle(17.66 MB)
    Microsoft.WindowsTerminal_Win11_1.14.2282.0_8wekyb3d8bbwe.msixbundle_Windows10_PreinstallKit.zip(64.72 MB)
  • v1.15.2002.0(Aug 5, 2022)

    This is a servicing release for the Preview channel of Windows Terminal.

    Note People in the Beta channel of the Windows Insider program will receive 1.15 as a Stable channel update while we test out coming features for the next version of Windows. It is roughly equivalent to the build included here, but it does not include the experimental text rendering engine.

    Warning There is a known issue in this release of Windows Terminal that may result in difficulty restoring the Terminal window from a minimized state.

    • Windows Terminal no longer depends on a sidecar package of MIDI instrument voices to play "In the Hall of the Mountain King" when an application requests it (that is: DECPS support now relies on DirectSound!) (#13471)
    • Enabling "read-only" mode for a pane will no longer result in a read only dialog appearing every time you focus, un-focus, move, highlight, or otherwise interact with the terminal inside it. Sorry about that! (#13483)
    • We will no longer reserve space for the scroll bar marks when there is no scroll bar (#13454)
    • doskey aliases can now be bypassed by inserting a space before them, as has apparently been documented since 1651 (#13476)
    • We've enabled word wrapping on more of the tooltips in the application (#13463)
    • The "Quake :tm: mode" window will no longer launch in full screen when the full screen launch mode is selected (#13473)
    • The "debug tap" now includes line breaks to make it easier to read (#13475)
    Source code(tar.gz)
    Source code(zip)
    Microsoft.WindowsTerminalPreview_Win10_1.15.2002.0_8wekyb3d8bbwe.msixbundle(37.60 MB)
    Microsoft.WindowsTerminalPreview_Win11_1.15.2003.0_8wekyb3d8bbwe.msixbundle(18.27 MB)
  • v1.14.1962.0(Aug 5, 2022)

    This servicing release of Windows Terminal v1.14 originally became available in the GA channel on July 19th.

    Warning There is a known issue in this release of Windows Terminal that may result in difficulty restoring the Terminal window from a minimized state.

    Preinstallation Kit info

    A preinstallation kit is available for system integrators and OEMs interested in prepackaging Windows Terminal with a Windows image. More information is available in the DISM documentation on preinstallation. Users who do not intend to preinstall Windows Terminal should continue using the msixbundle distribution.

    Why are there so many packages? How do I choose? This version of Windows Terminal is distributed in two bundles, one of which works on Windows 10-11 and the other of which only works on Windows 11. The Windows 11 version is much smaller because we no longer need to work around a platform issue related to our dependencies.

    If you intend on using Terminal as an unpackaged application--that is, extracting the msix file--we recommend that you use the Win10 bundle. You will need the Visual C++ runtime redistributable.

    In addition, if you install the packaged version on either Windows 10 or Windows 11, it now depends on the Visual C++ Universal Runtime Package.

    Despite these distributions having different version numbers, they are built from the same code and there is no functional difference between them.

    If you install the Windows 10 verison on Windows 11, it will probably automatically upgrade itself to the Windows 11 version. It turns out that it is impossible to have two bundles with the same version number, so it has to be this way.

    It contains the following fixes:

    • Enabling "read-only" mode for a pane will no longer result in a read only dialog appearing every time you focus, un-focus, move, highlight, or otherwise interact with the terminal inside it. Sorry about that! (#13483)
    • We've enabled word wrapping on more of the tooltips in the application (#13463)
    • The "Quake :tm: mode" window will no longer launch in full screen when the full screen launch mode is selected (#13473)
    • The "debug tap" now includes line breaks to make it easier to read (#13475)
    Source code(tar.gz)
    Source code(zip)
    Microsoft.WindowsTerminal_Win10_1.14.1962.0_8wekyb3d8bbwe.msixbundle(37.01 MB)
    Microsoft.WindowsTerminal_Win10_1.14.1962.0_8wekyb3d8bbwe.msixbundle_Windows10_PreinstallKit.zip(65.52 MB)
    Microsoft.WindowsTerminal_Win11_1.14.1963.0_8wekyb3d8bbwe.msixbundle(17.66 MB)
    Microsoft.WindowsTerminal_Win11_1.14.1963.0_8wekyb3d8bbwe.msixbundle_Windows10_PreinstallKit.zip(64.71 MB)
  • v1.15.1862.0(Jul 6, 2022)

    It's Summer in the US, which means that ~~it's really hot~~ there's a new Terminal preview release!

    Here's what's in it:

    Why are there so many packages? How do I choose? This version of Windows Terminal is distributed in two bundles, one of which works on Windows 10-11 and the other of which only works on Windows 11. The Windows 11 version is much smaller because we no longer need to work around a platform issue related to our dependencies.

    If you intend on using Terminal as an unpackaged application--that is, extracting the msix file--we recommend that you use the Win10 bundle. You will need the Visual C++ runtime redistributable.

    In addition, if you install the packaged version on either Windows 10 or Windows 11, it now depends on the Visual C++ Universal Runtime Package.

    Despite these distributions having different version numbers, they are built from the same code and there is no functional difference between them.

    If you install the Windows 10 version on Windows 11, it will probably automatically upgrade itself to the Windows 11 version. It turns out that it is impossible to have two bundles with the same version number, so it has to be this way.

    Features

    • Selecting text in the terminal just got better!
      • Use the markMode action to enter mark mode and create a selection at the cursor (#13053) (#13358)
        • This is bound to Ctrl+Shift+M by default. Be sure to try it out!
      • Selections made with the keyboard now display a selection marker UI (#10865)
      • Use the switchSelectionEndpoint action to switch which endpoint you are moving in a selection (#13370)
      • Use the toggleBlockSelection action to transform your existing selection into a block selection (#13219)
    • [Experimental] We now support scrollbar marks! (#12948) (#13163) (#13291) (#13414)
      • Use the addMark action to add a scrollbar mark
        • The color optional parameter can be used to specify a color
      • Use the scrollToMark action with a specified direction parameter to scroll between the marks
      • Use the clearMark action to remove a selected mark
      • Use the clearAllMarks action to remove all scrollbar marks
      • The experimental.autoMarkPrompts profile setting can be set to true to automatically mark each prompt
        • NOTE: This uses the FTCS_PROMPT sequence from FinalTerm, OSC 133 ; A, which we now support! (#13163)
      • The experimental.showMarksOnScrollbar profile setting can also be set to true to display the marks on your scrollbar
    • If you're new to Windows Terminal Preview, but already have Windows Terminal installed and customized, we now migrate your settings over (#12907) (thanks @huiyooumich!)
    • The tab's context menu now has "Find" as an option (#13055) (thanks @Predelnik!)

    Changes

    • "Open settings file" commands now explicitly mention "JSON" for easier searching (#13265)
    • Color schemes now support "purple" and "magenta" interchangeably in the JSON (#13261) (thanks @matthewd673!)
    • An accelerator key is now defined for the "Open in Terminal" shell extension (#13080) (thanks @ianjoneill!)
    • The settings UI's "Save" pane now aligns with the "Open JSON file" footer (#13282) (thanks @HO-COOH!)
    • The Default Terminal setting in settings UI now has a "Let Windows decide" option (#13160)
      • An occasional crash while opening the settings UI has been stomped out (same PR!)
    • The "Save" and "Discard changes" buttons were reordered in the settings UI to more closely follow the Windows UI guidelines (#13237)
    • @dansmor7 has refined how colored tabs look when they're out of focus or hovered (#13434) (thanks!)

    More Escape Sequences and expanded VT support

    Courtesy of @j4james:

    • Applications can now use DECCTR to alter the terminal's color scheme (#13139) (#13227)
    • The same applications can now use DECAC to assign a color to the default foreground and background colors, as well as change the tab background color (#13058)
    • Other applications can now use DECPS to play a basic sequence of musical notes (#13208)
      • This feature is preview-only until we can make sure the MIDI sound font is available everywhere Stable ships.

    Documentation

    • building.md and mouseInput.cpp got cleaned up a bit (#13333) (thanks @ofek and @oferze!)
    • We added a Gannt chart to the roadmap (#13234)

    On the back end...

    • @lhecker rewrote how we handle coordinates across the project, paving the way for a longer scrollback history and removing a bunch of sources of assertion failures; if you see anything weird that seems like a coordinate system issue, please file it! (#13025)

    Bug Fixes

    • We no longer suppress black background or gray foreground for PowerShell (#13352)
      • We have chosen to remove this workaround as newer versions of PowerShell's PSReadline component contain a fix for the issue.
      • This was a compatibility band-aid that was impacting the capabilities of great projects such as Oh My Posh.
      • ❗ If you see unexpected black backgrounds appearing behind text while typing a command in PowerShell, make sure your PSReadline version is up to date. You can update your version of PSReadline by running the command, Update-Module PSReadline.
    • The Default Terminal banner is now hidden if you opened a session via default terminal (#13344)
      • AKA: We won't nag you to set Terminal as your default if it's demonstrably the default ;P
    • [O is no longer output erroneously from focus events for clients of libuv like neovim (#13260)
    • AtlasEngine no longer secretly increases the font size of HTML/RTF copies when the font changes (#13384)
    • Keyboard selection is now limited to the scrollable area (#13318)
    • The "Open in Terminal" shell extension is now hidden when accessing a non-filesystem path like "Quick Actions" (#13206) (thanks @leejy12!)
    • Clearing the screen via cls or Clear-Host won't leave behind an erroneous line of text (#13324) (thanks @j4james!)
    • Default Terminal sessions now properly pass focus events when opened (#13247)
    • Terminal will now use Unicode 14.0 to determine the width of some Unicode characters (#13292)
    • We will no longer try to launch wsl to ask it to tell us about distributions when it's obvious that you don't have any (#13436)
    • We've fixed a minor race condition in default terminal handoff that impacted nobody (#13410)

    Reliability

    • We no longer crash when a screen reader is reading from a CLI app using the alt buffer (#13250) (#13244)
    • Deleting the last profile in the settings UI no longer causes a crash (#13242)
    • Opening Windows Terminal via the Win+X menu no longer occasionally crashes (#13212)
    • SetConsoleWindowInfo can no longer crash a terminal tab (#13212)
    Source code(tar.gz)
    Source code(zip)
    Microsoft.WindowsTerminalPreview_Win10_1.15.1862.0_8wekyb3d8bbwe.msixbundle(37.60 MB)
    Microsoft.WindowsTerminalPreview_Win11_1.15.1863.0_8wekyb3d8bbwe.msixbundle(18.27 MB)
  • v1.14.1861.0(Jul 6, 2022)

    This release brings a whole bunch of the preview changes in Windows Terminal 1.14 to the Stable channel. Notably:

    • Terminal now has better support for xterm's "Alternate Screen Buffer"
    • Console application windowing will now work more consistently within Terminal: when an application requests that it be hidden or minimized, we will minimize the associated terminal window.
    • Terminal can now pass xterm focus events on to connected client applications
    • We've added a new experimental setting, experimental.useBackgroundImageForWindow, that lets you use one image as the background for any number of panes (thanks @nico-abram!)
    • You can now change the bell sound with the profile.bellSound setting

    Note that the new text rendering engine is not included in this Stable build.

    IMPORTANT This version was made available to the Dev External flighting ring (Windows Insiders) first, and will be released to general availability one or two weeks later depending on its reliability.

    Please see the following release notes for additional details:

    As a reminder, Terminal 1.12 was the last version of Windows Terminal that supports Windows 19H1 or 19H2. That version of windows is going out of support soon, so you may want to consider upgrading.

    Preinstallation Kit info

    A preinstallation kit is available for system integrators and OEMs interested in prepackaging Windows Terminal with a Windows image. More information is available in the DISM documentation on preinstallation. Users who do not intend to preinstall Windows Terminal should continue using the msixbundle distribution.

    Why are there so many packages? How do I choose? This version of Windows Terminal is distributed in two bundles, one of which works on Windows 10-11 and the other of which only works on Windows 11. The Windows 11 version is much smaller because we no longer need to work around a platform issue related to our dependencies.

    If you intend on using Terminal as an unpackaged application--that is, extracting the msix file--we recommend that you use the Win10 bundle. You will need the Visual C++ runtime redistributable.

    In addition, if you install the packaged version on either Windows 10 or Windows 11, it now depends on the Visual C++ Universal Runtime Package.

    Despite these distributions having different version numbers, they are built from the same code and there is no functional difference between them.

    If you install the Windows 10 verison on Windows 11, it will probably automatically upgrade itself to the Windows 11 version. It turns out that it is impossible to have two bundles with the same version number, so it has to be this way.

    Also included in this release are some bug fixes and changes backported from 1.15:

    Bug Fixes and Changes

    • Keyboard selection now works better with copyOnSelect (#13360)
    • Keyboard selection is now limited to the scrollable area (#13353) (#13372)
    • "Open settings file" commands now explicitly mention "JSON" for easier searching (#13265)
    • An accelerator key is now defined for the "Open in Terminal" shell extension (#13080) (thanks @ianjoneill!)
    • We no longer crash when using the Default Terminal setting in the settings UI (#13160)
    • The Default Terminal banner is now hidden if you opened a session via default terminal (#13344)
    • [O is no longer output erroneously from focus events for clients of libuv like neovim (#13260)
    • We no longer crash when a screen reader is reading from a CLI app using the alt buffer (#13250)
    • Deleting the last profile in the settings UI no longer causes a crash (#13242)
    • Opening Windows Terminal via the Win+X menu no longer occasionally crashes (#13212)
    • The "Open in Terminal" shell extension is now hidden when accessing a non-filesystem path like "Quick Actions" (#13206) (thanks @leejy12!)
    • Clearing the screen via cls or Clear-Host won't leave behind an erroneous line of text (#13324) (thanks @j4james!)
    • Default Terminal sessions now properly pass focus events when opened (#13247)
    • Terminal will now use Unicode 14.0 to determine the width of some Unicode characters (#13292)
    • We will no longer try to launch wsl to ask it to tell us about distributions when it's obvious that you don't have any (#13436)
    • We've fixed a minor race condition in default terminal handoff that impacted nobody (#13410)
    • The tab's context menu now has "Find" as an option (#13055) (thanks @Predelnik!)
    • SetConsoleWindowInfo can no longer crash a terminal tab (#13212)
    • An occasional crash while opening the settings UI has been stomped out (#13160)
    Source code(tar.gz)
    Source code(zip)
    Microsoft.WindowsTerminal_Win10_1.14.1861.0_8wekyb3d8bbwe.msixbundle(37.01 MB)
    Microsoft.WindowsTerminal_Win10_1.14.1861.0_8wekyb3d8bbwe.msixbundle_Windows10_PreinstallKit.zip(65.52 MB)
    Microsoft.WindowsTerminal_Win11_1.14.1862.0_8wekyb3d8bbwe.msixbundle(17.66 MB)
    Microsoft.WindowsTerminal_Win11_1.14.1862.0_8wekyb3d8bbwe.msixbundle_Windows10_PreinstallKit.zip(64.71 MB)
  • v1.14.1451.0(Jun 10, 2022)

    This release of Windows Terminal Preview, 1.14.145, was made generally available on the 26th of May, 2022.

    It contains the following fixes, which are almost exclusively for bugs that we recalled 1.14.143 over!

    As with prior releases, you need to install Microsoft.VCLibs.UWPDesktop.140.00 or make sure it is installed prior to installing Terminal. If you are using Terminal unpackaged, you will need to make sure you have the systemwide "Microsoft Visual C++ Redistributable" installed, and choose the Win10 version of our msixbundle. Yeah, it's strange!

    Bug Fixes

    • Opening a new tab or pane will no longer un-maximize, un-snap, or otherwise move Terminal around the screen (!) (#13164)
    • We will no longer crash when you try to split panes in the Settings tab (#13172)
    • We have changed the display language names for the different local variations of Chinese to not include location names (#13148)
    Source code(tar.gz)
    Source code(zip)
    Microsoft.WindowsTerminalPreview_Win10_1.14.1451.0_8wekyb3d8bbwe.msixbundle(37.68 MB)
    Microsoft.WindowsTerminalPreview_Win11_1.14.1452.0_8wekyb3d8bbwe.msixbundle(18.34 MB)
  • v1.14.1432.0(May 24, 2022)

    Welcome to the terminaldome! Today this release page is graced by the works of pinch hitter (and pinch release notes writer) @carlos-zamora.

    Why are there so many packages? How do I choose? This version of Windows Terminal is distributed in two bundles, one of which works on Windows 10-11 and the other of which only works on Windows 11. The Windows 11 version is much smaller because we no longer need to work around a platform issue related to our dependencies.

    If you intend on using Terminal as an unpackaged application--that is, extracting the msix file--we recommend that you use the Win10 bundle. You will need the Visual C++ runtime redistributable.

    In addition, if you install the packaged version on either Windows 10 or Windows 11, it now depends on the Visual C++ Universal Runtime Package.

    Despite these distributions having different version numbers, they are built from the same code and there is no functional difference between them.

    If you install the Windows 10 verison on Windows 11, it will probably automatically upgrade itself to the Windows 11 version. It turns out that it is impossible to have two bundles with the same version number, so it has to be this way.

    Features

    • Windows Terminal now has better support for the xterm "Alternate Screen Buffer", and can now handle alternate scroll mode and resize/reflow better (#12561) (#12569) (#12719)
    • Using windowed applications from the terminal should work much better now
      • ConPTY can now handle show/hide window calls and even knows who the window owner is (#12515) (#12526)
      • Windows created by console apps now appear above the terminal (#12799) (#12899)
      • Focus events are now sent through VT input (#12900)
    • You can now use the experimental.useBackgroundImageForWindow (bool, default false) global setting to apply one background image for your entire window! (#12893) (#13114) (thanks @nico-abram!)
    • You are now able to select all the text in the buffer using the selectAll action. This is bound by default to ctrl+shift+a (#13045) (#13084)

    Changes

    UI

    • @dansmor7 contributed some visual changes to the tabs, scrollbar, new tab button, caption buttons, color picker, settings UI, command palette, and search box to move us closer to the Windows 11 design language. Really just about any WinUI surface we have, it's been polished up! (thanks @dansmor7!) (#12913) (#12916) (#12973) (#13083)
    • RadioButtons in the settings UI have been replaced with ComboBoxes. This gives an added bonus to keyboard and screen reader users, and makes it easier to navigate through and change these settings. (#12833)

    Interactivity

    • The IME input mode now defaults to English when interacting with Windows Terminal (#13028) (thanks @YanceyChiew!)
    • Terminal is now aware of toggled state for Caps Lock, Scroll Lock, and Num Lock (#12823) (thanks @matkaas!)

    Settings

    • There's now a VERY EXPERIMENTAL new VT passthrough mode setting that makes ConPTY do minimal translations and may make your terminal a little faster 🏃💨 and a lot more broken! (#11264) (#13051) (#13109)
      • Use the experimental.connection.passthroughMode (bool, default true) profile setting and it should be set on the profile's next launch
      • ⚠️ WARNING ⚠️ This seems to mostly work with CMD and WSL. PowerShell is mostly sad 😭.
    • The trimBlockSelection global setting now defaults to true (#12737)
    • Terminal now ignores newTab actions with a profile index greater than the number of profiles (#11621)

    Atlas Renderer Improvements

    • ClearType is no longer always enabled (#12705)
    • The grayscale blending shader should now be working properly (#12734)
    • OpenConsole's leak check report should be fixed now (#12415)
    • The shader power draw was reduced using explicit branching (#12552)
    • The renderer is now smarter about when to resize the buffer when scrolling (#13100)

    Documentation

    • Our GitHub repo now supports rich code navigation (#12855) (#12910) (#12910). Bug reports are also automatically tagged as bugs (#12404) (thanks @snxx-lppxx!)
    • We've uploaded specs for Theme-controlled color scheme switching (#12613) (thanks @arkthur!) and Default Terminal (#7414)
    • The README has been updated to mention the required .NET Targeting Pack (#12896) (thanks @pizzaz93!)
    • Words are hard! Thanks to @sebastiansterk, @DimitriPapadopoulos, and @jsoref for making sure we use the right words and grammar across our repo. (#12386) (#12475) (#12835)
    • bellSound is now in the schema (#13035) (thanks @pizzaz93!)

    Bug Fixes

    • Terminal should be able to find Cascadia Mono... Third time's the charm? 🍀 (#12904)
    • commandline in profile.defaults should no longer override the commandlines of profiles that specify cmd.exe or powershell.exe. (#12906)
    • Get rid of a memory leak in onecore interactivity (#12340)
    • We should be maintaining the virtual viewport bottom properly now (#12972) (#13052) (#13087) (thanks @j4james!)
    • Screen readers can now read some settings in the UI better (#13032)
    • Replace "acrylic" with "acrylic material" for localization purposes (#12505)
    • The "close tab" button color now matches the tab text color (#13018) (thanks @ianjoneill!)

    Reliability

    • Fix a crash when deleting the last profile in the settings UI (#13044)
    • Fix resize crash in OpenConsole when using the Atlas Renderer (#13015)

    Code health and Maintainability

    • @j4james unified the terminal and console's VT handlers, deleting thousands of lines of redundant code in the process! (#12207) (#12247) (#12389) (#12390) (#12568) (#12703) (#13024) (#13039) (thanks @j4james!)
    • Added some missing breaks to cases in IslandWindow (#12926) (thanks @jmelas!)
    • Added the MIT license for a few files that were missing it (#12368) (thanks @jerry-shao!)
    • Replaced sizeof with ARRAYSIZE in SystemConfigurationProvider (#12273) (thanks @abdoulkkonate!)
    • Use type inference throughout the project (#12975)
    • Use memcmp for TextAttribute & TextColor comparison (#10566) (thanks @skyline75489!)
    • Thanks to @ianjoneill, @achermack, @YanceyChiew, @EmJayGee, @dmachaj, and @j4james for performing a ton of build system, code health and maintainability improvements!
    Source code(tar.gz)
    Source code(zip)
    Microsoft.WindowsTerminalPreview_Win10_1.14.1432.0_8wekyb3d8bbwe.msixbundle(37.68 MB)
    Microsoft.WindowsTerminalPreview_Win11_1.14.1433.0_8wekyb3d8bbwe.msixbundle(18.34 MB)
  • v1.13.11431.0(May 24, 2022)

    This release brings many of the preview changes in Windows Terminal 1.13 to the Stable channel. Notably:

    IMPORTANT This version was made available to the Dev External flighting ring (Windows Insiders) first, and will be released to general availability one or two weeks later depending on its reliability.

    • You can now configure a profile to automatically launch as Administrator.
    • There is a new action, "Restore last closed pane or tab," that will do roughly what it says on the tin.
    • You can now change the bell sound with the profile.bellSound setting
    • Terminal has learned to save and restore your last opened window, position and all! Check it out in Settings > Startup.

    Note that the new text rendering engine is not included in this Stable build.

    Please see the following release notes for additional details:

    As a reminder, Terminal 1.12 is the last version of Windows Terminal that supports Windows 19H1 or 19H2. That version of windows is going out of support soon, so you may want to consider upgrading.

    Preinstallation Kit info

    A preinstallation kit is available for system integrators and OEMs interested in prepackaging Windows Terminal with a Windows image. More information is available in the DISM documentation on preinstallation. Users who do not intend to preinstall Windows Terminal should continue using the msixbundle distribution.

    Why are there so many packages? How do I choose? This version of Windows Terminal is distributed in two bundles, one of which works on Windows 10-11 and the other of which only works on Windows 11. The Windows 11 version is much smaller because we no longer need to work around a platform issue related to our dependencies.

    If you intend on using Terminal as an unpackaged application--that is, extracting the msix file--we recommend that you use the Win10 bundle. You will need the Visual C++ runtime redistributable.

    In addition, if you install the packaged version on either Windows 10 or Windows 11, it now depends on the Visual C++ Universal Runtime Package.

    Despite these distributions having different version numbers, they are built from the same code and there is no functional difference between them.

    If you install the Windows 10 verison on Windows 11, it will probably automatically upgrade itself to the Windows 11 version. It turns out that it is impossible to have two bundles with the same version number, so it has to be this way.

    Also included in this release are some bug fixes and changed backported from 1.14:

    Changes

    UI

    • @dansmor7 contributed some visual changes to the tabs, scrollbar, new tab button, caption buttons, color picker, settings UI, command palette, and search box to move us closer to the Windows 11 design language. Really just about any WinUI surface we have, it's been polished up! (thanks @dansmor7!) (#12913) (#12916) (#12973) (#13083)
    • RadioButtons in the settings UI have been replaced with ComboBoxes. This gives an added bonus to keyboard and screen reader users, and makes it easier to navigate through and change these settings. (#12833)

    Interactivity

    • Terminal is now aware of toggled state for Caps Lock, Scroll Lock, and Num Lock (#12823) (thanks @matkaas!)

    Settings

    • The trimBlockSelection global setting now defaults to true (#12737)
    • Terminal now ignores newTab actions with a profile index greater than the number of profiles (#11621)
    • bellSound is now in the schema (#13035) (thanks @pizzaz93!)

    Bug Fixes

    • Terminal should be able to find Cascadia Mono... Third time's the charm? 🍀 (#12904)
    • commandline in profile.defaults should no longer override the commandlines of profiles that specify cmd.exe or powershell.exe. (#12906)
    • Get rid of a memory leak in onecore interactivity (#12340)
    • Screen readers can now read some settings in the UI better (#13032)
    • Replace "acrylic" with "acrylic material" for localization purposes (#12505)
    • The "close tab" button color now matches the tab text color (#13018) (thanks @ianjoneill!)

    Reliability

    • Fix a crash when deleting the last profile in the settings UI (#13044)
    Source code(tar.gz)
    Source code(zip)
    Microsoft.WindowsTerminal_Win10_1.13.11431.0_8wekyb3d8bbwe.msixbundle(37.06 MB)
    Microsoft.WindowsTerminal_Win10_1.13.11431.0_8wekyb3d8bbwe.msixbundle_Windows10_PreinstallKit.zip(65.57 MB)
    Microsoft.WindowsTerminal_Win11_1.13.11432.0_8wekyb3d8bbwe.msixbundle(17.73 MB)
    Microsoft.WindowsTerminal_Win11_1.13.11432.0_8wekyb3d8bbwe.msixbundle_Windows10_PreinstallKit.zip(64.77 MB)
  • v1.13.10983.0(Apr 19, 2022)

    This is an update to fix a number of issues identified in 1.13.1073x.

    Why are there so many packages? How do I choose? This version of Windows Terminal is distributed in two bundles, one of which works on Windows 10-11 and the other of which only works on Windows 11. The Windows 11 version is much smaller because we no longer need to work around a platform issue related to our dependencies.

    If you intend on using Terminal as an unpackaged application--that is, extracting the msix file--we recommend that you use the Win10 bundle. You will need the Visual C++ runtime redistributable.

    In addition, if you install the packaged version on either Windows 10 or Windows 11, it now depends on the Visual C++ Universal Runtime Package.

    Despite these distributions having different version numbers, they are built from the same code and there is no functional difference between them.

    If you install the Windows 10 verison on Windows 11, it will probably automatically upgrade itself to the Windows 11 version. It turns out that it is impossible to have two bundles with the same version number, so it has to be this way.

    Since 1.12 is the final release that supports Windows 19H1, we're including a final update to 1.12 on the preview channel, just so that the four of you stuck on that version get the latest fixes. 😄 Install that manually at your own peril.

    Bug Fixes

    Appearance

    • Our Maximize/Restore button is now a fine round boi (#12660)

    Accessibility

    • The profile list in the Settings UI now offers tooltips for long profile names (#12448)
    • We'll automatically focus the window renamer textbox when it opens (#12798)
    • High contrast will no longer result in a ridiculous and bad titlebar color (#12839)
    • When you delete a color scheme, we'll move focus back to the color scheme list (#12841)
    • Two instances of huge debug log spam with a screen reader connected have been stamped out (#12698) (#12723)

    Usability

    • We've added some text to the color schemes page indicating that it is for editing--not setting--color schemes (#12663)
      • We're working to refine how color schemes are set and edited, so stay tuned for future improvements!
    • The retro terminal effect (as well as other shaders) will now work on pre-D3D11 hardware! (#12677)
    • Terminal will once again render properly when you move between different-DPI displays (#12713) (#12749)
    • Resizing the window while a background color or underline is displayed will no longer smear it across the whole screen (#12637) plus a fix for a huge crash that PR introduced (#12853)
    • It took us three releases to get it right, but we've finally solved the issue where we'd punch a hole straight through the Terminal when a dialog appeared (#12840)

    Reliability

    • There was an issue on Windows 11 where Terminal would queue up billions of animations while the screen was off; it will now no longer do so (#12820)
    • We've fixed crashes in ProposeCommandline (#12838), Monarch::_GetPID (#12856) and other parts of WT's RPC infrastructure (#12825)
    • On Windows 10, the settings UI will no longer sometimes crash on close (we've updated to a new build of WinUI 2 for the fix!) (#12847)

    Miscellaneous

    • Windows will no longer reject certain Terminal updates/reinstalls due to "differing package content" (#12779)
    • Fragments can once again override the names of generated profiles (#12627)
    • An issue from the 1073 series, where you could not upgrade the bundle using DISM, has been resolved (#12819)
      • As a result, our bundle version is now over three thousand!
    • @dmezh contributed some wording changes to the text about transparency/opacity (#12592) (#12727) (thanks!)
    • Some trailing commas that broke the JSON Schema document are no longer trailing, or present at all (#12644) (thanks @sowmya-hub!)
    Source code(tar.gz)
    Source code(zip)
    Microsoft.WindowsTerminalPreview_Old_Win10_1.12.10984.0_8wekyb3d8bbwe.msixbundle(37.27 MB)
    Microsoft.WindowsTerminalPreview_Win10_1.13.10983.0_8wekyb3d8bbwe.msixbundle(37.57 MB)
    Microsoft.WindowsTerminalPreview_Win11_1.13.10984.0_8wekyb3d8bbwe.msixbundle(18.23 MB)
  • v1.12.10982.0(Apr 19, 2022)

    This release was made available to insiders in the Dev and Beta channels on April 11 and is now generally available.

    Preinstallation Kit info

    A preinstallation kit is available for system integrators and OEMs interested in prepackaging Windows Terminal with a Windows image. More information is available in the DISM documentation on preinstallation. Users who do not intend to preinstall Windows Terminal should continue using the msixbundle distribution.

    Why are there so many packages? How do I choose? This version of Windows Terminal is distributed in two bundles, one of which works on Windows 10-11 and the other of which only works on Windows 11. The Windows 11 version is much smaller because we no longer need to work around a platform issue related to our dependencies.

    If you intend on using Terminal as an unpackaged application--that is, extracting the msix file--we recommend that you use the Win10 bundle. You will need the Visual C++ runtime redistributable.

    In addition, if you install the packaged version on either Windows 10 or Windows 11, it now depends on the Visual C++ Universal Runtime Package.

    Despite these distributions having different version numbers, they are built from the same code and there is no functional difference between them.

    If you install the Windows 10 verison on Windows 11, it will probably automatically upgrade itself to the Windows 11 version. It turns out that it is impossible to have two bundles with the same version number, so it has to be this way.

    Changes

    • The refreshed Windows 11 UI from the 1.13 preview builds is now available in 1.12!

    Bug Fixes

    Appearance

    • Our Maximize/Restore button is now a fine round boi (#12660)

    Accessibility

    • The profile list in the Settings UI now offers tooltips for long profile names (#12448)
    • We'll automatically focus the window renamer textbox when it opens (#12798)
    • High contrast will no longer result in a ridiculous and bad titlebar color (#12839)
    • When you delete a color scheme, we'll move focus back to the color scheme list (#12841)
    • When you delete a profile, we will re-focus the delete button automatically (#12558)
    • Two instances of huge debug log spam with a screen reader connected have been stamped out (#12698) (#12723)

    Usability

    • We've added some text to the color schemes page indicating that it is for editing--not setting--color schemes (#12663)
      • We're working to refine how color schemes are set and edited, so stay tuned for future improvements!
    • The retro terminal effect (as well as other shaders) will now work on pre-D3D11 hardware! (#12677)
    • Terminal will once again render properly when you move between different-DPI displays (#12713) (#12749)
    • Resizing the window while a background color or underline is displayed will no longer smear it across the whole screen (#12637) plus a fix for a huge crash that PR introduced (#12853)
    • It took us three releases to get it right, but we've finally solved the issue where we'd punch a hole straight through the Terminal when a dialog appeared (#12840)

    Reliability

    • Typing an invalid background image path into the Settings UI will no longer send Terminal to a farm upstate (#11542) (thanks @serd2011!)
    • There was an issue on Windows 11 where Terminal would queue up billions of animations while the screen was off; it will now no longer do so (#12820)
    • We've fixed crashes in ProposeCommandline (#12838), Monarch::_GetPID (#12856) and other parts of WT's RPC infrastructure (#12825)
    • On Windows 10, the settings UI will no longer sometimes crash on close (we've updated to a new build of WinUI 2 for the fix!) (#12847)

    Miscellaneous

    • Windows will no longer reject certain Terminal updates/reinstalls due to "differing package content" (#12779)
    • Fragments can once again override the names of generated profiles (#12627)
    • An issue from the 1073 series, where you could not upgrade the bundle using DISM, has been resolved (#12819)
      • As a result, our bundle version is now over three thousand!
    • @dmezh contributed some wording changes to the text about transparency/opacity (#12592) (#12727) (thanks!)
    Source code(tar.gz)
    Source code(zip)
    Microsoft.WindowsTerminal_Win10_1.12.10982.0_8wekyb3d8bbwe.msixbundle(36.89 MB)
    Microsoft.WindowsTerminal_Win10_1.12.10982.0_8wekyb3d8bbwe.msixbundle_Windows10_PreinstallKit.zip(65.40 MB)
    Microsoft.WindowsTerminal_Win11_1.12.10983.0_8wekyb3d8bbwe.msixbundle(17.56 MB)
    Microsoft.WindowsTerminal_Win11_1.12.10983.0_8wekyb3d8bbwe.msixbundle_Windows10_PreinstallKit.zip(64.60 MB)
  • v1.13.10733.0(Mar 25, 2022)

    This is a servicing release to fix a number of big issues in 1.13 preview.

    Changes

    This version of Windows Terminal is now distributed in two bundles, one of which works on Windows 10-11 and the other of which only works on Windows 11. The Windows 11 version is much smaller because we no longer need to work around a platform issue related to our dependencies.

    If you intend on using Terminal as an unpackaged application--that is, extracting the msix file--we recommend that you use the Win10 bundle. You will need the Visual C++ runtime redistributable.

    In addition, if you install the packaged version on either Windows 10 or Windows 11, it now depends on the Visual C++ Universal Runtime Package.

    Despite these distributions having different version numbers, they are built from the same code and there is no functional difference between them.

    If you install the Windows 10 verison on Windows 11, it will probably automatically upgrade itself to the Windows 11 version. It turns out that it is impossible to have two bundles with the same version number, so it has to be this way.

    Bug Fixes

    Usability

    • Terminal can once again be configured as a startup application, and can be detected by tools like PowerToys (#12491)
    • We are once again usable on N (non-media) SKUs of Windows (#12463)
    • There was a puzzling "Element not found" error during settings loading; there is no longer such an error (#12687)
    • Terminal will no longer mix up profiles when it is launched in response to a console application spawning (#12484)
    • Formatted copy will now try harder to preserve Unicode charatcers in RTF (#12586) (thanks @ianjoneill!)
    • Displaying multiple dialogs will no longer punch a giant hole in the Terminal (???) (#12625) (#12517)
    • You spoke up about the scroll bars being WAY TOO THIN, so we chonked them up (#12608)
    • We have replaced the word "Summon" with "Show/Hide" in the command palette for improved localization (#12603)
    • Our confidence in the settings UI's Save button has led to us no longer backing up the settings JSON file (#12652)
      • We won't be deleting the 61,000 backups we did leave on your hard drive, but what's a couple thousand kilobytes between friends?

    Appearance

    • We've improved the contrast of the tab strip (#12635) (#12529)
    • Our iconography has been updated to the Windows 11 style (#12469)
    • We have given the issue where acrylic in the titlebar looked weird the heave-ho (#12460)
    • Good good new UI fonts have been enabled (Segoe UI Variable) (#12462)

    Accessibility

    • Terminal now announces newly-printed text to any attached screen reader (#12358)
    • When you delete a profile, we will re-focus the delete button automatically (#12558)
    • Command palette search now tries to announce the number of results to the screen reader (#12429)

    Reliability

    • We won't crash any longer if you give us a command line that is a directory (#12538) (thanks @ianjoneill!)
    • Fixed a crash setting the hotkey during teardown (#12580)
    • Fixed a different pair of crashes, also likely related to default terminal handoff (#12666)
    • ScrollConsoleScreenBuffer no longer takes the console upstate (#12669)
    • Pressing Page Up or Page Down with an empty command palette, which seemed like a reasonable thing to do, was taught to not crash the Terminal (#12528)

    Rendering

    • Font axes/features once again work across a DPI change (#12492)
    • AtlasEngine: Fix ConstBuffer invalidation for background color changes (#12667)
    • AtlasEngine: Fix inverted cursor alpha (#12548)
    • On Windows 10, you should see fewer "couldn't find Cascadia Mono, even though it is RIGHT NEXT TO US" dialogs (#12554)
    Source code(tar.gz)
    Source code(zip)
    Microsoft.WindowsTerminalPreview_Win10_1.13.10733.0_8wekyb3d8bbwe.msixbundle(37.73 MB)
    Microsoft.WindowsTerminalPreview_Win11_1.13.10734.0_8wekyb3d8bbwe.msixbundle(18.31 MB)
  • v1.12.10732.0(Mar 25, 2022)

    This is a significant servicing release to fix a number of huge issues in 1.12.

    This release was made available to insiders in the Dev and Beta channels on March 25, and will be generally available to everyone once it is considered stable. You can always install the update from this release page or using winget.

    Preinstallation Kit info

    A preinstallation kit is available for system integrators and OEMs interested in prepackaging Windows Terminal with a Windows image. More information is available in the DISM documentation on preinstallation. Users who do not intend to preinstall Windows Terminal should continue using the msixbundle distribution.

    Changes

    This version of Windows Terminal is now distributed in two bundles, one of which works on Windows 10-11 and the other of which only works on Windows 11. The Windows 11 version is much smaller because we no longer need to work around a platform issue related to our dependencies.

    If you intend on using Terminal as an unpackaged application--that is, extracting the msix file--we recommend that you use the Win10 bundle. You will need the Visual C++ runtime redistributable.

    In addition, if you install the packaged version on either Windows 10 or Windows 11, it now depends on the Visual C++ Universal Runtime Package.

    Despite these distributions having different version numbers, they are built from the same code and there is no functional difference between them.

    If you install the Windows 10 verison on Windows 11, it will probably automatically upgrade itself to the Windows 11 version. It turns out that it is impossible to have two bundles with the same version number, so it has to be this way.

    Bug Fixes

    Usability

    • Terminal can once again be configured as a startup application, and can be detected by tools like PowerToys (#12491)
    • There was a puzzling "Element not found" error during settings loading; there is no longer such an error (#12687)
    • Terminal will no longer mix up profiles when it is launched in response to a console application spawning (#12484)
    • Formatted copy will now try harder to preserve Unicode charatcers in RTF (#12586) (thanks @ianjoneill!)
    • We have replaced the word "Summon" with "Show/Hide" in the command palette for improved localization (#12603)
    • Our confidence in the settings UI's Save button has led to us no longer backing up the settings JSON file (#12652)
      • We won't be deleting the 61,000 backups we did leave on your hard drive, but what's a couple thousand kilobytes between friends?

    Accessibility

    • Terminal now announces newly-printed text to any attached screen reader (#12358)
    • Command palette search now tries to announce the number of results to the screen reader (#12429)

    Reliability

    • We won't crash any longer if you give us a command line that is a directory (#12538) (thanks @ianjoneill!)
    • A crash on launch related to multi-windowing and the default terminal setting has been quashed (subset of #12205)
    • Fixed a crash setting the hotkey during teardown (#12580)
    • Fixed a different pair of crashes, also likely related to default terminal handoff (#12666)
    • ScrollConsoleScreenBuffer no longer takes the console upstate (#12669)
    • Pressing Page Up or Page Down with an empty command palette, which seemed like a reasonable thing to do, was taught to not crash the Terminal (#12528)

    Rendering

    • Font axes/features once again work across a DPI change (#12492)
    Source code(tar.gz)
    Source code(zip)
    Microsoft.WindowsTerminal_Win10_1.12.10732.0_8wekyb3d8bbwe.msixbundle(36.91 MB)
    Microsoft.WindowsTerminal_Win10_1.12.10732.0_8wekyb3d8bbwe.msixbundle_Windows10_PreinstallKit.zip(65.41 MB)
    Microsoft.WindowsTerminal_Win11_1.12.10733.0_8wekyb3d8bbwe.msixbundle(17.50 MB)
    Microsoft.WindowsTerminal_Win11_1.12.10733.0_8wekyb3d8bbwe.msixbundle_Windows10_PreinstallKit.zip(64.54 MB)
  • v1.13.10395.0(Feb 11, 2022)

    This is a quick servicing release to fix a couple of big issues in the initial 1.12 stable drop.

    As with the previous 1.13 release, it is shipping alongside a 1.12 release for anybody who is stuck on 19H1, 19H2 or 19H3.

    Bug Fixes

    • Terminal is once again localized (#12375)
      • We encountered an issue in automatic language detection, which resulted in our package's languages being ignored.
    • "Default Terminal" profile matching now works better for profiles containing unquoted whitespace (#12348)
    • We believe we have fixed an unusual crash on launch in constructing the taskbar Jump List (#12430)
    • Symbols are now published to the public symbol server! Woot! (#12441)
    • We've fixed a crash that used to surface while Magnifier or other assistive technologies were running (#12436)
    • Ubuntu users with overridden commandlines will no longer see a confusing "~ could not be found" error (#12437)
    • Toggle switches in the settings UI now fit longer languages (like Polish) (#12381)
    • More of the settings UI is centered horizontally (#12374)
    • The breadcrumbs have been picked up and will no longer navigate you to strange cottages (#12376)
    • The color schemes page no longer has a strange focus rectangle (#12439)
    • vifm can no longer trigger a race condition in cursor visibility (#12434)
    • The reset arrow icon is no longer a strange box containing only "hope" (#12438)
    • OSC 9;9 with an empty path will no longer send Terminal to a farm upstate (#12432)
    • When Terminal is set as your default terminal, autoelevation will no longer cause all handoffs to crash (#12442)
    Source code(tar.gz)
    Source code(zip)
    Microsoft.WindowsTerminalPreview_1.12.10394.0_8wekyb3d8bbwe.msixbundle(39.43 MB)
    Microsoft.WindowsTerminalPreview_1.13.10395.0_8wekyb3d8bbwe.msixbundle(39.83 MB)
  • v1.12.10393.0(Feb 11, 2022)

    This is a quick servicing release to fix a couple of big issues in the initial 1.12 stable drop.

    This release was made available to insiders in the Dev and Beta channels on February 10, and will be generally available to everyone shortly afterwards. You can always install the update from this release page or using winget.

    Preinstallation Kit info

    A preinstallation kit is available for system integrators and OEMs interested in prepackaging Windows Terminal with a Windows image. More information is available in the DISM documentation on preinstallation. Users who do not intend to preinstall Windows Terminal should continue using the msixbundle distribution.

    Bug Fixes

    • Terminal is once again localized (#12375)
      • We encountered an issue in automatic language detection, which resulted in our package's languages being ignored.
    • "Default Terminal" profile matching now works better for profiles containing unquoted whitespace (#12348)
    • We believe we have fixed an unusual crash on launch in constructing the taskbar Jump List (#12430)
    • Symbols are now published to the public symbol server! Woot! (#12441)
    • We've fixed a crash that used to surface while Magnifier or other assistive technologies were running (#12436)
    • Ubuntu users with overridden commandlines will no longer see a confusing "~ could not be found" error (#12437)
    Source code(tar.gz)
    Source code(zip)
    Microsoft.WindowsTerminal_1.12.10393.0_8wekyb3d8bbwe.msixbundle(39.04 MB)
    Microsoft.WindowsTerminal_1.12.10393.0_8wekyb3d8bbwe.msixbundle_Windows10_PreinstallKit.zip(38.56 MB)
  • v1.13.10336.0(Feb 3, 2022)

    Happy New Year! It's Terminal time once again! This is our first release of 2022, and it's a big one.

    Announcements

    • Windows Terminal Preview is now named Terminal Preview! It will, of course, still be called wt under the hood. (#12264)
      • Right now, you will not be able to find Windows Terminal _ (that is, with the "Windows" part) in the start menu. We are working with the search team to add a keyword match! Follow #12344 for updates._
      • Sorry about your muscle memory. :(
    • 1.12 is the last version of Terminal that will support Windows 19H1 or 19H2 (#12129)
      • Folks who are on the Preview channel on these versions of Windows will get a one-time upgrade to the last servicing release of 1.12.
      • This version of windows is going out of support soon, so you may want to consider upgrading.
      • You only need to install 1.12.10335.0 if you are on Windows 19H1 or 19H2; it is included here for completeness.

    Features

    • Terminal now follows the Windows 11 UI guidelines (#12241) (#12144) (#12208) (#12287) (#12326) (#11720) (#12321)
      • This will make it look a little out of place on Windows 10; we're sorry
    • We're testing out a new experimental text rendering engine, "AtlasEngine" (#11623) (#12304) (#12225) (#12189) (#12307) (#12278) (#12242) (#12227) (#12226)
      • You can enable it with the experimental.useAtlasEngine profile field or the "Use experimental text rendering engine" in Profile -> Advanced
      • We're tracking bugs, parity with the existing renderer, and future advancements in #9999.
    • You can now configure a profile to always launch elevated (in a separate window)! (#12137) (#12257)
      • This is controlled by the profile setting elevate (bool, default false).
      • Read more in our docs.
    • Terminal learned to restore the last closed pane or tab! (#11471) (thanks @Rosefield!)
      • NOTE: This action, accessible through the command palette, will launch a new tab that has the same settings as the previous tab. It cannot bring ~protagonists~ processes back from the dead!
    • You can now change the bell sound with profile.bellSound setting! (#11511)
      • bellSound takes a path to an audio file to play as the audible bell or an array of paths.
      • If you provide an array of paths, Terminal will choose one at random every single time it bells.
      • If you're a fan of Untitled Goose Game, this is an excellent opportunity to get your HONK on!
    • Dropping a file on a WSL instance will now insert the WSL converted path (!) (#11625) (thanks @petrsnm!)
    • You now have the option to strip trailing whitespace on paste (trimPaste global setting, bool, default true) (#11473) (thanks @lovef!)

    Changes

    • We're reworking how Terminal handles environment variables, starting with reverting the changes we made in Preview that broke PowerShell x86 (#12140)
    • The "adjust lightness of indistinguishable text" feature, present in 1.12 preview, has been disabled pending some bug fixes (#12160)
    • The "Open in Terminal" context menu is now localized in, like, 88 languages (#12090)
    • There is a new adjustOpacity action, which can be previewed live with the command palette (#12092)
    • Terminal will now store elevated window state separately from non-elevated window state (#11222)
    • You can now export the buffer with an action, exportBuffer (#12097)
    • There is now a "Settings" menu item in the title bar menu (#11404) (thanks @serd2011!)
    • You can now Ctrl-click on a profile in the dropdown to launch it as Administrator (in a separate window) (#12209)
    • Terminal (and conhost) will no longer accept C1 control codes by default (#11690) (thanks @j4james!)
    • The PowerShell profile generator now generates fully quoted paths (#12086) (thanks @ianjoneill!)
    • WSL instances now default to starting in ~ (or throwing an Invalid Parameter error) (#12315)
    • We've reworked how settings get into the individual terminal panes to prepare for tearoff and merge (#11619) (#12255) (#12095)

    Bug Fixes

    • The cursor should now start/stop blinking more reliably when Terminal is started without window focus (#12094)
    • Copying the "Azure Cloud Shell" profile will no longer result in a normal boring profile that tries to run Azure.exe (lol) (#12147)
    • The default "Command Prompt" and "Windows PowerShell" profiles have been updated to have fully qualified paths (again) (#12149)
    • Cursor movement will now more reliably update the IME/emoji picker/input line/cursor highlight for Accessibility (#12210)
    • HTML/RTF copy now respects the active background color instead of just the default one (#11991) (thanks @j4james!)
    • Session save/restore will now remember tab titles and maximize/focus/restore state (#12073) (thanks @Rosefield!)
    • The "Duplicate Profile" button will no longer be enabled when you don't actually have a profile selected (#12096) (thanks @DavideGiacometti!)
    • //wsl$ paths will no longer result in you being unceremoniously dumped in / (in WSL) (#12102)
    • ~ now works as a starting directory for wsl.exe (#12050) (thanks @LuanVSO!)
    • Application-controlled titles will be sanitized for control sequences even if they are set with the SetConsoleTitle API (#12211) (thanks @j4james!)

    Accessibility

    • The command palette will now announce if any suggestions were found to screen readers (#12266)
    • ... so will the search box! (#12301)
    • The tab row/titlebar have stopped acting as a keyboard input/focus trap -- you can use keyboard shortcuts up there now (#12260)
    • We've done a pass over the controls in the settings UI and given them accessible names for screen reader users (#12299) (#12324)
    • The "Default Terminal" section will now properly read out terminal names to Narrator (#12259)
    • "Open JSON File" is now a better accessibility citizen as well (#12286)

    Performance and Reliability

    • We've fixed a (small) binary size regression in OpenConsole, which was more than eclipsed by all the new features above (#11727)
    • Improved:
      • base64 decode performance (#11467)
      • conhost CPU usage during text selection (#11634)
      • performance and binary size of til::enumset (#11493)
      • responsiveness of conhost/ConPTY for large inputs (#11890)
    • Removed wasteful virtuals according to SizeBench (#11889)
    • Typing an invalid background image path into the Settings UI will no longer send Terminal to a farm upstate (#11542) (thanks @serd2011!)
    • "Export Text" is more worky and less crashy (#12180) (thanks @ianjoneill!)

    Documentation Changes

    We'd like to thank @eltociear, @BlakeHeimann, @ghost1372, @Schweinepriester, and @ianjoneill for their contributions to our documentation, roadmap, specs and schema.

    Behind the Scenes

    Over the holidays, we had an "Engineering Improvement" milestone! We chose to allocate it to improving our build system, remove some dead code, etc. and our excellent community stepped up and did the same!

    Here's some of the highlights
    • Enable Software Bill of Materials generation for Windows Terminal (#11908)
    • Enable Security and Compliance tasks in our Release pipeline (#11849)
    • Add noexcept to all FontInfo structs (#11640)
    • Consolidate the color palette APIs (#11784) (thanks @j4james!)
    • Consolidate the interfaces for setting VT input modes (#11384) (thanks @j4james!)
    • Delete RendererTests.cpp (#11872) (thanks @j4james!)
    • Enable /permissive- and remaining /Zc flags (#11816)
    • fix build error at 74d21af (#11691) (thanks @serd2011!)
    • Fix for missing CopyComplete files in TerminalConnection.vcxproj (#11804)
    • Misc pane refactoring (#11373) (thanks @Rosefield!)
    • Move the common render settings into a shared class (#12127) (thanks @j4james!)
    • Prepare til wrappers for migrating off of SMALL_RECT (#11902)
    • Rename the "Bold" SGR attribute as "Intense" (#12270) (thanks @j4james!)
    • Replace GetDefaultBrushColors with hardcoded default attributes (#11982) (thanks @j4james!)
    • Replaced the sizeof parameter of the if statement with ARRAYSIZE (#12273) (thanks @abdoulkkonate!)
    • Simplify the handling of alpha values in the color table (#11900) (thanks @j4james!)
    • Simplify the IStateMachineEngine interface (#12277) (thanks @j4james!)
    • Standardize the color table order (#11602) (thanks @j4james!)
    • Update RGB values when selecting a conhost color property (#12099) (thanks @j4james!)
    • Use the til::enumset type for the SgrSaveRestoreStackOptions enum (#11888) (thanks @j4james!)

    Finally -- if you want to see some of the wild stuff batch files are capable of, check out ansi-color, contributed by @rbeesley as a test validation tool. (#11932)

    Source code(tar.gz)
    Source code(zip)
    Microsoft.WindowsTerminalPreview_1.12.10335.0_8wekyb3d8bbwe.msixbundle(39.40 MB)
    Microsoft.WindowsTerminalPreview_1.13.10336.0_8wekyb3d8bbwe.msixbundle(39.81 MB)
  • v1.12.10334.0(Feb 3, 2022)

    Happy New Year!

    This release brings many of the preview changes in Windows Terminal 1.12 to the Stable channel. Notably:

    • On Windows 11, Terminal now supports non-acrylic transparency
    • Terminal will now automatically create profiles for Visual Studio Developer shells
    • Terminal will now try to guess which profile to open when it is launched as the ‘default terminal’ for an application
    • You can now update the endpoint of an existing selection using the keyboard

    Please see the following release notes for additional details:

    A preinstallation kit is available for system integrators and OEMs interested in prepackaging Windows Terminal with a Windows image. More information is available in the DISM documentation on preinstallation. Users who do not intend to preinstall Windows Terminal should continue using the msixbundle distribution.

    This release was made available to insiders in the Dev and Beta channels on February 3, and will be generally available to everyone shortly afterwards. You can always install the update from this release page or using winget.

    We've also backported the following features, changes and bug fixes from Windows Terminal Preview v1.13.10336.0:

    Announcements

    • Windows Terminal is now named Terminal! It will, of course, still be called wt under the hood. (#12264)
      • Right now, you will not be able to find Windows Terminal _ (that is, with the "Windows" part) in the start menu. We are working with the search team to add a keyword match! Follow #12344 for updates._
      • Sorry about your muscle memory. :(
    • 1.12 is the last version of Terminal that will support Windows 19H1 or 19H2 (#12129)
      • Folks who are on the Preview channel on these versions of Windows will get a one-time upgrade to the last servicing release of 1.12.
      • This version of windows is going out of support soon, so you may want to consider upgrading.

    Changes

    • We're reworking how Terminal handles environment variables, starting with reverting the changes we made in Preview that broke PowerShell x86 (#12140)
    • The "adjust lightness of indistinguishable text" feature, present in 1.12 preview, has been disabled pending some bug fixes (#12160)
    • The "Open in Terminal" context menu is now localized in, like, 88 languages (#12090)
    • The PowerShell profile generator now generates fully quoted paths (#12086) (thanks @ianjoneill!)
    • WSL instances now default to starting in ~ (or throwing an Invalid Parameter error) (#12315)

    Bug Fixes

    • The cursor should now start/stop blinking more reliably when Terminal is started without window focus (#12094)
    • Copying the "Azure Cloud Shell" profile will no longer result in a normal boring profile that tries to run Azure.exe (lol) (#12147)
    • The default "Command Prompt" and "Windows PowerShell" profiles have been updated to have fully qualified paths (again) (#12149)
    • Cursor movement will now more reliably update the IME/emoji picker/input line/cursor highlight for Accessibility (#12210)
    • HTML/RTF copy now respects the active background color instead of just the default one (#11991) (thanks @j4james!)
    • The "Duplicate Profile" button will no longer be enabled when you don't actually have a profile selected (#12096) (thanks @DavideGiacometti!)
    • //wsl$ paths will no longer result in you being unceremoniously dumped in / (in WSL) (#12102)
    • ~ now works as a starting directory for wsl.exe (#12050) (thanks @LuanVSO!)
    • Application-controlled titles will be sanitized for control sequences even if they are set with the SetConsoleTitle API (#12211) (thanks @j4james!)

    Accessibility

    • The command palette will now announce if any suggestions were found to screen readers (#12266)
    • ... so will the search box! (#12301)
    • The tab row/titlebar have stopped acting as a keyboard input/focus trap -- you can use keyboard shortcuts up there now (#12260)
    • We've done a pass over the controls in the settings UI and given them accessible names for screen reader users (#12299) (#12324)
    • The "Default Terminal" section will now properly read out terminal names to Narrator (#12259)
    • "Open JSON File" is now a better accessibility citizen as well (#12286)

    Documentation Changes

    We'd like to thank @eltociear, @BlakeHeimann, @ghost1372, @Schweinepriester, and @ianjoneill for their contributions to our documentation, roadmap, specs and schema.

    Source code(tar.gz)
    Source code(zip)
    Microsoft.WindowsTerminal_1.12.10334.0_8wekyb3d8bbwe.msixbundle(39.03 MB)
    Microsoft.WindowsTerminal_1.12.10334.0_8wekyb3d8bbwe.msixbundle_Windows10_PreinstallKit.zip(38.54 MB)
  • v1.12.3472.0(Dec 14, 2021)

    This release brings some assorted top-hitting bug fixes into the preview channel from the main development branch.

    For the holiday season, enjoy the following:

    Changes

    • This version of Windows Terminal ships with Cascadia Code 2111.01.
      • The hinting on the brace ligatures was incorrect in the Italic style, which looked downright hilarious. See microsoft/cascadia-code#595 for more details.
    • On Windows 11, the Terminal now supports the "snap layouts" feature (#11680)

    Bug Fixes

    • The Default Terminal option will now work on machines that do not have the Visual C++ Redistributable (#11610)
    • Splitting a non-focused tab will no longer blast Terminal into outer space (#11635)
    • All of the alternative character set slots have been defaulted to ASCII (#11658) (thanks @j4james!)
      • This is in line with other terminals, and should reduce the incidence of a stray escape character turning your screen into soup.
    • We were seeing some crashes on window painting in the synthetic test lab, which we think we've addressed (#11674)
    • The background image path should once again be displayed in the settings UI (#11580) (thanks @ianjoneill!)
    • AltGr should once again work in the Settings UI (#11808) (#11814)
    • GetConsoleCommandHistoryLengthA will now respond with the correct length (???) (#11897)
    • Fragments that update multiple profiles will no longer confuse and enrage us (#11598)
    • There will once again be a window border when you use Win+↓ in fullscreen mode (#11653) (thanks @serd2011!)
    • Launching additional applications in "default terminal" windows has been made more reliable (#11646)
    • The opacity slider once again appears when it should (and disappears when it shouldn't), rather than the other way around (#11643)
    • Our informational tips will no longer obscure the tabs when showTabsInTitleBar is false (#11609)
    • We made the mistake of printing hex error codes with negative signs (oops); we've fixed that (#11667)
    • Shutdown has been made slightly more reliable (#11857) (thanks @Rosefield!)
    • Detected URLs will no longer be offset by complex unicode characters on the same line (#11915) (thanks @comzyh!)
    • On Windows Server, Terminal will no longer render the display in "ransom note" style (#11764)
    Source code(tar.gz)
    Source code(zip)
    Microsoft.WindowsTerminalPreview_1.12.3472.0_8wekyb3d8bbwe.msixbundle(39.33 MB)
  • v1.11.3471.0(Dec 14, 2021)

    This release brings some assorted top-hitting bug fixes into the stable channel from the main development branch.

    A preinstallation kit is available for system integrators and OEMs interested in prepackaging Windows Terminal with a Windows image. More information is available in the DISM documentation on preinstallation. Users who do not intend to preinstall Windows Terminal should continue using the msixbundle distribution.

    This release was made available to insiders in the Dev and Beta channels on December 14, and will be generally available to everyone shortly afterwards. You can always install the update from this release page or using winget.

    For the holiday season, enjoy the following:

    Changes

    • This version of Windows Terminal ships with Cascadia Code 2111.01.
      • The hinting on the brace ligatures was incorrect in the Italic style, which looked downright hilarious. See microsoft/cascadia-code#595 for more details.

    Bug Fixes

    • The Default Terminal option will now work on machines that do not have the Visual C++ Redistributable (#11610)
    • Splitting a non-focused tab will no longer blast Terminal into outer space (#11635)
    • All of the alternative character set slots have been defaulted to ASCII (#11658) (thanks @j4james!)
      • This is in line with other terminals, and should reduce the incidence of a stray escape character turning your screen into soup.
    • We were seeing some crashes on window painting in the synthetic test lab, which we think we've addressed (#11674)
    • The background image path should once again be displayed in the settings UI (#11580) (thanks @ianjoneill!)
    • AltGr should once again work in the Settings UI (#11808) (#11814)
    • GetConsoleCommandHistoryLengthA will now respond with the correct length (???) (#11897)
    • There will once again be a window border when you use Win+↓ in fullscreen mode (#11653) (thanks @serd2011!)
    • Launching additional applications in "default terminal" windows has been made more reliable (#11646)
    • Our informational tips will no longer obscure the tabs when showTabsInTitleBar is false (#11609)
    • Detected URLs will no longer be offset by complex unicode characters on the same line (#11915) (thanks @comzyh!)
    • On Windows Server, Terminal will no longer render the display in "ransom note" style (#11764)
    • AltGr+Space should once again work (#11832)
    Source code(tar.gz)
    Source code(zip)
    Microsoft.WindowsTerminal_1.11.3471.0_8wekyb3d8bbwe.msixbundle(29.21 MB)
    Microsoft.WindowsTerminal_1.11.3471.0_8wekyb3d8bbwe.msixbundle_Windows10_PreinstallKit.zip(28.77 MB)
  • v1.12.2931.0(Oct 21, 2021)

  • v1.12.2922.0(Oct 20, 2021)

    Terminal v1.12 is here! It includes upgrades to our CascadiaCode, MUX and C++/WinRT versions, and also includes our first step to true session restoration! Here’s the full changelog:

    Features

    • Window/pane layouts can now be saved upon closing, and will be restored upon relaunch (#10972) (#10978) (#11083) (#11374) (thanks @Rosefield!)
      • Right now, Terminal will only save/restore active tabs, not screen contents or command history
      • This is our first step towards true session restoration
      • You can configure this with the firstWindowPreference global setting (an enum setting with possible values persistedWindowLayout or defaultProfile) in the settings.json file, or configure it in the Settings UI; the default value for this setting is defaultProfile
    • First-time Windows 11 users will receive an information popup about changing their default terminal to WT, along with a link to their settings (#11397) (#11491)
    • You can now update the endpoint of an existing selection using the keyboard (#10824)
      • Please note: Right now, this only works if you’ve already started a selection with the mouse. You can move the selection range using Shift + the arrow keys
    • Terminal now supports actions that can run multiple other actions (we heard you like actions, so we put actions in your actions so you can perform actions while you perform actions) (#11045) (thanks @Rosefield!)
      • For example, something like this:
        "action": "multipleActions",
        "name": "Move right->down",
        "actions": [
          {"action":  "moveFocus", "direction": "right" },
          {"action":  "moveFocus", "direction": "down" }]
        }
      
    • Terminal will now automatically create profiles for Visual Studio Developer shells (#7774) (thanks @trippwill and @heaths!)
    • Terminal will now try to guess which profile to open when it is launched as the ‘default terminal’ for an application (#11390)
    • You can now interact with subtrees of panes (instead of only the leaves) (#11153) (thanks @Rosefield!)
    • On Windows 11, Terminal now supports non-acrylic transparency (#11180)
      • Opacity has moved to a new setting named opacity (an integer with possible values in the range 0-100; defaults to 100)
      • Transparency is no longer configured with the useAcrylic option. If you set opacity <100 or acrylicOpacity <1.0, the terminal will become transparent
    • You can now always target the first pane in the tree for your swapping/moving focus purposes (#11044) (thanks @Rosefield!)
    • The tab row will now contain a helpful shield icon when Terminal is in elevated mode (#11224)
      • You can configure the visibility of the admin shield with the showAdminShield global setting (a Boolean setting that defaults to true)
    • We added an action that allows you to quit all terminal instances at once (#11143) (thanks @Rosefield!)
    • New panes can now be created to the left or above the existing pane, instead of only to the right or bottom (#11145) (thanks @Rosefield!)
      • The splitPane action can now take in directional arguments (left, right, down, up) and treats horizontal as right and vertical as down
    • The contents of the screen can now be exported into a file via the tab context menu (#11062) (thanks @Don-Vito!)
    • We added an action to manually clear the Terminal buffer (#10906)
    • There is now a setting that will automatically adjust your foreground color's lightness if it is nigh-imperceivable on the background (#11095)
      • This should help users of Solarized Dark to have an easier time using PowerShell
      • This can be turned off by setting "adjustIndistinguishableColors": "false" in your settings.json, or from the Settings UI
    • The command palette has been taught several neat tricks (thanks @Don-Vito!)
      • Hitting the right-arrow key will automatically fill in the currently selected command into the text box (#11069)
      • The command palette now filters out duplicate command lines (#11116)
      • The command palette now persists recent command lines (#11030)
    • We will now tell you how to get rid of “process exited with code xxx” errors and automatically close tabs with a new info bar, which can be permanently dismissed (#11139) (thanks @Don-Vito!)
    • Tabs can now be reordered in elevated mode if UAC is disabled (#11221)
    • The system menu can now be opened with its very own keybinding: openSystemMenu(#11086)
      • As a result, you can also disable the system menu by binding Alt+Space to unbound.

    Changes

    • We have updated to the new version of WinUI - 2.7 (#11240)
    • Autocorrect has now been disabled for our command, path and find text fields (#11137) (thanks @ianjoneill!)
    • The exit code now shows up as hexadecimal in addition to decimal (#11123)
    • You can now navigate focus between panes even while zoomed (#11046) (thanks @Rosefield!)
    • We now make sure to fully clean up state after closing a peasant Terminal session (#11217) (thanks @Rosefield!)
    • We’ve adjusted the padding between tabs in the titlebar (#11115) (thanks @gabrielconl!)
    • The Tray Icon's context menu now shows the names of the open tabs (#11043)
    • We made some sleek visual tweaks to our search box (#11105) (thanks @gabrielconl!)
    • "TrayIcon" and "Tray" have been renamed to "NotificationIcon" and "NotificationArea" (#11219)
      • This includes the JSON setting names.
    • Ctrl+numpad_0 will now also reset the font size (previously it was only ctrl+0) (#11243) (thanks @BenConstable9!)

    VT sequences

    • Terminal now supports the 'Request Selection or Setting' (DECRQSS) VT sequence (#11152) (thanks @j4james!)

    Bug Fixes

    • Opening the debug tap no longer crashes the terminal (#11445)
    • Moving the window after opening a dialog box no longer does strange things to the window (#11485) (thanks @mpela81)
    • All mouse events now get sent correctly even after the viewport is scrolled (#11290)
    • Pasting text now correctly clears the current selection (#11286) (thanks @serd2011!)
    • We fixed various compatibility issues with the profiles schema (#11360)
    • Fixed a typo that was causing us to fail to save the dropdown duration on the summon window action (#11401) (thanks @NotWearingPants!)
    • The tab background color is now applied correctly when the tab is unfocused (#11413)
    • wt command-lines are now escaped properly when used from the Open Terminal Here menu item (#11314) (thanks @ianjoneill!)
    • Terminal’s multi-process model should now be more robust (#11189) (thanks @Rosefield!)

    Settings UI

    • Fixed a crash that would occur when adding an action with the same key chord as an existing action (#11427)
    • The "Reset to inherited value" button for opacity now works correctly (#11391) (thanks @ianjoneill!)
    • There is no longer a nameless action in the actions dropdown (#11427)
    • The minimizeToTray and alwaysShowTrayIcon settings can now be configured in the settings UI (#11070)
    • Fixed various typos (#11362)

    Accessibility

    • Fixed a hang in narrator that would occur upon selecting some text in Terminal (#11386)
    • We now make sure the text buffer is present before we try to interact with it (#11312)
    • We treat the last character as the end of the buffer now, significantly improving the performance of word navigation (#11122)
    • Several previously nameless controls now have names! (#11364)
    • Fixed RadioButton content not showing up properly in UIA (#11442)

    Documentation, Schema and Code Health

    Thank you to @j4james, @ghost1372, @NotWearingPants, @heysujal and @saintmalik for contributions to the documentation, code health and JSON schema document.

    Source code(tar.gz)
    Source code(zip)
    Microsoft.WindowsTerminalPreview_1.12.2922.0_8wekyb3d8bbwe.msixbundle(39.29 MB)
  • v1.11.2921.0(Oct 20, 2021)

    This release brings many of the preview changes in Windows Terminal 1.11 to the stable channel. Please see the following release notes for additional details:

    A preinstallation kit is available for system integrators and OEMs interested in prepackaging Windows Terminal with a Windows image. More information is available in the DISM documentation on preinstallation. Users who do not intend to preinstall Windows Terminal should continue using the msixbundle distribution.

    We've also backported some features, changes and bug fixes from Windows Terminal Preview 1.12.2922.0 and earlier versions:

    Features

    • On Windows 11, Windows Terminal can now be set as the default console host (#9907) (#10170)
      • First-time Windows 11 users will receive an information popup about changing their default terminal to WT, along with a link to their settings (#11397) (#11491)
      • This only applies to Store and msixbundle installs of Terminal; scoop installs and other "extraction-based" installs cannot be registered as the default terminal.
    • We've reintroduced the UI that allows you to edit default settings that apply to all profiles, as well as arrow buttons that let you revert individual settings (#10588)
    • On the Actions page, you can now edit existing actions and add new ones (#10550) (#10220)
    • The keyboard service warning info bar can now be permanently dismissed (#11139) (thanks @Don-Vito!)

    Bug Fixes

    • Moving the window after opening a dialog box no longer does strange things to the window (#11485) (thanks @mpela81)

    Accessibility

    • Fixed RadioButton content not showing up properly in UIA (#11442)
    • Fixed a hang in narrator that would occur upon selecting some text in Terminal (#11386)
    Source code(tar.gz)
    Source code(zip)
    Microsoft.WindowsTerminal_1.11.2921.0_8wekyb3d8bbwe.msixbundle(29.19 MB)
    Microsoft.WindowsTerminal_1.11.2921.0_8wekyb3d8bbwe.msixbundle_Windows10_PreinstallKit.zip(28.75 MB)
  • v1.11.2731.0(Oct 4, 2021)

    This release brings some assorted top-hitting bug fixes into the preview channel from the main development trunk.

    There's also a breaking change included here to ensure our consistency as we move into 1.12. We were alerted that the terminology "tray" is inappropriate for Taskbar Notification Area. This means that the minimizeToTray setting is now the minimizeToNotificationArea setting and the alwaysShowTrayIcon setting is now the alwaysShowNotificationIcon setting. There is no automatic migration of these settings as this terminology was only ever used in preview channel. Preview users will have to fix their settings files manually. (#11219)

    Bug Fixes

    Accessibility

    • Resolves hang on launch for Windows Server 2022 (and similar client Windows versions) when tablet input keyboard is activated (#11312)
    • Selecting text in the terminal while Narrator is open will no longer hang (#11386)

    Reliability

    • Fix KeyChord constructor assertion failure during tab dragging (#11306)

    Terminal Emulation

    • Fixes alignment of the mouse coordinates when the viewport is scrolled for all events, not just mouse button pressed event. (#11290)

    User Interface

    • Clear selection on paste (#11286) (thanks @serd2011!)

    JSON Settings

    • Fix serialisation of findMatch action to persist the direction (#11233) (thanks @ianjoneill!)
    Source code(tar.gz)
    Source code(zip)
    Microsoft.WindowsTerminalPreview_1.11.2731.0_8wekyb3d8bbwe.msixbundle(29.52 MB)
  • v1.10.2714.0(Oct 4, 2021)

    This release brings some assorted top-hitting bug fixes into the stable channel from the main development trunk.

    If this looks very similar to the preview channel, you're correct. These were heavy hitters, so we're rolling out to the whole population as quickly as we can.

    A preinstallation kit is available for system integrators and OEMs interested in prepackaging Windows Terminal with a Windows image. More information is available in the DISM documentation on preinstallation. Users who do not intend to preinstall Windows Terminal should continue using the msixbundle distribution.

    Bug Fixes

    Accessibility

    • Resolves hang on launch for Windows Server 2022 (and similar client Windows versions) when tablet input keyboard is activated (#11312)

    Reliability

    • Fix KeyChord constructor assertion failure during tab dragging (#11306)

    Terminal Emulation

    • Fixes alignment of the mouse coordinates when the viewport is scrolled for all events, not just mouse button pressed event. (#11290)

    User Interface

    • Clear selection on paste (#11286) (thanks @serd2011!)

    JSON Settings

    • Fix serialisation of findMatch action to persist the direction (#11233) (thanks @ianjoneill!)
    Source code(tar.gz)
    Source code(zip)
    Microsoft.WindowsTerminal_1.10.2714.0_8wekyb3d8bbwe.msixbundle(28.75 MB)
    Microsoft.WindowsTerminal_1.10.2714.0_8wekyb3d8bbwe.msixbundle_Windows10_PreinstallKit.zip(28.32 MB)
  • v1.11.2421.0(Aug 31, 2021)

    It's that time of year again: Terminal day!

    You probably wouldn't have guessed that this was supposed to be a stabilization release, with a big focus on performance and bug fixes. Our beloved community, however made sure that we had more than enough features to go around! Thanks everyone!

    This version of Terminal ships with Cascadia Code 2108.26, which contains fixes for some ligature issues, Hebrew glyph positioning and more.

    Features

    • You can now delete autogenerated profiles. That just about says it all. Sorry for taking so long on this one! (#11007) (#10910)
    • Terminal will now optionally present a tray icon and minimize windows to it (#10368) (#10980) (#10938)
      • See alwaysShowTrayIcon (boolean, default false) and minimizeToTray (boolean, default false) in the settings JSON file
      • This feature is not yet present in the settings UI, which is an oversight we hope to rectify before 1.12.
    • You can now set special font features and custom axis values! (#10525) with bug fix (#10863)
      • This works great with Cascadia Code's new alternate italic style.
        • "font": { "face": "Cascadia Code", "features": { "salt": 1 } }
      • You can also disable ligatures in any font that supports them by setting the calt, clig or dlig features to 0. Consult your font's printed manual for more information.
    • Bold or "intense" text can now be displayed as bright colors, a bold font, or both (#10759)
      • We released 1.10 with the new default set to both bold and bright, but have reset it to just bright until we work out some text rendering issues (#10958)
      • Set intenseTextStyle (flag enum, default bright, options bold, bright, all) in any profile
    • There is a new "Split Tab" item in each tab's context menu, which will split the active profile (#10832)
    • Terminal now supports displaying the titlebar¹ or tab row with the acrylic material (#10864) (thanks @matthew4850!)
      • Settings key: useAcrylicInTabRow (boolean, default false)
      • ¹That is, if you have disabled "show tabs in the title bar"
    • There's a new "unfocused appearance" editor at the bottom of the Appearance page (per profile) (#10317)
    • Key bindings now support the browser keys found on some keyboards newer than, say, 2000? (#10801) (thanks @FWest98!)
      • browser_back, browser_forward, browser_refresh, browser_stop, browser_search, browser_favorites and browser_home
    • You can now open a new tab by dropping a folder on the + button (!) (#10073) (#10160) (thanks @Daniel599) with implementation fixes in (#10842) and tooltip help in (#10841) thanks to @ianjoneill!
    • Those of you with international keyboards can now specify very particular key bindings to "virtual key" codes or scancodes (#10666) (#10917) (#10945)
      • Use vk(xxx) or sc(xxx) to (in the darkness) bind these keys. The Settings UI will also produce them from time to time.
      • The "Quake Mode" key binding has been changed from windows+backtick to windows+sc(41), which is "the key where backtick is on the US-104 keyboard"

    Pane Management

    Of particular note, Schuyler Rosefield spent a lot of time working on panes this release. Thank you, @Rosefield!

    • Pane navigation with moveFocus now uses the visual, instead of the (il)logical layout (#10756) (#11023)
    • You can now swap the positions of two panes by using the swapPane action or the swap-pane command line argument (#10638)
      • Search the Command Palette (Ctrl+Shift+P by default) for "Swap" to learn more!
    • You can now move the active pane to any tab (or even a new tab!) with the movePane action or the move-pane/mp command (#10780) (#11039)
      • Search the Command Palette (Ctrl+Shift+P by default) for "move pane"!
    • The moveFocus and swapPane actions have been taught the nextInOrder and previousInOrder directions, which will walk the pane tree in creation order (#10927)
    • The moveFocus and swapPane actions have also been taught the first direction, which targets the first pane in the tab (#11044)
      • This is good for DWM-style split screen layouts where you have an active work pane and a set of auxiliary side panes!
    • There is a new toggleSplitOrientation action that will switch a pair of panes from vertical to horizontal layout (#10713)

    Changes

    • Terminal will now use no profile for incoming commandline commands and command-line applications launched via "default terminal" (#11022)
      • The settings that you'll see are dictated by the contents of the "Defaults" section in settings, or profiles.defaults in settings.json
      • It didn't make any sense for wt cmd to launch a profile with the PowerShell icon!
      • If you really want to run a command in a specific profile, use wt -p Profile command
      • The title of the new tab/pane will be derived from the command itself (#10998) (#11029)
    • Terminal will now try to launch WSL by moving the startingDirectory to the command line (#9223)
      • If you are on a newer version of Windows, you will be able to set the starting directory to ~ or any Linux path!
    • The Actions page in the Settings now has a live "key chord" editor -- you no longer need to type shortcuts like c t l r + e (and inevitably get them wrong) (#10652)
    • You can now un-bind alt+space from opening the system menu (#10799) (thanks @FWest98!)
    • The focusTab action will now always focus a tab, even if there aren't as many as you thought (#10651)
      • We have re-bound Ctrl+Shift+9 to "jump to final tab", as opposed to "jump to tab 9", as Edge, Firefox and other browsers do.
    • The settings will now reload when you change your active keyboard layout (#10876)
      • This is to support keyboard layouts that define different display keys for vk() and sc() codes.
    • In the settings UI, we've changed a number of tooltips to replace "checked" (as in, a checkbox) with "enabled" because they're toggle switches now (#10885)
    • We have done some internal work to prepare for tab tearoff (#10051) (#10874)
    • We've reworked how some of the settings UI values are generated and displayed (#10846) (thanks @chingucoding!)

    Performance

    The changelog messages in this section are

    • The console (and terminal) will no longer hold on to large memory allocations after large I/O requests (#10738)
    • Terminal now loads WSL distributions in a different way, and will not hang on startup waiting for them (#10967)
    • Settings reload will no longer visit each pane once per profile (#10997)
    • The UTF-16 <-> UTF-8 converter has been refactored to not waste memory (like, at all) (#10966) (thanks @german-one!)
    • We have made a number of changes to improve I/O and rendering performance (#10921) (#10653) (#10923)
      • More, thanks to @skyline75489 (#10621) (#10685)

    Bug Fixes

    Accessibility

    • An issue where opening a tab with Narrator running resulted in no output has been fixed (#10971)
    • Moving your screen reader cursor by line, character and document is now more reliable (#10991)
      • ...and should no longer cause an occasional deadlock. (#10937)

    "Default Terminal"

    • Command-line applications launched through "Default Terminal" now follow the windowing behavior setting (#10823)
    • Applications launched into terminal no longer erroneously believe the screen to be 9001 lines tall (#10772)
    • We fixed an issue resulting in Ctrl+C never reaching handoff applications (#10751)

    "Quake" Mode

    • The "quake" window's borders will no longer appear on adjacent monitors (#10676)
    • Dismissing the "quake" window and summoning it on another display will now properly update its size (#10674)
    • Snapping the "quake" window to another display will also properly update its size (#10744)

    Reliability

    • Saving your settings will no longer destroy them if settings.json is a symbolic link (#10908) (thanks @Don-Vito!)
    • When you attempt to use Alt+Arrow Keys with no panes, we will now send those keys to the connected client (#10806) (thanks @FWest98!)
    • focus-tab --previous/next now ignores tab switcher order (#10947) (thanks @Don-Vito!)
    • Duplicating a pane hosting a deleted profile will no longer result in ~ ~ weird behavior ~ ~ (#10982)
      • We will also spend a lot less time looking up profiles by their IDs (oops)
    • A crash during startup/commandline execution regarding moving focus to a new pane has been quashed (#11040) (thanks @Rosefield!)

    Terminal Emulation

    • You can no longer erroneously interact with mouse-mode applications at bad coordinates when they are scrolled away (#10642)
    • Selected text will no longer move off of its selected line as more text is output... (#10749)
      • ... until it no longer fits on screen, at which point it absolutely will.
    • The alternate buffer now inherits its cursor state from the main buffer (#10843) (#10878) (thanks @j4james!)
    • We've put a sock in a very loud exception handler (#10901)
    • We will no longer try to resize the display if the size hasn't changed, and no longer clear your selection (#10895) (thanks @Don-Vito!)
    • C1 control characters in SetConsoleTitle will no longer cause Terminal to lose sanity (#10847) (thanks @j4james!)
    • The terminal will no longer scroll vertically if you have a horizontal wheel (#10979)
    • RIS no longer even has a chance of failing (thanks to @amie42 for spotting this after the PR merged!) (#10661)

    User Interface

    • No longer will dropdown menus and combo boxes fly wildly off the screen if you scroll or drag the window! Rejoice! (#10922)
    • Progress bars: multiple panes and tabs displaying progress indicators will be merged for the taskbar (#10755)
    • Restoring from fullscreen no longer accidentally counts the window border as part of the new size (#10737)
    • The window border is likewise ignored when calculating the initial position of the window (#10902)
    • We have removed a double scrollbar from the settings UI, which was a fix for another issue, which has now been fixed properly (#10716) (thanks @mimvdb!)
    • We've fixed some focus tracking bugs that occur during complicated command line handling (#10978)
    • There is no longer an annoying issue where some people on non-100%-scaling displays would not be able to use the tab bar when maximized (#10746)
    • The settings UI animations are now slightly less obnoxious (#10934) (thanks @Don-Vito!)
    • Dragging content over the terminal will no longer cause it to spontaneously scroll everywhichway (#10650)
    • The color picker's minimum width is now better (#10663) (thanks @gabrielconl!)

    JSON Settings Schema

    • The hidden setting experimental.input.forceVT has been added to the JSON schema (oops!) (#10715)
    Source code(tar.gz)
    Source code(zip)
    Microsoft.WindowsTerminalPreview_1.11.2421.0_8wekyb3d8bbwe.msixbundle(29.50 MB)
  • v1.10.2383.0(Aug 31, 2021)

    This release brings many of the preview changes in Windows Terminal 1.10 to the stable channel. Notable changes include:

    • You can now select a different display language in the "Appearance" settings.
    • Terminal will now present an icon in the system notification area when "Quake" mode is enabled.

    Please see the following release notes for additional details:

    A preinstallation kit is available for system integrators and OEMs interested in prepackaging Windows Terminal with a Windows image. More information is available in the DISM documentation on preinstallation. Users who do not intend to preinstall Windows Terminal should continue using the msixbundle distribution.

    We've also backported the following features, changes and bug fixes from Windows Terminal Preview 1.11.2421.0:

    Features

    • You can now delete autogenerated profiles. That just about says it all. Sorry for taking so long on this one! (#11007) (#10910)
    • Bold or "intense" text can now be displayed as bright colors, a bold font, or both (#10759)
      • We released 1.10 with the new default set to both bold and bright, but have reset it to just bright until we work out some text rendering issues (#10958)
      • Set intenseTextStyle (flag enum, default bright, options bold, bright, all) in any profile

    Changes

    • This version of Terminal ships with Cascadia Code 2108.26, which contains fixes for some ligature issues, Hebrew glyph positioning and more.
    • In the settings UI, we've changed a number of tooltips to replace "checked" (as in, a checkbox) with "enabled" because they're toggle switches now (#10885)

    Performance

    • The console (and terminal) will no longer hold on to large memory allocations after large I/O requests (#10738)
    • Terminal now loads WSL distributions in a different way, and will not hang on startup waiting for them (#10967)

    Bug Fixes

    Accessibility

    • An issue where opening a tab with Narrator running resulted in no output has been fixed (#10971)
    • Moving your screen reader cursor by line, character and document is now more reliable (#10991)
      • ...and should no longer cause an occasional deadlock. (#10937)

    "Default Terminal"

    note: the default terminal functionality is not enabled in this release. These are just the bugfixes related to that functionality which happen to be in this release. For more details, see #11415

    • Command-line applications launched through "Default Terminal" now follow the windowing behavior setting (#10823)
    • Applications launched into terminal no longer erroneously believe the screen to be 9001 lines tall (#10772)
    • We fixed an issue resulting in Ctrl+C never reaching handoff applications (#10751)

    "Quake" Mode

    • The "quake" window's borders will no longer appear on adjacent monitors (#10676)
    • Dismissing the "quake" window and summoning it on another display will now properly update its size (#10674)
    • Snapping the "quake" window to another display will also properly update its size (#10744)

    Reliability

    • Saving your settings will no longer destroy them if settings.json is a symbolic link (#10908) (thanks @Don-Vito!)
    • When you attempt to use Alt+Arrow Keys with no panes, we will now send those keys to the connected client (#10806) (thanks @FWest98!)
    • A crash during startup/commandline execution regarding moving focus to a new pane has been quashed (#11040) (thanks @Rosefield!)

    Terminal Emulation

    • You can no longer erroneously interact with mouse-mode applications at bad coordinates when they are scrolled away (#10642)
    • Selected text will no longer move off of its selected line as more text is output... (#10749)
      • ... until it no longer fits on screen, at which point it absolutely will.
    • The alternate buffer now inherits its cursor state from the main buffer (#10843) (#10878) (thanks @j4james!)
    • We've put a sock in a very loud exception handler (#10901)
    • We will no longer try to resize the display if the size hasn't changed, and no longer clear your selection (#10895) (thanks @Don-Vito!)
    • C1 control characters in SetConsoleTitle will no longer cause Terminal to lose sanity (#10847) (thanks @j4james!)
    • The terminal will no longer scroll vertically if you have a horizontal wheel (#10979)
    • RIS no longer even has a chance of failing (thanks to @amie42 for spotting this after the PR merged!) (#10661)

    User Interface

    • No longer will dropdown menus and combo boxes fly wildly off the screen if you scroll or drag the window! Rejoice! (#10922)
    • Restoring from fullscreen no longer accidentally counts the window border as part of the new size (#10737)
    • The window border is likewise ignored when calculating the initial position of the window (#10902)
    • We have removed a double scrollbar from the settings UI, which was a fix for another issue, which has now been fixed properly (#10716) (thanks @mimvdb!)
    • We've fixed some focus tracking bugs that occur during complicated command line handling (#10978)
    • There is no longer an annoying issue where some people on non-100%-scaling displays would not be able to use the tab bar when maximized (#10746)
    • The settings UI animations are now slightly less obnoxious (#10934) (thanks @Don-Vito!)
    Source code(tar.gz)
    Source code(zip)
    Microsoft.WindowsTerminal_1.10.2383.0_8wekyb3d8bbwe.msixbundle(28.75 MB)
    Microsoft.WindowsTerminal_1.10.2383.0_8wekyb3d8bbwe.msixbundle_Windows10_PreinstallKit.zip(28.31 MB)
Owner
Microsoft
Open source projects and samples from Microsoft
Microsoft
Spitfire is a basic terminal language that can exicute code via the terminal.

Spitfire is a basic terminal language that can exicute code via the terminal. It is easy to learn and runs fast, considering that its just a 300 line c++ file.

jhomas tefferson 0 Nov 18, 2021
Free open-source modern C++17 / C++20 framework to create console, forms (GUI like WinForms) and unit test applications on Microsoft Windows, Apple macOS and Linux.

xtd Modern C++17/20 framework to create console (CLI), forms (GUI like WinForms) and tunit (unit tests like Microsoft Unit Testing Framework) applicat

Gammasoft 413 Nov 29, 2022
EAMain provides a multi-platform entry point used for platforms that don't support console output, return codes and command-line arguments.

EAMain provides a multi-platform entry point used for platforms that don't support console output, return codes and command-line arguments.

Electronic Arts 34 Oct 1, 2022
FastReport.Cloud console tool for Linux and perhaps some other OSes

FastReport Cloud console shell This is a simple console shell to FastReport Cloud service. Prerequests GNU packages for build shell: curl-development

Aleksey Mandrykin 2 Feb 10, 2022
Run commands with hidden console.

Minimal run This is a tiny C program for running Windows commands with a hidden console. It's suitable for use in Windows shortcuts, i.e. lnk files. I

Tavis Ormandy 22 Oct 15, 2022
cpp-progressbar is a small console program I wrote in c++. 3 themes are available

cpp-progressbar cpp-progressbar is a small console program I wrote in c++. 3 themes are available (this program only works on linux) Instalation Downl

Zielino 3 Jun 17, 2022
A C++ console tool to tracker baby actions.

BabyTracker This is a C++ console tool to tracker baby actions. Currently it supports adding Sleep Sessions Breast Feed Sessions Bottle Feed Sessions

YuchenPersonal 1 Oct 17, 2021
Terminal calculator made for programmers working with multiple number representations, sizes, and overall close to the bits

Programmer calculator The programmer calculator is a simple terminal tool designed to give maximum efficiency and flexibility to the programmer workin

romes 174 Nov 22, 2022
A C, C++ and Rust library to draw graphics with pixels in the terminal

A library to draw graphics with pixels in the terminal Who needs a GUI when you have a terminal ? Building To generate libpluto.a, run: $ make To ins

null 69 Nov 7, 2022
timg - Terminal Image and Video Viewer

timg - Terminal Image and Video Viewer

Henner Zeller 1.3k Nov 29, 2022
Small header only C++ library for writing multiplatform terminal applications

Terminal Terminal is small header only library for writing terminal applications. It works on Linux, macOS and Windows (in the native cmd.exe console)

Jupyter Xeus 263 Dec 1, 2022
:computer: C++ Functional Terminal User Interface. :heart:

FTXUI Functional Terminal (X) User interface A simple C++ library for terminal based user interface. Demo: Feature Functional style. Inspired by [1] a

Arthur Sonzogni 3.9k Nov 30, 2022
A little UNIX-inspired terminal application for the Numworks Calculator (not using escher).

L.E. Terminal (let for short) is a little UNIX-inspired terminal for the Numworks Calculator.

Cacahuète Sans Sel 20 Aug 31, 2022
Draw sequence diagram in text from terminal.

sequence-diagram-cli Draw seqence diagram from terminal.

null 44 Nov 26, 2022
X terminal emulator rendering through OpenGL ES Compute Shaders

Zutty is a terminal emulator for the X Window System, functionally similar to several other X terminal emulators such as xterm, rxvt and countless others

Tom Szilagyi 252 Dec 3, 2022
n³ The unorthodox terminal file manager

n³ The unorthodox terminal file manager

Mischievous Meerkat 15.3k Nov 30, 2022
Graphs the activity of a chia harvester in a linux terminal.

Chia Harvest Graph Monitor for Chia Harvesting Introduction The chiaharvestgraph tool will graph Chia Harvesting activity in a linux terminal. Use a 2

Bram Stolk 216 Nov 10, 2022
a simple to use linux terminal

a simple to use linux terminal

notaweeb 7 Feb 17, 2022
Collection of human friendly terminal interface for git.

A collection of human friendly terminal user interface for git.

Arthur Sonzogni 73 Nov 25, 2022