I'm sorry, but I don't have in-depth knowledge about the Win7 on screen keyboard under Win10. However, I may have some suggestions for you.
Before we start, I'm sure you have done this, but I'll mention the obvious thing. You have looked in the start tab in task manager, right?
The main suggestion is several paragraphs down. First we'll cover the "quick fix" approaches and their problems.
I might just be possible to permanently disable that executable. This approach has its dangers. One method might be to delete or rename that executable. Rename is the safer of those two. You could prefix the file name with "_HIDE_" and put a text file in your personal files that reminds you of the dir it is in. Then, you could always bring it back if needed. With either the delete or rename methods the executable might possibly come back on its own via Win Update or system restore, etc. Unlikely, but possible.
Another way to permanently disable that executable is to remove all permissions on the file - that means ALL permissions for ALL users, including system/yourself/etc. I have seen this approach work once or twice in nasty situations. With all permissions removed that file is going to be VERY hard pressed to "make a comeback," but I guess anything is possible. It is still there but not even the system can read / write / execute that file. I haven't tried that in Win10, but it used to work in Win7.
To find that executable run task manager while the on-screen keyboard is running. Sort the processes by name. Right click on that process. In there I believe that you'll be able to find the EXE name and directory, or maybe there's an "open that dir" option ... you get the idea. You may also be able to get the EXE name/dir from the start menu.
Because we're talking about the keyboard here it might not be a bad idea to clone your HDD to another HDD before you do the rename above. I don't see how it could happen, but if access to your REAL keyboard somehow got screwed up by the rename that would be nasty. It won't happen. The belt + suspenders approach is to clone the HDD. If you have a WD HDD there is a free version of Acronis for you. To clone you really need access to a desktop system because laptops typically have just one SATA connector. System restore might also work. Make a named restore point before you do anything.
Another possible "revert method" would be to boot from a Boot CD (assuming your BIOS allows that / you should be able to enable boot from CD/DVD) and do the rename from the OS of that Boot CD.
---
---
OK. HERE'S THE BEST/MAIN SUGGESTION IN MY POST and it is a drastic one that involves lots of work.
Reinstall Win10 from scratch. You already have a "digital entitlement" "on file with the M$ servers." That was put in place when the upgrade happened. They calculated a number/string/etc. based on your mobo/BIOS/etc. that identifies your machine and that info is permanently in the possession of M$. You can clean install Win10 and your machine will be recognized and the OS will auto-activate. I've seen that happen multiple times. Of course you want to do the install on a different HDD than you use for Win7 ... just in case ... but it will work. It is not only "just in case" because you want that HDD to be around so you can bring your personal files onto the new system.
What you are experiencing is a classic example of why clean installs are better than upgrade installs. Things are now screwed up in your OS as a result of the fact that an upgrade install was done (through no fault of you own). With a clean Win10 install you will have a well working, but empty machine. Then you do tons of work to reinstall all your applications/etc. For my money that's the way to go. It's not the "quick fix engineering" approach of the rename/etc. above, but it is the right way to go ... barring that someone knowledgeable about on-screen keyboard shows up in this thread and tells you how to fix the original problem.
The choices are yours to make.
Facebook
Twitter