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

Crash on startup #9482

New Issue
Closed
opened 2026-01-31 01:55:36 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 01:55:36 +00:00
Owner
Copy Link

Originally created by @aavinseth on GitHub (Jul 7, 2020).

Environment

Windows build number: Version 2004 (OS Build 19041.329)
Windows Terminal version (if applicable): 1.0.1811.0

Any other software?

Steps to reproduce

  1. Download Windows Terminal from Microsoft Store
  2. Open Windows Terminal from Start Menu

Expected behavior

Windows Terminal should open in maximize mode

Actual behavior

Windows Terminal crash on open

https://aka.ms/AA8wuqk

Originally created by @aavinseth on GitHub (Jul 7, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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: Version 2004 (OS Build 19041.329) Windows Terminal version (if applicable): 1.0.1811.0 Any other software? ``` # Steps to reproduce 1. Download Windows Terminal from Microsoft Store 2. Open Windows Terminal from Start Menu # Expected behavior Windows Terminal should open in maximize mode # Actual behavior Windows Terminal crash on open https://aka.ms/AA8wuqk
claunia added the Needs-TriageNeeds-Tag-FixResolution-No-ReproSeverity-Crash labels 2026-01-31 01:55:37 +00:00
claunia commented 2026-01-31 01:55:38 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Jul 8, 2020):

I was unable to get the Preview to update from the Store but I manually updated it and suffered no crashes. Also it doesn't open in maximum mode but more like "medium" that can be resized or set the maximum mode.

@WSLUser commented on GitHub (Jul 8, 2020): I was unable to get the Preview to update from the Store but I manually updated it and suffered no crashes. Also it doesn't open in maximum mode but more like "medium" that can be resized or set the maximum mode.
claunia commented 2026-01-31 01:55:38 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 10, 2020):

There's no reason terminal would default to maximized mode. I think you've left out one or two of the steps in the description. Can you help clarify?

Are you in tablet mode? What sort of hardware are you using? Are you in power saver mode? Have you changed any terminal settings?

@DHowett commented on GitHub (Jul 10, 2020): There's no reason terminal would default to maximized mode. I think you've left out one or two of the steps in the description. Can you help clarify? Are you in tablet mode? What sort of hardware are you using? Are you in power saver mode? Have you changed any terminal settings?
claunia commented 2026-01-31 01:55:38 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 10, 2020):

Unfortunately, your feedback item didn't include any crashes... which means that Terminal might be shutting down on its own (and not crashing!) ☹️

@DHowett commented on GitHub (Jul 10, 2020): Unfortunately, your feedback item didn't include any crashes... which means that Terminal might be shutting down on its own (and not crashing!) ☹️
claunia commented 2026-01-31 01:55:38 +00:00
Author
Owner
Copy Link

@aavinseth commented on GitHub (Jul 10, 2020):

@DHowett there was a update in Microsoft Store, so as usual I update it. After updating when I was trying to open the app it was shutting down or get crash. Regarding to maximize mode I mis spell it. After this issue, I have uninstalled and install it multiple times but still same thing. Even I have tried preview app but still same problem. Then I installed it again and just restart my system. After restarting, its working fine now.

@aavinseth commented on GitHub (Jul 10, 2020): @DHowett there was a update in Microsoft Store, so as usual I update it. After updating when I was trying to open the app it was shutting down or get crash. Regarding to maximize mode I mis spell it. After this issue, I have uninstalled and install it multiple times but still same thing. Even I have tried preview app but still same problem. Then I installed it again and just restart my system. After restarting, its working fine now.
claunia commented 2026-01-31 01:55:38 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 16, 2020):

After restarting, its working fine now.

Huh, I hate it when that happens. Maybe the Store left some bad cache laying around that was fixed by a reboot. Since this isn't reproing anymore, I'm gonna close this one out. Thanks!

@zadjii-msft commented on GitHub (Jul 16, 2020): > After restarting, its working fine now. Huh, I hate it when that happens. Maybe the Store left some bad cache laying around that was fixed by a reboot. Since this isn't reproing anymore, I'm gonna close this one out. Thanks!
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-Tag-Fix Needs-Triage Resolution-No-Repro Severity-Crash
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#9482
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?