Same scenario here.
Win11 Search and other apps typing issue
I have an issue where today (Jan 16,2024) in the taskbar search bar it either double types every character or doesn't at all. This is not just isolated to the search bar, when attempting to utilize any MS Win app feature that requires typing of any sort such as logging in to manage email accounts, Task Manager, Add or Remove Programs, etc. It all behaves the same way. I have tried many different options to include restarts, restarting the SearchBar, restarting Explorer, Uninstalling and Reinstalling my Keyboard and Mouse, changed the repeating character speed, etc. This doesn't happen in any other program which is evident in this question submission. I should add it also doesn't happen in MS Office software, or even when I go to Control Panel and test the repeating character text box. It's very odd that it specifically is happening to only certain features of which I use often. I'm not sure what else to try. I'd rather not have to clean wipe/clean install my OS to fix this issue.
Edition Windows 11 Pro
Version 21H2
Installed on 6/24/2022
OS build 22000.2538
Experience Windows Feature Experience Pack 1000.22001.1000.0
Windows for home | Windows 11 | Input and language
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
57 answers
Sort by: Newest
-
Anonymous
2024-03-20T07:48:10+00:00 -
Anonymous
2024-03-18T16:07:08+00:00 My thoughts and situation exactly.
-
Anonymous
2024-03-07T23:48:10+00:00 I have a Dell Precision 5560, Windows 11, it won't install the latest update even if I run the Windows11InstallationAssistant. it's afecting typing in the search and WhatsApp As well, so I think it's a bug with that type of search feild element.
-
Anonymous
2024-03-07T15:27:39+00:00 i have the 22h2 and problem is still doing same on my OEM Win 11 pro dell precision pc - actually on 2 here at my office
-
Anonymous
2024-03-04T10:25:01+00:00 I have the same issue, just started after updates, Microsoft needs to fix this in code.