Terminal doesn't accept any keyboard input #7801

Closed
opened 2026-01-31 01:12:57 +00:00 by claunia · 4 comments
Owner

Originally created by @Kerosz on GitHub (Apr 29, 2020).

After reinstalling the windows yesterday, switched my primary drive to another one, the terminal doesn't take any keyboard input, I cannot write anything in it. I can use the mouse to select and paste things into it.

Something I have tried is to uninstall and reinstall the terminal but it has the same behaviour, JSON settings are default.
Tried PowerShell and CMD separately and they work fine.

Any idea of what could cause this?

Originally created by @Kerosz on GitHub (Apr 29, 2020). After reinstalling the windows yesterday, switched my primary drive to another one, the terminal doesn't take any keyboard input, I cannot write anything in it. I can use the mouse to select and paste things into it. Something I have tried is to uninstall and reinstall the terminal but it has the same behaviour, JSON settings are default. Tried PowerShell and CMD separately and they work fine. Any idea of what could cause this?
claunia added the Area-InputResolution-DuplicateProduct-Terminal labels 2026-01-31 01:12:57 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Apr 29, 2020):

@Kerosz What version of the Terminal are you running?

Are you using PowerToys?

By any chance is what you're seeing similar to #4448?

@zadjii-msft commented on GitHub (Apr 29, 2020): @Kerosz What version of the Terminal are you running? Are you using PowerToys? By any chance is what you're seeing similar to #4448?
Author
Owner

@Kerosz commented on GitHub (Apr 29, 2020):

Windows Terminal 0.11.1191.0
OS Build: 19041.208 on Windows PRO for Workstations

No PowerToys used as it was a clean reinstall of windows and I didn't run the setup scripts yet.

Managed to fix the issue by going back to a previous version of windows using the recovery and updating again to the latest version. It was a 20 minutes process and it actually fixed the issue.

No idea what could have caused it as in both cases I just installed the latest version of W and got the WT from the store.

@Kerosz commented on GitHub (Apr 29, 2020): Windows Terminal 0.11.1191.0 OS Build: 19041.208 on Windows PRO for Workstations No PowerToys used as it was a clean reinstall of windows and I didn't run the setup scripts yet. Managed to fix the issue by going back to a previous version of windows using the recovery and updating again to the latest version. It was a 20 minutes process and it actually fixed the issue. No idea what could have caused it as in both cases I just installed the latest version of W and got the WT from the store.
Author
Owner

@DHowett-MSFT commented on GitHub (Apr 29, 2020):

Thanks for the report! Since you've worked around it for now I'm gonna track it with /dup #4448

@DHowett-MSFT commented on GitHub (Apr 29, 2020): Thanks for the report! Since you've worked around it for now I'm gonna track it with /dup #4448
Author
Owner

@ghost commented on GitHub (Apr 29, 2020):

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 (Apr 29, 2020): 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.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#7801