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 stops accepting capital Latin letters when I type or paste them in command line, after some time being used #11641

New Issue
Closed
opened 2026-01-31 02:53:23 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 02:53:23 +00:00
Owner
Copy Link

Originally created by @BurstX on GitHub (Dec 1, 2020).

Environment

Windows build number:
Platform      : Win32NT
ServicePack   :
Version       : 10.0.18362.0
VersionString : Microsoft Windows NT 10.0.18362.0

Windows Terminal version:
1.4.3243.0

Any other software?
OMG, it's a dev environment: MSSQL, Visual Studio 2019. VSCode, text editors like Notepad++, Notepad-2-mod,
PDF viewers, TotalCommander, Azure Data Studio, MS Office, Firefox, Google chrome, Edge browser (latest), IIS,
Git for Windows, Greenshot ... and God knows what else.

Steps to reproduce

  1. Run Windows Terminal as administrator. You've got the only tab with the only pane in it (Powershell as default environment.)
  2. Open second pane with vertical split in the same tab. (Powershell)
  3. Open second tab (PowerShell). Open second pane (Powershell) with vertical split in this second newly opened tab.
  4. Here comes the fuzzy part, because the terminal stays in this configuration (2 tabs with 2 panes in each). for quite some time (a couple of days) while I'm working in the terminals: run PowerShell scripts, execute commandlets, run .exe files, etc. I'm not sure what I'm doing in particular that can be the cause.

Expected behavior

At all times, Latin capital letters are typed in the terminal flawlessly. If I paste (from clipboard) a string with Latin capital letters into the command line, the string is pasted as is.

Actual behavior

After a couple of days of being used, this is what happens in the terminal (PowerShell):

  • When I type a capital Latin letter (English US keyboard), it is not typed in the terminal command line
  • When I paste a string containing Latin capital letters, the string is pasted without Latin capital letters as if they are filtered out explicitly. E.g. I copy a string "bugfix/KK-12345" to the clipboard and then paste it to the terminal's command line. The pasted string is "bugfix/-12345", without "AC".
    Note: If I open a new tab (Powershell) (keeping the problematic tabs open) in the same Windows Terminal instance, there is no issue with capital letters in the new tab. (But maybe it will misbehave again after a couple of days of usage.)
Originally created by @BurstX on GitHub (Dec 1, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: Platform : Win32NT ServicePack : Version : 10.0.18362.0 VersionString : Microsoft Windows NT 10.0.18362.0 Windows Terminal version: 1.4.3243.0 Any other software? OMG, it's a dev environment: MSSQL, Visual Studio 2019. VSCode, text editors like Notepad++, Notepad-2-mod, PDF viewers, TotalCommander, Azure Data Studio, MS Office, Firefox, Google chrome, Edge browser (latest), IIS, Git for Windows, Greenshot ... and God knows what else. ``` # Steps to reproduce 1. Run Windows Terminal as administrator. You've got the only __tab__ with the only __pane__ in it (Powershell as default environment.) 1. Open second __pane__ with vertical split in the same __tab__. (Powershell) 1. Open second __tab__ (PowerShell). Open second __pane__ (Powershell) with vertical split in this second newly opened __tab__. 1. Here comes the fuzzy part, because the terminal stays in this configuration (2 tabs with 2 panes in each). for quite some time (a couple of days) while I'm working in the terminals: run PowerShell scripts, execute commandlets, run .exe files, etc. I'm not sure what I'm doing in particular that can be the cause. # Expected behavior At all times, Latin capital letters are typed in the terminal flawlessly. If I paste (from clipboard) a string with Latin capital letters into the command line, the string is pasted as is. # Actual behavior **After a couple of days** of being used, this is what happens in the terminal (PowerShell): - When I type a capital Latin letter (English US keyboard), it is not typed in the terminal command line - When I paste a string containing Latin capital letters, the string is pasted without Latin capital letters as if they are filtered out explicitly. E.g. I copy a string "bugfix/**KK**-12345" to the clipboard and then paste it to the terminal's command line. The pasted string is "bugfix/-12345", without "AC". Note: If I open a new tab (Powershell) (keeping the problematic tabs open) in the same Windows Terminal instance, there is no issue with capital letters in the new tab. (But maybe it will misbehave again after a couple of days of usage.)
claunia commented 2026-01-31 02:53:25 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 1, 2020):

Okay, so this is bizarre. We've seen this intermittently once before, over in #7087. From that thread:https://github.com/microsoft/terminal/issues/7087#issuecomment-676782357

Found a fix. If you have the same problem as me, then updating PSReadLine to the latest preview version can help you. Check out this PowerShell/PowerShell#10794 and this PowerShell/PSReadLine for more information.

@BurstX Could you try that, and see if that resolves the issue?

@zadjii-msft commented on GitHub (Dec 1, 2020): Okay, so this is bizarre. We've seen this intermittently once before, over in #7087. From that thread:https://github.com/microsoft/terminal/issues/7087#issuecomment-676782357 > Found a fix. If you have the same problem as me, then updating PSReadLine to the latest preview version can help you. Check out this [PowerShell/PowerShell#10794](https://github.com/PowerShell/PowerShell/issues/10794) and this [PowerShell/PSReadLine](https://github.com/PowerShell/PSReadLine) for more information. @BurstX Could you try that, and see if that resolves the issue?
claunia commented 2026-01-31 02:53:26 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Dec 5, 2020):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Dec 5, 2020): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-31 02:53:26 +00:00
Author
Owner
Copy Link

@AmRo045 commented on GitHub (Apr 8, 2021):

I have the same issue and I attached a video for better demonstration of the issue:
https://www.dropbox.com/s/78zkkvgv4kqpjcs/WindowsTerminalCapitalLettersIssue.mp4?dl=0
Windows Terminal version: 1.6.10571.0

@AmRo045 commented on GitHub (Apr 8, 2021): I have the same issue and I attached a video for better demonstration of the issue: https://www.dropbox.com/s/78zkkvgv4kqpjcs/WindowsTerminalCapitalLettersIssue.mp4?dl=0 Windows Terminal version: **1.6.10571.0**
claunia commented 2026-01-31 02:53:26 +00:00
Author
Owner
Copy Link

@BurstX commented on GitHub (Apr 9, 2021):

I have the same issue and I attached a video for better demonstration of the issue:
https://www.dropbox.com/s/78zkkvgv4kqpjcs/WindowsTerminalCapitalLettersIssue.mp4?dl=0
Windows Terminal version: 1.6.10571.0

In my case, an update to the latest version of PSReadLine helped (see comment above). No issues since the update.

@BurstX commented on GitHub (Apr 9, 2021): > I have the same issue and I attached a video for better demonstration of the issue: > https://www.dropbox.com/s/78zkkvgv4kqpjcs/WindowsTerminalCapitalLettersIssue.mp4?dl=0 > Windows Terminal version: **1.6.10571.0** In my case, an update to the latest version of PSReadLine helped (see comment above). No issues since the update.
claunia commented 2026-01-31 02:53:26 +00:00
Author
Owner
Copy Link

@AmRo045 commented on GitHub (Apr 9, 2021):

@BurstX The problem solved after installing PSReadLine module.

@AmRo045 commented on GitHub (Apr 9, 2021): @BurstX The problem solved after installing PSReadLine module.
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 Area-Input Needs-Attention Needs-Tag-Fix Needs-Triage Product-Powershell
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#11641
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?