starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

One letter types twice #15941

New Issue
Open
opened 2026-01-31 04:52:55 +00:00 by claunia · 29 comments
claunia commented 2026-01-31 04:52:55 +00:00
Owner
Copy Link

Originally created by @hrueschwein on GitHub (Nov 21, 2021).

Windows Terminal version

1.11.2921.0

Windows build number

10.0.19044.0

Other Software

powershell 5.1 (build 19041 revision 1320)
mongosh 1.0.5 (I don't think that it's matter)

Steps to reproduce

  1. Open new tab
  2. Turn on something and wait for hour (i didn't anything else)
  3. Type something (e.x. "cls")

Expected Behavior

I see "cls"

Actual Behavior

I see "ccllss"

P.S. my keyboard is good, in other programs I don't get this result

Originally created by @hrueschwein on GitHub (Nov 21, 2021). ### Windows Terminal version 1.11.2921.0 ### Windows build number 10.0.19044.0 ### Other Software powershell 5.1 (build 19041 revision 1320) mongosh 1.0.5 (I don't think that it's matter) ### Steps to reproduce 1. Open new tab 2. Turn on something and wait for hour (i didn't anything else) 3. Type something (e.x. "cls") ### Expected Behavior I see "cls" ### Actual Behavior I see "ccllss" P.S. my keyboard is good, in other programs I don't get this result
claunia added the Issue-BugArea-InputNeeds-ReproProduct-Terminal labels 2026-01-31 04:52:56 +00:00
claunia commented 2026-01-31 04:52:57 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 23, 2021):

You know, I feel like we've seen this before but I can't seem to find a dupe...

Does this only happen when you're running mongosh? Does this occur in just a plain powershell tab, or even a Command Prompt tab?

What keyboard layout are you using? Are you possibly switching between keyboard layouts?

You might be able to run the Terminal with a debug tap to get a trace of all the input and output. Once the bug starts occuring, send us a screenshot and we might be able to figure out what the Terminal thinks it's getting here.

@zadjii-msft commented on GitHub (Nov 23, 2021): You know, I feel like we've seen this before but I can't seem to find a dupe... Does this only happen when you're running mongosh? Does this occur in just a plain powershell tab, or even a Command Prompt tab? What keyboard layout are you using? Are you possibly switching between keyboard layouts? You might be able to run the Terminal with a [debug tap](https://github.com/microsoft/terminal/wiki/Enabling-the-debug-tap) to get a trace of all the input and output. Once the bug starts occuring, send us a screenshot and we might be able to figure out what the Terminal thinks it's getting here.
claunia commented 2026-01-31 04:52:57 +00:00
Author
Owner
Copy Link

@hrueschwein commented on GitHub (Nov 23, 2021):

Does this only happen when you're running mongosh?

No, not only. Once I've just oppened new powershell tab and this bug repeated

Does this occur in just a plain powershell tab, or even a Command Prompt tab?

I haven't tested with other shells yet, so I don't know

What keyboard layout are you using? Are you possibly switching between keyboard layouts?

I use Russian standart layout (йцукен) and English (I think USA) (qwerty). I can switch them, in both layouts letters are doubling

@hrueschwein commented on GitHub (Nov 23, 2021): > Does this only happen when you're running mongosh? No, not only. Once I've just oppened new powershell tab and this bug repeated > Does this occur in just a plain powershell tab, or even a Command Prompt tab? I haven't tested with other shells yet, so I don't know > What keyboard layout are you using? Are you possibly switching between keyboard layouts? I use Russian standart layout (йцукен) and English (I think USA) (qwerty). I can switch them, in both layouts letters are doubling
claunia commented 2026-01-31 04:52:58 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 29, 2021):

Okay yea, a debug tap trace is the next best thing to try. Maybe that'll give us a hint.

@zadjii-msft commented on GitHub (Nov 29, 2021): Okay yea, a [debug tap](https://github.com/microsoft/terminal/wiki/Enabling-the-debug-tap) trace is the next best thing to try. Maybe that'll give us a hint.
claunia commented 2026-01-31 04:52:58 +00:00
Author
Owner
Copy Link

@hrueschwein commented on GitHub (Nov 29, 2021):

This problem didn't appear again for a month (maybe some of Windows updates affected this), but if you need debug tap:

␛[?9001h␛[2J␛[m␛[HWindows␣PowerShell␍␊(C)␣Корпорация␣Майкрософт␣(Microsoft␣Corporation).␣Все␣права␣защищены.␛[4;1HПопробуйте␣новую␣кроссплатформенную␣оболочку␣PowerShell␣(https://aka.ms/pscore6)␛]0;Windows␣PowerShell␇␛[?25h␛[?25l␛[7;1H␛[?25h␛[?25l␛[H␛[?25h␛[?25l␛[3J␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␛[H␛[?25h␛[?25l␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␛[H␛[?25hPS␣Z:\>␣
@hrueschwein commented on GitHub (Nov 29, 2021): This problem didn't appear again for a month (maybe some of Windows updates affected this), but if you need debug tap: ``` ␛[?9001h␛[2J␛[m␛[HWindows␣PowerShell␍␊(C)␣Корпорация␣Майкрософт␣(Microsoft␣Corporation).␣Все␣права␣защищены.␛[4;1HПопробуйте␣новую␣кроссплатформенную␣оболочку␣PowerShell␣(https://aka.ms/pscore6)␛]0;Windows␣PowerShell␇␛[?25h␛[?25l␛[7;1H␛[?25h␛[?25l␛[H␛[?25h␛[?25l␛[3J␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␛[H␛[?25h␛[?25l␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␍␊␛[K␛[H␛[?25hPS␣Z:\>␣ ```
claunia commented 2026-01-31 04:52:58 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 29, 2021):

This problem didn't appear again for a month

Ah, so okay, if it's not really happening anymore, then there's not much else we can do here 🤷 If it does start repro'ing consistently, then open up a new tab with the debug tap, use it like you would normally, and once it starts to repro, then copy-paste the content. We can re-open this then. Thanks!

@zadjii-msft commented on GitHub (Nov 29, 2021): > This problem didn't appear again for a month Ah, so okay, if it's not really happening anymore, then there's not much else we can do here 🤷 If it does start repro'ing consistently, then open up a new tab with the debug tap, use it like you would normally, and once it starts to repro, then copy-paste the content. We can re-open this then. Thanks!
claunia commented 2026-01-31 04:52:59 +00:00
Author
Owner
Copy Link

@gopat commented on GitHub (Nov 16, 2022):

Happened to me yesterday.
Enabled the debug tap mentioned in other post, opened a wsl tab and today got the same character doubling behabiour.
This is a screenshot:

wt_dupchars

@gopat commented on GitHub (Nov 16, 2022): Happened to me yesterday. Enabled the _debug tap_ mentioned in other post, opened a wsl tab and today got the same character doubling behabiour. This is a screenshot: ![wt_dupchars](https://user-images.githubusercontent.com/10393246/202220705-5ebdd81e-9ddd-4c4d-abd0-3bffb4a874a2.png)
claunia commented 2026-01-31 04:52:59 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 16, 2022):

The keys in that screenshot look normal - a down and an up for each.

Did this work before (and regress recently)? Is there anything else about your system that might have changed?

I suppose it's possible that there's some uninitialized memory that could trigger this, maybe.

Does this repro with cmd, pwsh? Or just bash in WSL?

@zadjii-msft commented on GitHub (Nov 16, 2022): The keys in that screenshot look normal - a down and an up for each. Did this work before (and regress recently)? Is there anything else about your system that might have changed? I suppose it's possible that there's some uninitialized memory that could trigger this, maybe. Does this repro with cmd, pwsh? Or just `bash` in WSL?
claunia commented 2026-01-31 04:53:00 +00:00
Author
Owner
Copy Link

@gopat commented on GitHub (Nov 17, 2022):

The keys in that screenshot look normal - a down and an up for each.

Did this work before (and regress recently)? Is there anything else about your system that might have changed?

In general, i have only experienced this issue recently, and always on tabs that have been open for a significant time.

In the case of the screenshot posted yesterday, a couple other tabs on the same wt window were affected by the issue but the other (fresh from the day) were not. Then, proceeded to set up the debug tap , open a new tab and leave it open (locking the session, with Win+L). This was on 2022-11-15 and while working on the pc directly.
Yesterday (2022 -11-16) connected to it though RDP (mstsc /v pchostname) and when i went to use it, it showed the same problem and it was then when i took that screenshot.

I suppose it's possible that there's some uninitialized memory that could trigger this, maybe.

🤷‍♂️ Don't know.
But there's one thing, it seems to be tab-local, i mean: there can be open tabs that are affected and others that are unaffected at the same time, side by side in the same wt window.

Also, once a tab starts to be affected by the issue, it seems to be affected until it is closed, it seems kinda permanent.

Yet another thing; don't know if it might be relevant, but after typing anything, it seems possible to delete characters one by one (Maybe keypresses from input that maps to control characters are not duplicated? 🤔)

Does this repro with cmd, pwsh? Or just bash in WSL?

Today (2022-11-17), physically on the pc, and in the very same tab of the previous screenshot (launching cmd.exe from the wsl shell):

imagen

(spammed the <Delete/Backspace> key and pressed <Enter> several times before screenshot)

Does not seem to care what it is running underneath, but i'll try to test it on a new tab for cmd/pwsh.

@gopat commented on GitHub (Nov 17, 2022): > The keys in that screenshot look normal - a down and an up for each. > > Did this work before (and regress recently)? Is there anything else about your system that might have changed? > In general, i have only experienced this issue recently, and always on tabs that have been open for a significant time. In the case of the screenshot posted yesterday, a couple other tabs on the same wt window were affected by the issue but the other (fresh from the day) were not. Then, proceeded to set up the _debug tap_ , open a new tab and leave it open (locking the session, with Win+L). This was on 2022-11-15 and while working on the pc directly. Yesterday (2022 -11-16) connected to it though RDP (`mstsc /v pchostname`) and when i went to use it, it showed the same problem and it was then when i took that screenshot. > I suppose it's possible that there's some uninitialized memory that could trigger this, maybe. > 🤷‍♂️ Don't know. But there's one thing, it seems to be tab-local, i mean: there can be open tabs that are affected and others that are unaffected at the same time, side by side in the same wt window. Also, once a tab starts to be affected by the issue, it seems to be affected until it is closed, it seems kinda permanent. Yet another thing; don't know if it might be relevant, but after typing anything, it seems possible to delete characters one by one (Maybe keypresses from input that maps to control characters are not duplicated? 🤔) > Does this repro with cmd, pwsh? Or just `bash` in WSL? Today (2022-11-17), physically on the pc, and in the very same tab of the previous screenshot (launching cmd.exe from the wsl shell): ![imagen](https://user-images.githubusercontent.com/10393246/202440436-1d6fcd43-6ff3-4239-9b58-301fc83aafdd.png) (spammed the \<Delete/Backspace\> key and pressed \<Enter\> several times before screenshot) Does not seem to care what it is running underneath, but i'll try to test it on a new tab for cmd/pwsh.
claunia commented 2026-01-31 04:53:01 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 21, 2022):

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 (Nov 21, 2022): 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 04:53:02 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 25, 2022):

Sorry about the overactive bot!

@DHowett commented on GitHub (Nov 25, 2022): Sorry about the overactive bot!
claunia commented 2026-01-31 04:53:02 +00:00
Author
Owner
Copy Link

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

oh hey we missed something! The input records are wrong, we've got both a character AND an INPUT_RECORD, which isn't what you want!

image

Maybe the Russian keyboard layout thing really matters here! IIRC this was noticed once before in an IME, but idk if it was in russian necessarily

@zadjii-msft commented on GitHub (Nov 28, 2022): oh hey we missed something! The input records _are_ wrong, we've got both a character AND an INPUT_RECORD, which isn't what you want! ![image](https://user-images.githubusercontent.com/18356694/204390112-c4a4fc81-d517-4a4f-ad52-6af5aed29ad2.png) Maybe the Russian keyboard layout thing really matters here! IIRC this was noticed once before in an IME, but idk if it was in russian necessarily
claunia commented 2026-01-31 04:53:03 +00:00
Author
Owner
Copy Link

@nalinvyas commented on GitHub (Feb 7, 2023):

This seems to have started after I opened the terminal from a read-only file. I am facing the same issue too.

@nalinvyas commented on GitHub (Feb 7, 2023): This seems to have started after I opened the terminal from a read-only file. I am facing the same issue too.
claunia commented 2026-01-31 04:53:03 +00:00
Author
Owner
Copy Link

@Dan-Albrecht commented on GitHub (Apr 4, 2023):

I hit this today. New tabs after turning on debugtap didn't repro. This happened in both a cmd and WSL tab.

This was on full English setup. Running Preview v1.18.902.0. The only weird things:

  • I may have taken an update to Terminal from Store when this started; exact timeline is unclear
    • New instance of terminal are throwing on launch which makes me think more I'm in some screwed up halfway updated state
  • On the taskbar I have a suspicious extra window called DesktopWindowXamlSource in the Terminal group (below)

image

@Dan-Albrecht commented on GitHub (Apr 4, 2023): I hit this today. New tabs after turning on debugtap didn't repro. This happened in both a cmd and WSL tab. This was on full English setup. Running Preview v1.18.902.0. The only weird things: - I _may_ have taken an update to Terminal from Store when this started; exact timeline is unclear - New instance of terminal are throwing on launch which makes me think more I'm in some screwed up halfway updated state - On the taskbar I have a suspicious extra window called `DesktopWindowXamlSource` in the Terminal group (below) ![image](https://user-images.githubusercontent.com/7351388/229918294-a72a7535-ede2-44fa-b160-5986bc7349ae.png)
claunia commented 2026-01-31 04:53:03 +00:00
Author
Owner
Copy Link

@kuro68k commented on GitHub (May 10, 2023):

I can reproduce this today. I do have an extra unusual keymap, but it happens with vanilla English UK and Japanese.

@kuro68k commented on GitHub (May 10, 2023): I can reproduce this today. I do have an extra unusual keymap, but it happens with vanilla English UK and Japanese.
claunia commented 2026-01-31 04:53:04 +00:00
Author
Owner
Copy Link

@Kufat commented on GitHub (May 12, 2023):

Windows 10 22H2, Terminal 1.16.10261.0. I'm experiencing this with a standard US keyboard layout and have been dealing with it intermittently for the past year+. It seems to start happening after I initiate a Remote Desktop session into my machine and continues until a given Terminal tab is closed, even when I subsequently log into the machine locally. (The Remote Desktop aspect might be a red herring; I'm not sure.)

Newly-started tabs are unaffected; I can switch from new to old and get doubled characters, and then switch back to new and type normally. Backspace, ^C, newlines, etc. seem unaffected; letters, numbers, and spaces are affected. I have a debug tap open on a new tab and will edit this comment with the results once that tab starts experiencing the issue.

@Kufat commented on GitHub (May 12, 2023): Windows 10 22H2, Terminal 1.16.10261.0. I'm experiencing this with a standard US keyboard layout and have been dealing with it intermittently for the past year+. It seems to start happening after I initiate a Remote Desktop session into my machine and continues until a given Terminal tab is closed, even when I subsequently log into the machine locally. (The Remote Desktop aspect might be a red herring; I'm not sure.) Newly-started tabs are unaffected; I can switch from new to old and get doubled characters, and then switch back to new and type normally. Backspace, ^C, newlines, etc. seem unaffected; letters, numbers, and spaces are affected. I have a debug tap open on a new tab and will edit this comment with the results once that tab starts experiencing the issue.
claunia commented 2026-01-31 04:53:04 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (May 12, 2023):

oh hey we missed something! The input records are wrong, we've got both a character AND an INPUT_RECORD, which isn't what you want!

image

@zadjii-msft I don't think there's anything wrong with that. What you're seeing is the key down and key up events. This is exactly what I get for a single keypress of q.

␛[81;16;113;1;32;1_␛[81;16;113;0;32;1_q

Virtual-key code for the Q key is 81.
Scan code for the Q key is 16.
ASCII value for q is 113.
Key down state is 1 then 0.
Control key state is 32 (NumLock on).
Repeat count is 1.

So it looks like we're sending the correct data through to conhost, but it might be the conhost translation of those records back into input events that is going wrong somewhere.

I wonder if it's possible for Windows Terminal and the connected conhost to end up with differing keyboard layouts, and whether that would have any weird side effects (e.g. WT is passing through a scan code for a US keyboard, but conhost thinks it's using some other layout). I can't imagine how that would trigger a repeated key though.

@j4james commented on GitHub (May 12, 2023): > oh hey we missed something! The input records _are_ wrong, we've got both a character AND an INPUT_RECORD, which isn't what you want! > > ![image](https://user-images.githubusercontent.com/18356694/204390112-c4a4fc81-d517-4a4f-ad52-6af5aed29ad2.png) <s>@zadjii-msft I don't think there's anything wrong with that. What you're seeing is the key down and key up events. This is exactly what I get for a single keypress of `q`. ␛[81;16;113;1;32;1_␛[81;16;113;0;32;1_q Virtual-key code for the `Q` key is 81. Scan code for the `Q` key is 16. ASCII value for `q` is 113. Key down state is 1 then 0. Control key state is 32 (`NumLock` on). Repeat count is 1. So it looks like we're sending the correct data through to conhost, but it might be the conhost translation of those records back into input events that is going wrong somewhere. I wonder if it's possible for Windows Terminal and the connected conhost to end up with differing keyboard layouts, and whether that would have any weird side effects (e.g. WT is passing through a scan code for a US keyboard, but conhost thinks it's using some other layout). I can't imagine how that would trigger a repeated key though.</s>
claunia commented 2026-01-31 04:53:04 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (May 12, 2023):

Doh! Disregard that. I completely missed the bright green square highlighting the first q passed though as a regular character!

@j4james commented on GitHub (May 12, 2023): Doh! Disregard that. I completely missed the bright green square highlighting the first `q` passed though as a regular character!
claunia commented 2026-01-31 04:53:05 +00:00
Author
Owner
Copy Link

@Kufat commented on GitHub (May 22, 2023):

Do you still need additional debug tap output?

@Kufat commented on GitHub (May 22, 2023): Do you still need additional debug tap output?
claunia commented 2026-01-31 04:53:05 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Jul 5, 2023):

Circling back to this one. We're going to mark this as a /dup of #15591 because the other one has more specific debugging notes in it (and a better title :P)

@carlos-zamora commented on GitHub (Jul 5, 2023): Circling back to this one. We're going to mark this as a /dup of #15591 because the other one has more specific debugging notes in it (and a better title :P)
claunia commented 2026-01-31 04:53:05 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Jul 5, 2023):

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!

@microsoft-github-policy-service[bot] commented on GitHub (Jul 5, 2023): 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!
claunia commented 2026-01-31 04:53:05 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 6, 2023):

Left a note on the other issue about why I think these are different.

@DHowett commented on GitHub (Jul 6, 2023): Left a note on the other issue about why I think these are different.
claunia commented 2026-01-31 04:53:05 +00:00
Author
Owner
Copy Link

@levicki commented on GitHub (Jul 6, 2023):

@zadjii-msft @carlos-zamora I concurr with @DHowett — these two issues don't seem to be related at all.

@levicki commented on GitHub (Jul 6, 2023): @zadjii-msft @carlos-zamora I concurr with @DHowett &mdash; these two issues don't seem to be related at all.
claunia commented 2026-01-31 04:53:06 +00:00
Author
Owner
Copy Link

@levicki commented on GitHub (Jul 6, 2023):

A couple of questions to narrow this input issue down:

  1. Do people encountering this issue use keyboards that have their own drivers (i.e. keyboards or mice with added functionality such as macro recording, faster polling rate, etc)?
  2. When you RDP into your PC and this double character input starts, does it still continue if you disconnect your RDP session (do not sign out, just click x on the connection bar), login on the PC directly, and use physical keyboard to type? Testing this would require physical presence and another device on the same network.
  3. When you RDP into your PC and this double character input starts, does it still continue if you type into Windows Terminal using on-screen keyboard instead of RDP or physical keyboard?
  4. Do you have any software on your PC which might have installed keyboard and/or mouse filter drivers?
  5. Do you have clipboard history enabled in Windows? How about clipboard cloud syncing?
@levicki commented on GitHub (Jul 6, 2023): A couple of questions to narrow this input issue down: 1. Do people encountering this issue use keyboards that have their own drivers (i.e. keyboards or mice with added functionality such as macro recording, faster polling rate, etc)? 2. When you RDP into your PC and this double character input starts, does it still continue if you disconnect your RDP session (do not sign out, just click x on the connection bar), login on the PC directly, and use physical keyboard to type? Testing this would require physical presence and another device on the same network. 3. When you RDP into your PC and this double character input starts, does it still continue if you type into Windows Terminal using on-screen keyboard instead of RDP or physical keyboard? 4. Do you have any software on your PC which might have installed keyboard and/or mouse filter drivers? 5. Do you have clipboard history enabled in Windows? How about clipboard cloud syncing?
claunia commented 2026-01-31 04:53:06 +00:00
Author
Owner
Copy Link

@Kufat commented on GitHub (Jul 6, 2023):

@levicki

  1. No, boring keyboard and mouse. The keyboard uses a PS/2 to USB adapter, the mouse is just a mouse. I do have a USB KVM, but it doesn't require any drivers. That said, it does disconnect the devices when it toggles.
  2. Yes, it continues. (I'm able to provide this info as an unexpected benefit of having occasional 15-ish second connectivity drops between work and home.)
    2a. If I open a new Terminal tab (whether over RDP or when I'm in front of the machine) the new tab will be OK and the existing tabs will still exhibit the issue.
  3. (Haven't tried. Will do so next time the issue occurs.)
  4. I haven't done a clean installation of Windows on this machine since 2009, so this seems like a promising avenue of investigation. Is there a way to enumerate all keyboard filter drivers on the system? I'm not finding useful results on Google for keyboard filter drivers in general, only specific keyboard filter drivers.
  5. Yes to history, no to sync. I don't think I've ever actually used clipboard history, but it's enabled and presumably has been for a while.
@Kufat commented on GitHub (Jul 6, 2023): @levicki 1. No, boring keyboard and mouse. The keyboard uses a PS/2 to USB adapter, the mouse is just a mouse. I do have a USB KVM, but it doesn't require any drivers. That said, it *does* disconnect the devices when it toggles. 2. Yes, it continues. (I'm able to provide this info as an unexpected benefit of having occasional 15-ish second connectivity drops between work and home.) 2a. If I open a new Terminal tab (whether over RDP or when I'm in front of the machine) the new tab will be OK and the existing tabs will still exhibit the issue. 3. (Haven't tried. Will do so next time the issue occurs.) 4. I haven't done a clean installation of Windows on this machine since 2009, so this seems like a promising avenue of investigation. Is there a way to enumerate all keyboard filter drivers on the system? I'm not finding useful results on Google for keyboard filter drivers in general, only specific keyboard filter drivers. 5. Yes to history, no to sync. I don't think I've ever actually *used* clipboard history, but it's enabled and presumably has been for a while.
claunia commented 2026-01-31 04:53:06 +00:00
Author
Owner
Copy Link

@levicki commented on GitHub (Jul 6, 2023):

@Kufat I'd like to make sure you understood my question 2 above -- what I meant is to remote into the PC while you physically next to it (i.e. from another PC, laptop, tablet, or even a phone), reproduce the problem, then disconnect RDP session and walk up to the PC to test what happens when you login and type into affected wt tab using physical keyboard.

Regarding keyboard filters the only thing that comes to mind is this or searching the registry for keywords UpperFilters (not sure if keyboards also have LowerFilters) and finding entries related to keyboards:

image

On the other hand, something worth testing would be connecting another keyboard (simple cheap USB one), and connecting keyboard directly without KVM.

Finally, 2009 was a long time ago and I heard (aside from a hardware fault) there isn't any problem that can't be solved by reinstalling Windows.

@levicki commented on GitHub (Jul 6, 2023): @Kufat I'd like to make sure you understood my question 2 above -- what I meant is to remote into the PC while you physically next to it (i.e. from another PC, laptop, tablet, or even a phone), reproduce the problem, then disconnect RDP session and walk up to the PC to test what happens when you login and type into affected wt tab using physical keyboard. Regarding keyboard filters the only thing that comes to mind is this or searching the registry for keywords `UpperFilters` (not sure if keyboards also have `LowerFilters`) and finding entries related to keyboards: ![image](https://github.com/microsoft/terminal/assets/16415478/f1a2663a-f166-48f8-a31a-855dedd0d106) On the other hand, something worth testing would be connecting another keyboard (simple cheap USB one), and connecting keyboard directly without KVM. Finally, 2009 was a long time ago and I heard (aside from a hardware fault) there isn't any problem that can't be solved by reinstalling Windows.
claunia commented 2026-01-31 04:53:06 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Jul 6, 2023):

@DHowett @zadjii-msft BTW, relatedly, I noticed today that we don't handle CONSOLE_IGNORE_NEXT_KEYUP in ConPTY/WT (just search it in the project if you're curious - it's only 4 matches). Edit: Opened #15662

@lhecker commented on GitHub (Jul 6, 2023): @DHowett @zadjii-msft BTW, relatedly, I noticed today that we don't handle `CONSOLE_IGNORE_NEXT_KEYUP` in ConPTY/WT (just search it in the project if you're curious - it's only 4 matches). Edit: Opened #15662
claunia commented 2026-01-31 04:53:06 +00:00
Author
Owner
Copy Link

@sagittarius89 commented on GitHub (Jul 12, 2023):

I can reproduce an issue each time my computer wake up after sleep. It disappears when I open a new tab.

Version: 1.17.11461.0

@sagittarius89 commented on GitHub (Jul 12, 2023): I can reproduce an issue each time my computer wake up after sleep. It disappears when I open a new tab. Version: 1.17.11461.0
claunia commented 2026-01-31 04:53:07 +00:00
Author
Owner
Copy Link

@veloutin commented on GitHub (Sep 5, 2023):

I've never had this issue until today, but now all I have to do is change users and it happens on any open console.
Version: 1.17.11461.0

@veloutin commented on GitHub (Sep 5, 2023): I've never had this issue until today, but now all I have to do is change users and it happens on any open console. Version: 1.17.11461.0
claunia commented 2026-01-31 04:53:07 +00:00
Author
Owner
Copy Link

@nonkelhans commented on GitHub (May 29, 2024):

I had this doing my first session on Azure Cloud Shell. Nice going Microsoft! I really like your product. Very impressive

@nonkelhans commented on GitHub (May 29, 2024): I had this doing my first session on Azure Cloud Shell. Nice going Microsoft! I really like your product. Very impressive
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 Issue-Bug Needs-Repro Product-Terminal
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#15941
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?