windows terminal don&#39;t open from Win + X menù #16499

@ThemisterNaim commented on GitHub (Jan 25, 2022):

yes

@ThemisterNaim commented on GitHub (Jan 25, 2022): yes

claunia commented

@ThemisterNaim commented on GitHub (Jan 25, 2022):

nice bot by the way

@ThemisterNaim commented on GitHub (Jan 25, 2022): nice bot by the way

claunia commented

@zadjii-msft commented on GitHub (Jan 25, 2022):

Huh. That's definitely unexpected. Have you tried rebooting since re-installing the Terminal? Maybe there's some package catalog data stuck in the cache that might just go away with a reboot.

By any chance, have you messed with the permissions on C:\Program Files\WindowsApps? This sounds like #12204 et. al.

@zadjii-msft commented on GitHub (Jan 25, 2022): Huh. That's definitely unexpected. Have you tried rebooting since re-installing the Terminal? Maybe there's some package catalog data stuck in the cache that might just go away with a reboot. By any chance, have you messed with the permissions on `C:\Program Files\WindowsApps`? This sounds like #12204 et. al.

claunia commented

@ThemisterNaim commented on GitHub (Jan 25, 2022):

no, i haven't messed windows apps (at least i haven't messed with windowsapps\windowsTerminal😂).
tomorrow i will try to reinstall agan.

@ThemisterNaim commented on GitHub (Jan 25, 2022): no, i haven't messed windows apps (at least i haven't messed with windowsapps\windowsTerminal😂). tomorrow i will try to reinstall agan.

claunia commented

@ThemisterNaim commented on GitHub (Jan 25, 2022):

nope, i reinstalled.
and, like before, it won't open, and (like before) if you wan't to open wt by win + x like an admin, the security request appear; but than it doesn't do anithing

@ThemisterNaim commented on GitHub (Jan 25, 2022): nope, i reinstalled. and, like before, it won't open, and (like before) if you wan't to open wt by win + x like an admin, the security request appear; but than it doesn't do anithing

claunia commented

@ThemisterNaim commented on GitHub (Jan 26, 2022):

@zadjii-msft, so... what is the problem?

@ThemisterNaim commented on GitHub (Jan 26, 2022): @zadjii-msft, so... what is the problem?

claunia commented

@zadjii-msft commented on GitHub (Jan 26, 2022):

If I knew, I'd tell you 😉

I'm gonna try reaching out to the App Execution Alias team to see if they have more guidance here. If the Terminal can be launched just fine from the Start Menu, but specifically wt.exe doesn't work^[1], then there's something outside our control that's going wrong that we'll need some help figuring out.

Usually toggling the app execution alias in the Settings app should fix this. Worst case, repairing the app via the settings app should also help. But for some reason those don't seem to help everyone, so we need to figure out what's wrong when those don't work.

In the meantime, can you share the output of icacls "C:\Program Files\WindowsApps" (from an admin shell?) Filing feedback on "Developer Platform > Desktop Bridge" might also help get some traces to the folks that own this.

Correct WindowsApps permissions

\Program Files\WindowsApps NT SERVICE\TrustedInstaller:(F)
                           NT SERVICE\TrustedInstaller:(OI)(CI)(IO)(F)
                           S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204:(RX)
                           S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204:(OI)(CI)(IO)(GR,GE)
                           NT AUTHORITY\SYSTEM:(F)
                           NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(F)
                           BUILTIN\Administrators:(CI)(RX)
                           NT AUTHORITY\LOCAL SERVICE:(OI)(CI)(RX)
                           NT AUTHORITY\NETWORK SERVICE:(OI)(CI)(RX)
                           NT AUTHORITY\RESTRICTED:(OI)(CI)(RX)
                           BUILTIN\Users:(Rc,S,RD,REA,X,RA)

As a matter of cross-linking:

#9452 is our bucket for "the permissions are wrong on WindowsApps, and that will break wt.exe
#10149, #12249 and #12204 all seem to be the same "none of the above fixed it" issues. VERY good chance I de-dupe these all.

^[1]: The Win+X menu is also powered by wt.exe on builds above 22000.490. Before that, it only used Windows Terminal stable. If you only have Windows Terminal Preview installed, that won't work right below that build.

@zadjii-msft commented on GitHub (Jan 26, 2022): If I knew, I'd tell you 😉 I'm gonna try reaching out to the App Execution Alias team to see if they have more guidance here. If the Terminal can be launched just fine from the Start Menu, but specifically `wt.exe` doesn't work<sup>[1]</sup>, then there's something outside our control that's going wrong that we'll need some help figuring out. Usually toggling the app execution alias in the Settings app should fix this. Worst case, repairing the app via the settings app should also help. But for some reason those don't seem to help everyone, so we need to figure out what's wrong when those don't work. In the meantime, can you share the output of `icacls "C:\Program Files\WindowsApps"` (from an admin shell?) Filing feedback on "Developer Platform > Desktop Bridge" might also help get some traces to the folks that own this. ![image](https://user-images.githubusercontent.com/18356694/151219053-b5a4b199-9c15-42f6-bedc-8bfa86ca888a.png) <details> <summary>Correct WindowsApps permissions</summary> ``` \Program Files\WindowsApps NT SERVICE\TrustedInstaller:(F) NT SERVICE\TrustedInstaller:(OI)(CI)(IO)(F) S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204:(RX) S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204:(OI)(CI)(IO)(GR,GE) NT AUTHORITY\SYSTEM:(F) NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(F) BUILTIN\Administrators:(CI)(RX) NT AUTHORITY\LOCAL SERVICE:(OI)(CI)(RX) NT AUTHORITY\NETWORK SERVICE:(OI)(CI)(RX) NT AUTHORITY\RESTRICTED:(OI)(CI)(RX) BUILTIN\Users:(Rc,S,RD,REA,X,RA) ``` </details> As a matter of cross-linking: * #9452 is our bucket for "the permissions are wrong on WindowsApps, and that will break `wt.exe` * #10149, #12249 and #12204 all seem to be the same "none of the above fixed it" issues. VERY good chance I de-dupe these all. <sup>[1]</sup>: The Win+X menu is also powered by `wt.exe` on builds above 22000.490. Before that, it **only** used Windows Terminal stable. If you only have Windows Terminal Preview installed, that won't work right below that build.

claunia commented

@ThemisterNaim commented on GitHub (Jan 27, 2022):

In the meantime, can you share the output of icacls "C:\Program Files\WindowsApps" (from an admin shell?) Filing feedback on "Developer Platform > Desktop Bridge" might also help get some traces to the folks that own this.

here you go

C:\Program Files\WindowsApps NT SERVICE\TrustedInstaller:(F)
                             NT SERVICE\TrustedInstaller:(OI)(CI)(IO)(F)
                             S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204:(RX)
                             S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204:(OI)(CI)(IO)(RX)
                             NT AUTHORITY\SYSTEM:(F)
                             NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(F)
                             BUILTIN\Administrators:(CI)(RX)
                             NT AUTHORITY\SERVIZIO LOCALE:(OI)(CI)(RX)
                             NT AUTHORITY\SERVIZIO DI RETE:(OI)(CI)(RX)
                             NT AUTHORITY\RESTRIZIONI:(OI)(CI)(RX)
                             BUILTIN\Users:(Rc,S,RD,REA,X,RA)

@ThemisterNaim commented on GitHub (Jan 27, 2022): > In the meantime, can you share the output of `icacls "C:\Program Files\WindowsApps"` (from an admin shell?) Filing feedback on "Developer Platform > Desktop Bridge" might also help get some traces to the folks that own this. here you go ``` C:\Program Files\WindowsApps NT SERVICE\TrustedInstaller:(F) NT SERVICE\TrustedInstaller:(OI)(CI)(IO)(F) S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204:(RX) S-1-15-3-1024-3635283841-2530182609-996808640-1887759898-3848208603-3313616867-983405619-2501854204:(OI)(CI)(IO)(RX) NT AUTHORITY\SYSTEM:(F) NT AUTHORITY\SYSTEM:(OI)(CI)(IO)(F) BUILTIN\Administrators:(CI)(RX) NT AUTHORITY\SERVIZIO LOCALE:(OI)(CI)(RX) NT AUTHORITY\SERVIZIO DI RETE:(OI)(CI)(RX) NT AUTHORITY\RESTRIZIONI:(OI)(CI)(RX) BUILTIN\Users:(Rc,S,RD,REA,X,RA) ```

claunia commented

@zadjii-msft commented on GitHub (Jan 27, 2022):

Hmm. You're on https://github.com/microsoft/terminal/releases/tag/v1.11.3471.0, which should be a stable build, so you're not hitting the same thing as #12204...

@zadjii-msft commented on GitHub (Jan 27, 2022): Hmm. You're on https://github.com/microsoft/terminal/releases/tag/v1.11.3471.0, which should be a stable build, so you're not hitting the same thing as #12204...

claunia commented

@ThemisterNaim commented on GitHub (Jan 30, 2022):

if this information could help you; if I try to run wt.exe by win + R it don't work, but, if I open windows terminal or powershell or cmd, and i write wt.exe, those programs will open windows terminal

@ThemisterNaim commented on GitHub (Jan 30, 2022): if this information could help you; if I try to run wt.exe by win + R it don't work, but, if I open windows terminal or powershell or cmd, and i write wt.exe, those programs will open windows terminal

claunia commented

@ThemisterNaim commented on GitHub (Feb 1, 2022):

is there anything I can to for help?

@ThemisterNaim commented on GitHub (Feb 1, 2022): is there anything I can to for help?

claunia commented

@zadjii-msft commented on GitHub (Feb 12, 2022):

if this information could help you; if I try to run wt.exe by win + R it don't work, but, if I open windows terminal or powershell or cmd, and i write wt.exe, those programs will open windows terminal

That sure is weird. I feel like there was one recently where the Run PATH was different than the one that's used by the Start Menu for some reason.
If you open Command Prompt (cmd.exe) from Start Menu and from run, what's the output of echo %PATH% in each?

I am at a bit of a loss here 😕

@zadjii-msft commented on GitHub (Feb 12, 2022): > if this information could help you; if I try to run wt.exe by win + R it don't work, but, if I open windows terminal or powershell or cmd, and i write wt.exe, those programs will open windows terminal That sure is weird. I feel like there was one recently where the Run PATH was different than the one that's used by the Start Menu for some reason. If you open Command Prompt (cmd.exe) from Start Menu and from run, what's the output of `echo %PATH%` in each? I am at a bit of a loss here 😕

claunia commented

@ThemisterNaim commented on GitHub (Feb 13, 2022):

from cmd:
C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files (x86)\Common Files\Acronis\SnapAPI\;C:\Program Files (x86)\Common Files\Acronis\VirtualFile\;C:\Program Files (x86)\Common Files\Acronis\VirtualFile64\;C:\Program Files\dotnet\;C:\Program Files (x86)\PowerShell\7\;C:\Users\Naim\AppData\Local\Microsoft\WindowsApps;

@ThemisterNaim commented on GitHub (Feb 13, 2022): from cmd: `C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files (x86)\Common Files\Acronis\SnapAPI\;C:\Program Files (x86)\Common Files\Acronis\VirtualFile\;C:\Program Files (x86)\Common Files\Acronis\VirtualFile64\;C:\Program Files\dotnet\;C:\Program Files (x86)\PowerShell\7\;C:\Users\Naim\AppData\Local\Microsoft\WindowsApps;`

claunia commented

@zadjii-msft commented on GitHub (Feb 14, 2022):

Sorry, more specifically:

what's the output when starting cmd from the start menu?
what's the output when starting cmd from the run dialog?

@zadjii-msft commented on GitHub (Feb 14, 2022): Sorry, more specifically: * what's the output when starting cmd from the start menu? * what's the output when starting cmd from the run dialog?

claunia commented

@ThemisterNaim commented on GitHub (Feb 15, 2022):

from start menu:

C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files (x86)\Common Files\Acronis\SnapAPI\;C:\Program Files (x86)\Common Files\Acronis\VirtualFile\;C:\Program Files (x86)\Common Files\Acronis\VirtualFile64\;C:\Program Files\dotnet\;C:\Program Files (x86)\PowerShell\7\;C:\Users\Naim\AppData\Local\Microsoft\WindowsApps;

from run:

C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files (x86)\Common Files\Acronis\SnapAPI\;C:\Program Files (x86)\Common Files\Acronis\VirtualFile\;C:\Program Files (x86)\Common Files\Acronis\VirtualFile64\;C:\Program Files\dotnet\;C:\Program Files (x86)\PowerShell\7\;C:\Users\Naim\AppData\Local\Microsoft\WindowsApps;

@ThemisterNaim commented on GitHub (Feb 15, 2022): from start menu: ``` C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files (x86)\Common Files\Acronis\SnapAPI\;C:\Program Files (x86)\Common Files\Acronis\VirtualFile\;C:\Program Files (x86)\Common Files\Acronis\VirtualFile64\;C:\Program Files\dotnet\;C:\Program Files (x86)\PowerShell\7\;C:\Users\Naim\AppData\Local\Microsoft\WindowsApps; ``` from run: ``` C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files (x86)\Common Files\Acronis\SnapAPI\;C:\Program Files (x86)\Common Files\Acronis\VirtualFile\;C:\Program Files (x86)\Common Files\Acronis\VirtualFile64\;C:\Program Files\dotnet\;C:\Program Files (x86)\PowerShell\7\;C:\Users\Naim\AppData\Local\Microsoft\WindowsApps; ```

claunia commented

@zadjii-msft commented on GitHub (Feb 15, 2022):

Butts. Those are exactly the same. Okay yep, I dunno what's up here.

✅ it works from the Start menu
✅ it works for wt.exe from another shell
❌ it DOESN'T work for wt.exe from the Run dialog
❌ it DOESN'T work from Win+X

by all accounts, that doesn't make sense.

if you wan't to open wt by win + x like an admin, the security request appear; but than it doesn't do anithing

What does the UAC prompt there say is requesting to run? Presumably Windows Terminal, but what's the fill path when you click "Show More Details"? (You may need a another device to take a screenshot)

@zadjii-msft commented on GitHub (Feb 15, 2022): Butts. Those are exactly the same. Okay yep, I dunno what's up here. * ✅ it works from the Start menu * ✅ it works for `wt.exe` from another shell * ❌ it DOESN'T work for `wt.exe` from the Run dialog * ❌ it DOESN'T work from Win+X by all accounts, that doesn't make sense. > if you wan't to open wt by win + x like an admin, the security request appear; but than it doesn't do anithing What does the UAC prompt there say is requesting to run? Presumably Windows Terminal, but what's the fill path when you click "Show More Details"? (You may need a another device to take a screenshot) ![image](https://user-images.githubusercontent.com/18356694/154108235-214b8a92-04f0-485b-bd9d-86e376801cd0.png)

claunia commented

@ThemisterNaim commented on GitHub (Feb 15, 2022):

@ThemisterNaim commented on GitHub (Feb 15, 2022): ![20220215_175138](https://user-images.githubusercontent.com/96649980/154109908-75cb02e2-5800-497b-b68e-916c3c905495.jpg)

claunia commented

@zadjii-msft commented on GitHub (Feb 28, 2022):

MSFT:37730421, MSFT:38299191 internally

@zadjii-msft commented on GitHub (Feb 28, 2022): MSFT:37730421, MSFT:38299191 internally

claunia commented

2026-01-31 05:14:01 +00:00

@ThemisterNaim commented on GitHub (Mar 2, 2022):

MSFT:37730421, MSFT:38299191 internally

what?

@ThemisterNaim commented on GitHub (Mar 2, 2022): > [MSFT:37730421](https://task.ms/37730421), [MSFT:38299191](https://task.ms/38299191) internally what?

claunia commented

@zadjii-msft commented on GitHub (Mar 2, 2022):

Sorry, you're seeing a bit of a "how the sausage is made" 😅 Those are some internal bug numbers for what appears to be the same issue. I was just leaving them here as notes. MSFT:38143400 too was another one I found, which I've got assigned to the Taskbar team right now to help investigate.

@zadjii-msft commented on GitHub (Mar 2, 2022): Sorry, you're seeing a bit of a "how the sausage is made" 😅 Those are some internal bug numbers for _what appears to be_ the same issue. I was just leaving them here as notes. MSFT:38143400 too was another one I found, which I've got assigned to the Taskbar team right now to help investigate.

claunia commented

2026-01-31 05:14:01 +00:00

@hedw1gP commented on GitHub (Apr 25, 2022):

Won't open. My version is 1.12.10983.0. Clicking on "Windows Terminal", nothing; Clicking on "Windows Terminal (Admin)", a UAC pops up, click Yes, nothing appears.

And by the way, now it tells me wt.exe is an unsigned application. It doesn't show "Verified Publisher: Microsoft Corporation".

Comes from a fresh install Windows 11 iso downloaded yesterday. Did not touch WindowsApps permissions.

Running wt from any CMD, Powershell and Windows Terminal (CMD/Powershell) will actually open up a new Windows Terminal window no problem.

@hedw1gP commented on GitHub (Apr 25, 2022): Won't open. My version is 1.12.10983.0. Clicking on "Windows Terminal", nothing; Clicking on "Windows Terminal (Admin)", a UAC pops up, click Yes, nothing appears. And by the way, now it tells me wt.exe is an unsigned application. It doesn't show "Verified Publisher: Microsoft Corporation". Comes from a fresh install Windows 11 iso downloaded yesterday. Did not touch WindowsApps permissions. Running `wt` from any CMD, Powershell and Windows Terminal (CMD/Powershell) will actually open up a new Windows Terminal window no problem. ![image](https://user-images.githubusercontent.com/11908157/165116045-0ff64de0-ae0d-4865-a367-9512a985770d.png)

claunia commented

2026-01-31 05:14:01 +00:00

@himangshusingh commented on GitHub (May 17, 2022):

even i'm facing the same problem as @ThemisterNaim , after upgrading to win 11 the terminal option in win+X menu is not opening terminal, plus running wt from win+R is also not working,
i tried reset and repair in the settings>apps>Terminal
i even tried uninstalling and then installing

nothing seems to work in this case

@himangshusingh commented on GitHub (May 17, 2022): even i'm facing the same problem as @ThemisterNaim , after upgrading to win 11 the terminal option in win+X menu is not opening terminal, plus running wt from win+R is also not working, i tried reset and repair in the settings>apps>Terminal i even tried uninstalling and then installing nothing seems to work in this case

claunia commented

2026-01-31 05:14:02 +00:00

@hedw1gP commented on GitHub (May 17, 2022):

@reyan1357 take a shot at this, it works for me

https://github.com/microsoft/terminal/issues/7081#issuecomment-1065833836

@hedw1gP commented on GitHub (May 17, 2022): @reyan1357 take a shot at this, it works for me https://github.com/microsoft/terminal/issues/7081#issuecomment-1065833836

claunia commented

2026-01-31 05:14:02 +00:00

@himangshusingh commented on GitHub (May 17, 2022):

@reyan1357 take a shot at this, it works for me

#7081 (comment)

yeahh, it workedd after so many months, thanks a lot mann <3

@himangshusingh commented on GitHub (May 17, 2022): > @reyan1357 take a shot at this, it works for me > > [#7081 (comment)](https://github.com/microsoft/terminal/issues/7081#issuecomment-1065833836) yeahh, it workedd after so many months, thanks a lot mann <3

claunia commented

@DanTheMan827 commented on GitHub (Jun 5, 2022):

I'm experiencing the same issue, but this is on a fresh windows reset with no files kept.

I'm hesitant on messing with the Windows Store ACLs because that's the reason that I re-installed in the first place.

@DanTheMan827 commented on GitHub (Jun 5, 2022): I'm experiencing the same issue, but this is on a fresh windows reset with no files kept. I'm hesitant on messing with the Windows Store ACLs because that's the reason that I re-installed in the first place.

claunia commented

@zadjii-msft commented on GitHub (Jul 28, 2022):

Internal bugs show that this was fixed in build number 22591, or maybe 25091. Hard to tell how those numbers line up with the 22000.xyz series of releases. I suspect this is fixed in Insiders builds of Windows, but I have no idea how long before this rolls out more broadly.

@zadjii-msft commented on GitHub (Jul 28, 2022): Internal bugs show that this was fixed in build number 22591, or maybe 25091. Hard to tell how those numbers line up with the 22000.xyz series of releases. I suspect this is fixed in Insiders builds of Windows, but I have no idea how long before this rolls out more broadly.

claunia commented

@maxwowpow commented on GitHub (Apr 25, 2024):

from other terminal (clink/ps)
- admin+nonadmin: wt.exe - crashing.
win+x/win+r:
- admin OK 1 tab
- admin more tabs -> crash
- non admin -> crash
uac active, without background darkening

@maxwowpow commented on GitHub (Apr 25, 2024): - from other terminal (clink/ps) - admin+nonadmin: `wt.exe` - crashing. - win+x/win+r: - admin OK 1 tab - admin more tabs -> crash - non admin -> crash - uac active, without background darkening

claunia commented