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

Windows terminal doesn't start from command line, but will start if executed from Start menu #18028

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

Originally created by @eblis on GitHub (Jul 25, 2022).

Windows Terminal version

1.14.1962.0

Windows build number

10.0.19044 Build 19044

Other Software

No response

Steps to reproduce

Trying to start Windows terminal from a command prompt results in an error.

Faulting application name: WindowsTerminal.exe, version: 1.14.2207.15002, time stamp: 0x62d1f0dc
Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf
Exception code: 0xc0000409
Fault offset: 0x000000000007286e
Faulting process id: 0x77e8
Faulting application start time: 0x01d89ff96485caf2
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.14.1962.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: bb86db60-2ffc-4156-a74c-a1c4b9e1a6ec
Faulting package full name: 
Faulting package-relative application ID:

But if I start the application from the start menu then Windows Terminal starts successfully.
I've read #1364 a bit and tried some of the ideas there, installed PowerShell 7, forced terminal to use my integrated Intel display driver but none of them worked. I'm not sure it's the same issue because in that issue people couldn't get terminal to work in any scenario, but for me it works if I start from start menu.

Not sure if relevant but I don't have wt.exe and WindowsTerminal.exe in my path.
If I browse to the folder with windows terminal and try to run the command they do nothing, even wt -h or wt --version don't work.

I've installed Windows Terminal from the GitHub releases, but then updated it via Windows Update.

Also, my Windows Terminal icon is broken and I can't figure out how to fix it.
image

Expected Behavior

Windows terminal should be able to start from a command prompt as well.

Actual Behavior

Windows terminal crashes if started from a command prompt, but works if started from Start menu.

Originally created by @eblis on GitHub (Jul 25, 2022). ### Windows Terminal version 1.14.1962.0 ### Windows build number 10.0.19044 Build 19044 ### Other Software _No response_ ### Steps to reproduce Trying to start Windows terminal from a command prompt results in an error. ``` Faulting application name: WindowsTerminal.exe, version: 1.14.2207.15002, time stamp: 0x62d1f0dc Faulting module name: ucrtbase.dll, version: 10.0.19041.789, time stamp: 0x2bd748bf Exception code: 0xc0000409 Fault offset: 0x000000000007286e Faulting process id: 0x77e8 Faulting application start time: 0x01d89ff96485caf2 Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.14.1962.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe Faulting module path: C:\WINDOWS\System32\ucrtbase.dll Report Id: bb86db60-2ffc-4156-a74c-a1c4b9e1a6ec Faulting package full name: Faulting package-relative application ID: ``` But if I start the application from the start menu then Windows Terminal starts successfully. I've read #1364 a bit and tried some of the ideas there, installed PowerShell 7, forced terminal to use my integrated Intel display driver but none of them worked. I'm not sure it's the same issue because in that issue people couldn't get terminal to work in any scenario, but for me it works if I start from start menu. Not sure if relevant but I don't have `wt.exe` and `WindowsTerminal.exe` in my path. If I browse to the folder with windows terminal and try to run the command they do nothing, even `wt -h` or `wt --version` don't work. I've installed Windows Terminal from the GitHub releases, but then updated it via Windows Update. Also, my Windows Terminal icon is broken and I can't figure out how to fix it. ![image](https://user-images.githubusercontent.com/540188/180724259-8448eee5-4cea-418c-97d0-596a460169e9.png) ### Expected Behavior Windows terminal should be able to start from a command prompt as well. ### Actual Behavior Windows terminal crashes if started from a command prompt, but works if started from Start menu.
claunia added the Needs-TriageIssue-BugNeeds-Tag-FixNeeds-Attention labels 2026-01-31 06:01:38 +00:00
claunia commented 2026-01-31 06:01:39 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 25, 2022):

Not sure if relevant but I don't have wt.exe and WindowsTerminal.exe in my path.
If I browse to the folder with windows terminal and try to run the command they do nothing, even wt -h or wt --version don't work.

Which directory specifically/? The WindowsApps directory is special and isn't supposed to be accessed directly by the user. The App Execution Alias for Terminal, wt.exe, is a special type of link that the OS uses to do some extra validation before starting the Terminal. The OS won't let you run the app directly out of WindowsApps.

@zadjii-msft commented on GitHub (Jul 25, 2022): > Not sure if relevant but I don't have `wt.exe` and `WindowsTerminal.exe` in my path. > If I browse to the folder with windows terminal and try to run the command they do nothing, even `wt -h` or `wt --version` don't work. Which directory specifically/? The `WindowsApps` directory is special and isn't supposed to be accessed directly by the user. The App Execution Alias for Terminal, `wt.exe`, is a special type of link that the OS uses to do some extra validation before starting the Terminal. The OS won't let you run the app directly out of `WindowsApps`.
claunia commented 2026-01-31 06:01:40 +00:00
Author
Owner
Copy Link

@eblis commented on GitHub (Jul 25, 2022):

This is the folder: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.14.1861.0_x64__8wekyb3d8bbwe (it used to be C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.14.1962.0_x64__8wekyb3d8bbwe but I uninstalled Windows Terminal and then installed the latest version available in GitHub releases again)
But if I type wt in a normal command prompt it's not recognized, there's nothing in the %PATH% variable pointing to Windows Terminal. How is it finding the executable to run in that case ?

@eblis commented on GitHub (Jul 25, 2022): This is the folder: `C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.14.1861.0_x64__8wekyb3d8bbwe` (it used to be `C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.14.1962.0_x64__8wekyb3d8bbwe` but I uninstalled Windows Terminal and then installed the latest version available in GitHub releases again) But if I type `wt` in a normal command prompt it's not recognized, there's nothing in the `%PATH%` variable pointing to Windows Terminal. How is it finding the executable to run in that case ?
claunia commented 2026-01-31 06:01:40 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 25, 2022):

You need to enable the App Execution Alias for the Terminal in the Settings app

image

That'll place a wt.exe "execution alias" onto the path, which will effectively do the same thing as launching the app from the Start Menu

@zadjii-msft commented on GitHub (Jul 25, 2022): You need to enable the App Execution Alias for the Terminal in the Settings app ![image](https://user-images.githubusercontent.com/18356694/180803232-3a4904a2-016a-4377-9ce9-9da40b5d76b7.png) That'll place a `wt.exe` "execution alias" onto the path, which will effectively do the same thing as launching the app from the Start Menu
claunia commented 2026-01-31 06:01:40 +00:00
Author
Owner
Copy Link

@eblis commented on GitHub (Jul 25, 2022):

image

@eblis commented on GitHub (Jul 25, 2022): ![image](https://user-images.githubusercontent.com/540188/180808615-aeace917-47b5-43b5-81b2-8927b567a785.png)
claunia commented 2026-01-31 06:01:40 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 25, 2022):

After enabling the execution alias, did you start a fresh Command Prompt window/? Is C:\Users\<username>\AppData\Local\Microsoft\WindowsApps\ on your %PATH%? (I'm suspecting the latter isn't true, if winget wasn't there either)

@zadjii-msft commented on GitHub (Jul 25, 2022): After enabling the execution alias, did you start a fresh Command Prompt window/? Is `C:\Users\<username>\AppData\Local\Microsoft\WindowsApps\` on your `%PATH%`? (I'm suspecting the latter isn't true, if `winget` wasn't there either)
claunia commented 2026-01-31 06:01:41 +00:00
Author
Owner
Copy Link

@eblis commented on GitHub (Jul 25, 2022):

Thanks for the input.
I was just searching online for this issue and found this.
The C:\Users\<username>\AppData\Local\Microsoft\WindowsApps\ entry was not in my PATH variable.

I added it and now everything is working (including winget).

That's why I added winget in the screenshot as well, none of the aliases were working.

Thanks for your help

@eblis commented on GitHub (Jul 25, 2022): Thanks for the input. I was just searching online for this issue and found [this](https://superuser.com/a/1569403). The `C:\Users\<username>\AppData\Local\Microsoft\WindowsApps\` entry was not in my `PATH` variable. I added it and now everything is working (including winget). That's why I added winget in the screenshot as well, none of the aliases were working. Thanks for your help
claunia commented 2026-01-31 06:01:41 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 25, 2022):

No problem, glad we could get it sorted out 😄

@zadjii-msft commented on GitHub (Jul 25, 2022): No problem, glad we could get it sorted out 😄
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-Tag-Fix 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#18028
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?