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

wt: The term 'wt' is not recognized as a name of a cmdlet #21891

New Issue
Closed
opened 2026-01-31 07:57:33 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 07:57:33 +00:00
Owner
Copy Link

Originally created by @Rusinas on GitHub (Jun 21, 2024).

Windows Terminal version

No response

Windows build number

No response

Other Software

No response

Steps to reproduce

Try to execute wt from the terminal

Expected Behavior

Opening another windows terminal

Actual Behavior

Well, I don't know what happened, everything worked just fine yesterday and all of a sudden I started to get this error. Reinstallation didn't help, but I found that it is now being installed into the Program Files directory instead of AppData/Local and it creates inaccessible WindowsApp folder:
image

I think that's the reason, but I don't know how to solve it, couldn't manage to gain the access to that folder

Originally created by @Rusinas on GitHub (Jun 21, 2024). ### Windows Terminal version _No response_ ### Windows build number _No response_ ### Other Software _No response_ ### Steps to reproduce Try to execute `wt` from the terminal ### Expected Behavior Opening another windows terminal ### Actual Behavior Well, I don't know what happened, everything worked just fine yesterday and all of a sudden I started to get this error. Reinstallation didn't help, but I found that it is now being installed into the `Program Files` directory instead of `AppData/Local` and it creates inaccessible `WindowsApp` folder: ![image](https://github.com/microsoft/terminal/assets/42975143/51bd79d3-613b-4e47-8ea0-06fab300b81a) I think that's the reason, but I don't know how to solve it, couldn't manage to gain the access to that folder
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 07:57:34 +00:00
claunia commented 2026-01-31 07:57:35 +00:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 21, 2024):

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@github-actions[bot] commented on GitHub (Jun 21, 2024): Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! ### Closed similar issues: - [`wt` doesn't work anymore (#12767)](https://github.com/microsoft/terminal/issues/12767), similarity score: 0.81 > Note: You can give me feedback by thumbs upping or thumbs downing this comment.
claunia commented 2026-01-31 07:57:35 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Jun 21, 2024):

Is the wt.exe alias still enabled for you?

image

(In your case it wouldn't have "Canary" in the name.)

@lhecker commented on GitHub (Jun 21, 2024): Is the wt.exe alias still enabled for you? ![image](https://github.com/microsoft/terminal/assets/2256941/c2b2a146-9285-4482-b396-c166c414be36) (In your case it wouldn't have "Canary" in the name.)
claunia commented 2026-01-31 07:57:35 +00:00
Author
Owner
Copy Link

@Rusinas commented on GitHub (Jun 22, 2024):

@lhecker oh, yes, I forgot to mention that I toggled it back and forth too, didn't help 😭
image

@Rusinas commented on GitHub (Jun 22, 2024): @lhecker oh, yes, I forgot to mention that I toggled it back and forth too, didn't help 😭 ![image](https://github.com/microsoft/terminal/assets/42975143/8474d5ba-9349-47be-93a9-befe975d17e3)
claunia commented 2026-01-31 07:57:35 +00:00
Author
Owner
Copy Link

@Rusinas commented on GitHub (Jun 22, 2024):

Now I manually opened C:\Users\andre\AppData\Local\Microsoft\WindowsApps\Microsoft.WindowsTerminal_8wekyb3d8bbwe and found there wt,exe with 0 KB size which is weird.
image

Unfortunately, I can't remove or replace it for some reason:
image

I also tried to add C:\Program Files\WindowsApps to the Path, as well as C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.20.11381.0_x64__8wekyb3d8bbwe specifically, nothing of this worked, even though there is valid wt.exe in that folder

@Rusinas commented on GitHub (Jun 22, 2024): Now I manually opened `C:\Users\andre\AppData\Local\Microsoft\WindowsApps\Microsoft.WindowsTerminal_8wekyb3d8bbwe` and found there `wt,exe` with 0 KB size which is weird. ![image](https://github.com/microsoft/terminal/assets/42975143/d8e3af0e-06cb-4450-abed-d5831b03a6e4) Unfortunately, I can't remove or replace it for some reason: ![image](https://github.com/microsoft/terminal/assets/42975143/537c0191-2cb6-4d28-a366-2ab4f95041de) I also tried to add `C:\Program Files\WindowsApps` to the `Path`, as well as `C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.20.11381.0_x64__8wekyb3d8bbwe` specifically, nothing of this worked, even though there is valid `wt.exe` in that folder
claunia commented 2026-01-31 07:57:35 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 22, 2024):

I just want to quick jump in and say: Don't mess with the permissions on C:\Program Files\WindowsApps. That can permanently mess up the OS install.

The 0-byte wt.exe is something called an "App Execution Alias". It's basically a link to the one that lives in C:\Program Files\WindowsApps. The OS is supposed to have built-in special casing for those such that when they try to launch the thing from C:\Program Files\WindowsApps and fail, the OS will instead boot the thing from C:\Program Files\WindowsApps with the correct package identity.

Do any other app execution aliases work for you/?

@zadjii-msft commented on GitHub (Jun 22, 2024): I just want to quick jump in and say: Don't mess with the permissions on `C:\Program Files\WindowsApps`. That can _permanently_ mess up the OS install. The 0-byte `wt.exe` is something called an "App Execution Alias". It's basically a link to the one that lives in `C:\Program Files\WindowsApps`. The OS is supposed to have built-in special casing for those such that when they try to launch the thing from `C:\Program Files\WindowsApps` and fail, the OS will instead boot the thing from `C:\Program Files\WindowsApps` with the correct package identity. Do any other app execution aliases work for you/?
claunia commented 2026-01-31 07:57:35 +00:00
Author
Owner
Copy Link

@Rusinas commented on GitHub (Jun 23, 2024):

@zadjii-msft yeah, I just was desperate. Resintalled windows, now everything is fine 😂

@Rusinas commented on GitHub (Jun 23, 2024): @zadjii-msft yeah, I just was desperate. Resintalled windows, now everything is fine 😂
claunia commented 2026-01-31 07:57:36 +00:00
Author
Owner
Copy Link

@Fred-Vatin commented on GitHub (Sep 10, 2025):

Adding %LocalAppData%\Microsoft\WindowsApps to the user path did the trick.

@Fred-Vatin commented on GitHub (Sep 10, 2025): Adding `%LocalAppData%\Microsoft\WindowsApps` to the user path did the trick.
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-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#21891
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?