Windows Terminal v1.17.11461.0

[DHowett]

Enjoy this quick bug fix release!

• The "Developer Command Prompt" profiles are no longer totally busted (Fix VS profile command generation #15439)
• Terminal no longer crashes when you have focusFollowMouse mode enabled (Fix focusFollowMouse #15420)

---

Asset Hashes

• Microsoft.WindowsTerminal_1.17.11461.0_8wekyb3d8bbwe.msixbundle
  • SHA256 E3A5A581F2A404D9D97F6826890BE9FD7BFC827498035D6C45E1C12F9D2D4E8F
• Microsoft.WindowsTerminal_1.17.11461.0_8wekyb3d8bbwe.msixbundle_Windows10_PreinstallKit.zip
  • SHA256 2BB87BC4EA358F58D1F1BF69486B133DB09EC509BF07A7BD740F9ABBE2F25CB5
• Microsoft.WindowsTerminal_1.17.11461.0_arm64.zip
  • SHA256 2CB999CC7AF12245E08D57D5472571C126A411C38E20F8D66E2110650FD0D757
• Microsoft.WindowsTerminal_1.17.11461.0_x64.zip
  • SHA256 F2B1539649D17752888D7944F97D6372F8D48EB1CEB024501DF8D8E9D3352F25
• Microsoft.WindowsTerminal_1.17.11461.0_x86.zip
  • SHA256 6A052D0501680EEADF7971B72734AC0084ECBD65B0A420E3C49014BE1860E070

---

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

[evilgordita]

Are there any potential reasons why Terminal wouldn't update from the store? I'm still on 1.16.10261.0 on both of my Windows 10 machines (Pro and Home respectively). I just now tried uninstalling and installing fresh from the store and it's still giving me 1.16.10261.0. I don't have the preview installed. Is delayed rollout a thing or is something broken with the release in the store?

I can download the GitHub release but I'm not too fussed over it right now.

[DHowett]

Thanks for asking! We're doing a delayed rollout for all Stable channel users, just to make sure we don't have a terrible bug that's gonna break a few million machines 😄

[tusharsnx]

Oh I just checked that my terminal is also on v1.16, I thought we are on v1.15 as the store page is still showing v1.15 in 'What's new in this version' section. I think that needs to be updated or completely removed to not cause any confusion 🤦‍♂️

[skst]

@tusharsnn, if you scroll down farther on the Store page, it displays the Installed version as 1.16.10262.0. I agree the What's New section could use a little love though. :)

@DHowett, if we download Microsoft.WindowsTerminal_1.17.11461.0_8wekyb3d8bbwe.msixbundle and install it, will it replace the Store version and still allow us to install the next upgrade from the Store or will it install side-by-side with the Store version?

[DHowett]

@DHowett, if we download Microsoft.WindowsTerminal_1.17.11461.0_8wekyb3d8bbwe.msixbundle and install it, will it replace the Store version and still allow us to install the next upgrade from the Store or will it install side-by-side with the Store version?

@skst Yep, this will work as expected! It will upgrade the store-installed version, and the store will upgrade over it next time there's an even newer release.

[DHowett]

This version is now officially rolling out to 100% of users!

[melanchall]

Hello @DHowett,

I've downloaded the Microsoft.WindowsTerminal_1.17.11461.0_8wekyb3d8bbwe.msixbundle file but I can't install the Terminal on my Windows 10 (22H2 / 19045.2965). The error is

This app package is not supported for installation by App Installer because it uses certain restricted capabilities.

Can you please help with the installations? Is Win 10 supported?

Thank you,
Max

[DHowett]

If you download the "Preinstallation Kit" from our Releases page, it comes with all of the dependencies you will need. :)

[DHowett]

@melanchall sorry about that error. You should be able to install it using Add-AppxPackage as noted above.

[j0le]

If you download the "Preinstallation Kit" from our Releases page, it comes with all of the dependencies you will need. :)

Thank you, @DHowett! That's a good tip. Next time I will know and try that.

[melanchall]

Thanks @DHowett, that works! Just a small question: so you won't provide a simple msixbundle file that can be installed by double click on Win 10 anymore?

[DHowett]

We tested this out before shipping it on Windows 10, and it worked fine for simple double-click install! We believe that it requires the newest version of the "Desktop App Installer," which is the package that provides the UI you see when double-clicking msixbundle files. (It also contains winget, which is perhaps more interesting.)

[jabaya91]

Howdy ya'll,

I was having some trouble with my windows terminal so I ended up uninstalling it(used REVO) and reinstalling it again to this version. I am running into two issues. One of which is wt command not opening up the terminal itself. This may have something to do with how it is named. Shows it to be "WT.exe" on my work computer; at home the application is named just "wt" Having trouble renaming it and im sure it just needs some permissions to be tweaked, but if you have any insight great. Secondly, my main issue, i cannot open admin instances from within the console. The UAC comes up as unknown program. I click allow and nothing happens. I can open up the whatever console in admin itself but not from within the terminal. Thank you in advance!

[zadjii-msft]

Sorry, just seeing this now.

Please for the love of god, don't try and fuck with the permissions for the app package. Others have tried to before, and oftentimes it ends up with a machine in a permenantly busted state. The app package permissions are very sensitive.

The UAC comes up as unknown program

That's #12357, which is the internal bug MSFT:37540496. I think that was fixed and being serviced, but it's unclear which versions of Windows exactly have that fix.

i cannot open admin instances from within the console ... I click allow and nothing happens

Sounds a bit like #15576

[m0rph0]

Hi Dustin, can you have a look at Pull request 108350 for Windows Terminal 1.17, it's been waiting for actions since May 29th.. Thanks!

[zadjii-msft]

Sorry... which PR? We're only in the 15xxx range of number of total issues 😅

[m0rph0]

microsoft/winget-pkgs#108350

[zadjii-msft]

That looks like it's still blocked on the upstream microsoft/winget-cli#163.