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

Closed
opened 2026-01-31 05:41:44 +00:00 by claunia · 7 comments
Owner

Originally created by @0warning0error on GitHub (May 6, 2022).

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 .

Originally created by @0warning0error on GitHub (May 6, 2022). ### 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 .
claunia added the Issue-BugResolution-DuplicateCulprit-Centennial labels 2026-01-31 05:41:45 +00:00
Author
Owner

@qhzy1999 commented on GitHub (May 7, 2022):

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

@qhzy1999 commented on GitHub (May 7, 2022): I have the same problem and don't know what to do
Author
Owner

@0warning0error commented on GitHub (May 7, 2022):

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

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

@0warning0error commented on GitHub (May 7, 2022): > I have the same problem and don't know what to do 在微软商店里打开,或者在explorer里右键点击用终端打开。但很麻烦 ![image](https://user-images.githubusercontent.com/42114116/167236239-cf75c081-9d81-44f7-8546-ca332bad1d29.png) ![image](https://user-images.githubusercontent.com/42114116/167236256-c664c421-5f95-4375-9d32-902700793d8c.png)
Author
Owner

@zadjii-msft commented on GitHub (May 16, 2022):

Hmm. We see this from time to time

  • there was another one like this just filed in #13108.
  • Another similar report in #12767.
  • #12545 only has to do with the env being different, so that's definitely different.
  • #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.

@zadjii-msft commented on GitHub (May 16, 2022): Hmm. We see this from time to time - there was another one like this just filed in #13108. - Another similar report in #12767. - #12545 only has to do with the env being different, so that's definitely different. - #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.
Author
Owner

@0warning0error commented on GitHub (May 17, 2022):

Hmm. We see this from time to time

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?

@0warning0error commented on GitHub (May 17, 2022): > 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](https://github.com/microsoft/terminal/issues/13108). > * Another similar report in [`wt` doesn't work anymore #12767](https://github.com/microsoft/terminal/issues/12767). > * [Open alias "wt" have unexpected behavior. #12545](https://github.com/microsoft/terminal/issues/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](https://github.com/microsoft/terminal/issues/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?
Author
Owner

@notis58 commented on GitHub (May 28, 2022):

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

@notis58 commented on GitHub (May 28, 2022): I have the same problem Is there any progress on it?
Author
Owner

@lhecker commented on GitHub (Jul 7, 2022):

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

@lhecker commented on GitHub (Jul 7, 2022): I believe this was fixed as part of #13193. /dup #13193
Author
Owner

@ghost commented on GitHub (Jul 7, 2022):

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!

@ghost commented on GitHub (Jul 7, 2022): 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!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#17412