v1.15.3465.0 (Windows 10) and v1.15.3466.0 (Windows 11) are servicing updates to Windows Terminal Stable v1.15.
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
GitHub - microsoft/terminal: The new Windows Terminal and the original Windows console host, all in the same place!).
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
github.com
