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 with v1.7.1033.0 and v1.8.1032.0 Preview #13448

New Issue
Closed
opened 2026-01-31 03:42:58 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 03:42:58 +00:00
Owner
Copy Link

Originally created by @CrendKing on GitHub (Apr 14, 2021).

Windows Terminal version (or Windows build number)

v1.7.1033.0, v1.8.1032.0

Other Software

No response

Steps to reproduce

  1. Launch WindowsTerminal.exe.

Expected Behavior

Terminal appears.

Actual Behavior

A white window appears for half a second then disappear. Event viewer shows crash:

Faulting application name: WindowsTerminal.exe, version: 1.7.2104.13003, time stamp: 0x60761d23
Faulting module name: TerminalApp.dll, version: 1.7.2104.13003, time stamp: 0x60761c93
Exception code: 0xc0000005
Fault offset: 0x000000000000ee80
Faulting process id: 0x2f04
Faulting application start time: 0x01d73179fb298d9b
Faulting application path: C:\Scoop\apps\windows-terminal\current\WindowsTerminal.exe
Faulting module path: C:\Scoop\apps\windows-terminal\current\TerminalApp.dll
Report Id: c86dab41-9431-4ec1-8fa3-04599035cb08
Faulting package full name: 
Faulting package-relative application ID: 

Faulting application name: WindowsTerminal.exe, version: 1.8.2104.13002, time stamp: 0x60762171
Faulting module name: TerminalApp.dll, version: 1.8.2104.13002, time stamp: 0x607620b9
Exception code: 0xc0000005
Fault offset: 0x000000000000e810
Faulting process id: 0x7c8
Faulting application start time: 0x01d731799b803273
Faulting application path: C:\CascadiaPackage_1.8.1032.0_x64\WindowsTerminal.exe
Faulting module path: C:\CascadiaPackage_1.8.1032.0_x64\TerminalApp.dll
Report Id: aa51fc66-b66a-482a-9145-61505aaff01d
Faulting package full name: 
Faulting package-relative application ID:

Tested with and without removing settings.json. The last working version is v1.7.572.0

Originally created by @CrendKing on GitHub (Apr 14, 2021). ### Windows Terminal version (or Windows build number) v1.7.1033.0, v1.8.1032.0 ### Other Software _No response_ ### Steps to reproduce 1. Launch WindowsTerminal.exe. ### Expected Behavior Terminal appears. ### Actual Behavior A white window appears for half a second then disappear. Event viewer shows crash: ``` Faulting application name: WindowsTerminal.exe, version: 1.7.2104.13003, time stamp: 0x60761d23 Faulting module name: TerminalApp.dll, version: 1.7.2104.13003, time stamp: 0x60761c93 Exception code: 0xc0000005 Fault offset: 0x000000000000ee80 Faulting process id: 0x2f04 Faulting application start time: 0x01d73179fb298d9b Faulting application path: C:\Scoop\apps\windows-terminal\current\WindowsTerminal.exe Faulting module path: C:\Scoop\apps\windows-terminal\current\TerminalApp.dll Report Id: c86dab41-9431-4ec1-8fa3-04599035cb08 Faulting package full name: Faulting package-relative application ID: ``` ``` Faulting application name: WindowsTerminal.exe, version: 1.8.2104.13002, time stamp: 0x60762171 Faulting module name: TerminalApp.dll, version: 1.8.2104.13002, time stamp: 0x607620b9 Exception code: 0xc0000005 Fault offset: 0x000000000000e810 Faulting process id: 0x7c8 Faulting application start time: 0x01d731799b803273 Faulting application path: C:\CascadiaPackage_1.8.1032.0_x64\WindowsTerminal.exe Faulting module path: C:\CascadiaPackage_1.8.1032.0_x64\TerminalApp.dll Report Id: aa51fc66-b66a-482a-9145-61505aaff01d Faulting package full name: Faulting package-relative application ID: ``` Tested with and without removing settings.json. The last working version is v1.7.572.0
claunia added the Resolution-Duplicate label 2026-01-31 03:42:58 +00:00
claunia commented 2026-01-31 03:42:59 +00:00
Author
Owner
Copy Link

@DHowett 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 wya that they installed us.

@DHowett 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 wya that they installed us.
claunia commented 2026-01-31 03:42:59 +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!
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#13448
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?