Cannot Run terminal by double-clicking the app or running the command

[0warning0error]

Windows Terminal version

1.12.10982.0

Windows build number

10.0.19044.0

Other Software

No response

Steps to reproduce

press win buttom and input wt to run

or double-click the exe file directly

Expected Behavior

here comes a terminal

Actual Behavior

nothing happens.
but if I open it in Microsoft Store, it comes out as expected .

[qhzy1999]

I have the same problem and don't know what to do

[0warning0error]

I have the same problem and don't know what to do

在微软商店里打开，或者在explorer里右键点击用终端打开。但很麻烦

[zadjii-msft]

Hmm. We see this from time to time

• there was another one like this just filed in Windows Terminal crashes immmediately when launched from Win+X menu #13108.
• Another similar report in wt doesn't work anymore #12767.
• Open alias "wt" have unexpected behavior. #12545 only has to do with the env being different, so that's definitely different.
• windows terminal don't open from Win + X menù #12249 is similar - the win+x menu should be powered by wt.exe

I really need to come up with a diagnostic script that can just run all these test cases for us. It's possible the wt.exe alias has gotten all messed up, but usually a uninstall, reboot the PC, and re-install the Terminal would fix that. Perhaps the permissions on WindowsApps is messed up. That would be super bad, and is harder to fix. Maybe it's simply your path is in the wrong order.

Like I said, we really need a diagnostic script for these scenarios.

[0warning0error]

Hmm. We see this from time to time

• there was another one like this just filed in Windows Terminal crashes immmediately when launched from Win+X menu #13108.
• Another similar report in wt doesn't work anymore #12767.
• Open alias "wt" have unexpected behavior. #12545 only has to do with the env being different, so that's definitely different.
• windows terminal don't open from Win + X menù #12249 is similar - the win+x menu should be powered by wt.exe

I really need to come up with a diagnostic script that can just run all these test cases for us. It's possible the wt.exe alias has gotten all messed up, but usually a uninstall, reboot the PC, and re-install the Terminal would fix that. Perhaps the permissions on WindowsApps is messed up. That would be super bad, and is harder to fix. Maybe it's simply your path is in the wrong order.

Like I said, we really need a diagnostic script for these scenarios.

I tried to re-install the APP as you said but nothing changed. It's weird that I can run it by CMD or Powershell.
It seems that you have trouble debugging and testing it. Maybe it is caused by OS itself?

[notis58]

I have the same problem
Is there any progress on it?

[lhecker]

I believe this was fixed as part of #13193.
/dup #13193

[ghost]

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!