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:
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
wtunder 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 anInvalid Parametererror) (#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 forwsl.exe(#12050) (thanks @LuanVSO!)- Application-controlled titles will be sanitized for control sequences even if they are set with the
SetConsoleTitleAPI (#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.