Microsoft released a new version of Windows Terminal 1.12.1073. As in the previous release, there is a Windows 10 version and a separate Windows 11 version available for download.
This is a significant servicing release to fix a number of huge issues in 1.12.
This release was made available to insiders in the Dev and Beta channels on March 25 and will be generally available to everyone once it is considered stable.
Changelog for Windows Terminal 1.12.1073
- Terminal can once again be configured as a startup application, and can be detected by tools like PowerToys (#12491)
- There was a puzzling “Element not found” error during settings loading; there is no longer such an error (#12687)
- Terminal will no longer mix up profiles when it is launched in response to a console application spawning (#12484)
- Formatted copy will now try harder to preserve Unicode charatcers in RTF (#12586) (thanks @ianjoneill!)
- We have replaced the word “Summon” with “Show/Hide” in the command palette for improved localization (#12603)
- Our confidence in the settings UI’s Save button has led to us no longer backing up the settings JSON file (#12652)
- We won’t be deleting the 61,000 backups we did leave on your hard drive, but what’s a couple thousand kilobytes between friends?
- Terminal now announces newly-printed text to any attached screen reader (#12358)
- Command palette search now tries to announce the number of results to the screen reader (#12429)
- We won’t crash any longer if you give us a command line that is a directory (#12538) (thanks @ianjoneill!)
- A crash on launch related to multi-windowing and the default terminal setting has been quashed (subset of #12205)
- Fixed a crash setting the hotkey during teardown (#12580)
- Fixed a different pair of crashes, also likely related to default terminal handoff (#12666)
ScrollConsoleScreenBufferno longer takes the console upstate (#12669)
- Pressing Page Up or Page Down with an empty command palette, which seemed like a reasonable thing to do, was taught to not crash the Terminal (#12528)
- Font axes/features once again work across a DPI change (#12492)