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

Show "Windows Terminal" in Search when typing "wt" #9378

New Issue
Closed
opened 2026-01-31 01:53:03 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 01:53:03 +00:00
Owner
Copy Link

Originally created by @skyanchor on GitHub (Jul 1, 2020).

Description of the new feature/enhancement

When typing "cmd" in Windows Search, there comes "Command Prompt". On the other hand, when typing "wt" in Search, it shows a common icon with "Run Command". I'm wondering if it could show the app's icon and name.
image
image

Proposed technical implementation details (optional)

Originally created by @skyanchor on GitHub (Jul 1, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement When typing "cmd" in Windows Search, there comes "Command Prompt". On the other hand, when typing "wt" in Search, it shows a common icon with "Run Command". I'm wondering if it could show the app's icon and name. ![image](https://user-images.githubusercontent.com/52092252/86258185-1c05b200-bbed-11ea-890f-174518d35af5.png) ![image](https://user-images.githubusercontent.com/52092252/86258212-23c55680-bbed-11ea-85ba-72dc54c078bd.png) <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> # Proposed technical implementation details (optional) <!-- A clear and concise description of what you want to happen. -->
claunia added the Tracking-External label 2026-01-31 01:53:03 +00:00
claunia commented 2026-01-31 01:53:04 +00:00
Author
Owner
Copy Link

@KalleOlaviNiemitalo commented on GitHub (Jul 6, 2020):

On Windows 10 version 2004 (OS Build 19041.329), if I create the following Registry value, then the Start Menu shows the Windows Terminal icon when I search for wt, regardless of whether the wt.exe app execution alias is enabled:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\wt.exe]
@="C:\\Program Files\\WindowsApps\\Microsoft.WindowsTerminal_1.0.1811.0_x64__8wekyb3d8bbwe\\WindowsTerminal.exe"

Unfortunately, this Registry value also prevents Windows Terminal from starting when I click "Open" in the Start Menu after searching for wt, even if the wt.exe app execution alias is enabled. Process Monitor shows that it RuntimeBroker.exe tries to open "C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.0.1811.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe" for execute access, gets an ACCESS DENIED error, tries "%LOCALAPPDATA%\Microsoft\WindowsApps\WindowsTerminal.exe", and gets a NAME NOT FOUND error because the app execution alias is wt.exe rather than WindowsTerminal.exe.

If I instead search for skype.exe and click "Open", then RuntimeBroker.exe tries to open "C:\Program Files\WindowsApps\Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c\Skype\Skype.exe" for execute access, get an ACCESS DENIED error, tries "%LOCALAPPDATA%\Microsoft\WindowsApps\Skype.exe", and succeeds.

So, I think implementing this enhancement on Windows 10 version 2004 would require two things:

Ultimately, it would be better if this were implemented in Windows itself, so that the feature would apply to all apps that have app execution aliases.

@KalleOlaviNiemitalo commented on GitHub (Jul 6, 2020): On Windows 10 version 2004 (OS Build 19041.329), if I create the following Registry value, then the Start Menu shows the Windows Terminal icon when I search for `wt`, regardless of whether the `wt.exe` app execution alias is enabled: ``` Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\wt.exe] @="C:\\Program Files\\WindowsApps\\Microsoft.WindowsTerminal_1.0.1811.0_x64__8wekyb3d8bbwe\\WindowsTerminal.exe" ``` Unfortunately, this Registry value also prevents Windows Terminal from starting when I click "Open" in the Start Menu after searching for `wt`, even if the `wt.exe` app execution alias is enabled. Process Monitor shows that it RuntimeBroker.exe tries to open "C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.0.1811.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe" for execute access, gets an ACCESS DENIED error, tries "%LOCALAPPDATA%\Microsoft\WindowsApps\WindowsTerminal.exe", and gets a NAME NOT FOUND error because the app execution alias is `wt.exe` rather than `WindowsTerminal.exe`. If I instead search for `skype.exe` and click "Open", then RuntimeBroker.exe tries to open "C:\Program Files\WindowsApps\Microsoft.SkypeApp_15.61.100.0_x86__kzf8qxf38zg5c\Skype\Skype.exe" for execute access, get an ACCESS DENIED error, tries "%LOCALAPPDATA%\Microsoft\WindowsApps\Skype.exe", and succeeds. So, I think implementing this enhancement on Windows 10 version 2004 would require two things: - Add `wt.exe` to the directory of Windows Terminal, as planned in <https://github.com/microsoft/terminal/issues/6625#issuecomment-647816383>. - Add the Registry value under `App Paths`. Is this even possible from within an MSIX package? Ultimately, it would be better if this were implemented in Windows itself, so that the feature would apply to all apps that have app execution aliases.
claunia commented 2026-01-31 01:53:04 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 16, 2020):

Ultimately, it would be better if this were implemented in Windows itself, so that the feature would apply to all apps that have app execution aliases.

I fully concur with this. Let's use this as an opportunity to improve the entire platform.

@DHowett Do we know which team owns execution aliases, and if they'd be willing to pick this up for the next release?

@zadjii-msft commented on GitHub (Jul 16, 2020): > Ultimately, it would be better if this were implemented in Windows itself, so that the feature would apply to all apps that have app execution aliases. I fully concur with this. Let's use this as an opportunity to improve the entire platform. @DHowett Do we know which team owns execution aliases, and if they'd be willing to pick this up for the next release?
claunia commented 2026-01-31 01:53:04 +00:00
Author
Owner
Copy Link

@KalleOlaviNiemitalo commented on GitHub (Aug 5, 2020):

This issue has been sort-of fixed in Windows Terminal Preview. Now that the package contains wt.exe, AppXSvc creates wt.exe Registry keys under App Paths, and the Start menu shows the proper icon if I type wt. There is the https://github.com/microsoft/terminal/issues/7188 side effect, though.

@KalleOlaviNiemitalo commented on GitHub (Aug 5, 2020): This issue has been sort-of fixed in Windows Terminal Preview. Now that the package contains `wt.exe`, AppXSvc creates `wt.exe` Registry keys under App Paths, and the Start menu shows the proper icon if I type `wt`. There is the <https://github.com/microsoft/terminal/issues/7188> side effect, though.
claunia commented 2026-01-31 01:53:04 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Aug 5, 2020):

Marking tracking-external with MSFT:28186919. Feature request has been made to the appropriate folks.

@DHowett commented on GitHub (Aug 5, 2020): Marking tracking-external with MSFT:28186919. Feature request has been made to the appropriate folks.
claunia commented 2026-01-31 01:53:04 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 19, 2022):

Alrighty so chatted a bit with the search folks - this is gonna be the final form of this (at least for the long foreseeable future). Search will show the icon of the app the execution alias, but ultimately the important piece of data to surface is the execution alias itself.

Thanks!

@zadjii-msft commented on GitHub (Aug 19, 2022): Alrighty so chatted a bit with the search folks - this is gonna be the final form of this (at least for the long foreseeable future). Search will show the icon of the app the execution alias, but ultimately the important piece of data to surface is the execution alias itself. Thanks!
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 Tracking-External
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#9378
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?