Windows Terminal v1.12.1073

[DHowett]

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. You can always install the update from this release page or using winget.

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.

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 (Copy localized strings from ContextMenu into the resource root #12491)
• There was a puzzling "Element not found" error during settings loading; there is no longer such an error (Fix "Element not found" error during settings loading #12687)
• Terminal will no longer mix up profiles when it is launched in response to a console application spawning (Fix off-by-one bug in NormalizeCommandLine #12484)
• Formatted copy will now try harder to preserve Unicode charatcers in RTF (Fix RTF generation for Unicode characters #12586) (thanks @ianjoneill!)
• We have replaced the word "Summon" with "Show/Hide" in the command palette for improved localization (Replace Summon with Show/Hide for improved i18n #12603)
• Our confidence in the settings UI's Save button has led to us no longer backing up the settings JSON file (Stop making settings.json backups #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?

Accessibility

• Terminal now announces newly-printed text to any attached screen reader (Use UIA notifications for text output #12358)
• Command palette search now tries to announce the number of results to the screen reader (Update the cmdpal narrator message to include the number of results. #12429)

Reliability

• We won't crash any longer if you give us a command line that is a directory (Don't crash trying to parse a command line that's a directory #12538) (thanks @ianjoneill!)
• A crash on launch related to multi-windowing and the default terminal setting has been quashed (subset of Misc. elevation crash fixes #12205)
• Fixed a crash setting the hotkey during teardown (Fix a crash setting the hotkey during teardown #12580)
• Fixed a different pair of crashes, also likely related to default terminal handoff (Fix a pair of crashes, likely related to defterm #12666)
• ScrollConsoleScreenBuffer no longer takes the console upstate (Fix overflow in Viewport::FromDimensions #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 (Protect the command palette against being paged with no items #12528)

Rendering

• Font axes/features once again work across a DPI change (Fix font axes/features not working on DPI change #12492)

---

This discussion was created from the release Windows Terminal v1.12.1073.

[melanchall]

Hello,

Is all OK with the version?

I have 1.12.10393.0 installed, trying to install new version I get this message:

10732 is obviously greater than 10393 so this looks strange. I suppose there is no 2 last digit in this new release version in fact so real version is 1.12.1073 and 1073 is indeed less than 10393.

Can you please check the version in the installer?

[DHowett]

ALRIGHT, Finally I can come back to you with a solution. I shared a link to the dism bundle in #12816 -- can you try installing the msixbundle from inside it? It's got a weird hashed name, but... eh.

[melanchall]

@DHowett Thanks. Now update available, BUT

This progress is more than hour :( So installation stuck and don't move.

[MOHAMED-EHAB-DEV]

Please tell me how to install the app because microsoft store have a problem

[zadjii-msft]

@Programing-School Please read the README: https://github.com/microsoft/terminal#via-github

[zadjii-msft]

@melanchall @DHowett UHG I hate that that issue is back: https://github.com/microsoft/terminal/issues?q=is%3Aissue+%22installing+required+frameworks%22

You might want to use the Win10 preinstall kit, because that one bundles the framework packages straight up in our msix.

[DanRotaru]

When new win ui (like wt preview) ?

[DHowett]

Depends. We are trying to get this out to people, but we are worried about the impact it's going to have on our users. Do you want the new UI?

[DanRotaru]

yep

[DHowett]

1.12.1098 is rolling out with the Win11 UI

[MilioD]

This release was made available to insiders in the Dev and Beta channels on March 25

I'm in the Windows Insiders Beta channel on OS build 22581.100, but I still have Terminal version 1.12.10393.0. I know it has only been 2 days and that I could get the update through winget. Also I use the Terminal Preview on the latest version already, so it isn't an issue for me. I just want to know if there is some kind of A/B testing going on with the versions because the same thing happened to me with the previous Terminal update which I only received on the 23^rd of March.

[DHowett]

Oh, dang! I apparently only published this to Dev channel. Fixing. 😄

[MilioD]

Sounds good! Thanks a lot for your help with this and all your work on the Terminal.

[DimitriDR]

Note: it is the last installable version on Windows Server (or machines that don't have MS Store) via Add AppxPackage.