Windows Terminal v1.12.1098

[DHowett]

This release was made available to insiders in the Dev and Beta channels on April 11 and is now generally available.

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 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.

Changes

• The refreshed Windows 11 UI from the 1.13 preview builds is now available in 1.12!

Bug Fixes

Appearance

• Our Maximize/Restore button is now a fine round boi (Round our Maximize button to match ControlsV2 styles #12660)

Accessibility

• The profile list in the Settings UI now offers tooltips for long profile names (Add tooltips for nav items in the SUI #12448)
• We'll automatically focus the window renamer textbox when it opens (Auto-focus window renamer textbox on open #12798)
• High contrast will no longer result in a ridiculous and bad titlebar color (HC A11y - Make sure we have a sensible HC color for the titlebar #12839)
• When you delete a color scheme, we'll move focus back to the color scheme list (Manually focus the scheme dropdown when deleting a scheme #12841)
• When you delete a profile, we will re-focus the delete button automatically (When we delete a profile, focus the delete button automatically #12558)
• Two instances of huge debug log spam with a screen reader connected have been stamped out (Fix exception spam if UIA is running #12698) (Hush a garrulous event from TerminalControl #12723)

Usability

• We've added some text to the color schemes page indicating that it is for editing--not setting--color schemes (Add some disclaimer text to the schemes page #12663)
  • We're working to refine how color schemes are set and edited, so stay tuned for future improvements!
• The retro terminal effect (as well as other shaders) will now work on pre-D3D11 hardware! (DxEngine: Fix shader compilation on pre-D3D11 hardware #12677)
• Terminal will once again render properly when you move between different-DPI displays (Fix engine size not being changed on DPI changes #12713) (Fix engine size not being changed on DPI changes #12749)
• Resizing the window while a background color or underline is displayed will no longer smear it across the whole screen (Manually copy trailing attributes on a resize #12637) plus a fix for a huge crash that PR introduced (Fix DBCS attribute corruption during reflow #12853)
• It took us three releases to get it right, but we've finally solved the issue where we'd punch a hole straight through the Terminal when a dialog appeared (Manually put our ContentDialogs in the tab content, rather than above #12840)

Reliability

• Typing an invalid background image path into the Settings UI will no longer send Terminal to a farm upstate (Adds exception handling of uri creation in profile background image update #11542) (thanks @serd2011!)
• There was an issue on Windows 11 where Terminal would queue up billions of animations while the screen was off; it will now no longer do so (Autocomplete keyframe animations when occluded on Windows 11 #12820)
• We've fixed crashes in ProposeCommandline (Crash on launch - Cache ProposeCommandlineResult locally #12838), Monarch::_GetPID (Remove default_interface from Monarch #12856) and other parts of WT's RPC infrastructure (Try to silently fall back to a local monarch #12825)
• On Windows 10, the settings UI will no longer sometimes crash on close (we've updated to a new build of WinUI 2 for the fix!) (Upgrade WinUI2 to 2.7.1 #12847)

Miscellaneous

• Windows will no longer reject certain Terminal updates/reinstalls due to "differing package content" (Add mp:PhoneIdentity to stop Store from rewriting our packages #12779)
• Fragments can once again override the names of generated profiles (Allow fragments to override the name of new profiles #12627)
• An issue from the 1073 series, where you could not upgrade the bundle using DISM, has been resolved (Force the bundle major version to be over 3000 #12819)
  • As a result, our bundle version is now over three thousand!
• @dmezh contributed some wording changes to the text about transparency/opacity (Inconsistency between 'opacity' and 'transparency' in settings UI #12592) (Fix transparency/opacity inconsistency in help text (#12592) #12727) (thanks!)

---

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

[skycommand]

It appears Windows App Installer mistakenly thinks there is a newer version of 1.12.10983 available. Please note the erroneous 3 at the end of the build number. (Must be 2.)