Windows Terminal v1.13.1143 #13156
DHowett
announced in
Announcements
Replies: 3 comments 2 replies
-
The windows 10 msixbundle failed for me (on Windows 10 20H2), with error "App Installer failed to install package dependencies. Ask the developer for package." I've installed the 1.12.10393.0 version and previously fine. |
Beta Was this translation helpful? Give feedback.
1 reply
-
How long before the update pops up in the Store or on winget? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This release brings many of the preview changes in Windows Terminal 1.13 to the Stable channel. Notably:
profile.bellSound
settingNote that the new text rendering engine is not included in this Stable build.
Please see the following release notes for additional details:
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 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 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
RadioButton
s in the settings UI have been replaced withComboBox
es. This gives an added bonus to keyboard and screen reader users, and makes it easier to navigate through and change these settings. (ReplaceRadioButton
expanders withComboBox
es #12833)Interactivity
Settings
trimBlockSelection
global setting now defaults totrue
(Change trimBlockSelection default to true #12737)newTab
actions with a profile index greater than the number of profiles (IgnorenewTab
actions with a profile index greater than the number of profiles #11621)bellSound
is now in the schema (WIP for adding BellSound to schema #13035) (thanks @pizzaz93!)Bug Fixes
commandline
inprofile.defaults
should no longer override thecommandline
s of profiles that specify cmd.exe or powershell.exe. (Fix profile commandlines being overwritten by profile.defaults #12906)Reliability
ProfileVM.DeleteProfile
handler once #13044)This discussion was created from the release Windows Terminal v1.13.1143.
Beta Was this translation helpful? Give feedback.
All reactions