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

Unresponsive / Won't accept input #23142

New Issue
Open
opened 2026-01-31 08:33:30 +00:00 by claunia · 8 comments
claunia commented 2026-01-31 08:33:30 +00:00
Owner
Copy Link

Originally created by @thecaligarmo on GitHub (Apr 13, 2025).

Windows Terminal version

1.22.10731.0

Windows build number

10.0.26100.3775

Other Software

No response

Steps to reproduce

Not sure what happened/was changed, but this morning my terminal stopped accepting input every so often. (So not sure how to reproduce it). In essence what I noticed:

  1. WSL was not responding to keyboard input, I thought it had crashed so closed it and reopened, with no succes.
  2. I restarted my computer to see if a simple on/off cycle would fix it. At first it accepted when I typed ls, but then shortly after it stopped accepting input again.
  3. I thought maybe it was due to lack of space (as it seemed to happen after I downloaded something), but this was not true:
aram:~ $ df -h
Filesystem      Size  Used Avail Use% Mounted on
none            7.8G     0  7.8G   0% /usr/lib/modules/5.15.167.4-microsoft-standard-WSL2
none            7.8G  4.0K  7.8G   1% /mnt/wsl
drivers         1.9T  1.4T  513G  73% /usr/lib/wsl/drivers
/dev/sdc       1007G   86G  870G   9% /
none            7.8G   92K  7.8G   1% /mnt/wslg
none            7.8G     0  7.8G   0% /usr/lib/wsl/lib
rootfs          7.8G  2.4M  7.8G   1% /init
none            7.8G  996K  7.8G   1% /run
none            7.8G     0  7.8G   0% /run/lock
none            7.8G     0  7.8G   0% /run/shm
tmpfs           4.0M     0  4.0M   0% /sys/fs/cgroup
none            7.8G  1.1M  7.8G   1% /mnt/wslg/versions.txt
none            7.8G  1.1M  7.8G   1% /mnt/wslg/doc
C:\             1.9T  1.4T  513G  73% /mnt/c
tmpfs           7.8G  216K  7.8G   1% /run/qemu
snapfuse        128K  128K     0 100% /snap/bare/5
snapfuse         74M   74M     0 100% /snap/core22/1802
snapfuse        506M  506M     0 100% /snap/gnome-42-2204/176
snapfuse        517M  517M     0 100% /snap/gnome-42-2204/202
snapfuse         92M   92M     0 100% /snap/gtk-common-themes/1535
snapfuse         45M   45M     0 100% /snap/snapd/23545
snapfuse         45M   45M     0 100% /snap/snapd/23771
snapfuse        131M  131M     0 100% /snap/ubuntu-desktop-installer/1284
snapfuse        132M  132M     0 100% /snap/ubuntu-desktop-installer/1286
snapfuse         74M   74M     0 100% /snap/core22/1908
  1. I opened command prompt to see if it was a wsl thing, but after one command, the command prompt stopped working as well.
  2. After waiting a few minutes (5-10), the command prompt (and wsl) both started accepting input, but then less than 1 minute later it stopped accepting input again.
  3. Just to double check it was an input problem and not an output problem, I started a terminal with htop running, and the output was constantly changing even though I was not able to input anything into any of the other prompts.

I'm not sure, but #18755 seems to be having similar problems (but maybe it's unrelated). I've tried adding a dump file, but not sure if it worked properly or not.

Expected Behavior

Smooth keyboard input.

Actual Behavior

Input stops being accepted every so often.

Originally created by @thecaligarmo on GitHub (Apr 13, 2025). ### Windows Terminal version 1.22.10731.0 ### Windows build number 10.0.26100.3775 ### Other Software _No response_ ### Steps to reproduce Not sure what happened/was changed, but this morning my terminal stopped accepting input every so often. (So not sure how to reproduce it). In essence what I noticed: 1. WSL was not responding to keyboard input, I thought it had crashed so closed it and reopened, with no succes. 2. I restarted my computer to see if a simple on/off cycle would fix it. At first it accepted when I typed `ls`, but then shortly after it stopped accepting input again. 3. I thought maybe it was due to lack of space (as it seemed to happen after I downloaded something), but this was not true: ``` aram:~ $ df -h Filesystem Size Used Avail Use% Mounted on none 7.8G 0 7.8G 0% /usr/lib/modules/5.15.167.4-microsoft-standard-WSL2 none 7.8G 4.0K 7.8G 1% /mnt/wsl drivers 1.9T 1.4T 513G 73% /usr/lib/wsl/drivers /dev/sdc 1007G 86G 870G 9% / none 7.8G 92K 7.8G 1% /mnt/wslg none 7.8G 0 7.8G 0% /usr/lib/wsl/lib rootfs 7.8G 2.4M 7.8G 1% /init none 7.8G 996K 7.8G 1% /run none 7.8G 0 7.8G 0% /run/lock none 7.8G 0 7.8G 0% /run/shm tmpfs 4.0M 0 4.0M 0% /sys/fs/cgroup none 7.8G 1.1M 7.8G 1% /mnt/wslg/versions.txt none 7.8G 1.1M 7.8G 1% /mnt/wslg/doc C:\ 1.9T 1.4T 513G 73% /mnt/c tmpfs 7.8G 216K 7.8G 1% /run/qemu snapfuse 128K 128K 0 100% /snap/bare/5 snapfuse 74M 74M 0 100% /snap/core22/1802 snapfuse 506M 506M 0 100% /snap/gnome-42-2204/176 snapfuse 517M 517M 0 100% /snap/gnome-42-2204/202 snapfuse 92M 92M 0 100% /snap/gtk-common-themes/1535 snapfuse 45M 45M 0 100% /snap/snapd/23545 snapfuse 45M 45M 0 100% /snap/snapd/23771 snapfuse 131M 131M 0 100% /snap/ubuntu-desktop-installer/1284 snapfuse 132M 132M 0 100% /snap/ubuntu-desktop-installer/1286 snapfuse 74M 74M 0 100% /snap/core22/1908 ``` 4. I opened command prompt to see if it was a wsl thing, but after one command, the command prompt stopped working as well. 5. After waiting a few minutes (5-10), the command prompt (and wsl) both started accepting input, but then less than 1 minute later it stopped accepting input again. 6. Just to double check it was an input problem and not an output problem, I started a terminal with `htop` running, and the output was constantly changing even though I was not able to input anything into any of the other prompts. I'm not sure, but #18755 seems to be having similar problems (but maybe it's unrelated). I've tried adding a dump file, but not sure if it worked properly or not. <!-- Failed to upload "WindowsTerminal.DMP" --> ### Expected Behavior Smooth keyboard input. ### Actual Behavior Input stops being accepted every so often.
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 08:33:30 +00:00
claunia commented 2026-01-31 08:33:30 +00:00
Author
Owner
Copy Link

@thecaligarmo commented on GitHub (Apr 13, 2025):

Some extra notes:

  1. While this was happening, htop was not showing an increased memory or CPU usage. They were all fairly low.
  2. I tried disabling every program that was running (except for opera and dropbox) and the issue was still persistent.
  3. It seems to not always occur (for example: earlier it was happening after 1-2 commands, but now I've been able to run a few different commands without an issue.... [of course it starts working after I submit an issue 😅 ])
  4. Finally, during this time I was still able to use VS Code's terminal without any issue.
@thecaligarmo commented on GitHub (Apr 13, 2025): Some extra notes: 1. While this was happening, `htop` was not showing an increased memory or CPU usage. They were all fairly low. 2. I tried disabling every program that was running (except for opera and dropbox) and the issue was still persistent. 3. It seems to not always occur (for example: earlier it was happening after 1-2 commands, but now I've been able to run a few different commands without an issue.... [of course it starts working after I submit an issue 😅 ]) 4. Finally, during this time I was still able to use VS Code's terminal without any issue.
claunia commented 2026-01-31 08:33:31 +00:00
Author
Owner
Copy Link

@thecaligarmo commented on GitHub (Apr 13, 2025):

PS I noticed that the file didn't upload for some reason. When I tried doing it again I get the following error:
Failed to upload "WindowsTerminal.DMP"
from Github. I'm not sure what the best way to upload a file is since github won't let me.

@thecaligarmo commented on GitHub (Apr 13, 2025): PS I noticed that the file didn't upload for some reason. When I tried doing it again I get the following error: `Failed to upload "WindowsTerminal.DMP"` from Github. I'm not sure what the best way to upload a file is since github won't let me.
claunia commented 2026-01-31 08:33:31 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 16, 2025):

Hey, this one is quite strange!

  • Do you have anything anomalous in the Event Viewer?
  • When you say "command prompt" do you mean inside Terminal or are you launching it in the "Windows Console Host"? I'm guessing the former, but just wanted to make sure.
  • Have you changed the settings on the "Touch, Keyboard and Handwriting" service in services.msc/?
@DHowett commented on GitHub (Apr 16, 2025): Hey, this one is quite strange! - Do you have anything anomalous in the Event Viewer? - When you say "command prompt" do you mean _inside Terminal_ or are you launching it in the "Windows Console Host"? I'm guessing the former, but just wanted to make sure. - Have you changed the settings on the "Touch, Keyboard and Handwriting" service in `services.msc`/?
claunia commented 2026-01-31 08:33:31 +00:00
Author
Owner
Copy Link

@thecaligarmo commented on GitHub (Apr 17, 2025):

To Answer your questions.

  1. I've not checked Event Viewer, but not really sure where to look inside of it directly.
  2. By Command prompt I mean inside the terminal. As in, think of a normal linux terminal, and when I'm trying to type inside it, nothing happens.
  3. I have not touched any settings in the services. When I use run to open services.msc, there's not even a "Touch, Keyboard and Handwriting" option in there...

Note: I realised I can't upload the file because it's a .dmp file and according to github, I can't upload .dmp files: https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/attaching-files

I haven't been using the terminal as much over the past few days, so have not seen if this is still happening or if it "magically fixed itself" as things sometimes like to do.

@thecaligarmo commented on GitHub (Apr 17, 2025): To Answer your questions. 1. I've not checked Event Viewer, but not really sure where to look inside of it directly. 2. By Command prompt I mean *inside* the terminal. As in, think of a normal linux terminal, and when I'm trying to type inside it, nothing happens. 3. I have not touched any settings in the services. When I use `run` to open `services.msc`, there's not even a "Touch, Keyboard and Handwriting" option in there... Note: I realised I can't upload the file because it's a `.dmp` file and according to github, I can't upload `.dmp` files: https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/attaching-files I haven't been using the terminal as much over the past few days, so have not seen if this is still happening or if it "magically fixed itself" as things sometimes like to do.
claunia commented 2026-01-31 08:33:31 +00:00
Author
Owner
Copy Link

@thecaligarmo commented on GitHub (Apr 21, 2025):

I'm not sure if this helps, but it started doing it again this morning, so I checked Event Viewer to see if there's anything showing up. Here's some images of what I'm seeing. Coincidentally, the timing seems to match with my previous instance as well (and a couple of other times, but I probably didn't notice those)

Errors:

Image

Image

Image

Image

Warnings:

Image

@thecaligarmo commented on GitHub (Apr 21, 2025): I'm not sure if this helps, but it started doing it again this morning, so I checked `Event Viewer` to see if there's anything showing up. Here's some images of what I'm seeing. Coincidentally, the timing seems to match with my previous instance as well (and a couple of other times, but I probably didn't notice those) **Errors:** ![Image](https://github.com/user-attachments/assets/fe9b6ea9-4c60-4ad9-93f8-1da58c885a35) ![Image](https://github.com/user-attachments/assets/ff60bf42-c66d-4b63-a91f-cba906c7b46a) ![Image](https://github.com/user-attachments/assets/6b2f71cc-8829-4490-b266-6867e54acdc1) ![Image](https://github.com/user-attachments/assets/d4fdc960-4d5b-46e3-97f1-a1ae04dd1d1a) **Warnings:** ![Image](https://github.com/user-attachments/assets/e55b2542-f1c8-494d-9892-0ffdfccfa51b)
claunia commented 2026-01-31 08:33:31 +00:00
Author
Owner
Copy Link

@thecaligarmo commented on GitHub (May 28, 2025):

Is there any update on this? The issue is still persistent. Here are my current version info:

Windows Terminal version
1.22.11141.0

Windows build number
10.0.26100.4061

@thecaligarmo commented on GitHub (May 28, 2025): Is there any update on this? The issue is still persistent. Here are my current version info: Windows Terminal version 1.22.11141.0 Windows build number 10.0.26100.4061
claunia commented 2026-01-31 08:33:32 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Aug 6, 2025):

We have several theories why this may happen. Previously we had hangs like this due to driver issues, incompatibilities with AV vendors, etc. Could you try to record an ETW trace for us? Here are the instructions: https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capturing-a-debug-etl-trace

The trace will contain every input and output of your terminal so make sure it doesn't contain any sensitive data. But the good news is that you can leave the trace running for long periods of time if needed. It'll hopefully show if your input even goes through the terminal into the console application.

FWIW the error messages you're seeing in Event Viewer don't look too good either. Getting that addressed (or reinstalling Windows) may be useful in any case.

@lhecker commented on GitHub (Aug 6, 2025): We have several theories why this may happen. Previously we had hangs like this due to driver issues, incompatibilities with AV vendors, etc. Could you try to record an ETW trace for us? Here are the instructions: https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips#capturing-a-debug-etl-trace The trace will contain every input and output of your terminal so make sure it doesn't contain any sensitive data. But the good news is that you can leave the trace running for long periods of time if needed. It'll hopefully show if your input even goes through the terminal into the console application. FWIW the error messages you're seeing in Event Viewer don't look too good either. Getting that addressed (or reinstalling Windows) may be useful in any case.
claunia commented 2026-01-31 08:33:32 +00:00
Author
Owner
Copy Link

@thecaligarmo commented on GitHub (Aug 18, 2025):

Sounds good. I'll try and do a ETW trace if I see it happen again. I haven't noticed it happen recently, but mostly because I've been away from my computer for the past few weeks. I'll also make sure no sensitive data gets logged.

Yeah, I'm not sure what the event viewer stuff is. I had bought my laptop from Alienware and every time I mentioned problems they just said "our diagnostic isn't showing anything" and so refused to help. I'll need to see what I can do once I have backup computer. Thanks for the advice.

@thecaligarmo commented on GitHub (Aug 18, 2025): Sounds good. I'll try and do a ETW trace if I see it happen again. I haven't noticed it happen recently, but mostly because I've been away from my computer for the past few weeks. I'll also make sure no sensitive data gets logged. Yeah, I'm not sure what the event viewer stuff is. I had bought my laptop from Alienware and every time I mentioned problems they just said "our diagnostic isn't showing anything" and so refused to help. I'll need to see what I can do once I have backup computer. Thanks for the advice.
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 Needs-Attention Needs-Triage
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#23142
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?