Can't type on Windows Terminal #14622

Closed
opened 2026-01-31 04:15:13 +00:00 by claunia · 3 comments
Owner

Originally created by @brunnolira on GitHub (Jul 20, 2021).

When I open the Terminal the cursor is blinking but keyboard input does not work.

Already tried the thread https://github.com/microsoft/terminal/issues/4448 and it did not worked for me.
Service "Touch Keyboard and Handwriting Service" is not disabled and I don't have MSI Afterburner installed.

Windows Terminal Version - 1.8.1444.0
Windows Version - Windows 10 Pro - 21H1 - 19043.1110

Originally created by @brunnolira on GitHub (Jul 20, 2021). When I open the Terminal the cursor is blinking but keyboard input does not work. Already tried the thread https://github.com/microsoft/terminal/issues/4448 and it did not worked for me. Service "Touch Keyboard and Handwriting Service" is not disabled and I don't have MSI Afterburner installed. Windows Terminal Version - 1.8.1444.0 Windows Version - Windows 10 Pro - 21H1 - 19043.1110
claunia added the Needs-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-31 04:15:14 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Jul 20, 2021):

There's a bunch of help from @‍ebadger in #9890 - could you try following the steps in that thread, and see if that resolves the issue?

(sorry for the runaround, we really need to turn that thread into a guide on the troubleshooting page of the docs)

(see also #10095)

@zadjii-msft commented on GitHub (Jul 20, 2021): There's a bunch of help from **@‍ebadger** in #9890 - could you try following the steps in that thread, and see if that resolves the issue? (sorry for the runaround, we really need to turn that thread into a guide on the troubleshooting page of the docs) (see also #10095)
Author
Owner

@brunnolira commented on GitHub (Jul 22, 2021):

Thanks a lot @zadjii-msft, both threads help me.

I had the same situation as #9890, just killing the process returned by the command "tasklist /m msctfmonitor.dll" and starting "ctfmon.exe" made the Terminal work again.

Shame that I have to do this every time I restart the PC, and that I wasn't able to find this tread before asking for help, maybe because of it's title.

But anyway, thanks again.

@brunnolira commented on GitHub (Jul 22, 2021): Thanks a lot @zadjii-msft, both threads help me. I had the same situation as #9890, just killing the process returned by the command "tasklist /m msctfmonitor.dll" and starting "ctfmon.exe" made the Terminal work again. Shame that I have to do this every time I restart the PC, and that I wasn't able to find this tread before asking for help, maybe because of it's title. But anyway, thanks again.
Author
Owner

@brunnolira commented on GitHub (Jul 22, 2021):

Made this powershell script to help.

# Stop process taskhostw.exe
if((Get-Process -Module msctfmonitor.dll -ea SilentlyContinue) -ne $Null){ 
    Stop-Process -ErrorAction SilentlyContinue
}

# Start process ctfmon.exe
if((Get-Process ctfmon -ea SilentlyContinue) -eq $Null){ 
    ctfmon.exe
}

# Start Windows Terminal
wt
@brunnolira commented on GitHub (Jul 22, 2021): Made this powershell script to help. ```powershell # Stop process taskhostw.exe if((Get-Process -Module msctfmonitor.dll -ea SilentlyContinue) -ne $Null){ Stop-Process -ErrorAction SilentlyContinue } # Start process ctfmon.exe if((Get-Process ctfmon -ea SilentlyContinue) -eq $Null){ ctfmon.exe } # Start Windows Terminal wt ```
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#14622