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

No longer launched from win 10 search WT #17703

New Issue
Closed
opened 2026-01-31 05:50:52 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 05:50:52 +00:00
Owner
Copy Link

Originally created by @jredfox on GitHub (Jun 12, 2022).

Windows Terminal version

1.13.11431.0

Windows build number

10.0.19044.1706

Other Software

No response

Steps to reproduce

  • search in the windows 10 search bar wt
  • Capture
  • click enter once it's highlighted
  • nothing happens
  • search wt using where.exe
C:\Users\jredfox>where wt
C:\Users\jredfox\AppData\Local\Microsoft\WindowsApps\wt.exe

I also tried:

  • repairing the app from apps and features
  • resetting the app data from apps and features
  • unintstalling and re-installing the app from the windows store
  • double clicking wt.exe found in this path. the path was determined by clicking open file location of wt from the start menu C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.13.11431.0_x64__8wekyb3d8bbwe\wt.exe and the same result happens
  • running in cmd start "" "C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.13.11431.0_x64__8wekyb3d8bbwe\wt.exe" -p "Command Prompt" w -1
  • running in cmd start "" "C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.13.11431.0_x64__8wekyb3d8bbwe\wt.exe" -p "Command Prompt" new-tab

Expected Behavior

it opens up WT UI

Actual Behavior

it either runs in the background then closes or doesn't open at all.

Originally created by @jredfox on GitHub (Jun 12, 2022). ### Windows Terminal version 1.13.11431.0 ### Windows build number 10.0.19044.1706 ### Other Software _No response_ ### Steps to reproduce - search in the windows 10 search bar wt - ![Capture](https://user-images.githubusercontent.com/9736369/173471529-e6bba328-c469-460a-9597-6044682ef0cb.PNG) - click enter once it's highlighted - nothing happens - search wt using `where.exe` ``` C:\Users\jredfox>where wt C:\Users\jredfox\AppData\Local\Microsoft\WindowsApps\wt.exe ``` I also tried: - repairing the app from apps and features - resetting the app data from apps and features - unintstalling and re-installing the app from the windows store - double clicking wt.exe found in this path. the path was determined by clicking open file location of wt from the start menu `C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.13.11431.0_x64__8wekyb3d8bbwe\wt.exe` and the same result happens - running in cmd `start "" "C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.13.11431.0_x64__8wekyb3d8bbwe\wt.exe" -p "Command Prompt" w -1` - running in cmd `start "" "C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.13.11431.0_x64__8wekyb3d8bbwe\wt.exe" -p "Command Prompt" new-tab` ### Expected Behavior it opens up WT UI ### Actual Behavior it either runs in the background then closes or doesn't open at all.
claunia added the Needs-TriageIssue-BugNeeds-Tag-FixNeeds-Attention labels 2026-01-31 05:50:52 +00:00
claunia commented 2026-01-31 05:50:53 +00:00
Author
Owner
Copy Link

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

I'm pretty confident that C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_... isn't actually supposed to be used. There's an "app execution alias" for the Terminal at %LOCALAPPDATA%\Microsoft\WindowsApps\wt.exe which should probably be used instead. Is there a wt.exe your PATH/? (an easy way to check this is where wt in Command Prompt)

If there isn't, but %LOCALAPPDATA%\Microsoft\WindowsApps is on the PATH, then you might need to re-enable the wt execution alias:

image

@zadjii-msft commented on GitHub (Jun 13, 2022): I'm pretty confident that `C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_...` isn't actually supposed to be used. There's an "app execution alias" for the Terminal at `%LOCALAPPDATA%\Microsoft\WindowsApps\wt.exe` which should probably be used instead. Is there a `wt.exe` your PATH/? (an easy way to check this is `where wt` in Command Prompt) If there isn't, but `%LOCALAPPDATA%\Microsoft\WindowsApps` is on the PATH, then you might need to re-enable the `wt` execution alias: ![image](https://user-images.githubusercontent.com/18356694/173403444-6e49275c-f116-49ab-9e42-9c446787cb6d.png)
claunia commented 2026-01-31 05:50:54 +00:00
Author
Owner
Copy Link

@jredfox commented on GitHub (Jun 14, 2022):

Idk it appeared in the search bar after reinstalling the app if it's suppose to only be terminal or windows terminal shortcut which does work then the original needs to be removed

Wt launches from command prompt. It's from the search bar that doesn't work

@jredfox commented on GitHub (Jun 14, 2022): Idk it appeared in the search bar after reinstalling the app if it's suppose to only be terminal or windows terminal shortcut which does work then the original needs to be removed Wt launches from command prompt. It's from the search bar that doesn't work
claunia commented 2026-01-31 05:50:54 +00:00
Author
Owner
Copy Link

@jredfox commented on GitHub (Jun 14, 2022):

Capture

@jredfox commented on GitHub (Jun 14, 2022): ![Capture](https://user-images.githubusercontent.com/9736369/173471529-e6bba328-c469-460a-9597-6044682ef0cb.PNG)
claunia commented 2026-01-31 05:50:54 +00:00
Author
Owner
Copy Link

@jkyndir commented on GitHub (Jul 6, 2022):

@jredfox

Hi, there.

I had the exact same problem where I cannot open windows terminal in the start menu or in windows explorer's address bar.

HELP!
Would appreciate your help so much.

Literally begging on my knees...

@jkyndir commented on GitHub (Jul 6, 2022): @jredfox Hi, there. I had the exact same problem where I cannot open windows terminal in the start menu or in windows explorer's address bar. HELP! Would appreciate your help so much. Literally begging on my knees...
claunia commented 2026-01-31 05:50:55 +00:00
Author
Owner
Copy Link

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

@jkyndir Can you file a new issue? Make sure to include build numbers, Terminal version numbers, specific repro steps, etc. Also make sure to try toggling the wt.exe "app execution alias", and make sure that there's a wt.exe on your PATH (where wt in a Command Prompt window may be enlightening)

@zadjii-msft commented on GitHub (Jul 6, 2022): @jkyndir Can you file a new issue? Make sure to include build numbers, Terminal version numbers, specific repro steps, etc. Also make sure to try toggling the `wt.exe` "app execution alias", and make sure that there's a `wt.exe` on your `PATH` (`where wt` in a Command Prompt window may be enlightening)
claunia commented 2026-01-31 05:50:55 +00:00
Author
Owner
Copy Link

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

I came to this issue because I was having the same troubles recently. The alias was still enabled but "where wt" wasn't returning anything. Sure enough checking my PATH no longer had the entry for some reason. Manually adding %LOCALAPPDATA%\Microsoft\WindowsApps\wt.exe resulted in "wt" finding the terminal from the Start menu again.

Thanks for the tips @zadjii-msft. I'm not sure why it suddenly disappeared but it's definitely working as expected for me now!

@zamadatix commented on GitHub (Jul 7, 2022): I came to this issue because I was having the same troubles recently. The alias was still enabled but "where wt" wasn't returning anything. Sure enough checking my PATH no longer had the entry for some reason. Manually adding %LOCALAPPDATA%\Microsoft\WindowsApps\wt.exe resulted in "wt" finding the terminal from the Start menu again. Thanks for the tips @zadjii-msft. I'm not sure why it suddenly disappeared but it's definitely working as expected for me now!
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 Issue-Bug Needs-Attention 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#17703
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?