-
Notifications
You must be signed in to change notification settings - Fork 8.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No longer launched from win 10 search WT
#13286
Comments
WT
I'm pretty confident that If there isn't, but |
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 |
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! Literally begging on my knees... |
@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 |
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! |
Windows Terminal version
1.13.11431.0
Windows build number
10.0.19044.1706
Other Software
No response
Steps to reproduce
where.exe
I also tried:
C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.13.11431.0_x64__8wekyb3d8bbwe\wt.exe
and the same result happensstart "" "C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.13.11431.0_x64__8wekyb3d8bbwe\wt.exe" -p "Command Prompt" w -1
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.
The text was updated successfully, but these errors were encountered: