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

Wrong wt.exe binary picked up when invoked through explorer's search bar #10692

New Issue
Closed
opened 2026-01-31 02:27:33 +00:00 by claunia · 11 comments
claunia commented 2026-01-31 02:27:33 +00:00
Owner
Copy Link

Originally created by @erikha1501 on GitHub (Sep 19, 2020).

Environment

Windows build number:
Microsoft Windows [Version 10.0.19041.508]

Windows Terminal version (if applicable):
1.3.200825002-release1.3 (installed through Microsoft store)

Steps to reproduce

  1. Open Windows Explorer
  2. Type in the search box "wt" or "wt -d ." then hit enter
  3. Check the path where wt.exe is located. It looks something like this: "C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.3.2382.0_x64__8wekyb3d8bbwe\wt.exe"
    The newly opened Windows Terminal has this info:
Windows Terminal (Unpackaged)
Version: 1.3.200825002-release1.3

Expected behavior

The actual wt.exe binary should be located at "~\AppData\Local\Microsoft\WindowsApps\wt.exe". Running wt.exe through:

  • Run Dialog (Win+R)
  • Start (typing "wt" in Windows search)
  • Explorer's search bar

yield the same result.
However if I run it via cmd or powershell the correct Windows Terminal shows up.

I'm not sure if this is a bug in the terminal installation process or my windows environment is messed up. Here's a few things I noticed:

  • "~\AppData\Local\Microsoft\WindowsApps" directory is included in the PATH environment variable
  • PATH does not contain anything like "C:\Program Files\WindowsApps"
  • The "wrong" version of wt.exe fires up a Windows Terminal associated with a settings.json file located at "~\AppData\Local\Microsoft\Windows Terminal\settings.json". In contrast the normal settings.json lives at "~\AppData\Local\Packages\Microsoft.WindowsTerminalPreview_8wekyb3d8bbwe\LocalState\settings.json"
  • This problem persists if I switch to the stable version of Windows Terminal
Originally created by @erikha1501 on GitHub (Sep 19, 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! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: Microsoft Windows [Version 10.0.19041.508] Windows Terminal version (if applicable): 1.3.200825002-release1.3 (installed through Microsoft store) ``` # Steps to reproduce 1. Open Windows Explorer 2. Type in the search box "wt" or "wt -d ." then hit enter 3. Check the path where wt.exe is located. It looks something like this: "C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.3.2382.0_x64__8wekyb3d8bbwe\wt.exe" The newly opened Windows Terminal has this info: ``` Windows Terminal (Unpackaged) Version: 1.3.200825002-release1.3 ``` <!-- A description of how to trigger this bug. --> # Expected behavior The actual wt.exe binary should be located at "\~\AppData\Local\Microsoft\WindowsApps\wt.exe". Running wt.exe through: - Run Dialog (Win+R) - Start (typing "wt" in Windows search) - Explorer's search bar yield the same result. However if I run it via cmd or powershell the correct Windows Terminal shows up. I'm not sure if this is a bug in the terminal installation process or my windows environment is messed up. Here's a few things I noticed: - "\~\AppData\Local\Microsoft\WindowsApps" directory is included in the PATH environment variable - PATH does not contain anything like "C:\Program Files\WindowsApps" - The "wrong" version of wt.exe fires up a Windows Terminal associated with a settings.json file located at "\~\AppData\Local\Microsoft\Windows Terminal\settings.json". In contrast the normal settings.json lives at "\~\AppData\Local\Packages\Microsoft.WindowsTerminalPreview_8wekyb3d8bbwe\LocalState\settings.json" - This problem persists if I switch to the stable version of Windows Terminal
claunia added the Issue-QuestionNeeds-Tag-FixResolution-Answered labels 2026-01-31 02:27:33 +00:00
claunia commented 2026-01-31 02:27:34 +00:00
Author
Owner
Copy Link

@erikha1501 commented on GitHub (Sep 21, 2020):

It seems like the installation process adds 2 following entries to registry:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\wt.exe
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\wt.exe

Each has a pair of [Default] and Path string values pointing to the "wrong" wt.exe binary. Windows Explorer and Run Dialog Box might query this information to locate wt.exe. After removing these 2 entries, the expected behavior is observed.

@erikha1501 commented on GitHub (Sep 21, 2020): It seems like the installation process adds 2 following entries to registry: ``` HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\wt.exe HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\wt.exe ``` Each has a pair of [Default] and Path string values pointing to the "wrong" wt.exe binary. Windows Explorer and Run Dialog Box might query this information to locate wt.exe. After removing these 2 entries, the expected behavior is observed.
claunia commented 2026-01-31 02:27:35 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 21, 2020):

@DHowett @cinnamon-msft we should author a docs page about how wt works with both stable and preview installed, and how to pick which one you want to use in the settings app, since we keep getting this issue

@zadjii-msft commented on GitHub (Sep 21, 2020): @DHowett @cinnamon-msft we should author a docs page about how `wt` works with both stable and preview installed, and how to pick which one you want to use in the settings app, since we keep getting this issue
claunia commented 2026-01-31 02:27:35 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 21, 2020):

@zadjii-msft so this is weird—it doesn’t look like stable vs preview here, it looks like one of their versions is unpackaged.

@erikha1501 you haven’t changed any permissions in Program Files\WindowsApps, have you?

@DHowett commented on GitHub (Sep 21, 2020): @zadjii-msft so this is weird—it doesn’t look like stable vs preview here, it looks like one of their versions is _unpackaged_. @erikha1501 you haven’t changed any permissions in Program Files\WindowsApps, have you?
claunia commented 2026-01-31 02:27:35 +00:00
Author
Owner
Copy Link

@erikha1501 commented on GitHub (Sep 21, 2020):

I once took ownership of Program Files\WindowsApps to give me full control access. I added an permission entry then gave the ownership back to TrustedInstaller. This might be the culprit.

@erikha1501 commented on GitHub (Sep 21, 2020): I once took ownership of Program Files\WindowsApps to give me full control access. I added an permission entry then gave the ownership back to TrustedInstaller. This might be the culprit.
claunia commented 2026-01-31 02:27:35 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 21, 2020):

So, the files in that directory are usually only protected by the permissions that stop you from seeing them.

I believe that if the files in that folder are visible, the App Paths entry for wt might accidentally launch it directly out of Program Files. This would be like taking the contents of the application and running them without the rest of the package identity.

Terminal sorta supports this, but it's supposed to be by user choice.

If you remove the permission entry that you added, does the issue go away?

@DHowett commented on GitHub (Sep 21, 2020): So, the files in that directory are usually only protected by the permissions that stop you from seeing them. I believe that _if the files in that folder are visible_, the `App Paths` entry for `wt` might accidentally launch it directly out of Program Files. This would be like taking the contents of the application and running them without the rest of the package identity. Terminal sorta supports this, but it's supposed to be by user choice. If you remove the permission entry that you added, does the issue go away?
claunia commented 2026-01-31 02:27:35 +00:00
Author
Owner
Copy Link

@KalleOlaviNiemitalo commented on GitHub (Sep 21, 2020):

So, the files in that directory are usually only protected by the permissions that stop you from seeing them.

On Windows 10 version 2004 (OS Build 19041.508), I am able to list the files with dir "C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.3.2382.0_x64__8wekyb3d8bbwe" and run wt.exe from there, as a standard user. I have not changed the permissions nor ownership there. On the other hand, dir "C:\Program Files\WindowsApps" does not work, unless elevated.

@KalleOlaviNiemitalo commented on GitHub (Sep 21, 2020): > So, the files in that directory are usually only protected by the permissions that stop you from seeing them. On Windows 10 version 2004 (OS Build 19041.508), I am able to list the files with `dir "C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.3.2382.0_x64__8wekyb3d8bbwe"` and run `wt.exe` from there, as a standard user. I have not changed the permissions nor ownership there. On the other hand, `dir "C:\Program Files\WindowsApps"` does not work, unless elevated.
claunia commented 2026-01-31 02:27:35 +00:00
Author
Owner
Copy Link

@erikha1501 commented on GitHub (Sep 22, 2020):

If you remove the permission entry that you added, does the issue go away?

It did. After removing the entry and reinstalling Windows Terminal, the "unpackaged" version goes away.
I still can take a peak inside Program Files\WindowsApps\Microsoft.WindowsTerminal_1.2.2381.0_x64__8wekyb3d8bbwe, run wt.exe directly and it still works. Somehow that previously added permission entry prevented Windows Terminal from installing/running correctly. Messing with Program Files\WindowsApps folder was not a good idea after all.

@DHowett @cinnamon-msft we should author a docs page about how wt works with both stable and preview installed, and how to pick which one you want to use in the settings app, since we keep getting this issue

Documentation on how wt.exe works is definitely welcomed.

@erikha1501 commented on GitHub (Sep 22, 2020): > If you remove the permission entry that you added, does the issue go away? It did. After removing the entry and reinstalling Windows Terminal, the "unpackaged" version goes away. I still can take a peak inside `Program Files\WindowsApps\Microsoft.WindowsTerminal_1.2.2381.0_x64__8wekyb3d8bbwe`, run `wt.exe` directly and it still works. Somehow that previously added permission entry prevented Windows Terminal from installing/running correctly. Messing with `Program Files\WindowsApps` folder was _not_ a good idea after all. > @DHowett @cinnamon-msft we should author a docs page about how `wt` works with both stable and preview installed, and how to pick which one you want to use in the settings app, since we keep getting this issue Documentation on how `wt.exe` works is definitely welcomed.
claunia commented 2026-01-31 02:27:36 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 22, 2020):

Thanks for confirming! I'm gonna close this as resolved, but the learnings are still pretty interesting. I can bring them back to the application install folks -- they own the code that writes the App Paths entries that have been implicated in a number of our issues.

wt.exe actually just runs WindowsTerminal.exe from the same folder. There's nothing special about it; it's just that Terminal supports running inside and outside a "package" and it was never expected that it would be able to run outside of a package even though it had been installed inside one!

@DHowett commented on GitHub (Sep 22, 2020): Thanks for confirming! I'm gonna close this as resolved, but the learnings are still pretty interesting. I can bring them back to the application install folks -- they own the code that writes the App Paths entries that have been implicated in a number of our issues. `wt.exe` actually just runs `WindowsTerminal.exe` from the same folder. There's nothing special about it; it's just that Terminal supports running inside and outside a "package" and it was never expected that it would be able to run outside of a package even though it had been installed _inside_ one!
claunia commented 2026-01-31 02:27:36 +00:00
Author
Owner
Copy Link

@erikha1501 commented on GitHub (Sep 22, 2020):

wt.exe actually just runs WindowsTerminal.exe from the same folder

It definitely does more than just runs WindowsTerminal.exe as I can't get WindowsTerminal.exe to run on its own (Windows cannot access the specified device, path... error pops up if I try to do so). I suppose this behavior is intended. Nevertheless I can always look at the source code to see what wt.exe does.

Anyway thanks for the support on this one!

@erikha1501 commented on GitHub (Sep 22, 2020): > `wt.exe` actually just runs `WindowsTerminal.exe` from the same folder It definitely does more than just runs `WindowsTerminal.exe` as I can't get `WindowsTerminal.exe` to run on its own (`Windows cannot access the specified device, path...` error pops up if I try to do so). I suppose this behavior is intended. Nevertheless I can always look at the source code to see what `wt.exe` does. Anyway thanks for the support on this one!
claunia commented 2026-01-31 02:27:36 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 22, 2020):

I promise you that's all it does on our side. Here's the source, all 36 lines of it: https://github.com/microsoft/terminal/blob/master/src/cascadia/wt/shim.cpp

The app platform sets up permissions such that wt.exe is the only executable in the package that can be invoked directly -- this is part of the "app execution alias" infrastructure that populates %LOCALAPPDATA%\microsoft\windowsapps and in general does the work of exposing packaged executables as "normal" executables.

@DHowett commented on GitHub (Sep 22, 2020): I promise you that's all it does on our side. Here's the source, all 36 lines of it: https://github.com/microsoft/terminal/blob/master/src/cascadia/wt/shim.cpp The app platform sets up permissions such that `wt.exe` is the only executable in the package that can be invoked directly -- this is part of the "app execution alias" infrastructure that populates `%LOCALAPPDATA%\microsoft\windowsapps` and in general does the work of exposing packaged executables as "normal" executables.
claunia commented 2026-01-31 02:27:36 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 22, 2020):

But all of that stuff happens outside of our codebase, in the AppXSvc system service. The extent of our code is "just launch WindowsTerminal.exe". Once the process has "package identity" granted to it by the OS, it's allowed to do so.

@DHowett commented on GitHub (Sep 22, 2020): But all of that stuff happens outside of our codebase, in the `AppXSvc` system service. The extent of our code is "just launch WindowsTerminal.exe". Once the process has "package identity" granted to it by the OS, it's allowed to do so.
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-Question Needs-Tag-Fix Resolution-Answered
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#10692
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?