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

Windows Terminal Quits Immediately on Start #2 #14012

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

Originally created by @Sgt-Nukem on GitHub (May 28, 2021).

Windows Terminal version (or Windows build number)

10.0.19043.0 Microsoft Windows NT 10.0.19043.0

Other Software

No response

Steps to reproduce

Just click the Windows Terminal icon in the taskbar I have there for ages.

Expected Behavior

Windows Terminal just starts - like always - with my WSL2 default profile.

Actual Behavior

For the fraction of a second you can see that a windows was about to spawn, but then it vanishes immediately.

Note: Because of this this may be a separate bug to bug #10248.

Originally created by @Sgt-Nukem on GitHub (May 28, 2021). ### Windows Terminal version (or Windows build number) 10.0.19043.0 Microsoft Windows NT 10.0.19043.0 ### Other Software _No response_ ### Steps to reproduce Just click the Windows Terminal icon in the taskbar I have there for ages. ### Expected Behavior Windows Terminal just starts - like always - with my WSL2 default profile. ### Actual Behavior For the fraction of a second you can see that a windows was about to spawn, but then it vanishes immediately. Note: Because of this this may be a separate bug to bug #10248.
claunia added the Resolution-DuplicateProduct-Terminal labels 2026-01-31 03:58:27 +00:00
claunia commented 2026-01-31 03:58:29 +00:00
Author
Owner
Copy Link

@Sgt-Nukem commented on GitHub (May 28, 2021):

I already found out the problem manifests with my default profile (i.e. WSL2) only.

If I start Windows Terminal via the jump list selecting PowerShell or classic CMD it works as expected.
Starting a new WSL2 from the open Windows Terminal produces a new tab for the blink of an eye - then closes it immediately.

I didn't change any settings for like months and are working with it everyday!

(If there are any logs or something I could append here please guide me to them.)

@Sgt-Nukem commented on GitHub (May 28, 2021): I already found out the problem manifests with my default profile (i.e. WSL2) *only*. If I start Windows Terminal via the jump list selecting PowerShell or classic CMD it works as expected. Starting a new WSL2 from the open Windows Terminal produces a new tab for the blink of an eye - then closes it immediately. **I didn't change any settings for like months and are working with it everyday!** _(If there are any logs or something I could append here please guide me to them.)_
claunia commented 2026-01-31 03:58:29 +00:00
Author
Owner
Copy Link

@Sgt-Nukem commented on GitHub (May 28, 2021):

Okay, I found the culprit: If I remove the starting directory (i.e. leave it blank) from my default profile everything is working again.

This was set to /var/www/_Frontend_/ (i.e. a Linux path - the Apache site directory) for ages. The directory exists and it's no problem to just go there in a new WSL2 instance spawned manually from CMD.

The only real change this week has been the Feature Update of Windows 10 to 21H1.

@Sgt-Nukem commented on GitHub (May 28, 2021): Okay, I found the culprit: If I remove the `starting directory` (i.e. leave it blank) from my default profile everything is working again. This was set to `/var/www/_Frontend_/` (i.e. a Linux path - the Apache site directory) for ages. The directory exists and it's no problem to just go there in a new WSL2 instance spawned manually from CMD. The only real change this week has been the Feature Update of Windows 10 to 21H1.
claunia commented 2026-01-31 03:58:29 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 28, 2021):

What version of the Terminal do you have? You can find this with wt --version.

Out of curiosity, did the startingDirectory being set to /var/www/_Frontend_/ ever actually work before? Or did that profile just open in %USERPROFILE%?

@zadjii-msft commented on GitHub (May 28, 2021): What version of the Terminal do you have? You can find this with `wt --version`. Out of curiosity, did the `startingDirectory` being set to `/var/www/_Frontend_/` ever actually _work_ before? Or did that profile just open in `%USERPROFILE%`?
claunia commented 2026-01-31 03:58:29 +00:00
Author
Owner
Copy Link

@Sgt-Nukem commented on GitHub (May 28, 2021):

What version of the Terminal do you have? You can find this with wt --version.

Out of curiosity, did the startingDirectory being set to /var/www/_Frontend_/ ever actually work before? Or did that profile just open in %USERPROFILE%?

1.8.1444.0

I'm pretty sure it worked - although not 100% so as nowadays I don't use the WSL2 prompt that much anymore.

I found a workaround using //wsl$/Ubuntu-20.04/var/www/ at least.
BUT: //wsl$/Ubuntu-20.04/var/www/_Frontend_/ results in the bugged behavior, too!

Turns out: _Frontend_ under /var/www is a symbolic link so Apache can access my project files on the Windows side. Maybe that's the culprit?

I think it should navigate into a default path at least instead of just closing the terminal window.

@Sgt-Nukem commented on GitHub (May 28, 2021): > What version of the Terminal do you have? You can find this with `wt --version`. > > Out of curiosity, did the `startingDirectory` being set to `/var/www/_Frontend_/` ever actually _work_ before? Or did that profile just open in `%USERPROFILE%`? 1.8.1444.0 I'm pretty sure it worked - although not 100% so as nowadays I don't use the WSL2 prompt that much anymore. I found a workaround using `//wsl$/Ubuntu-20.04/var/www/` at least. BUT: `//wsl$/Ubuntu-20.04/var/www/_Frontend_/` results in the bugged behavior, too! Turns out: `_Frontend_` under `/var/www` is a symbolic link so Apache can access my project files on the Windows side. Maybe that's the culprit? I think it should navigate into a default path at least instead of just closing the terminal window.
claunia commented 2026-01-31 03:58:29 +00:00
Author
Owner
Copy Link

@ajurna commented on GitHub (May 30, 2021):

i have the same issue but i'm just using the default config. there is no starting directory setting in my config.

@ajurna commented on GitHub (May 30, 2021): i have the same issue but i'm just using the default config. there is no starting directory setting in my config.
claunia commented 2026-01-31 03:58:29 +00:00
Author
Owner
Copy Link

@Sgt-Nukem commented on GitHub (May 31, 2021):

i have the same issue but i'm just using the default config. there is no starting directory setting in my config.

Same version?

I'm pretty sure it worked - although not 100% so as nowadays I don't use the WSL2 prompt that much anymore.

I have more doubts now - as my other PC has set the //wsl$/... path, too - contrary to my memory. Take it as 50/50 at best.

(N.B.: But I would expect Windows Terminal to support Linux paths! As a "wrapper" around many different console sessions it should obey their path particularities. I find it kinda strange to have to set it to //wsl$/... - a hidden SMB/CIFS remote filesystem path - to start in Apache's local DocumentRoot.)

@Sgt-Nukem commented on GitHub (May 31, 2021): > i have the same issue but i'm just using the default config. there is no starting directory setting in my config. Same version? > I'm pretty sure it worked - although not 100% so as nowadays I don't use the WSL2 prompt that much anymore. I have more doubts now - as my other PC has set the `//wsl$/...` path, too - contrary to my memory. Take it as 50/50 at best. (N.B.: But I would _expect_ Windows Terminal to support Linux paths! As a "wrapper" around many different console sessions it should obey their path particularities. I find it kinda strange to have to set it to `//wsl$/...` - **a hidden SMB/CIFS remote filesystem path** - to start in Apache's local DocumentRoot.)
claunia commented 2026-01-31 03:58:30 +00:00
Author
Owner
Copy Link

@ajurna commented on GitHub (May 31, 2021):

yes i confirmed it was the same version.

@ajurna commented on GitHub (May 31, 2021): yes i confirmed it was the same version.
claunia commented 2026-01-31 03:58:30 +00:00
Author
Owner
Copy Link

@koenigseggcc commented on GitHub (May 31, 2021):

I have the same problem. However, the workaround of trying to start with a different shell does not work for me.

Application is completely borked, and even uninstalling/reinstalling to try to clear config doesn't help.

I've also tried resetting its config via Windows App Settings. Still won't start.

@koenigseggcc commented on GitHub (May 31, 2021): I have the same problem. However, the workaround of trying to start with a different shell does not work for me. Application is completely borked, and even uninstalling/reinstalling to try to clear config doesn't help. I've also tried resetting its config via Windows App Settings. Still won't start.
claunia commented 2026-01-31 03:58:30 +00:00
Author
Owner
Copy Link

@koenigseggcc commented on GitHub (May 31, 2021):

Apparently there is some Windows Update that was required to get Terminal to run. I cannot tell which update it was, because when I initially opened the 'Updates' section, it told me there was nothing to install.

KB5003173 appears to be the requirement.

@koenigseggcc commented on GitHub (May 31, 2021): Apparently there is some Windows Update that was required to get Terminal to run. I cannot tell which update it was, because when I initially opened the 'Updates' section, it told me there was nothing to install. KB5003173 appears to be the requirement.
claunia commented 2026-01-31 03:58:30 +00:00
Author
Owner
Copy Link

@ajurna commented on GitHub (May 31, 2021):

well i updated to 21H1 and that resolved it for me. but hardly the best solution.

@ajurna commented on GitHub (May 31, 2021): well i updated to 21H1 and that resolved it for me. but hardly the best solution.
claunia commented 2026-01-31 03:58:30 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 1, 2021):

Okay so I think OP's issue here is #10245 - for everyone else in this thread, I'm gonna redirect you to #10305 which has a big ol' list of all the crashes we're seeing, and various steps to mitigate them.

/dup #10245

Thanks!

@zadjii-msft commented on GitHub (Jun 1, 2021): Okay so I think OP's issue here is #10245 - for everyone else in this thread, I'm gonna redirect you to #10305 which has a big ol' list of all the crashes we're seeing, and various steps to mitigate them. /dup #10245 Thanks!
claunia commented 2026-01-31 03:58:31 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 1, 2021):

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 (Jun 1, 2021): 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 Product-Terminal 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#14012
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?