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

Windows Terminal freezes after typing a particular character #17104

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

Originally created by @zp-zpanda on GitHub (Mar 28, 2022).

Windows Terminal version

1.13.10733.0

Windows build number

10.0.19044.1526

Other Software

No response

Steps to reproduce

  1. Open a prompt
  2. Type a particular character
  3. Windows Terminal just freezes

Affected Prompts:

  • Command Prompt
  • Windows PowerShell
  • PowerShell
  • VS Developer PowerShell (17.0.5)
  • Git Bash

Unaffected Prompts:

  • VS Developer Command Prompt (17.0.5)

Expected Behavior

The particular character gets typed

Actual Behavior

Windows Terminal freezes

Notes

This issue only affects one tab at a time.
The particular character is different every time.

Originally created by @zp-zpanda on GitHub (Mar 28, 2022). ### Windows Terminal version 1.13.10733.0 ### Windows build number 10.0.19044.1526 ### Other Software _No response_ ### Steps to reproduce 1. Open a prompt 2. Type a particular character 3. Windows Terminal just freezes Affected Prompts: * Command Prompt * Windows PowerShell * PowerShell * VS Developer PowerShell (17.0.5) * Git Bash Unaffected Prompts: * VS Developer Command Prompt (17.0.5) ### Expected Behavior The particular character gets typed ### Actual Behavior Windows Terminal freezes ### Notes This issue only affects one tab at a time. The particular character is different every time.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 05:32:20 +00:00
claunia commented 2026-01-31 05:32:21 +00:00
Author
Owner
Copy Link

@OfekShilon commented on GitHub (Mar 28, 2022):

Same for me. Terminal version 1.12.10393.0 - I think this started with the latest windows insider build (22581)
Terminal becomes unresponsive when typing any character, typically returns to being responsive after 30-60s. (And freezes again on the next character typed).

@OfekShilon commented on GitHub (Mar 28, 2022): Same for me. Terminal version 1.12.10393.0 - I *think* this started with the latest windows insider build (22581) Terminal becomes unresponsive when typing **any** character, typically returns to being responsive after 30-60s. (And freezes again on the next character typed).
claunia commented 2026-01-31 05:32:21 +00:00
Author
Owner
Copy Link

@ScottESanDiego commented on GitHub (Mar 28, 2022):

I see it in 1.13.10734.0. It's any character, and the freeze isn't just terminal input - the window is not responsive (no dragging, drop-down, etc.) as well.

If I "Run as Administrator", I don't see the slowdown. (Maybe that's because it doesn't open in Windows Terminal, but in some other pwsh console?)

@ScottESanDiego commented on GitHub (Mar 28, 2022): I see it in 1.13.10734.0. It's any character, and the freeze isn't just terminal input - the window is not responsive (no dragging, drop-down, etc.) as well. If I "Run as Administrator", I don't see the slowdown. (Maybe that's because it doesn't open in Windows Terminal, but in some other pwsh console?)
claunia commented 2026-01-31 05:32:21 +00:00
Author
Owner
Copy Link

@OfekShilon commented on GitHub (Mar 28, 2022):

Unlike @ScottESanDiego, I see the same window freeze even when I 'run as admin'.

@OfekShilon commented on GitHub (Mar 28, 2022): Unlike @ScottESanDiego, I see the same window freeze even when I 'run as admin'.
claunia commented 2026-01-31 05:32:22 +00:00
Author
Owner
Copy Link

@justinledwards commented on GitHub (Mar 28, 2022):

I get the freeze running as admin as well. Mine started on build 22581.100 just like @OfekShilon

@justinledwards commented on GitHub (Mar 28, 2022): I get the freeze running as admin as well. Mine started on build 22581.100 just like @OfekShilon
claunia commented 2026-01-31 05:32:22 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 28, 2022):

@ebadger Here's another thread, with another 4 reports. This might be a broad issue.

If anyone who's hitting this is willing, could you uninstall the Terminal and install a much older version, like, 1.10? and just sit with that for a few days to check if it repros there? I'm 99% sure that this is an OS bug, not a Terminal one, so having a repro on a much older Terminal verison might help ID that it's not a Terminal regression.

See also #12746 (which I very well may close this as a dupe of)

@zadjii-msft commented on GitHub (Mar 28, 2022): @ebadger Here's another thread, with another 4 reports. This might be a broad issue. If anyone who's hitting this is willing, could you uninstall the Terminal and install a _much_ older version, like, 1.10? and just sit with that for a few days to check if it repros there? I'm 99% sure that this is an OS bug, not a Terminal one, so having a repro on a much older Terminal verison might help ID that it's not a Terminal regression. See also #12746 (which I very well may close this as a dupe of)
claunia commented 2026-01-31 05:32:22 +00:00
Author
Owner
Copy Link

@OfekShilon commented on GitHub (Mar 28, 2022):

@zadjii-msft I just installed Terminal 1.10.2714 from the github release (https://github.com/microsoft/terminal/releases/tag/v1.10.2714.0) and can confirm that the same freeze happens there. On Windows 11 build 22581.

@OfekShilon commented on GitHub (Mar 28, 2022): @zadjii-msft I just installed Terminal 1.10.2714 from the github release (https://github.com/microsoft/terminal/releases/tag/v1.10.2714.0) and can confirm that the same freeze happens there. On Windows 11 build 22581.
claunia commented 2026-01-31 05:32:22 +00:00
Author
Owner
Copy Link

@OfekShilon commented on GitHub (Mar 29, 2022):

I can also verify that rebooting solved it (or at least made it go away for a while).

And also - I noticed what I thought was a different issue, but it disappeared after a reboot too which makes me suspect it has the same root cause and might help analyze:
I wasn't able to record a trace with Windows-Performance-Recorder, neither to memory or disk. Upon 'Start', the recorder consistently threw a message box saying 'The requested resource is in use'.
Gone after a reboot too.

@OfekShilon commented on GitHub (Mar 29, 2022): I can also verify that rebooting solved it (or at least made it go away for a while). And also - I noticed what I thought was a different issue, but it disappeared after a reboot too which makes me suspect it has the same root cause and might help analyze: I wasn't able to record a trace with Windows-Performance-Recorder, neither to memory or disk. Upon 'Start', the recorder consistently threw a message box saying 'The requested resource is in use'. Gone after a reboot too.
claunia commented 2026-01-31 05:32:22 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 29, 2022):

@OfekShilon Thanks for the diligence on that one. Makes me sleep at night a bit easier 😆

I'm gonna combine this discussion with #12746 just for tracking purposes. Thanks all!

/dup #12746

@zadjii-msft commented on GitHub (Mar 29, 2022): @OfekShilon Thanks for the diligence on that one. Makes me sleep at night a bit easier 😆 I'm gonna combine this discussion with #12746 just for tracking purposes. Thanks all! /dup #12746
claunia commented 2026-01-31 05:32:22 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Mar 29, 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 (Mar 29, 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#17104
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?