Windows Terminal Preview 1.13.1073 for Windows 10 and Windows 11


  • Staff
This is a servicing release to fix a number of big issues in 1.13 preview.

Changes​

This version of Windows Terminal is now 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 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.

Bug Fixes​

Usability​

  • Terminal can once again be configured as a startup application, and can be detected by tools like PowerToys (#12491)
  • We are once again usable on N (non-media) SKUs of Windows (#12463)
  • 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!)
  • Displaying multiple dialogs will no longer punch a giant hole in the Terminal (???) (#12625) (#12517)
  • You spoke up about the scroll bars being WAY TOO THIN, so we chonked them up (#12608)
  • 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?

Appearance​

  • We've improved the contrast of the tab strip (#12635) (#12529)
  • Our iconography has been updated to the Windows 11 style (#12469)
  • We have given the issue where acrylic in the titlebar looked weird the heave-ho (#12460)
  • Good good new UI fonts have been enabled (Segoe UI Variable) (#12462)

Accessibility​

  • Terminal now announces newly-printed text to any attached screen reader (#12358)
  • When you delete a profile, we will re-focus the delete button automatically (#12558)
  • Command palette search now tries to announce the number of results to the screen reader (#12429)

Reliability​

  • We won't crash any longer if you give us a command line that is a directory (#12538) (thanks @ianjoneill!)
  • Fixed a crash setting the hotkey during teardown (#12580)
  • Fixed a different pair of crashes, also likely related to default terminal handoff (#12666)
  • ScrollConsoleScreenBuffer no 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)

Rendering​

  • Font axes/features once again work across a DPI change (#12492)
  • AtlasEngine: Fix ConstBuffer invalidation for background color changes (#12667)
  • AtlasEngine: Fix inverted cursor alpha (#12548)
  • On Windows 10, you should see fewer "couldn't find Cascadia Mono, even though it is RIGHT NEXT TO US" dialogs (#12554)


Source:

 

Attachments

  • windows_terminal_pre.png
    windows_terminal_pre.png
    4.2 KB · Views: 0
Back
Top Bottom