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 crashes when opened #15230

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

Originally created by @hicksjacobp on GitHub (Sep 15, 2021).

Windows Terminal version (or Windows build number)

1.9.1942.0

Other Software

Windows 10 Version 21H1 OS Build 19043.1165

Steps to reproduce

I was initially having some crashing issues with Windows Terminal after installing the latest release (1.10.2383.0). I missed that a newer Windows version is necessary to use that release, so then I uninstalled what I had and installed 1.9.1942.0.

However, I still can't start Windows Terminal.

For some reason, I also cannot open the Feedback Hub in order to provide any diagnostic data...

Expected Behavior

Windows Terminal should start.

Actual Behavior

Windows Terminal stops working with never showing a window. Windows shows Windows Terminal stopped working and only gives me the options to debug or close.

image

Originally created by @hicksjacobp on GitHub (Sep 15, 2021). ### Windows Terminal version (or Windows build number) 1.9.1942.0 ### Other Software Windows 10 Version 21H1 OS Build 19043.1165 ### Steps to reproduce I was initially having some crashing issues with Windows Terminal after installing the latest release (1.10.2383.0). I missed that a newer Windows version is necessary to use that release, so then I uninstalled what I had and installed 1.9.1942.0. However, I still can't start Windows Terminal. For some reason, I also cannot open the Feedback Hub in order to provide any diagnostic data... ### Expected Behavior Windows Terminal should start. ### Actual Behavior Windows Terminal stops working with never showing a window. Windows shows Windows Terminal stopped working and only gives me the options to debug or close. ![image](https://user-images.githubusercontent.com/832739/133487450-0a3b8598-182a-475d-b92a-724e0f33fb5a.png)
claunia added the Needs-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-31 04:32:04 +00:00
claunia commented 2026-01-31 04:32:05 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 15, 2021):

I missed that a newer Windows version is necessary to use that release

Whoa whoa whoa what? Where'd you hear that?

@DHowett commented on GitHub (Sep 15, 2021): > I missed that a newer Windows version is necessary to use that release Whoa whoa whoa what? Where'd you hear that?
claunia commented 2026-01-31 04:32:05 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 15, 2021):

If you leave that dialog up, and then go to Task Manager, is WindowsTerminal.exe still present in the Details tab? If so, would you mind using Create Dump and mailing that to me (or placing it on your favourite cloud storage provider (OneDrive)?)

@DHowett commented on GitHub (Sep 15, 2021): If you leave that dialog up, and then go to Task Manager, is `WindowsTerminal.exe` still present in the Details tab? If so, would you mind using `Create Dump` and mailing that to me (or placing it on your favourite cloud storage provider (OneDrive)?)
claunia commented 2026-01-31 04:32:05 +00:00
Author
Owner
Copy Link

@hicksjacobp commented on GitHub (Sep 15, 2021):

I missed that a newer Windows version is necessary to use that release

Whoa whoa whoa what? Where'd you hear that?

Perhaps I misunderstood the description here while I was quickly skimming? Perhaps Windows Terminal 1.10+ is required if using Windows 22000.65+?

https://github.com/microsoft/terminal/releases/tag/v1.10.1933.0

Due to the change, 1.10+ is required with Windows 22000.65 and above.

Regardless, I was having the same symptoms of Windows Terminal failing to start.

Since I was having issues with Feedback Hub, I also attempted a couple fixes from searching around:

  • Resetting Feedback Hub

  • Running the following as admin:

    Get-AppXPackage | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

After doing these, it noted I needed to restart Windows, so I did. After restarting, Windows Terminal 1.9.1942.0 now appears to start 😕.

Since it appears I misunderstood the Windows version requirement with 1.10+, I've now installed 1.10.2383.0, which also appears to start fine.

So I'll chalk this up to my machine being in some weird state (or perhaps that PowerShell command did something)! I apologize for the unnecessary issue.

@hicksjacobp commented on GitHub (Sep 15, 2021): > > I missed that a newer Windows version is necessary to use that release > > Whoa whoa whoa what? Where'd you hear that? Perhaps I misunderstood the description here while I was quickly skimming? Perhaps Windows Terminal 1.10+ is required if using Windows 22000.65+? https://github.com/microsoft/terminal/releases/tag/v1.10.1933.0 > Due to the change, 1.10+ is required with Windows 22000.65 and above. Regardless, I was having the same symptoms of Windows Terminal failing to start. ---- Since I was having issues with Feedback Hub, I also attempted a couple fixes from searching around: - Resetting Feedback Hub - Running the following as admin: ```powershell Get-AppXPackage | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} ``` After doing these, it noted I needed to restart Windows, so I did. After restarting, Windows Terminal 1.9.1942.0 now appears to start 😕. Since it appears I misunderstood the Windows version requirement with 1.10+, I've now installed 1.10.2383.0, which also appears to start fine. So I'll chalk this up to my machine being in some weird state (or perhaps that PowerShell command did something)! I apologize for the unnecessary issue.
claunia commented 2026-01-31 04:32:06 +00:00
Author
Owner
Copy Link

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

Due to the change, 1.10+ is required with Windows 22000.65 and above.

That's a perhaps confusingly worded sentence. More correctly: If you're using Windows 22000.65 or greater, you'll need to update to 1.10 or above. And that's really only for the "default terminal" feature.

Since the issue went away on it's own, I'm guessing this is one of those font issues we were seeing earlier on in 1.9.

@zadjii-msft commented on GitHub (Sep 15, 2021): > Due to the change, 1.10+ is required with Windows 22000.65 and above. That's a perhaps confusingly worded sentence. More correctly: If you're using Windows 22000.65 or greater, you'll need to update to 1.10 or above. And that's really only for the "default terminal" feature. Since the issue went away on it's own, I'm guessing this is one of those font issues we were seeing earlier on in 1.9.
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 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#15230
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?