Keyboard on Windows 10 Pro doesn't work with Windows applications (Parallels 12)

Keyboard on Windows 10 Pro doesn't work with Windows native applications.
- My Apple keyboard is American.
- I am using Parallels 12.
- I am using US-International keyboard on Windows 10 Pro.
- Other no windows applications everything ok.
- Windows is updated.
- I have installed Windows 10 pro from "zero"
I need help ! Please !

 

I wish I could help. I have exactly the same problem with Win10 on Parallels 13 Pro. Keyboard works within non-Windows apps but nothing happens if I use it in the box where it says "Type here to search" or in the enter web address bar in MS Edge. Works within the apps I use but it is really strange behavior I wish I could eliminate. HELP!!!

 

Parallels 13 here and have the same problem. Keyboard works fine inside of apps, but won't work in Windows (like the search or file explorer for example). This is something that started happening after Windows 10 was installed (I've used Parallels since about version 3!) Tried the Settings->Access in the KB articles, I've rebooted, reinstalled the toolbox, fiddled with mouse and keyboard settings. Nothing changes behavior ... keyboard works fine TO LOG IN (type password) and after that only within Apps (not for anything directly to do with Windows ... even the Edge browser search bar has stopped working (that used to work at least).

If you go to the Win10 control panel for the keyboard, I can type in the key repeat test box and everything works. It thinks everything is OK. Drivers are OK. It just doesn't work for the Windows OS specific stuff. Obviously keyboard is there and works INSIDE other apps. Strange and frustrating.

 

Parallels Team should be to fix this... Maybe a problem in Parallels Desktop Home...

 

Hi PauloC1, MichaelS39 and KenM1. Kindly be informed that this is a known issue with Windows 10 and happens on real Windows PC's as well. As a workaround (results not guaranteed), navigate to C:\Windows\System32 and locate the application 'ctfmon'. Next, press CMD+R in Windows to launch the Run window, type 'shell:startup' (without the quotes) in the text field, hit 'Enter' (which opens a new window), drag and drop the 'ctfmon' application from the other window into the new window, launch it (no application window will open and nothing will seem to happen because, after being launched, the application will simply run hidden in the background) and restart Windows.

 

OK, after a bit of a struggle (and surprisingly CMD R was recognized in Windows! Figured it wouldn't allow the keyboard to work ... but it did!) ... I got ctfmon.exe copied into the Startup ... launched it ... Viola! Keyboard seems to work in all modes now ... (I had to do "Run as administrator" to get it to launch correctly, but that got it going)

Feeling lucky, I rebooted Windows ... sure enough, the startup hack did the trick and it all seems to work. Thanks for the work around!

 

Glad to know that you were able to sort out the issue. Please get back to us for any further queries.

 

The Parallels team answered me below. I'll try the procedure. Thank you Parallels!

Kindly be informed that this is a known issue with Windows 10 and happens on real Windows PC's as well. As a workaround (results not guaranteed), navigate to C:\Windows\System32 and locate the application 'ctfmon'. Next, press CMD+R in Windows to launch the Run window, type 'shell:startup' (without the quotes) in the text field, hit 'Enter' (which opens a new window), drag the 'ctfmon' application from the other window into the new window, launch it (no application window will open and nothing will seem to happen because, after being launched, the application will simply run hidden in the background) and restart Windows

 

Thank you Parallels Team! Now the keyboard is working...

 

Hi @PauloC1 , glad that your issue is resolved. Please reach us anytime for further assistance.

 

Hello community ,
i am unable to text anythings anywhere in windows . :/

do you think i can resolve the problem with any other solution ?

thanks a lot

 

Have you tried the workaround and checked?

 

I got this problem a couple of weeks after starting with P13 and W10. The suggested fix has worked for me. If it goes wrong again I will add another message.

 

Feel free to reach us anytime for support.