Keyboard input does not work on 10.0.22581.0+ / 22H2 #17066

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

Sorry to hear about this! We've actually got an internal mail thread discussing something similar right now. Lemme bump that thread and see if I can't get someone on the input team to point you in the direction of some traces to take.

@ebadger here's a external report of that issue we've got the internal thread on.

@zadjii-msft commented on GitHub (Mar 24, 2022): Sorry to hear about this! We've actually got an internal mail thread discussing something similar right now. Lemme bump that thread and see if I can't get someone on the input team to point you in the direction of some traces to take. @ebadger here's a external report of that issue we've got the internal thread on.

claunia commented

@BobbyWibowo commented on GitHub (Mar 26, 2022):

Can confirm the same thing happens to me on the same Windows Terminal build and Windows build (received the big update via Windows Update earlier this afternoon).

UPDATE: Still happens with Windows Terminal build 1.12.10732.0.

@BobbyWibowo commented on GitHub (Mar 26, 2022): Can confirm the same thing happens to me on the same Windows Terminal build and Windows build (received the big update via Windows Update earlier this afternoon). --- **UPDATE:** Still happens with Windows Terminal build 1.12.10732.0.

claunia commented

@asgeirn commented on GitHub (Mar 26, 2022):

Issue seems to have been resolved with release 1.13.10734.0

@asgeirn commented on GitHub (Mar 26, 2022): Issue seems to have been resolved with release 1.13.10734.0

claunia commented

@bwets commented on GitHub (Mar 27, 2022):

tried installing 1.13.10734.0, issue still here on 22581.100

Edit: Also have similar issue while typing in Windows Store search bar

@bwets commented on GitHub (Mar 27, 2022): tried installing 1.13.10734.0, issue still here on 22581.100 Edit: Also have similar issue while typing in Windows Store search bar

claunia commented

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

The issue seems to go away after some time. I'm still at Terminal build 1.12.10732.0 (updated yesterday), but I'm no longer having the issue, despite being absolutely positive I still had the issue previously even after updating to said Terminal build.

However I cannot even begin to understand how or why it fixes itself.

@BobbyWibowo commented on GitHub (Mar 28, 2022): The issue seems to go away after some time. I'm still at Terminal build 1.12.10732.0 (updated yesterday), but I'm no longer having the issue, despite being absolutely positive I still had the issue previously even after updating to said Terminal build. However I cannot even begin to understand how or why it fixes itself.

claunia commented

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

note to self: MSFT:38495673

We're still trying to track down a root cause. Issue does seem intermittent, and seems to go away with a reboot, if you are affected by this.

@zadjii-msft commented on GitHub (Mar 28, 2022): note to self: MSFT:38495673 We're still trying to track down a root cause. Issue does seem intermittent, and seems to go away with a reboot, if you are affected by this.

claunia commented

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

There are 4 additional reports in #12772. Collected notes:

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

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).

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.

I see the same window freeze even when I 'run as admin'.

I get the freeze running as admin as well. Mine started on build 22581.100

I just installed Terminal 1.10.2714 from the github release (v1.10.2714.0 (release)) and can confirm that the same freeze happens there. On Windows 11 build 22581.

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.

@zadjii-msft commented on GitHub (Mar 29, 2022): There are 4 additional reports in #12772. Collected notes: > This issue only affects one tab at a time. > The particular character is different every time. > 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). > 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. > I see the same window freeze even when I 'run as admin'. > I get the freeze running as admin as well. Mine started on build 22581.100 > I just installed Terminal 1.10.2714 from the github release ([`v1.10.2714.0` (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. > 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

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

Build 22581.200 (KB5013296) seems to have fixed it

@justinledwards commented on GitHub (Mar 29, 2022): Build 22581.200 (KB5013296) seems to have fixed it

claunia commented

2026-01-31 05:31:23 +00:00

@agentmerlot1412 commented on GitHub (Apr 4, 2022):

I'm facing the same issue on Terminal and Terminal Preview, but as a side note, it seems like this issue pops up in WSA applications and Microsoft Store too, although the severity of the issue in Store is much lower than that of Terminal and WSA.

@agentmerlot1412 commented on GitHub (Apr 4, 2022): I'm facing the same issue on Terminal and Terminal Preview, but as a side note, it seems like this issue pops up in WSA applications and Microsoft Store too, although the severity of the issue in Store is much lower than that of Terminal and WSA.

claunia commented

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

Hey everybody - I believe there's a new flight that's out for Insiders, and the Input team has a sneaking suspicion that this may have been fixed in that build. Is anyone seeing this on 22593?

@zadjii-msft commented on GitHub (Apr 11, 2022): Hey everybody - I believe there's a new flight that's out for Insiders, and the Input team has a sneaking suspicion that this may have been fixed in that build. Is anyone seeing this on **[22593](https://blogs.windows.com/windows-insider/2022/04/06/announcing-windows-11-insider-preview-build-22593/)**?

claunia commented

2026-01-31 05:31:23 +00:00

@BobbyWibowo commented on GitHub (Apr 12, 2022):

I personally haven't encountered this issue ever again since this reply from 15 days ago
Since then, I have updated Terminal to build 1.12.10733.0, and also updated Windows to Insiders build 22593.1 about 3 days ago
Still haven't encountered the issue again

@BobbyWibowo commented on GitHub (Apr 12, 2022): I personally haven't encountered this issue ever again since [this reply](#issuecomment-1080038675) from 15 days ago Since then, I have updated Terminal to build 1.12.10733.0, and also updated Windows to Insiders build 22593.1 about 3 days ago Still haven't encountered the issue again

claunia commented

2026-01-31 05:31:23 +00:00

@asgeirn commented on GitHub (Apr 12, 2022):

I no longer have this issue, currently on 22593.1 and Terminal versjon 1.13.10984.0

@asgeirn commented on GitHub (Apr 12, 2022): I no longer have this issue, currently on 22593.1 and Terminal versjon 1.13.10984.0

claunia commented

@agentmerlot1412 commented on GitHub (Apr 12, 2022):

Same

@agentmerlot1412 commented on GitHub (Apr 12, 2022): Same

claunia commented

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

Awesome, I'm glad to hear it! Since this seems resolved, I'm gonna close this one out. Thanks everybody!

@zadjii-msft commented on GitHub (Apr 12, 2022): Awesome, I'm glad to hear it! Since this seems resolved, I'm gonna close this one out. Thanks everybody!

claunia commented

@jcwhitney commented on GitHub (May 9, 2022):

still a problem on 22616.1 with feature pack 1000.22632.1000.0
cortana and Settings search not seeing any keyboard input.
Chrome / notepad etc all work

@jcwhitney commented on GitHub (May 9, 2022): still a problem on 22616.1 with feature pack 1000.22632.1000.0 cortana and Settings search not seeing any keyboard input. Chrome / notepad etc all work

claunia commented