starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Windows Terminal crashes immmediately when launched from Win+X menu #17487

New Issue
Closed
opened 2026-01-31 05:43:56 +00:00 by claunia · 24 comments
claunia commented 2026-01-31 05:43:56 +00:00
Owner
Copy Link

Originally created by @notis58 on GitHub (May 15, 2022).

Windows Terminal and Windows Terminal (Admin) crash immmediately when launched from Win+X menu.
It will also crash if wt.exe is started from the Win+R menu.

It starts normally from the Explorer context menu and from the Start menu/All apps.
wt.exe starts also form the Task Manager, but only as administrator.

I have tried all fixes I found: Repair, Reset in settings, Uninstall and reinstall from Microsoft Store, toggle the App execution aliases.

Nothing worked.

My Windows specification:

Edition Windows 11 Pro
Version 21H2
Installed on ‎5/‎13/‎2022
OS build 22000.675
Experience Windows Feature Experience Pack 1000.22000.675.0

Windows Terninal Version: 1.12.10983.0

Originally created by @notis58 on GitHub (May 15, 2022). Windows Terminal and Windows Terminal (Admin) crash immmediately when launched from Win+X menu. It will also crash if wt.exe is started from the Win+R menu. It starts normally from the Explorer context menu and from the Start menu/All apps. wt.exe starts also form the Task Manager, but only as administrator. I have tried all fixes I found: Repair, Reset in settings, Uninstall and reinstall from Microsoft Store, toggle the App execution aliases. Nothing worked. My Windows specification: Edition Windows 11 Pro Version 21H2 Installed on ‎5/‎13/‎2022 OS build 22000.675 Experience Windows Feature Experience Pack 1000.22000.675.0 Windows Terninal Version: 1.12.10983.0
claunia commented 2026-01-31 05:43:57 +00:00
Author
Owner
Copy Link

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

Does it open and then exit immediately, or does it straight up just not launch at all? Could you repro this with the Feedback Hub? That might catch whatever error is happening on launch.

/feedback

@zadjii-msft commented on GitHub (May 16, 2022): Does it open and then exit immediately, or does it straight up just not launch at all? Could you repro this with the Feedback Hub? That _might_ catch whatever error is happening on launch. /feedback
claunia commented 2026-01-31 05:43:58 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (May 16, 2022):

Hi there!

Can you please send us feedback with the Feedback Hub with this issue? Make sure to click the "Start recording" button, then reproduce the issue before submitting the feedback. Once it's submitted, paste the link here so we can more easily find your crash information on the back end?

Thanks!

image

image

image

@ghost commented on GitHub (May 16, 2022): Hi there!<br><br>Can you please send us feedback with the [Feedback Hub](https://support.microsoft.com/en-us/windows/send-feedback-to-microsoft-with-the-feedback-hub-app-f59187f8-8739-22d6-ba93-f66612949332) with this issue? Make sure to click the "Start recording" button, then reproduce the issue before submitting the feedback. Once it's submitted, paste the link here so we can more easily find your crash information on the back end?<br><br>Thanks!<br><br>![image](https://user-images.githubusercontent.com/18356694/140811502-a068f78b-89d2-4587-925a-73e19652b830.png)<br><br>![image](https://user-images.githubusercontent.com/18356694/140811557-cdc22a0f-fa6a-4f6a-953e-73b51f5548a3.png)<br><br>![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png)
claunia commented 2026-01-31 05:43:58 +00:00
Author
Owner
Copy Link

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

Here ist the link from the recording in th e feedback hub:
https://aka.ms/AAgxcoo

@zadjii-msft: It opens and exits immediately. I see it does open in the task manager

@notis58 commented on GitHub (May 16, 2022): Here ist the link from the recording in th e feedback hub: https://aka.ms/AAgxcoo @zadjii-msft: It opens and exits immediately. I see it does open in the task manager
claunia commented 2026-01-31 05:43:58 +00:00
Author
Owner
Copy Link

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

Any update on this?

@notis58 commented on GitHub (May 28, 2022): Any update on this?
claunia commented 2026-01-31 05:43:58 +00:00
Author
Owner
Copy Link

@AlifianK commented on GitHub (Jun 4, 2022):

Hi, I have the same issue with this.

https://aka.ms/AAh47m0

@AlifianK commented on GitHub (Jun 4, 2022): Hi, I have the same issue with this. https://aka.ms/AAh47m0
claunia commented 2026-01-31 05:43:58 +00:00
Author
Owner
Copy Link

@qihs97 commented on GitHub (Jun 21, 2022):

I met the same problem, did you solve it?

@qihs97 commented on GitHub (Jun 21, 2022): I met the same problem, did you solve it?
claunia commented 2026-01-31 05:43:59 +00:00
Author
Owner
Copy Link

@notis58 commented on GitHub (Jun 21, 2022):

I met the same problem, did you solve it?

No, unortunately not. It's up to the developers to solve it and it seems no one is dealing with it.

@notis58 commented on GitHub (Jun 21, 2022): > I met the same problem, did you solve it? No, unortunately not. It's up to the developers to solve it and it seems no one is dealing with it.
claunia commented 2026-01-31 05:43:59 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 21, 2022):

  • registry seems to have the right guids for defterm to work with terminal stable.
  • dmp only included three conhosts, which had nothing useful in them. Three threads, but no crashes in there.
  • etl log had nothing interesting. Two TerminalApp launches, that both hit three 0x80070005 access denied's, but those had no line number, or anything else interesting. They seemed to bubble up to the windowsterminal.exe layer, as well.
  • two different conhost buckets: 15cdd140-8a18-37f0-9565-7514747b3463 and ffe8b5db-bcc5-7941-75b1-ed66cb4bbdbe, these are both useless conhost!unknown buckets that don't actually capture that something went wrong.
  • actually all three conhosts look like they were started to service some other commandline application, and not related to the Terminal at all.

There's unfortunately basically nothing to go on here 😕

Did Terminal 1.12 / 1.11 / 1.10 work? Does manually uninstalling the Terminal, and manually installing an older version like 1.11 seem to fix it?

We don't really own the win+x menu shortcut, so you might need to file feedback on
image

to try and sort out what's going on here.

@zadjii-msft commented on GitHub (Jun 21, 2022): * registry seems to have the right guids for defterm to work with terminal stable. * dmp only included three conhosts, which had nothing useful in them. Three threads, but no crashes in there. * etl log had nothing interesting. Two TerminalApp launches, that both hit three `0x80070005` access denied's, but those had no line number, or anything else interesting. They seemed to bubble up to the windowsterminal.exe layer, as well. * two different conhost buckets: `15cdd140-8a18-37f0-9565-7514747b3463` and `ffe8b5db-bcc5-7941-75b1-ed66cb4bbdbe`, these are both useless `conhost!unknown` buckets that don't actually capture that something went wrong. * actually all three conhosts look like they were started to service some other commandline application, and not related to the Terminal at all. There's unfortunately basically nothing to go on here 😕 Did Terminal 1.12 / 1.11 / 1.10 work? Does manually uninstalling the Terminal, and manually installing an older version like 1.11 seem to fix it? We don't really own the win+x menu shortcut, so you might need to file feedback on ![image](https://user-images.githubusercontent.com/18356694/174822391-648ef4e9-e98d-4d02-a774-9a810c70ea3c.png) to try and sort out what's going on here.
claunia commented 2026-01-31 05:44:01 +00:00
Author
Owner
Copy Link

@notis58 commented on GitHub (Jun 23, 2022):

It’s not just the Win+X menu.

The terminal (wt.exe) starts and crashes when run form the Task Manager.

It only starts from there if run with administrator privileges.

From: Mike Griese @.>
Sent: Tuesday, June 21, 2022 5:19 PM
To: microsoft/terminal @.>
Cc: notis58 @.>; Author @.>
Subject: Re: [microsoft/terminal] Windows Terminal crashes immmediately when launched from Win+X menu (Issue #13108)

  • registry seems to have the right guids for defterm to work with terminal stable.
  • dmp only included three conhosts, which had nothing useful in them. Three threads, but no crashes in there.
  • etl log had nothing interesting. Two TerminalApp launches, that both hit three 0x80070005 access denied's, but those had no line number, or anything else interesting. They seemed to bubble up to the windowsterminal.exe layer, as well.
  • two different conhost buckets: 15cdd140-8a18-37f0-9565-7514747b3463 and ffe8b5db-bcc5-7941-75b1-ed66cb4bbdbe, these are both useless conhost!unknown buckets that don't actually capture that something went wrong.
  • actually all three conhosts look like they were started to service some other commandline application, and not related to the Terminal at all.

There's unfortunately basically nothing to go on here 😕

Did Terminal 1.12 / 1.11 / 1.10 work? Does manually uninstalling the Terminal, and manually installing an older version like 1.11 seem to fix it?

We don't really own the win+x menu shortcut, so you might need to file feedback on
https://user-images.githubusercontent.com/18356694/174822391-648ef4e9-e98d-4d02-a774-9a810c70ea3c.png

to try and sort out what's going on here.

—
Reply to this email directly, view it on GitHub https://github.com/microsoft/terminal/issues/13108#issuecomment-1161811312 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AYRI5ZWWC2YA3BFY4BD2LK3VQHFOHANCNFSM5V7J6MRQ .
You are receiving this because you authored the thread. https://github.com/notifications/beacon/AYRI5ZQGBSL37XYCF3VGSZDVQHFOHA5CNFSM5V7J6MR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOIU75K4A.gif Message ID: @.***>

@notis58 commented on GitHub (Jun 23, 2022): It’s not just the Win+X menu. The terminal (wt.exe) starts and crashes when run form the Task Manager. It only starts from there if run with administrator privileges. From: Mike Griese ***@***.***> Sent: Tuesday, June 21, 2022 5:19 PM To: microsoft/terminal ***@***.***> Cc: notis58 ***@***.***>; Author ***@***.***> Subject: Re: [microsoft/terminal] Windows Terminal crashes immmediately when launched from Win+X menu (Issue #13108) * registry seems to have the right guids for defterm to work with terminal stable. * dmp only included three conhosts, which had nothing useful in them. Three threads, but no crashes in there. * etl log had nothing interesting. Two TerminalApp launches, that both hit three 0x80070005 access denied's, but those had no line number, or anything else interesting. They seemed to bubble up to the windowsterminal.exe layer, as well. * two different conhost buckets: 15cdd140-8a18-37f0-9565-7514747b3463 and ffe8b5db-bcc5-7941-75b1-ed66cb4bbdbe, these are both useless conhost!unknown buckets that don't actually capture that something went wrong. * actually all three conhosts look like they were started to service some other commandline application, and not related to the Terminal at all. There's unfortunately basically nothing to go on here 😕 Did Terminal 1.12 / 1.11 / 1.10 work? Does manually uninstalling the Terminal, and manually installing an older version like 1.11 seem to fix it? We don't really own the win+x menu shortcut, so you might need to file feedback on <https://user-images.githubusercontent.com/18356694/174822391-648ef4e9-e98d-4d02-a774-9a810c70ea3c.png> to try and sort out what's going on here. — Reply to this email directly, view it on GitHub <https://github.com/microsoft/terminal/issues/13108#issuecomment-1161811312> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AYRI5ZWWC2YA3BFY4BD2LK3VQHFOHANCNFSM5V7J6MRQ> . You are receiving this because you authored the thread. <https://github.com/notifications/beacon/AYRI5ZQGBSL37XYCF3VGSZDVQHFOHA5CNFSM5V7J6MR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOIU75K4A.gif> Message ID: ***@***.***>
claunia commented 2026-01-31 05:44:02 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 23, 2022):

Hmm, that sounds like a riff on #13197

@zadjii-msft commented on GitHub (Jun 23, 2022): Hmm, that sounds like a riff on #13197
claunia commented 2026-01-31 05:44:02 +00:00
Author
Owner
Copy Link

@notis58 commented on GitHub (Jun 23, 2022):

Well, not quite.

In my case:

From the Start menu the Terminal runs both without and with admin privileges

From the Win+X menu it runs but crashes immediately both without and with admin privileges (immediately after the UAC prompt in the admin case)

From The Task Manager it runs with admin privileges but crashes immediately without

Crazy?

@notis58 commented on GitHub (Jun 23, 2022): Well, not quite. In my case: From the Start menu the Terminal runs both without and with admin privileges From the Win+X menu it runs but crashes immediately both without and with admin privileges (immediately after the UAC prompt in the admin case) From The Task Manager it runs with admin privileges but crashes immediately without Crazy?
claunia commented 2026-01-31 05:44:03 +00:00
Author
Owner
Copy Link

@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
claunia commented 2026-01-31 05:44:03 +00:00
Author
Owner
Copy Link

@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!
claunia commented 2026-01-31 05:44:03 +00:00
Author
Owner
Copy Link

@notis58 commented on GitHub (Jul 8, 2022):

Well, it was not fixed!!!

And even worse

I downloaded and installed the preview version, which supposedly solved the issue and it messed everything up!!!

Now Windows Terminal runs only if I navigate to “C:\Users<user>\AppData\Local\Microsoft\WindowsApps\Microsoft.WindowsTerminal_8wekyb3d8bbwe" or "C:\Users\Notis\AppData\Local\Microsoft\WindowsApps\Microsoft.WindowsTerminalPreview_8wekyb3d8bbwe" and double click on wt.exe. Both versions, old and preview, work this way

If I try to run wt.exe from Run or the task manager or the Win+X menu it returns an error: 0xc0000022

This happens with any of the aliases enabled

This mentioned in #7081
Now that I’ve checked #13193, https://github.com/microsoft/terminal/issues/13193#issuecomment-1177510405 is asking if it resolves my issue and some others.

How did you come up with the idea that this would resolve my issue in the first place?
Your comment instead of resolving my issue made things worse

@notis58 commented on GitHub (Jul 8, 2022): Well, it was not fixed!!! And even worse I downloaded and installed the preview version, which supposedly solved the issue and it messed everything up!!! Now Windows Terminal runs only if I navigate to “C:\Users\<user>\AppData\Local\Microsoft\WindowsApps\Microsoft.WindowsTerminal_8wekyb3d8bbwe" or "C:\Users\Notis\AppData\Local\Microsoft\WindowsApps\Microsoft.WindowsTerminalPreview_8wekyb3d8bbwe" and double click on wt.exe. Both versions, old and preview, work this way If I try to run wt.exe from Run or the task manager or the Win+X menu it returns an error: 0xc0000022 This happens with any of the aliases enabled This mentioned in #7081 Now that I’ve checked #13193, https://github.com/microsoft/terminal/issues/13193#issuecomment-1177510405 is asking if it resolves my issue and some others. How did you come up with the idea that this would resolve my issue in the first place? Your comment instead of resolving my issue made things worse
claunia commented 2026-01-31 05:44:04 +00:00
Author
Owner
Copy Link

@notis58 commented on GitHub (Jul 8, 2022):

After lhecker's comment my issue was closed
I had the (obviously wrong) impression that an issue is closed after the solution is checked. Apparently not.

I checked #13193 and installed Windows Terminal Preview v1.15.186

Now everything is messed up

Windows Terminal will not start and returns an error

image

This is mentioned in #7081 but there seems to be no solution there

I uninstalled the preview version but the issue persists

How do I fix the new issue now?

@notis58 commented on GitHub (Jul 8, 2022): After lhecker's comment my issue was closed I had the (obviously wrong) impression that an issue is closed after the solution is checked. Apparently not. I checked #13193 and installed Windows Terminal Preview v1.15.186 Now everything is messed up Windows Terminal will not start and returns an error ![image](https://user-images.githubusercontent.com/102928102/178056232-e8146852-fc2a-4094-aa94-2668383669e5.png) This is mentioned in #7081 but there seems to be no solution there I uninstalled the preview version but the issue persists How do I fix the new issue now?
claunia commented 2026-01-31 05:44:04 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 8, 2022):

Can you try to "Repair" the installation of Windows Terminal in the "Apps and Features" control panel? 0xC0000022 is an error originating from the application platform, which is unfortunately just as mystifying to us as it is to the general public.

@DHowett commented on GitHub (Jul 8, 2022): Can you try to "Repair" the installation of Windows Terminal in the "Apps and Features" control panel? `0xC0000022` is an error originating from the application platform, which is unfortunately just as mystifying to us as it is to the general public.
claunia commented 2026-01-31 05:44:04 +00:00
Author
Owner
Copy Link

@notis58 commented on GitHub (Jul 8, 2022):

I have already tried repairing and resetting Windows Terminal
Nothing worked

@notis58 commented on GitHub (Jul 8, 2022): I have already tried repairing and resetting Windows Terminal Nothing worked
claunia commented 2026-01-31 05:44:04 +00:00
Author
Owner
Copy Link

@AlifianK commented on GitHub (Jul 15, 2022):

Updating to v1.14.186 fixed the Win+X problem for me, but still the same with Win+R. Terminal refuses to open with no crash dialogue.

@AlifianK commented on GitHub (Jul 15, 2022): Updating to [v1.14.186](https://github.com/microsoft/terminal/releases/tag/v1.14.1861.0) fixed the Win+X problem for me, but still the same with Win+R. Terminal refuses to open with no crash dialogue.
claunia commented 2026-01-31 05:44:05 +00:00
Author
Owner
Copy Link

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

Can you run:

  • conhost -- cmd.exe /k where wt & path

for me, from the run dialog (win+r)/? Try it both as admin and not, that should get a read on what's diffent between the two. I'm hoping that you're just missing %localappdata%\Microsoft\WindowsApps from your PATH, which is why it seems like it won't launch.

@zadjii-msft commented on GitHub (Jul 28, 2022): Can you run: * `conhost -- cmd.exe /k where wt & path` for me, from the run dialog (win+r)/? Try it both as admin and not, that should get a read on what's diffent between the two. I'm hoping that you're just missing `%localappdata%\Microsoft\WindowsApps` from your `PATH`, which is why it seems like it won't launch.
claunia commented 2026-01-31 05:44:05 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Aug 1, 2022):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Aug 1, 2022): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-31 05:44:05 +00:00
Author
Owner
Copy Link

@notis58 commented on GitHub (Aug 2, 2022):

Can you run:

  • conhost -- cmd.exe /k where wt & path

for me, from the run dialog (win+r)/? Try it both as admin and not, that should get a read on what's diffent between the two. I'm hoping that you're just missing %localappdata%\Microsoft\WindowsApps from your PATH, which is why it seems like it won't launch.
It's not missing:
run as admin

C:\Users\Notis\AppData\Local\Microsoft\WindowsApps\wt.exe PATH=C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Program Files (x86)\VMware\VMware Workstation\bin\;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\iCLS\;C:\Program Files\Intel\Intel(R) Management Engine Components\iCLS\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files\dotnet\;C:\Program Files\PowerShell\7\;C:\Program Files\Microsoft VS Code\bin;C:\Program Files\Microsoft SQL Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\170\Tools\Binn\;C:\Program Files\MySQL\MySQL Shell 8.0\bin\;C:\Users\Notis\AppData\Local\Microsoft\WindowsApps

run not admin

C:\Users\Notis\AppData\Local\Microsoft\WindowsApps\wt.exe PATH=C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Program Files (x86)\VMware\VMware Workstation\bin\;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\iCLS\;C:\Program Files\Intel\Intel(R) Management Engine Components\iCLS\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files\dotnet\;C:\Program Files\PowerShell\7\;C:\Program Files\Microsoft VS Code\bin;C:\Program Files\Microsoft SQL Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\170\Tools\Binn\;C:\Program Files\MySQL\MySQL Shell 8.0\bin\;C:\Users\Notis\AppData\Local\Microsoft\WindowsApps

The Win+X issue is resolved after the last Windows update, but the Win+R issue remains. If run as admin, it asks for confirmation and then nothing. Strangely enough, when started from Win+R it tries to open wt.exe in %programfiles%\WindowsApps\Microsoft.WindowsTerminal_1.14.1963.0_x64__8wekyb3d8bbwe, which is not in my PATH

@notis58 commented on GitHub (Aug 2, 2022): > Can you run: > > * `conhost -- cmd.exe /k where wt & path` > > for me, from the run dialog (win+r)/? Try it both as admin and not, that should get a read on what's diffent between the two. I'm hoping that you're just missing `%localappdata%\Microsoft\WindowsApps` from your `PATH`, which is why it seems like it won't launch. It's not missing: run as admin `C:\Users\Notis\AppData\Local\Microsoft\WindowsApps\wt.exe PATH=C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Program Files (x86)\VMware\VMware Workstation\bin\;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\iCLS\;C:\Program Files\Intel\Intel(R) Management Engine Components\iCLS\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files\dotnet\;C:\Program Files\PowerShell\7\;C:\Program Files\Microsoft VS Code\bin;C:\Program Files\Microsoft SQL Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\170\Tools\Binn\;C:\Program Files\MySQL\MySQL Shell 8.0\bin\;C:\Users\Notis\AppData\Local\Microsoft\WindowsApps` run not admin `C:\Users\Notis\AppData\Local\Microsoft\WindowsApps\wt.exe PATH=C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Program Files (x86)\VMware\VMware Workstation\bin\;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\iCLS\;C:\Program Files\Intel\Intel(R) Management Engine Components\iCLS\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files\dotnet\;C:\Program Files\PowerShell\7\;C:\Program Files\Microsoft VS Code\bin;C:\Program Files\Microsoft SQL Server\150\Tools\Binn\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\170\Tools\Binn\;C:\Program Files\MySQL\MySQL Shell 8.0\bin\;C:\Users\Notis\AppData\Local\Microsoft\WindowsApps` The Win+X issue is resolved after the last Windows update, but the Win+R issue remains. If run as admin, it asks for confirmation and then nothing. Strangely enough, when started from Win+R it tries to open wt.exe in `%programfiles%\WindowsApps\Microsoft.WindowsTerminal_1.14.1963.0_x64__8wekyb3d8bbwe`, which is not in my `PATH`
claunia commented 2026-01-31 05:44:06 +00:00
Author
Owner
Copy Link

@saifsiddiquee commented on GitHub (Nov 1, 2022):

Go to Settings->Apps->Installed Apps->Terminal>Advanced option.
Then repair and reset. It worked for me.

terminal

If it does not work, you can uninstall terminal and install again from the windows store.

@saifsiddiquee commented on GitHub (Nov 1, 2022): `Go to Settings->Apps->Installed Apps->Terminal>Advanced option.` Then repair and reset. It worked for me. ![terminal](https://user-images.githubusercontent.com/34885954/199197137-8ab7e163-7ad4-4aea-ad39-ecd71705dfe4.png) _If it does not work, you can uninstall terminal and install again from the windows store._
claunia commented 2026-01-31 05:44:06 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 8, 2023):

Any chance this is fixed in https://github.com/microsoft/terminal/releases/tag/v1.16.10261.0/? This might have been the elevate:true crash, in retrospect.

@zadjii-msft commented on GitHub (Feb 8, 2023): Any chance this is fixed in https://github.com/microsoft/terminal/releases/tag/v1.16.10261.0/? This might have been the `elevate:true` crash, in retrospect.
claunia commented 2026-01-31 05:44:06 +00:00
Author
Owner
Copy Link

@notis58 commented on GitHub (Feb 9, 2023):

Any chance this is fixed in https://github.com/microsoft/terminal/releases/tag/v1.16.10261.0/? This might have been the elevate:true crash, in retrospect.

It's fixed!
Terminal starts normally using Win+X and running wt.exe from Win+R
Both as admin and normal user

@notis58 commented on GitHub (Feb 9, 2023): > Any chance this is fixed in https://github.com/microsoft/terminal/releases/tag/v1.16.10261.0/? This might have been the `elevate:true` crash, in retrospect. It's fixed! Terminal starts normally using Win+X and running wt.exe from Win+R Both as admin and normal user
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Culprit-Centennial Needs-Attention Needs-Repro Needs-Tag-Fix Needs-Triage
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#17487
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?