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 doesn't work anymore #17093

New Issue
Closed
opened 2026-01-31 05:32:02 +00:00 by claunia · 12 comments
claunia commented 2026-01-31 05:32:02 +00:00
Owner
Copy Link

Originally created by @MikronT on GitHub (Mar 26, 2022).

Windows Terminal version

1.13.1073

Windows build number

10.0.19044.1620

Other Software

No any special conflicting software is installed.

Outdated path C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.13.10336.0_x64__8wekyb3d8bbwe was found specified in Path environment variable, but the folder itself contains only font files CascadiaMono.ttf and CascadiaMonoItalic.ttf.

Steps to reproduce

Expected Behavior

Open a new Terminal window or a new tab

Actual Behavior

Command prompt doesn't recognize wt at all.

Microsoft Windows [Version 10.0.19044.1620]
(c) Microsoft Corporation. All rights reserved.

C:\Users\User>wt
'wt' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\User>

If you run it using either Run dialog or Search, terminal fails to start.

image

Your mouse pointer shows that the app is working in the background for a while. Also, a Windows Problem Reporting process appears in Task Manager for a moment.

Originally created by @MikronT on GitHub (Mar 26, 2022). ### Windows Terminal version 1.13.1073 ### Windows build number 10.0.19044.1620 ### Other Software No any special conflicting software is installed. Outdated path `C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.13.10336.0_x64__8wekyb3d8bbwe` was found specified in `Path` environment variable, but the folder itself contains only font files `CascadiaMono.ttf` and `CascadiaMonoItalic.ttf`. ### Steps to reproduce - Update to the latest [Windows Terminal Preview v1.13.1073](https://github.com/microsoft/terminal/releases/tag/v1.13.10733.0) - Run terminal using `wt` anywhere ### Expected Behavior Open a new Terminal window or a new tab ### Actual Behavior Command prompt doesn't recognize `wt` at all. ```text Microsoft Windows [Version 10.0.19044.1620] (c) Microsoft Corporation. All rights reserved. C:\Users\User>wt 'wt' is not recognized as an internal or external command, operable program or batch file. C:\Users\User> ``` If you run it using either Run dialog or Search, terminal fails to start. ![image](https://user-images.githubusercontent.com/45333177/160242226-1d6e4024-da4e-4b4d-bcf2-3f6a888bc9db.png) Your mouse pointer shows that the app is working in the background for a while. Also, a Windows Problem Reporting process appears in Task Manager for a moment.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 05:32:02 +00:00
claunia commented 2026-01-31 05:32:03 +00:00
Author
Owner
Copy Link

@MikronT commented on GitHub (Mar 27, 2022):

Application error information from Windows Event Viewer:

Faulting application name: WindowsTerminal.exe, version: 1.13.2203.14003, time stamp: 0x622fbb2a
Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf
Exception code: 0xc0000409
Fault offset: 0x000000000007286e
Faulting process id: 0x13bc
Faulting application start time: 0x01d8411827544d62
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.13.10733.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report Id: ede4bd23-847b-422d-9dc7-48933c3e073c
Faulting package full name: 
Faulting package-relative application ID:

Fields Faulting process id, Faulting application start time, and Report Id are different in different log entries.

@MikronT commented on GitHub (Mar 27, 2022): Application error information from Windows Event Viewer: ```text Faulting application name: WindowsTerminal.exe, version: 1.13.2203.14003, time stamp: 0x622fbb2a Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf Exception code: 0xc0000409 Fault offset: 0x000000000007286e Faulting process id: 0x13bc Faulting application start time: 0x01d8411827544d62 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.13.10733.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\Windows\System32\ucrtbase.dll Report Id: ede4bd23-847b-422d-9dc7-48933c3e073c Faulting package full name: Faulting package-relative application ID: ``` Fields `Faulting process id`, `Faulting application start time`, and `Report Id` are different in different log entries.
claunia commented 2026-01-31 05:32:03 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 27, 2022):

Does starting "Windows Terminal" from the Start Menu work? Like, is it just wt.exe specifically that doesn't work?

What does your %PATH% look like?

@zadjii-msft commented on GitHub (Mar 27, 2022): Does starting "Windows Terminal" from the Start Menu work? Like, is it just `wt.exe` specifically that doesn't work? What does your `%PATH%` look like?
claunia commented 2026-01-31 05:32:03 +00:00
Author
Owner
Copy Link

@MikronT commented on GitHub (Mar 27, 2022):

Yes, starting Windows Terminal from the Start Menu works. Even starting terminal profiles from PowerToys Run works.

Here's my %Path%

C:\Program Files\Common Files\Oracle\Java\javapath
C:\ProgramData\Oracle\Java\javapath
C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\intel64\compiler
C:\Windows\system32
C:\Windows
C:\Windows\System32\Wbem
C:\Windows\System32\WindowsPowerShell\v1.0\
C:\Windows\System32\OpenSSH\
C:\Program Files\mingw-w64\x86_64-8.1.0-posix-seh-rt_v6-rev0\mingw64\bin
C:\Program Files (x86)\GnuWin32\bin
C:\Program Files\dotnet\
C:\Program Files (x86)\Avogadro\bin
C:\Program Files\Gource\cmd
C:\Program Files\NVIDIA Corporation\NVIDIA NvDLISR
C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common
C:\Program Files\Git\cmd
C:\Program Files\Apache\maven-3.8.4\bin
C:\Program Files\VideoLAN\VLC
C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.13.10336.0_x64__8wekyb3d8bbwe
C:\Program Files\WindowsApps\Microsoft.DesktopAppInstaller_1.17.10271.0_x64__8wekyb3d8bbwe
C:\Program Files\PuTTY\
C:\Program Files\PowerShell\7\
C:\Users\User\AppData\Local\Programs\Python\Python310\Scripts\
C:\Users\User\AppData\Local\Programs\Python\Python310\
C:\Users\User\scoop\shims
C:\Users\User\AppData\Local\Programs\Microsoft VS Code\bin
C:\Users\User\AppData\Local\GitHubDesktop\bin
@MikronT commented on GitHub (Mar 27, 2022): Yes, starting Windows Terminal from the Start Menu works. Even starting terminal profiles from PowerToys Run works. Here's my `%Path%` ```text C:\Program Files\Common Files\Oracle\Java\javapath C:\ProgramData\Oracle\Java\javapath C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\intel64\compiler C:\Windows\system32 C:\Windows C:\Windows\System32\Wbem C:\Windows\System32\WindowsPowerShell\v1.0\ C:\Windows\System32\OpenSSH\ C:\Program Files\mingw-w64\x86_64-8.1.0-posix-seh-rt_v6-rev0\mingw64\bin C:\Program Files (x86)\GnuWin32\bin C:\Program Files\dotnet\ C:\Program Files (x86)\Avogadro\bin C:\Program Files\Gource\cmd C:\Program Files\NVIDIA Corporation\NVIDIA NvDLISR C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common C:\Program Files\Git\cmd C:\Program Files\Apache\maven-3.8.4\bin C:\Program Files\VideoLAN\VLC C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.13.10336.0_x64__8wekyb3d8bbwe C:\Program Files\WindowsApps\Microsoft.DesktopAppInstaller_1.17.10271.0_x64__8wekyb3d8bbwe C:\Program Files\PuTTY\ C:\Program Files\PowerShell\7\ C:\Users\User\AppData\Local\Programs\Python\Python310\Scripts\ C:\Users\User\AppData\Local\Programs\Python\Python310\ C:\Users\User\scoop\shims C:\Users\User\AppData\Local\Programs\Microsoft VS Code\bin C:\Users\User\AppData\Local\GitHubDesktop\bin ```
claunia commented 2026-01-31 05:32:03 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 28, 2022):

Did you add C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.13.10336.0_x64__8wekyb3d8bbwe to the PATH yourself? Pretty sure that's not supposed to be there. wt.exe is supposed to be accessed via C:\Users\migrie\AppData\Local\Microsoft\WindowsApps\wt.exe, which is an "app execution alias", which is a special type of shortcut that sets the OS up to actually start the one that's in C:\Program Files\WindowsApps\Microsoft.WindowsTerminal*__8wekyb3d8bbwe. If you launch the one in C:\Program Files\WindowsApps\Microsoft.WindowsTerminal*__8wekyb3d8bbwe directly, you're guaranteed to have a bad time 😄

@zadjii-msft commented on GitHub (Mar 28, 2022): Did you add `C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.13.10336.0_x64__8wekyb3d8bbwe` to the PATH yourself? _Pretty sure_ that's not supposed to be there. `wt.exe` is supposed to be accessed via `C:\Users\migrie\AppData\Local\Microsoft\WindowsApps\wt.exe`, which is an "app execution alias", which is a special type of shortcut that sets the OS up to actually start the one that's in `C:\Program Files\WindowsApps\Microsoft.WindowsTerminal*__8wekyb3d8bbwe`. If you launch the one in `C:\Program Files\WindowsApps\Microsoft.WindowsTerminal*__8wekyb3d8bbwe` directly, you're guaranteed to have a bad time 😄
claunia commented 2026-01-31 05:32:04 +00:00
Author
Owner
Copy Link

@MikronT commented on GitHub (Mar 28, 2022):

Did you add C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.13.10336.0_x64__8wekyb3d8bbwe to the PATH yourself? Pretty sure that's not supposed to be there.

I'm sure I didn't modify the Path environment variable by myself and I don't know why an outdated path was specified there. I removed it manually and rebooted my PC. Nothing changed.

wt.exe is supposed to be accessed via C:\Users\migrie\AppData\Local\Microsoft\WindowsApps\wt.exe, which is an "app execution alias", which is a special type of shortcut that sets the OS up to actually start the one that's in C:\Program Files\WindowsApps\Microsoft.WindowsTerminal*__8wekyb3d8bbwe.

The app execution alias C:\Users\User\AppData\Local\Microsoft\WindowsApps\wt.exe is in its place. Many other aliases, like winget.exe and python.exe, work like expected.

@MikronT commented on GitHub (Mar 28, 2022): > Did you add `C:\Program Files\WindowsApps\Microsoft.WindowsTerminalPreview_1.13.10336.0_x64__8wekyb3d8bbwe` to the PATH yourself? _Pretty sure_ that's not supposed to be there. I'm sure I didn't modify the `Path` environment variable by myself and I don't know why an outdated path was specified there. I removed it manually and rebooted my PC. Nothing changed. > `wt.exe` is supposed to be accessed via `C:\Users\migrie\AppData\Local\Microsoft\WindowsApps\wt.exe`, which is an "app execution alias", which is a special type of shortcut that sets the OS up to actually start the one that's in `C:\Program Files\WindowsApps\Microsoft.WindowsTerminal*__8wekyb3d8bbwe`. The app execution alias `C:\Users\User\AppData\Local\Microsoft\WindowsApps\wt.exe` is in its place. Many other aliases, like `winget.exe` and `python.exe`, work like expected.
claunia commented 2026-01-31 05:32:04 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 28, 2022):

Oh, you might need to add C:\Users\User\AppData\Local\Microsoft\WindowsApps back to your PATH. Though, I have no idea why winget and python would still work here.

Before you add WindowsApps back to the PATH, what's the output of

  • where winget
  • where python
  • where wt
@zadjii-msft commented on GitHub (Mar 28, 2022): Oh, you might need to add `C:\Users\User\AppData\Local\Microsoft\WindowsApps` back to your PATH. Though, I have no idea why `winget` and `python` would still work here. Before you add `WindowsApps` back to the PATH, what's the output of * `where winget` * `where python` * `where wt`
claunia commented 2026-01-31 05:32:04 +00:00
Author
Owner
Copy Link

@MikronT commented on GitHub (Mar 29, 2022):

Here's the output you asked for:

C:\Users\User>where winget
C:\Program Files\WindowsApps\Microsoft.DesktopAppInstaller_1.17.10271.0_x64__8wekyb3d8bbwe\winget.exe

C:\Users\User>where python
C:\Users\User\AppData\Local\Programs\Python\Python310\python.exe

C:\Users\User>where wt
INFO: Could not find files for the given pattern(s).

Ok, python and winget seem to add their root dirs to the Path variable manually. At the same time, they try to use app execution aliases too because appropriate files exist in the C:\Users\User\AppData\Local\Microsoft\WindowsApps folder.

When it comes to C:\Users\User\AppData\Local\Microsoft\WindowsApps that mysteriously disappeared during the last update, adding it to the Path variable solves the issue partially:

  • The alias works fine in any command-line environment (here are 3 new tabs created by 3 wt executions)
    image

  • Other places, like Win+R dialog, Explorer path, and PowerToys Run, can't run terminal (nothing happens)

@MikronT commented on GitHub (Mar 29, 2022): Here's the output you asked for: ```text C:\Users\User>where winget C:\Program Files\WindowsApps\Microsoft.DesktopAppInstaller_1.17.10271.0_x64__8wekyb3d8bbwe\winget.exe C:\Users\User>where python C:\Users\User\AppData\Local\Programs\Python\Python310\python.exe C:\Users\User>where wt INFO: Could not find files for the given pattern(s). ``` Ok, `python` and `winget` seem to add their root dirs to the `Path` variable manually. At the same time, they try to use app execution aliases too because appropriate files exist in the `C:\Users\User\AppData\Local\Microsoft\WindowsApps` folder. --- When it comes to `C:\Users\User\AppData\Local\Microsoft\WindowsApps` that mysteriously disappeared during the last update, adding it to the `Path` variable **solves the issue partially**: - The alias works fine in any command-line environment (here are 3 new tabs created by 3 `wt` executions) ![image](https://user-images.githubusercontent.com/45333177/160500565-2d7dddea-3cc6-48ee-9fb8-d76c40d21ba1.png) - Other places, like `Win+R` dialog, Explorer path, and PowerToys Run, **can't run terminal** (nothing happens)
claunia commented 2026-01-31 05:32:05 +00:00
Author
Owner
Copy Link

@omaus commented on GitHub (May 2, 2022):

Does not work for me as well, same error information in Event Viewer ("Response: Not available").

Some findings:

  • any of
    • WinKey -> wt -> Enter
    • Ctrl + R -> wt -> Enter
    • wt in File Explorer address bar -> Enter
    • lead to "C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.12.10982.0_x64__8wekyb3d8bbwe\wt.exe"
  • "C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.12.10982.0_x64__8wekyb3d8bbwe\wt.exe" fails silently with error in Event Manager as indicated above
  • "C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.12.10982.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe" fails too
  • "%localappdata%\Microsoft\WindowsApps\wt.exe" works properly
  • "%localappdata%\Microsoft\WindowsApps\Microsoft.WindowsTerminal_8wekyb3d8bbwe\wt.exe" works properly too

How is it even possible that Windows links wt to an .exe in C:\Program Files... though it is NOT in PATH?

My User PATH:
image

My System PATH:
image

@omaus commented on GitHub (May 2, 2022): Does not work for me as well, same error information in Event Viewer ("Response: Not available"). Some findings: - any of - WinKey -> `wt` -> Enter - Ctrl + R -> `wt` -> Enter - `wt` in File Explorer address bar -> Enter - lead to "C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.12.10982.0_x64__8wekyb3d8bbwe\wt.exe" - "C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.12.10982.0_x64__8wekyb3d8bbwe\wt.exe" fails silently with error in Event Manager as indicated above - "C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.12.10982.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe" fails too - "%localappdata%\Microsoft\WindowsApps\wt.exe" works properly - "%localappdata%\Microsoft\WindowsApps\Microsoft.WindowsTerminal_8wekyb3d8bbwe\wt.exe" works properly too How is it even possible that Windows links `wt` to an .exe in C:\Program Files\... though it is **NOT** in PATH? My User PATH: ![image](https://user-images.githubusercontent.com/47781170/166266549-6e8a1639-0e9e-4d60-ab10-1597cea128ce.png) My System PATH: ![image](https://user-images.githubusercontent.com/47781170/166266799-6df1c987-924a-4634-b2a2-8973e8ab6ae8.png)
claunia commented 2026-01-31 05:32:05 +00:00
Author
Owner
Copy Link

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

How is it even possible that Windows links wt to an .exe in C:\Program Files... though it is NOT in PATH?

ShellExecute can read the path from [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\wt.exe] or from the same in HKEY_LOCAL_MACHINE. The store package installer apparently sets those. See Using the App Paths Subkey.

@KalleOlaviNiemitalo commented on GitHub (Jun 14, 2022): > How is it even possible that Windows links `wt` to an .exe in C:\Program Files... though it is **NOT** in PATH? ShellExecute can read the path from [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\wt.exe] or from the same in HKEY_LOCAL_MACHINE. The store package installer apparently sets those. See [Using the App Paths Subkey](https://docs.microsoft.com/en-us/windows/win32/shell/app-registration#using-the-app-paths-subkey).
claunia commented 2026-01-31 05:32:05 +00:00
Author
Owner
Copy Link

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

How is it even possible that Windows links wt to an .exe in C:\Program Files... though it is NOT in PATH?

ShellExecute can read the path from [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\wt.exe] or from the same in HKEY_LOCAL_MACHINE. The store package installer apparently sets those. See Using the App Paths Subkey.

Good to know.

@omaus commented on GitHub (Jun 14, 2022): > > How is it even possible that Windows links `wt` to an .exe in C:\Program Files... though it is **NOT** in PATH? > > ShellExecute can read the path from [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\wt.exe] or from the same in HKEY_LOCAL_MACHINE. The store package installer apparently sets those. See [Using the App Paths Subkey](https://docs.microsoft.com/en-us/windows/win32/shell/app-registration#using-the-app-paths-subkey). Good to know.
claunia commented 2026-01-31 05:32:05 +00:00
Author
Owner
Copy Link

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

I believe this was fixed as part of #13193.
/dup #13193

@lhecker commented on GitHub (Jul 7, 2022): I believe this was fixed as part of #13193. /dup #13193
claunia commented 2026-01-31 05:32:05 +00:00
Author
Owner
Copy Link

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

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Jul 7, 2022): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
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 Resolution-Duplicate
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#17093
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?