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

Terminal stopped receiving input from keystrokes after recent update (dump, video in issue) #17173

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

Originally created by @GavinRay97 on GitHub (Apr 6, 2022).

Windows Terminal version

1.13.10734.0

Windows build number

10.0.22581.0

Other Software

No response

Steps to reproduce

I'm not sure, unfortunately =(
It happens immediately upon opening the terminal as you can see below

Expected Behavior

Video below of behavior:

https://user-images.githubusercontent.com/26604994/162031815-57a71904-956b-45dc-8e89-65ffa232f940.mp4

Here's the output of analyze -v in WinDbg Preview of the dump:

For analysis of this file, run !analyze -v
win32u!NtUserGetMessage+0x14:
00007ffd`f5ca1534 c3              ret
0:000> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

FILE_IN_CAB:  WindowsTerminal.exe.dmp

NTGLOBALFLAG:  0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

APPLICATION_VERIFIER_FLAGS:  0

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 0000000000000000
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 0

FAULTING_THREAD:  00001ee8

PROCESS_NAME:  WindowsTerminal.exe

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION}  Breakpoint  A breakpoint has been reached.

EXCEPTION_CODE_STR:  80000003

STACK_TEXT:  
0000002d`d6f6f5f8 00007ffd`f83d733e     : 00000000`20020001 00000000`00000000 000001fa`00000000 00000000`00000001 : win32u!NtUserGetMessage+0x14
0000002d`d6f6f600 00007ff6`e9891327     : 00000000`00000000 00000000`00000005 00000000`00000000 00000000`00000000 : user32!GetMessageW+0x2e
0000002d`d6f6f660 00007ff6`e989c8d2     : 00000000`00000005 00000000`00000000 00000000`00000000 00000000`00000000 : WindowsTerminal!wWinMain+0x1b7
0000002d`d6f6fa30 00007ffd`f6766624     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : WindowsTerminal!__scrt_common_main_seh+0x106
0000002d`d6f6fa70 00007ffd`f889a958     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
0000002d`d6f6faa0 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x28


STACK_COMMAND:  ~0s; .ecxr ; kb

SYMBOL_NAME:  win32u!NtUserGetMessage+14

MODULE_NAME: win32u

IMAGE_NAME:  win32u.dll

FAILURE_BUCKET_ID:  BREAKPOINT_80000003_win32u.dll!NtUserGetMessage

OS_VERSION:  10.0.22581.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

IMAGE_VERSION:  10.0.22581.1

FAILURE_ID_HASH:  {3112b5eb-303b-e877-0655-90bdfa336126}

Followup:     MachineOwner
---------

And here's a zip of the dump file:

https://drive.google.com/file/d/1kECXRcVzEm_l6tD7UJfEphAczmohzBdr/view?usp=sharing

Actual Behavior

No input appears to be received into the terminal

Originally created by @GavinRay97 on GitHub (Apr 6, 2022). ### Windows Terminal version 1.13.10734.0 ### Windows build number 10.0.22581.0 ### Other Software _No response_ ### Steps to reproduce I'm not sure, unfortunately =( It happens immediately upon opening the terminal as you can see below ### Expected Behavior Video below of behavior: https://user-images.githubusercontent.com/26604994/162031815-57a71904-956b-45dc-8e89-65ffa232f940.mp4 Here's the output of `analyze -v` in WinDbg Preview of the dump: ``` For analysis of this file, run !analyze -v win32u!NtUserGetMessage+0x14: 00007ffd`f5ca1534 c3 ret 0:000> !analyze -v ******************************************************************************* * * * Exception Analysis * * * ******************************************************************************* FILE_IN_CAB: WindowsTerminal.exe.dmp NTGLOBALFLAG: 0 PROCESS_BAM_CURRENT_THROTTLED: 0 PROCESS_BAM_PREVIOUS_THROTTLED: 0 APPLICATION_VERIFIER_FLAGS: 0 EXCEPTION_RECORD: (.exr -1) ExceptionAddress: 0000000000000000 ExceptionCode: 80000003 (Break instruction exception) ExceptionFlags: 00000000 NumberParameters: 0 FAULTING_THREAD: 00001ee8 PROCESS_NAME: WindowsTerminal.exe ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION} Breakpoint A breakpoint has been reached. EXCEPTION_CODE_STR: 80000003 STACK_TEXT: 0000002d`d6f6f5f8 00007ffd`f83d733e : 00000000`20020001 00000000`00000000 000001fa`00000000 00000000`00000001 : win32u!NtUserGetMessage+0x14 0000002d`d6f6f600 00007ff6`e9891327 : 00000000`00000000 00000000`00000005 00000000`00000000 00000000`00000000 : user32!GetMessageW+0x2e 0000002d`d6f6f660 00007ff6`e989c8d2 : 00000000`00000005 00000000`00000000 00000000`00000000 00000000`00000000 : WindowsTerminal!wWinMain+0x1b7 0000002d`d6f6fa30 00007ffd`f6766624 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : WindowsTerminal!__scrt_common_main_seh+0x106 0000002d`d6f6fa70 00007ffd`f889a958 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14 0000002d`d6f6faa0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x28 STACK_COMMAND: ~0s; .ecxr ; kb SYMBOL_NAME: win32u!NtUserGetMessage+14 MODULE_NAME: win32u IMAGE_NAME: win32u.dll FAILURE_BUCKET_ID: BREAKPOINT_80000003_win32u.dll!NtUserGetMessage OS_VERSION: 10.0.22581.1 BUILDLAB_STR: ni_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 IMAGE_VERSION: 10.0.22581.1 FAILURE_ID_HASH: {3112b5eb-303b-e877-0655-90bdfa336126} Followup: MachineOwner --------- ``` And here's a zip of the dump file: https://drive.google.com/file/d/1kECXRcVzEm_l6tD7UJfEphAczmohzBdr/view?usp=sharing ### Actual Behavior No input appears to be received into the terminal
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 05:34:16 +00:00
claunia commented 2026-01-31 05:34:17 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 6, 2022):

I'm guessing you're hitting the same thing as #12746

@zadjii-msft commented on GitHub (Apr 6, 2022): I'm guessing you're hitting the same thing as #12746
claunia commented 2026-01-31 05:34:18 +00:00
Author
Owner
Copy Link

@GavinRay97 commented on GitHub (Apr 6, 2022):

@zadjii-msft You're right, should I close this as a duplicate?

Reading through thread, seems like a reboot should fix it?
If so, I hope the dump I grabbed before rebooting if it's an intermittent issue is helpful in diagnosing/reproducing 👍

@GavinRay97 commented on GitHub (Apr 6, 2022): @zadjii-msft You're right, should I close this as a duplicate? Reading through thread, seems like a reboot should fix it? If so, I hope the dump I grabbed before rebooting if it's an intermittent issue is helpful in diagnosing/reproducing 👍
claunia commented 2026-01-31 05:34:18 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 7, 2022):

Cool thanks for the confirmation! I think we've got some folks on the input team trying to debug this from their side, but thanks for the dump!

/dup #12746

@zadjii-msft commented on GitHub (Apr 7, 2022): Cool thanks for the confirmation! I think we've got some folks on the input team trying to debug this from their side, but thanks for the dump! /dup #12746
claunia commented 2026-01-31 05:34:18 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 7, 2022):

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 7, 2022): 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 Issue-Bug 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#17173
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?