Jump to content

Windows Terminal Windows Terminal v1.15.252


Recommended Posts

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.

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

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



  • 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)


  • @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


  • 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 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.


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


  • 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.


Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...