Windows Terminal v1.15.3465.0 and v1.15.3466.0 #14555
DHowett
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
v1.15.3465.0 (Windows 10) and v1.15.3466.0 (Windows 11) are servicing updates to Windows Terminal Stable v1.15.
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 thatyou 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
useAcrylic
to use it! (Enable vintage opacity on Windows 10 #14481)Bug Fixes
RIS
will no longer utterly tank Terminal's ability to handleC1
control characters (Make sure Terminal state machine always accepts C1 controls #13969) (thanks @j4james!)DECPS
sounds (thanks @dgl for reporting) (Skip DECPS/MIDI output on Ctrl+C/Break #14214)startingDirectory
is now correctly identified as supportingnull
([schema] Update allowed types for startingDirectory #14408)Accessibility & Usability
Reliability
cmd.exe
back to back will no longer take down your console session (MSFT PR !8072712, 86928bb)WriteString
with a null terminal instance (Added null check before rendering a string from the terminal connection #14515)Code Hygiene
Dependency Updates
brought to you by @AtariDreams
This discussion was created from the release Windows Terminal v1.15.3465.0 and v1.15.3466.0.
Beta Was this translation helpful? Give feedback.
All reactions