Windows Terminal v1.15.3465.0 and v1.15.3466.0

v1.15.3465.0 (Windows 10) and v1.15.3466.0 (Windows 11) are servicing updates to Windows Terminal Stable v1.15.

Warning
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 2022, so you really may want to consider upgrading.

This message will self-destruct before the next release.

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 includes the following fixes (backported from 1.16 and https://github.com/microsoft/terminal/tree/main).

Changes

• Vintage transparency now works on Windows 10! Turn off useAcrylic to use it! (#14481)
• Using the mouse wheel to turn off transparency will now disable the acrylic material effect (#14193) (thanks @JerBast!)

Bug Fixes

• Bracketed paste, forced titles, and the default cursor shape are no longer randomly initialized (#14345)
  • This fixes an issue where pasted text would occasionally be incorrectly mangled (as opposed to correctly mangled...)
• RIS will no longer utterly tank Terminal's ability to handle C1 control characters (#13969) (thanks @j4james!)
• Console applications will now be correctly identified as the owners of their associated "pseudo-console" window (#14196)
• Ctrl+C will now skip any currently-playing DECPS sounds (thanks @dgl for reporting) (#14214)
• Applications should more reliably receive close signals when you close a tab, and we will no longer unceremoniously terminate their console sessions (#14282)
• JSON Schema: startingDirectory is now correctly identified as supporting null (#14408)

Accessibility & Usability

• Text boxes in the settings UI have been made more discoverable by screen readers (#14178)
• There will no longer no longer not be redundant tooltips in the Settings UI (#14244)

Reliability

• We've fixed one source of deadlocks in windowing management for console applications (such as hanging when they're exiting...) (#14463)
• Launching thousands of instances of cmd.exe back to back will no longer take down your console session (MSFT PR !8072712, 86928bb)
• We've worked around a miscompilation in Visual Studio 2022 Update 4 that results in an out-of-bounds read (MSFT PR !8189936, 3c10444)
• wpf: it is no longer possible to call WriteString with a null terminal instance (#14515)
• wpf: It is now no longer possible to resize the terminal down to 0x0 (#14467)

Code Hygiene

Dependency Updates

brought to you by @AtariDreams

• IntervalTree.h (#14148)
• jsoncpp 1.9.3 => 1.9.5 (#14122)
• libpopcnt => 2.5 (#14140)
• XAML => 2.7.3 (#14123)

Windows Terminal Preview v1.16.3463.0 and v1.16.3464.0

Finally, a servicing update for our beloved Preview users! Sorry we left you on read for so long... but we think you'll like the changes in this update. Hope they're worth the wait!

Windows Terminal v1.16.346{3,4}.0 contain the following backports from https://github.com/microsoft/terminal/tree/main:

Changes

• Vintage transparency now works on Windows 10! Turn off useAcrylic to use it! (#14481)
• You can now configure whether you are warned before you close more than one tab (#14419) (thanks @leejy12!) (with wording improvements (#14473) thanks to @crazo7924!)
• Multiple changes to the new text rendering engine:
  • We will now attempt to better scale block and box drawing glyphs (#14099)
  • It will no longer crash with a heap overflow when presented with a malformed DBCS sequence (#14275)
  • We've adjusted how glyphs are scaled when they are way outside their bounding boxes in poorly-behaved fonts (#14085)
• We've started collecting information on how often FTCS marks and themes are used (#14356)
• We've tweaked the layout of the color schemes page to address some issues on Windows 10 (#14223)
• Using the mouse wheel to turn off transparency will now disable the acrylic material effect (#14193) (thanks @JerBast!)

Bug Fixes

• 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) REMOTE CODE EXECUTION CVE-2022-44702
  • OSC 8 URIs will be limited to 2MB in length, following iTerm2 (and only 1024 bytes will be displayed in the tooltip) (#14198)
• We will no longer leak OpenConsole processes when they're running a Visual Studio Developer Shell (#14160)
• experimental.useBackgroundImageForWindow has 50% fewer rendering bugs! (#14456)
• We will no longer clip the progress ring in tab when the tab title is too long (#14167) (thanks @JonathanMeier!)
• START /MAX should now more reliably maximize the Terminal window when Terminal is set as the default console host (#14222)
• --pos will now override the "center on launch" setting when specified on the command line (#14229) (thanks @ianjoneill!)
• Bracketed paste, forced titles, and the default cursor shape are no longer randomly initialized (#14345)
  • This fixes an issue where pasted text would occasionally be incorrectly mangled (as opposed to correctly mangled...)
• RIS will no longer utterly tank Terminal's ability to handle C1 control characters (#13969) (thanks @j4james!)
• Console applications will now be correctly identified as the owners of their associated "pseudo-console" window (#14196)
• Ctrl+C will now skip any currently-playing DECPS sounds (thanks @dgl for reporting) (#14214)
• Applications should more reliably receive close signals when you close a tab, and we will no longer unceremoniously terminate their console sessions (#14282)
• 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)
• intenseTextStyle is now included properly in the JSON schema (whoops) (#14210) (thanks @neersighted!)
• JSON Schema: startingDirectory is now correctly identified as supporting null (#14408)

Accessibility & Usability

• Alt+Space will now open the system menu in the Settings UI and Command Palette (#14221)
• Text boxes in the settings UI have been made more discoverable by screen readers (#14178)
• There will no longer no longer not be redundant tooltips in the Settings UI (#14244)
• The WPF control now supports accessibility notifications (#14097)
• The Settings UI title/breadcrumb bar is now readable by screen readers (#14180)

Reliability

• 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 one source of deadlocks in windowing management for console applications (such as hanging when they're exiting...) (#14463)
• Launching thousands of instances of cmd.exe back to back will no longer take down your console session (MSFT PR !8072712, 86928bb)
• We've worked around a miscompilation in Visual Studio 2022 Update 4 that results in an out-of-bounds read (MSFT PR !8189936, 3c10444)
• wpf: it is no longer possible to call WriteString with a null terminal instance (#14515)
• wpf: It is now no longer possible to resize the terminal down to 0x0 (#14467)

Code Hygiene

• ConsoleProcessList has been given some love and modernized to improve some of our ConPTY infrastructure (#14421)

Dependency Updates

brought to you by @AtariDreams

• IntervalTree.h (#14148)
• jsoncpp 1.9.3 => 1.9.5 (#14122)
• libpopcnt => 2.5 (#14140)
• XAML => 2.7.3 (#14123)

Windows Terminal v1.15.2874 and v1.15.2875

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) REMOTE CODE EXECUTION CVE-2022-44702
  • 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!)

Windows Terminal Preview v1.16.264

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)

Windows Terminal Preview v1.16.252

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.

Windows Terminal v1.15.252

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:

• Windows Terminal Preview v1.15.228
• Windows Terminal Preview v1.15.200
• Windows Terminal Preview v1.15.186

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.

Windows Terminal Preview v1.15.228

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

Windows Terminal v1.14.228

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)

Windows Terminal Preview v1.15.200

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 ™️ 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)

Windows Terminal v1.14.196

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 ™️ 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)