Windows Terminal Preview v1.14.143

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!

Windows Terminal v1.13.1143

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:

• Windows Terminal Preview v1.13.1098
• Windows Terminal Preview v1.13.1073
• Windows Terminal Preview v1.13.10395.0
• Windows Terminal Preview v1.13.10336.0

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)

Windows Terminal Preview v1.13.1098

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

Windows Terminal v1.12.1098

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

Windows Terminal Preview v1.13.1073

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)

Windows Terminal v1.12.1073

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)

Windows Terminal Preview v1.13.10395.0

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)

Windows Terminal v1.12.10393.0

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)

Windows Terminal Preview v1.13.10336.0

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)

Windows Terminal v1.12.10334.0

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:

• Windows Terminal Preview v1.12.2922.0
• Windows Terminal Preview v1.12.3472.0

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.