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

win+r > wt dont work in 1.18.3181.0 #20950

New Issue
Closed
opened 2026-01-31 07:28:41 +00:00 by claunia · 15 comments
claunia commented 2026-01-31 07:28:41 +00:00
Owner
Copy Link

Originally created by @ilcpm on GitHub (Dec 4, 2023).

Windows Terminal version

1.18.3181.0

Windows build number

10.0.19045.0

Other Software

No response

Steps to reproduce

after update to 1.18.3181.0 from Microsoft store on win10, I could not start windows terminal by other programs use the command wt

I test for using win+R to run wt, then nothing will happen. by taskmanager I can see a wt thread open and immediately disappear.
image

but while I'm in the command line like powershell or wt, it can be open by the command wt
image
image

Expected Behavior

No response

Actual Behavior

empty

Originally created by @ilcpm on GitHub (Dec 4, 2023). ### Windows Terminal version 1.18.3181.0 ### Windows build number 10.0.19045.0 ### Other Software _No response_ ### Steps to reproduce after update to 1.18.3181.0 from Microsoft store on win10, I could not start windows terminal by other programs use the command `wt` I test for using `win+R` to run `wt`, then nothing will happen. by taskmanager I can see a wt thread open and immediately disappear. ![image](https://github.com/microsoft/terminal/assets/36830343/b3194e9e-fc66-45a9-951a-2b46717d1099) but while I'm in the command line like powershell or wt, it can be open by the command `wt` ![image](https://github.com/microsoft/terminal/assets/36830343/340286e2-b84c-4588-bd36-e1fe93e8d1cc) ![image](https://github.com/microsoft/terminal/assets/36830343/e71841d5-750a-4c99-ad54-76fa33e0e88c) ### Expected Behavior _No response_ ### Actual Behavior empty
claunia commented 2026-01-31 07:28:43 +00:00
Author
Owner
Copy Link

@ilcpm commented on GitHub (Dec 4, 2023):

maybe wt should add an optional win shortcut in system to directly open wt, just like win + T in ubuntu, I use other program to set win + N to do so.(and because of the bug above, it can't work now)

@ilcpm commented on GitHub (Dec 4, 2023): maybe wt should add an optional `win` shortcut in system to directly open wt, just like `win + T` in ubuntu, I use other program to set `win + N` to do so.(and because of the bug above, it can't work now)
claunia commented 2026-01-31 07:28:44 +00:00
Author
Owner
Copy Link

@timadye commented on GitHub (Dec 4, 2023):

I have the same issue. I can start Windows Terminal with the wt command from the Command Prompt, but can't start it from the Start Menu, either from the Terminal menu item, or with Run > wt.

As @ilcpm notes, it just gives me a "waiting" cursor for a second, but no window opens.

I see this with both the release (1.18.3181.0) and preview (1.19.3172.0) versions on two different Windows 10 22H2 systems.

@timadye commented on GitHub (Dec 4, 2023): I have the same issue. I can start Windows Terminal with the `wt` command from the Command Prompt, but can't start it from the Start Menu, either from the `Terminal` menu item, or with `Run` > `wt`. As @ilcpm notes, it just gives me a "waiting" cursor for a second, but no window opens. I see this with both the release (1.18.3181.0) and preview (1.19.3172.0) versions on two different Windows 10 22H2 systems.
claunia commented 2026-01-31 07:28:44 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 4, 2023):

I feel like we had another thread for this just recently, but I can't find it. The last one I can find has all sorts of notes about people disabling UAC, or otherwise attempting to mess with the permissions on WindowsApps

NOTE: Here's your reminder! NEVER mess with the permissions anywhere on WindowsApps!

Doing that may irreversibly break your OS install. Like, literally no way to recover without reinstalling the OS. Don't ever do it.

@zadjii-msft commented on GitHub (Dec 4, 2023): I feel like we had another thread for this just recently, but I can't find it. The last one I can find has all sorts of notes about people disabling UAC, or otherwise attempting to mess with the permissions on WindowsApps ### **NOTE**: Here's your reminder! NEVER mess with the permissions anywhere on `WindowsApps`! Doing that may irreversibly break your OS install. Like, literally no way to recover without reinstalling the OS. Don't ever do it.
claunia commented 2026-01-31 07:28:44 +00:00
Author
Owner
Copy Link

@timadye commented on GitHub (Dec 4, 2023):

Hi @zadjii-msft,

I feel like we had another thread for this just recently, but I can't find it. The last one I can find has all sorts of notes about people disabling UAC, or otherwise attempting to mess with the permissions on WindowsApps
NOTE: Here's your reminder! NEVER mess with the permissions anywhere on WindowsApps!

Thanks for the warning, but I don't think that could be what is happening, at least for me. This used to work a few weeks ago. I certainly haven't touched WindowsApps since then. Also, I get the same on a fresh install of Windows.

It may be correlated with the v1.18.3181.0 update. What's the best way to revert to the previous version to see if that helps?

@timadye commented on GitHub (Dec 4, 2023): Hi @zadjii-msft, > I feel like we had another thread for this just recently, but I can't find it. The last one I can find has all sorts of notes about people disabling UAC, or otherwise attempting to mess with the permissions on WindowsApps > NOTE: Here's your reminder! NEVER mess with the permissions anywhere on `WindowsApps`! Thanks for the warning, but I don't think that could be what is happening, at least for me. This used to work a few weeks ago. I certainly haven't touched `WindowsApps` since then. Also, I get the same on a fresh install of Windows. It may be correlated with the v1.18.3181.0 update. What's the best way to revert to the previous version to see if that helps?
claunia commented 2026-01-31 07:28:45 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 6, 2023):

Hmm, #13622 might have been the latest report of this (though I still feel like there was a newer one than that). That thread was from like a year ago, and ultimately was root caused to the user disabling UAC (by setting EnableLUA=0). Turns out packaged apps really hate that.

I think it's very curious that OP is also running elevated ("as admin"). Perhaps that has some interplay here.

@timadye an idea might be to uninstall the Terminal, and go grab an earlier version off of https://github.com/microsoft/terminal/releases.

Or, another possibly dumb idea would be to install Terminal Preview (1.19), then go to the settings app for "App Execution Aliases" and switch wt to point at Terminal Preview instead. This would help rule out a bad MUX package install as a possible problem here. Derp I can't read, you already tried that

@zadjii-msft commented on GitHub (Dec 6, 2023): Hmm, #13622 _might_ have been the latest report of this (though I still feel like there was a newer one than that). That thread was from like a year ago, and ultimately was root caused to the user disabling UAC (by setting EnableLUA=0). Turns out packaged apps really hate that. I think it's very curious that OP is also running elevated ("as admin"). Perhaps that has some interplay here. @timadye an idea might be to uninstall the Terminal, and go grab an earlier version off of https://github.com/microsoft/terminal/releases. ~Or, another possibly dumb idea would be to install Terminal Preview (1.19), then go to the settings app for ["App Execution Aliases"](https://stackoverflow.com/questions/58296925/what-is-zero-byte-executable-files-in-windows/66539884#66539884) and switch `wt` to point at Terminal Preview instead. This would help rule out a bad MUX package install as a possible problem here.~ Derp I can't read, you already tried that
claunia commented 2026-01-31 07:28:45 +00:00
Author
Owner
Copy Link

@ilcpm commented on GitHub (Dec 6, 2023):

@zadjii-msft I have tried all UAC options, the result is the same

@ilcpm commented on GitHub (Dec 6, 2023): @zadjii-msft I have tried all UAC options, the result is the same
claunia commented 2026-01-31 07:28:45 +00:00
Author
Owner
Copy Link

@timadye commented on GitHub (Dec 6, 2023):

@zadjii-msft, thanks for the pointer. I uninstalled the Microsoft Store Terminal Preview and installed a few other versions, all with the same results (can't start Terminal from Start Menu).

For the record, here is what I tested:

  1. Reset Terminal Preview settings from the Apps Settings.
  2. Uninstall Windows Terminal Preview 1.19.3172.0.
  3. PS> Add-AppPackage .\Microsoft.WindowsTerminal_1.18.2822.0_8wekyb3d8bbwe.msixbundle. Then uninstall.
  4. PS> Add-AppPackage .\Microsoft.WindowsTerminal_1.17.11461.0_8wekyb3d8bbwe.msixbundle. Then uninstall and reboot.
  5. PS> Add-AppPackage .\Microsoft.WindowsTerminal_Win10_1.16.10261.0_8wekyb3d8bbwe.msixbundle. Then uninstall.
  6. Reinstall Windows Terminal (not Preview this time) from Microsoft Store.

Even the first old release (1.18.2822.0) is from 11 Oct, before I remember seeing this issue. The last (1.16) is from 27 Jan, long before. Each version exhibited the same symptoms: starts OK from wt, but not from Start Menu.

@timadye commented on GitHub (Dec 6, 2023): @zadjii-msft, thanks for the pointer. I uninstalled the Microsoft Store Terminal Preview and installed a few other versions, all with the same results (can't start Terminal from Start Menu). For the record, here is what I tested: 1. Reset Terminal Preview settings from the Apps Settings. 2. Uninstall Windows Terminal Preview 1.19.3172.0. 3. `PS> Add-AppPackage .\Microsoft.WindowsTerminal_1.18.2822.0_8wekyb3d8bbwe.msixbundle`. Then uninstall. 4. `PS> Add-AppPackage .\Microsoft.WindowsTerminal_1.17.11461.0_8wekyb3d8bbwe.msixbundle`. Then uninstall and reboot. 5. `PS> Add-AppPackage .\Microsoft.WindowsTerminal_Win10_1.16.10261.0_8wekyb3d8bbwe.msixbundle`. Then uninstall. 6. Reinstall Windows Terminal (not Preview this time) from Microsoft Store. Even the first old release (1.18.2822.0) is from 11 Oct, before I remember seeing this issue. The last (1.16) is from 27 Jan, long before. Each version exhibited the same symptoms: starts OK from `wt`, but not from Start Menu.
claunia commented 2026-01-31 07:28:45 +00:00
Author
Owner
Copy Link

@timadye commented on GitHub (Dec 6, 2023):

And here are all the ways I found that work and don't work to start Windows Terminal.

Doesn't work

  1. Start Menu Run and type wt
  2. From Start Menu, select Terminal or Terminal Preview, depending on which is installed (this is what I usually use)
  3. Start when pinned to the task bar, or a shortcut on the desktop
  4. Start from Open Shell Apps.

Works

  1. From Command Prompt, type wt
  2. From WSL2, type wt.exe
  3. From Microsoft Store, press Open
  4. When Windows Terminal is the default terminal application, start Command Prompt from the Start Menu

[edited to move (1) to the doesn't work section]

@timadye commented on GitHub (Dec 6, 2023): And here are all the ways I found that work and don't work to start Windows Terminal. **Doesn't work** 1. Start Menu `Run` and type `wt` 2. From Start Menu, select `Terminal` or `Terminal Preview`, depending on which is installed (this is what I usually use) 3. Start when pinned to the task bar, or a shortcut on the desktop 4. Start from Open Shell Apps. **Works** 5. From Command Prompt, type `wt` 6. From WSL2, type `wt.exe` 7. From Microsoft Store, press `Open` 8. When `Windows Terminal` is the default terminal application, start `Command Prompt` from the Start Menu [edited to move (1) to the doesn't work section]
claunia commented 2026-01-31 07:28:46 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Dec 6, 2023):

Works

  1. Start Menu Run and type wt

This indicates that your issue is different from OP, right? Does this issue also happen without Open Shell? It's a fantastic extension, but I wonder if there might be a new incompatibility there... I'd say that it could be the search index too, but then I wouldn't understand why it happens with pinned taskbar items.

Maybe Windows Terminal is crashing during launch? You could follow this section and see if it results in a dump: https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capture-automatically

It's also possible that there might be relevant output visible when running DebugView simultaneously.

@lhecker commented on GitHub (Dec 6, 2023): > #### Works > 5. Start Menu Run and type wt This indicates that your issue is different from OP, right? Does this issue also happen without Open Shell? It's a fantastic extension, but I wonder if there might be a new incompatibility there... I'd say that it could be the search index too, but then I wouldn't understand why it happens with pinned taskbar items. --- Maybe Windows Terminal is crashing during launch? You could follow this section and see if it results in a dump: https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capture-automatically It's also possible that there might be relevant output visible when running [DebugView](https://learn.microsoft.com/en-us/sysinternals/downloads/debugview) simultaneously.
claunia commented 2026-01-31 07:28:46 +00:00
Author
Owner
Copy Link

@timadye commented on GitHub (Dec 6, 2023):

My tests with different versions of Windows Terminal, and the fact that this started in the last few weeks, indicate that this is probably something to do with updates to the Windows version, configuration, or other software.

I have Windows 10 Enterprise version 22H2, build 19045.3693. That's from KB5032189, installed on ‎18/‎11/‎2023, which could be when the problem appeared. Sorry, I don't remember exactly when it first started.

I see the issue on two different Dell laptops. The old one was initially installed in 2018. The new one was installed last week (29/11/2023). Both have similar software, though.

@zadjii-msft, your comment about UAC prompts me to note that we recently had Admin By Request installed by our IT department. I think that was installed a bit earlier than when I started seeing the issue, but it's possible this is relevant.

@timadye commented on GitHub (Dec 6, 2023): My tests with different versions of Windows Terminal, and the fact that this started in the last few weeks, indicate that this is probably something to do with updates to the Windows version, configuration, or other software. I have Windows 10 Enterprise version 22H2, build 19045.3693. That's from KB5032189, installed on ‎18/‎11/‎2023, which *could* be when the problem appeared. Sorry, I don't remember exactly when it first started. I see the issue on two different Dell laptops. The old one was initially installed in 2018. The new one was installed last week (29/11/2023). Both have similar software, though. @zadjii-msft, your comment about UAC prompts me to note that we recently had [Admin By Request](https://www.adminbyrequest.com/) installed by our IT department. I *think* that was installed a bit earlier than when I started seeing the issue, but it's possible this is relevant.
claunia commented 2026-01-31 07:28:46 +00:00
Author
Owner
Copy Link

@timadye commented on GitHub (Dec 6, 2023):

Works
5. Start Menu Run and type wt

This indicates that your issue is different from OP, right?

Oh, I'm terribly sorry, this one doesn't work, as see by the OP. I edited my previous comment.

@timadye commented on GitHub (Dec 6, 2023): > > **Works** > > 5. Start Menu Run and type wt > > This indicates that your issue is different from OP, right? Oh, I'm terribly sorry, this one **doesn't work**, as see by the OP. I edited my previous comment.
claunia commented 2026-01-31 07:28:46 +00:00
Author
Owner
Copy Link

@timadye commented on GitHub (Dec 6, 2023):

Does this issue also happen without Open Shell? It's a fantastic extension, but I wonder if there might be a new incompatibility there...

I can try uninstalling and see if it makes a difference, though I doubt it since I had the same version of Open Shell for a long time on my old laptop and this issue appeared recently.

Also, just to be clear: in my list above, I tried starting with both (2) the normal Windows Start Menu (shift-Start) and (4) the Open Shell menu (Start without shift).

@timadye commented on GitHub (Dec 6, 2023): > Does this issue also happen without Open Shell? It's a fantastic extension, but I wonder if there might be a new incompatibility there... I can try uninstalling and see if it makes a difference, though I doubt it since I had the same version of Open Shell for a long time on my old laptop and this issue appeared recently. Also, just to be clear: in my list above, I tried starting with both (2) the normal Windows Start Menu (shift-Start) and (4) the Open Shell menu (Start without shift).
claunia commented 2026-01-31 07:28:47 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 6, 2023):

Okay, so there are two separate things going on here.

Problem the first: @ilcpm we think there might be an issue with app paths. If you just go toggle the app execution alias for wt, we think it might Just Work.

If it doesn't, then the output of reg query "HKCU\Software\Microsoft\Windows\CurrentVersion\App Paths\wt.exe" /s might be helpful

It should look something like this:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\App Paths\wt.exe
    (Default)    REG_SZ    C:\Program Files\WindowsApps\Microsoft.WindowsTerminalCanary_1.20.3391.0_x64__8wekyb3d8bbwe\wt.exe
    Path    REG_SZ    C:\Program Files\WindowsApps\Microsoft.WindowsTerminalCanary_1.20.3391.0_x64__8wekyb3d8bbwe`

(depending on the terminal branding and version)

Problem the second: @timadye we think there's probably a better dupe somewhere around here for what you're seeing, but we don't know off the top of our heads. Probably on in https://github.com/microsoft/terminal/issues?q=is%3Aissue+is%3Aopen+label%3ACulprit-Centennial

@zadjii-msft commented on GitHub (Dec 6, 2023): Okay, so there are two separate things going on here. --- Problem the first: @ilcpm we think there might be an issue with app paths. If you just go toggle the app execution alias for `wt`, we think it might Just Work. If it doesn't, then the output of `reg query "HKCU\Software\Microsoft\Windows\CurrentVersion\App Paths\wt.exe" /s` might be helpful It should look something like this: ``` HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\App Paths\wt.exe (Default) REG_SZ C:\Program Files\WindowsApps\Microsoft.WindowsTerminalCanary_1.20.3391.0_x64__8wekyb3d8bbwe\wt.exe Path REG_SZ C:\Program Files\WindowsApps\Microsoft.WindowsTerminalCanary_1.20.3391.0_x64__8wekyb3d8bbwe` ``` (depending on the terminal branding and version) ---- Problem the second: @timadye we think there's probably a better dupe somewhere around here for what you're seeing, but we don't know off the top of our heads. Probably on in https://github.com/microsoft/terminal/issues?q=is%3Aissue+is%3Aopen+label%3ACulprit-Centennial
claunia commented 2026-01-31 07:28:47 +00:00
Author
Owner
Copy Link

@D-Maxwell commented on GitHub (Dec 9, 2023):

I feel like we had another thread for this just recently, but I can't find it. The last one I can find has all sorts of notes about people disabling UAC, or otherwise attempting to mess with the permissions on WindowsApps

NOTE: Here's your reminder! NEVER mess with the permissions anywhere on WindowsApps!

Doing that may irreversibly break your OS install. Like, literally no way to recover without reinstalling the OS. Don't ever do it.

This has happened to me in the past, and after lots of fiddling around, resetting WindowsApps permissions to their defaults, and reinstalling affected packages, I can affirm it is in fact possible to recover from such a manipulation (on which I would like to know the internal reasons that make this a hassle in the first place ?)

@D-Maxwell commented on GitHub (Dec 9, 2023): > I feel like we had another thread for this just recently, but I can't find it. The last one I can find has all sorts of notes about people disabling UAC, or otherwise attempting to mess with the permissions on WindowsApps > > ### **NOTE**: Here's your reminder! NEVER mess with the permissions anywhere on `WindowsApps`! > Doing that may irreversibly break your OS install. Like, literally no way to recover without reinstalling the OS. Don't ever do it. This has happened to me in the past, and after lots of fiddling around, resetting WindowsApps permissions to their defaults, and reinstalling affected packages, I can affirm it is in fact possible to recover from such a manipulation (on which I would like to know the internal reasons that make this a hassle in the first place ?)
claunia commented 2026-01-31 07:28:47 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Dec 18, 2023):

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.

@microsoft-github-policy-service[bot] commented on GitHub (Dec 18, 2023): 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**. <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
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 Issue-Bug Needs-Author-Feedback Needs-Triage No-Recent-Activity
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#20950
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?