starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 00:15:10 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Opening "About" crashes the terminal #5942

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

Originally created by @Cry0nicS on GitHub (Jan 15, 2020).

Environment

Windows build number:  Win32NT             10.0.18362.0 Microsoft Windows NT 10.0.18362.0
Windows Terminal version (if applicable):0.8.10091.0

Any other software?
I have Windows Terminal installed via `scoop`

Steps to reproduce

  1. Open Windows Terminal
  2. Click on About under the "arrow" menu.

Expected behavior

I expect to see some information about the application.

Actual behavior

The application just crashes without any message or alike.
Here's a quick video about it: https://imgur.com/phob2O1

For what is worth, I didn't have this issue with the previous version of WT.

Originally created by @Cry0nicS on GitHub (Jan 15, 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: Win32NT 10.0.18362.0 Microsoft Windows NT 10.0.18362.0 Windows Terminal version (if applicable):0.8.10091.0 Any other software? I have Windows Terminal installed via `scoop` ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> 1. Open Windows Terminal 2. Click on `About` under the "arrow" menu. # Expected behavior I expect to see _some_ information about the application. <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior <!-- What's actually happening? --> The application just crashes without any message or alike. Here's a quick video about it: https://imgur.com/phob2O1 For what is worth, I didn't have this issue with the previous version of WT.
claunia commented 2026-01-31 00:26:06 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 15, 2020):

Thanks for the report! Would you mind capturing this crash with the Feedback Hub, so we can try and figure out the root cause? /feedback

@zadjii-msft commented on GitHub (Jan 15, 2020): Thanks for the report! Would you mind capturing this crash with the Feedback Hub, so we can try and figure out the root cause? /feedback
claunia commented 2026-01-31 00:26:06 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jan 15, 2020):

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 (Jan 15, 2020): 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-31 00:26:06 +00:00
Author
Owner
Copy Link

@Cry0nicS commented on GitHub (Jan 15, 2020):

@zadjii-msft I think I did. I added a link to this issue in the description.

@Cry0nicS commented on GitHub (Jan 15, 2020): @zadjii-msft I _think_ I did. I added a link to this issue in the description.
claunia commented 2026-01-31 00:26:06 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 15, 2020):

@Cry0nicS Could you post the aka.ms link to the feedback item that's generated by clicking this button:
image

That's usually the easiest way for us to drill in on the specific item

@zadjii-msft commented on GitHub (Jan 15, 2020): @Cry0nicS Could you post the aka.ms link to the feedback item that's generated by clicking this button: ![image](https://user-images.githubusercontent.com/18356694/72443522-018d6880-3774-11ea-9acd-3ee167715990.png) That's usually the easiest way for us to drill in on the specific item
claunia commented 2026-01-31 00:26:06 +00:00
Author
Owner
Copy Link

@Cry0nicS commented on GitHub (Jan 15, 2020):

@zadjii-msft I guess first time I couldn't do this because I wasn't logged in.

Anyway, here it is: https://aka.ms/AA704rx
Let me know if it helps or if there's anything else I can provide.

@Cry0nicS commented on GitHub (Jan 15, 2020): @zadjii-msft I guess first time I couldn't do this because I wasn't logged in. Anyway, here it is: https://aka.ms/AA704rx Let me know if it helps or if there's anything else I can provide.
claunia commented 2026-01-31 00:26:07 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jan 24, 2020):

I've pulled off the Triage tag and moved this into the v0.10 milestone. It still Needs-Repro, though, since none of us can get this to happen. Thanks for the report!

@DHowett-MSFT commented on GitHub (Jan 24, 2020): I've pulled off the Triage tag and moved this into the v0.10 milestone. It still Needs-Repro, though, since none of us can get this to happen. Thanks for the report!
claunia commented 2026-01-31 00:26:07 +00:00
Author
Owner
Copy Link

@bartlibert commented on GitHub (Feb 11, 2020):

I have this issue as well, vs debugger give the following info (don't know it if helps):

Unhandled exception at 0x00007FFE4AC22EC0 (Windows.UI.Xaml.dll) in WindowsTerminal.exe: 0xC000027B: An application-internal exception has occurred (parameters: 0x000001D4EE280440, 0x0000000000000005). occurred

@bartlibert commented on GitHub (Feb 11, 2020): I have this issue as well, vs debugger give the following info (don't know it if helps): Unhandled exception at 0x00007FFE4AC22EC0 (Windows.UI.Xaml.dll) in WindowsTerminal.exe: 0xC000027B: An application-internal exception has occurred (parameters: 0x000001D4EE280440, 0x0000000000000005). occurred
claunia commented 2026-01-31 00:26:07 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Feb 27, 2020):

installed via scoop

Wait a second. Scoop installs WT by extracting the zip, which is not supported. This causes an application name lookup failure.

I'm reprioritizing this out of version 1.0 for the use of an alternative installation method. Sorry.

@DHowett-MSFT commented on GitHub (Feb 27, 2020): > installed via scoop Wait a second. Scoop installs WT by extracting the zip, which is not supported. This causes an application name lookup failure. I'm reprioritizing this out of version 1.0 for the use of an alternative installation method. Sorry.
claunia commented 2026-01-31 00:26:07 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Feb 27, 2020):

Actually, closing as not supported.

@DHowett-MSFT commented on GitHub (Feb 27, 2020): Actually, closing as not supported.
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 Area-UserInterface Help Wanted Issue-Bug Needs-Repro Priority-1 Product-Terminal Resolution-By-Design 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#5942
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?