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

Terminal won't start / immediately crashes as of v0.5.2661.0 #4031

New Issue
Closed
opened 2026-01-30 23:36:24 +00:00 by claunia · 11 comments
claunia commented 2026-01-30 23:36:24 +00:00
Owner
Copy Link

Originally created by @vsalvino on GitHub (Sep 25, 2019).

Environment

Windows build number: 10.0.18363.0
Windows Terminal version (if applicable): v0.5.2661.0

Any other software? PowerShell Core 6.2.2 is also installed.

Steps to reproduce

  1. Install windows terminal from either Microsoft Store, or via download from GitHub release.
  2. Try to launch the terminal.

Have tried un-installing/re-installing/rebooting multiple times to no avail.

Expected behavior

Terminal should launch, and at least show an error message.

Actual behavior

Terminal immediately crashes, you can see the ghost of a window frame before it disappears.

Originally created by @vsalvino on GitHub (Sep 25, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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: 10.0.18363.0 Windows Terminal version (if applicable): v0.5.2661.0 Any other software? PowerShell Core 6.2.2 is also installed. ``` # Steps to reproduce 1. Install windows terminal from either Microsoft Store, or via download from GitHub release. 2. Try to launch the terminal. Have tried un-installing/re-installing/rebooting multiple times to no avail. <!-- A description of how to trigger this bug. --> # Expected behavior Terminal should launch, and at least show an error message. <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior <!-- What's actually happening? --> Terminal immediately crashes, you can see the ghost of a window frame before it disappears.
claunia added the Resolution-Duplicate label 2026-01-30 23:36:24 +00:00
claunia commented 2026-01-30 23:36:24 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Sep 25, 2019):

Can you share the contents of your profiles.json? %LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\profiles.json

Thanks.

@DHowett-MSFT commented on GitHub (Sep 25, 2019): Can you share the contents of your profiles.json? `%LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\profiles.json` Thanks.
claunia commented 2026-01-30 23:36:25 +00:00
Author
Owner
Copy Link

@vsalvino commented on GitHub (Sep 25, 2019):

Ah thanks for the path, was having trouble tracking down the install folder. The profile seems suspiciously small compared to past versions?

// To view the default settings, hold "alt" while clicking on the "Settings" button.
// For documentation on these settings, see: https://aka.ms/terminal-documentation

{
    "$schema": "https://aka.ms/terminal-profiles-schema",

    "defaultProfile": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",

    "profiles":
    [
        {
            // Make changes here to the powershell.exe profile
            "guid": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",
            "name": "Windows PowerShell",
            "commandline": "powershell.exe",
            "hidden": false
        },
        {
            // Make changes here to the cmd.exe profile
            "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
            "name": "cmd",
            "commandline": "cmd.exe",
            "hidden": false
        },
        {
            "guid": "{574e775e-4f2a-5b96-ac1e-a2962a402336}",
            "hidden": false,
            "name": "PowerShell Core",
            "source": "Windows.Terminal.PowershellCore"
        },
        {
            "guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}",
            "hidden": false,
            "name": "Azure Cloud Shell",
            "source": "Windows.Terminal.Azure"
        }
    ],

    // Add custom color schemes to this array
    "schemes": [],

    // Add any keybinding overrides to this array.
    // To unbind a default keybinding, set the command to "unbound"
    "keybindings": []
}
@vsalvino commented on GitHub (Sep 25, 2019): Ah thanks for the path, was having trouble tracking down the install folder. The profile seems suspiciously small compared to past versions? ``` // To view the default settings, hold "alt" while clicking on the "Settings" button. // For documentation on these settings, see: https://aka.ms/terminal-documentation { "$schema": "https://aka.ms/terminal-profiles-schema", "defaultProfile": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}", "profiles": [ { // Make changes here to the powershell.exe profile "guid": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}", "name": "Windows PowerShell", "commandline": "powershell.exe", "hidden": false }, { // Make changes here to the cmd.exe profile "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}", "name": "cmd", "commandline": "cmd.exe", "hidden": false }, { "guid": "{574e775e-4f2a-5b96-ac1e-a2962a402336}", "hidden": false, "name": "PowerShell Core", "source": "Windows.Terminal.PowershellCore" }, { "guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}", "hidden": false, "name": "Azure Cloud Shell", "source": "Windows.Terminal.Azure" } ], // Add custom color schemes to this array "schemes": [], // Add any keybinding overrides to this array. // To unbind a default keybinding, set the command to "unbound" "keybindings": [] } ```
claunia commented 2026-01-30 23:36:25 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Sep 25, 2019):

Indeed! That's part of the recent settings reform.

Since it doesn't look like a bad default profile, would you mind sharing a feedback hub link?

@DHowett-MSFT commented on GitHub (Sep 25, 2019): Indeed! That's part of the recent settings reform. Since it doesn't look like a bad default profile, would you mind sharing a feedback hub link?
claunia commented 2026-01-30 23:36:25 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Sep 25, 2019):

/feedback

@DHowett-MSFT commented on GitHub (Sep 25, 2019): /feedback
claunia commented 2026-01-30 23:36:25 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 25, 2019):

Hi there!

Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?

Thanks!

image image

@ghost commented on GitHub (Sep 25, 2019): Hi there!<br><br>Can you please send us feedback with the Feedback Hub with this issue and paste the link here so we can more easily find your crash information on the back end?<br><br>Thanks!<br><br>![image](https://user-images.githubusercontent.com/18221333/62478757-b69d0d00-b760-11e9-9626-1fa33c91e7c5.png) ![image](https://user-images.githubusercontent.com/18221333/62478649-6de55400-b760-11e9-806e-5aab7e085a9f.png)
claunia commented 2026-01-30 23:36:25 +00:00
Author
Owner
Copy Link

@vsalvino commented on GitHub (Sep 25, 2019):

Feedback hub: https://aka.ms/AA63w7j

@vsalvino commented on GitHub (Sep 25, 2019): Feedback hub: https://aka.ms/AA63w7j
claunia commented 2026-01-30 23:36:26 +00:00
Author
Owner
Copy Link

@vsalvino commented on GitHub (Sep 25, 2019):

After tinkering with the profile.json, It only exhibits this problem when trying to open a Windows PowerShell terminal (which was the default). Changing the default to PowerShell Core or CMD works! Same problem persists when trying to open a Windows PowerShell tab: the new tab immediately crashes/closes.

Investigating further, powershell.exe is not on the PATH. If I change this to the full path to the executable, it works (C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe).

Perhaps a couple ideas here, start by providing the full path in the default profile.json, and also show an error if there is a problem executing commandline.

@vsalvino commented on GitHub (Sep 25, 2019): After tinkering with the profile.json, It only exhibits this problem when trying to open a Windows PowerShell terminal (which was the default). Changing the default to PowerShell Core or CMD works! Same problem persists when trying to open a Windows PowerShell tab: the new tab immediately crashes/closes. Investigating further, `powershell.exe` is not on the PATH. If I change this to the full path to the executable, it works (`C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe`). Perhaps a couple ideas here, start by providing the full path in the default profile.json, and also show an error if there is a problem executing `commandline`.
claunia commented 2026-01-30 23:36:26 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Sep 25, 2019):

If powershell's not on your path, that's a sign of a serious system misconfiguration. Has something changed the systemwide PATH variable? The system-provided powershell should definitely be there.

Otherwise, this is /dup #2563.

@DHowett-MSFT commented on GitHub (Sep 25, 2019): If powershell's not on your path, that's a sign of a serious system misconfiguration. Has something changed the systemwide `PATH` variable? The system-provided powershell should definitely be there. Otherwise, this is /dup #2563.
claunia commented 2026-01-30 23:36:27 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 25, 2019):

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 (Sep 25, 2019): 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!
claunia commented 2026-01-30 23:36:27 +00:00
Author
Owner
Copy Link

@vsalvino commented on GitHub (Sep 25, 2019):

Thanks for the help. Glad there is already an issue for this problem. Yes, many things have changed the PATH over the years (countless developer tools such as git, python, node/npm, ruby, dotnet, docker, and all of the other cruft that comes along with such toolchains). I imagine some botched install or crappy tool must have hosed the PATH at one time.

@vsalvino commented on GitHub (Sep 25, 2019): Thanks for the help. Glad there is already an issue for this problem. Yes, many things have changed the PATH over the years (countless developer tools such as git, python, node/npm, ruby, dotnet, docker, and all of the other cruft that comes along with such toolchains). I imagine some botched install or crappy tool must have hosed the PATH at one time.
claunia commented 2026-01-30 23:36:27 +00:00
Author
Owner
Copy Link

@GaaTY commented on GitHub (Oct 2, 2019):

I can confirm the PATH thing.

The app was also closing on startup, checked my PATH. No reference to powershell. Added the powershell path to PATH, Terminal opens on my default (which I set to Powershell).

@GaaTY commented on GitHub (Oct 2, 2019): I can confirm the PATH thing. The app was also closing on startup, checked my PATH. No reference to powershell. Added the powershell path to PATH, Terminal opens on my default (which I set to Powershell).
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 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#4031
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?