Windows Terminal 1.16.1023 (10231 and 10232) release Windows 10 and 11

  • Staff
After a long wait, many of the features in Terminal Preview 1.16 are making their way to the stable channel:
  • Themes: Terminal now has support for themes!
  • We have a new experimental text rendering engine, which is off by default. It's faster and handles some situations better (and some much worse, like certain fonts that don't have a true "italic" style). You can enable it in the Rendering settings.
  • This release marks the triumphant return of the "adjust brightness of indistinguishable colors" feature
  • For the old conhost fans in the room, you can now set experimental.enableColorSelection (global, bool, default false)
After this release, Terminal Stable is moving to a quarterly feature release cycle. Since we're the default console host in Windows 11 October 2022 Update, some care is required in how quickly we distribute updates. That having been said: there will still be servicing updates and Preview channel updates, so stay tuned!

Please see the following release notes for additional details:
Note that the new 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 later depending on its reliability.

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



  • The contents of the Terminal package are now code-signed, so those of you who deploy it unzipped will no longer get in
    trouble with your IT folks (#14710)

Bug Fixes​

  • We now attempt to account for transparent tab backgrounds when calculating the text foreground color (#14643)
  • You can now drag/drop more than 16 items directly out of 7-Zip (and some other applications) (#14648) (thanks @jiejasonliu!)
  • Malformed settings objects will no longer cause an "Application error 0x%" settings warning (#14668)
  • We've updated the JSON schema to contain theme objects (#14672) (#14666)


  • We've removed a leading cause of crashes closing panes and tabs while screen reading was active (#14714)
  • Input will no longer (rarely) trigger a crash when a screen reader is enabled (#14694)
  • wpf: stop dereferencing null pointers already! come on, it's 2023! (#14678)


  • We have removed our dependency on Microsoft.Toolkit.Win32.UI.XamlApplication.dll (#14520)


  • Our internal management window will no longer appear as an empty pane to screen readers (#14541)




  • Windows_Terminal.png
    5.5 KB · Views: 0

Latest Support Threads

Top Bottom