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

Stopped responding and was closed #10764

New Issue
Closed
opened 2026-01-31 02:29:39 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 02:29:39 +00:00
Owner
Copy Link

Originally created by @mkahvi on GitHub (Sep 25, 2020).

Environment

Windows build number: 10.0.19041.0
Windows Terminal version (if applicable): 1.3.2641.0

Any other software? Node.js

Steps to reproduce

Unknown. Node.js was run. Desktop was locked. These don't cause it to happen on their own tho.

Expected behavior

No crash.

Actual behavior

Terminal crashed. The Node.js server kept running with no live terminal to control it by.

Windows application log has following entry:

The program WindowsTerminal.exe version 1.2.2008.25001 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
Process ID: 1c50
Start Time: 01d691043827f38c
Termination Time: 4294967295
Application Path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.2.2381.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Report Id: d667144b-73e4-4526-9fcb-5f660e582e7f
Faulting package full name: Microsoft.WindowsTerminal_1.2.2381.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Hang type: Quiesce

Judging by the error above, the terminal was automatically updated during or shortly after the problem before I noticed it?

There was also these errors logged at the same time, possibly related to it:

Fault bucket 2028434469579443634, type 5
Event Name: MoAppHang
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft.WindowsTerminal_1.2.2381.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.2.2008.25001
P4: 5f45901e
P5: 0c21
P6: 2097152

And this:

Fault bucket 1707257287759330481, type 5
Event Name: PowerShell
Response: Not available
Cab Id: 0

Problem signature:
P1: powershell.exe
P2: 10.0.19041.1
P3: System.InvalidOperationException
P4: System.InvalidOperationException
P5: unknown
P6: System.Console.ReadKey
P7: unknown

Originally created by @mkahvi on GitHub (Sep 25, 2020). # Environment ```none Windows build number: 10.0.19041.0 Windows Terminal version (if applicable): 1.3.2641.0 Any other software? Node.js ``` # Steps to reproduce Unknown. Node.js was run. Desktop was locked. These don't cause it to happen on their own tho. # Expected behavior No crash. # Actual behavior Terminal crashed. The Node.js server kept running with no live terminal to control it by. Windows application log has following entry: > The program WindowsTerminal.exe version 1.2.2008.25001 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel. > Process ID: 1c50 > Start Time: 01d691043827f38c > Termination Time: 4294967295 > Application Path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.2.2381.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe > Report Id: d667144b-73e4-4526-9fcb-5f660e582e7f > Faulting package full name: Microsoft.WindowsTerminal_1.2.2381.0_x64__8wekyb3d8bbwe > Faulting package-relative application ID: App > Hang type: Quiesce Judging by the error above, the terminal was automatically updated during or shortly after the problem before I noticed it? There was also these errors logged at the same time, possibly related to it: > Fault bucket 2028434469579443634, type 5 > Event Name: MoAppHang > Response: Not available > Cab Id: 0 > > Problem signature: > P1: Microsoft.WindowsTerminal_1.2.2381.0_x64__8wekyb3d8bbwe > P2: praid:App > P3: 1.2.2008.25001 > P4: 5f45901e > P5: 0c21 > P6: 2097152 And this: > Fault bucket 1707257287759330481, type 5 > Event Name: PowerShell > Response: Not available > Cab Id: 0 > > Problem signature: > P1: powershell.exe > P2: 10.0.19041.1 > P3: System.InvalidOperationException > P4: System.InvalidOperationException > P5: unknown > P6: System.Console.ReadKey > P7: unknown
claunia added the Resolution-Duplicate label 2026-01-31 02:29:39 +00:00
claunia commented 2026-01-31 02:29:39 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 29, 2020):

I'm almost certain that this is caused by the Microsoft Store auto-updating the Terminal for you. I believe there's threads linked to #6726 that have more details. IIRC, we've got an open thread with the app platform team right now to try and find a better way to prevent us from getting terminated. (@ future me: the thread is titled "hits for HANG_QUESCE that don't point to anything").

See also #7350, #6726

/dup #6726

@zadjii-msft commented on GitHub (Sep 29, 2020): I'm almost _certain_ that this is caused by the Microsoft Store auto-updating the Terminal for you. I believe there's threads linked to #6726 that have more details. IIRC, we've got an open thread with the app platform team right now to try and find a better way to prevent us from getting terminated. (@ future me: the thread is titled "hits for HANG_QUESCE that don't point to anything"). See also #7350, #6726 /dup #6726
claunia commented 2026-01-31 02:29:40 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 29, 2020):

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 (Sep 29, 2020): 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#10764
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?