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

Startup Crash Frequently #13455

New Issue
Closed
opened 2026-01-31 03:43:11 +00:00 by claunia · 9 comments
claunia commented 2026-01-31 03:43:11 +00:00
Owner
Copy Link

Originally created by @mingsxs on GitHub (Apr 15, 2021).

Windows Terminal version (or Windows build number)

Windows build number: 18363.1440 Windows Terminal version: 1.7.1033.0

Other Software

Nothing

Steps to reproduce

Just double click it will crash and exit, very little chance it can start up successfully.

Expected Behavior

No response

Actual Behavior

double click to open and then it crashes and exits.

Originally created by @mingsxs on GitHub (Apr 15, 2021). ### Windows Terminal version (or Windows build number) Windows build number: 18363.1440 Windows Terminal version: 1.7.1033.0 ### Other Software Nothing ### Steps to reproduce Just double click it will crash and exit, very little chance it can start up successfully. ### Expected Behavior _No response_ ### Actual Behavior double click to open and then it crashes and exits.
claunia added the Resolution-Duplicate label 2026-01-31 03:43:11 +00:00
claunia commented 2026-01-31 03:43:12 +00:00
Author
Owner
Copy Link

@mingsxs commented on GitHub (Apr 15, 2021):

Sorry that I closed it accidentally.

@mingsxs commented on GitHub (Apr 15, 2021): Sorry that I closed it accidentally.
claunia commented 2026-01-31 03:43:12 +00:00
Author
Owner
Copy Link

@mingsxs commented on GitHub (Apr 15, 2021):

Screenshot 2021-04-15 140840

@mingsxs commented on GitHub (Apr 15, 2021): ![Screenshot 2021-04-15 140840](https://user-images.githubusercontent.com/46848431/114822789-2cda8980-9df5-11eb-926b-64a272c332a4.png)
claunia commented 2026-01-31 03:43:12 +00:00
Author
Owner
Copy Link

@mingsxs commented on GitHub (Apr 15, 2021):

You can see clearly from the screenshot, after opening the terminal, the window leaves blank and soon it will exit with No Response.

@mingsxs commented on GitHub (Apr 15, 2021): You can see clearly from the screenshot, after opening the terminal, the window leaves blank and soon it will exit with No Response.
claunia commented 2026-01-31 03:43:12 +00:00
Author
Owner
Copy Link

@igitur commented on GitHub (Apr 15, 2021):

@mingsxs Same here. I installed Terminal using scoop package manager. I'm just wondering how you installed it. Maybe that's relevant here.

@igitur commented on GitHub (Apr 15, 2021): @mingsxs Same here. I installed Terminal using scoop package manager. I'm just wondering how you installed it. Maybe that's relevant here.
claunia commented 2026-01-31 03:43:12 +00:00
Author
Owner
Copy Link

@igitur commented on GitHub (Apr 15, 2021):

If I uninstall my current instance (that I originally installed through scoop package manager) and I download the .msixbundle file from https://github.com/microsoft/terminal/releases/tag/v1.7.1033.0 and install it manually using Add-AppPackage in PowerShell, then Windows Terminal opens successfully.

If I remove it again using Remove-AppPackage and reinstall it via scoop package manager, it fails again. So I'm guessing something is wrong with the scoop install script.

@igitur commented on GitHub (Apr 15, 2021): If I uninstall my current instance (that I originally installed through scoop package manager) and I download the .msixbundle file from https://github.com/microsoft/terminal/releases/tag/v1.7.1033.0 and install it manually using `Add-AppPackage` in PowerShell, then Windows Terminal opens successfully. If I remove it again using `Remove-AppPackage` and reinstall it via scoop package manager, it fails again. So I'm guessing something is wrong with the scoop install script.
claunia commented 2026-01-31 03:43:13 +00:00
Author
Owner
Copy Link

@justinkb commented on GitHub (Apr 15, 2021):

If I uninstall my current instance (that I originally installed through scoop package manager) and I download the .msixbundle file from https://github.com/microsoft/terminal/releases/tag/v1.7.1033.0 and install it manually using Add-AppPackage in PowerShell, then Windows Terminal opens successfully.

If I remove it again using Remove-AppPackage and reinstall it via scoop package manager, it fails again. So I'm guessing something is wrong with the scoop install script.

https://github.com/lukesampson/scoop-extras/blob/master/bucket/windows-terminal.json

doubtful anything is wrong with the script, most likely it's just intermittent failures and it happened to work a few times when you installed it manually

@justinkb commented on GitHub (Apr 15, 2021): > If I uninstall my current instance (that I originally installed through scoop package manager) and I download the .msixbundle file from https://github.com/microsoft/terminal/releases/tag/v1.7.1033.0 and install it manually using `Add-AppPackage` in PowerShell, then Windows Terminal opens successfully. > > If I remove it again using `Remove-AppPackage` and reinstall it via scoop package manager, it fails again. So I'm guessing something is wrong with the scoop install script. https://github.com/lukesampson/scoop-extras/blob/master/bucket/windows-terminal.json doubtful anything is wrong with the script, most likely it's just intermittent failures and it happened to work a few times when you installed it manually
claunia commented 2026-01-31 03:43:13 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 15, 2021):

/dup #9821

Scoop installs terminal in an unsupported way. We're working on fixing it, but we have never supported the way that they installed us.

@zadjii-msft commented on GitHub (Apr 15, 2021): /dup #9821 Scoop installs terminal in an unsupported way. We're working on fixing it, but we have never supported the way that they installed us.
claunia commented 2026-01-31 03:43:13 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 15, 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 (Apr 15, 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!
claunia commented 2026-01-31 03:43:13 +00:00
Author
Owner
Copy Link

@mingsxs commented on GitHub (Apr 16, 2021):

@igitur Hey there, yeah, I do install with scoop, didn't realize that it could be relevant to it. Thanks for this information

@mingsxs commented on GitHub (Apr 16, 2021): @igitur Hey there, yeah, I do install with scoop, didn't realize that it could be relevant to it. Thanks for this information
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#13455
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?