ReplaceOSK icon indicating copy to clipboard operation
ReplaceOSK copied to clipboard

Doesn't work since migrated to Windows 11

Open bolinocroustibat opened this issue 3 years ago • 5 comments

Thanks for making this!

I used the script on a Windows 10 console device (OneXplayer) with a physical "display virtual keyboard" button. It worked very well.

But since I upgraded to Windows 11, it doesn't work anymore. The physical keyboard button shows the old On-Screen keyboard app instead of the new fancy W11 virtual keyboard overlay. Of course I tried to redownload the script and run it again, with no success.

Any idea on how to completely reset the W11 behaviour / registry?

bolinocroustibat avatar Dec 21 '21 10:12 bolinocroustibat

Did you run the script again twice? The first time would only uninstall everything left over from before. The second time would install the script again.

Lulech23 avatar Dec 21 '21 15:12 Lulech23

Thanks for answering. Yes I did run it several times, and tried in between.

I wonder what is the app path of the new W11 touch keyboard. Couldn't find on Google. I believe I could probably fix that in the registry, replacing the calls to osk.exe with it.

bolinocroustibat avatar Dec 22 '21 02:12 bolinocroustibat

That would be because there is no single app path for the Windows keyboard. It's a ridiculously complex black box intertwined deep within the Windows OS, which is why ReplaceOSK (or more specifically, TabTipProxy) exists.

However, the Windows 11 keyboard is fundamentally the same as the Windows 10 keyboard. All paths remained the same across versions.

I would suggest downloading the precompiled TabTipProxy.exe from this repository and run it. If it opens the keyboard successfully, then it's more likely a permissions issue with C:\Windows\System32\osk.exe. ReplaceOSK attempts to take ownership of this file automatically, but in some rare cases even that fails and you have to do the job yourself.

Lulech23 avatar Dec 22 '21 03:12 Lulech23

Thanks. I read your README but naively thought MS did simplified the whole thing with Windows 11.

Anyway I tried to run the TabTipProxy.exe from your repo, and it works. Seems to be indeed a permission issue with osk.exe. Been trying to rename it and replace it by TabTipProxy.exe from the administrator-run terminal, but keeps getting permission errors for now. Will try other ways

EDIT: successfully edited the permissions of osk.exe (god how the Windows permissions UX is prehistoric) and replaced it by the compiled TabTipProxy.exe. Works like a charm now! Thanks for your efficient help @Lulech23

bolinocroustibat avatar Dec 22 '21 04:12 bolinocroustibat

I would recommend running ReplaceOSK to install rather than replacing osk.exe manually. Windows will often detect this as a virus and may suddenly remove the executable or block it from running. ReplaceOSK uses a less invasive method that doesn't trigger virus checks.

Lulech23 avatar Dec 22 '21 04:12 Lulech23

Closing this since there have been no further comments, and compatibility with Windows 11 22H2 is confirmed.

Lulech23 avatar Oct 02 '22 18:10 Lulech23

I had the same issue when running it it fails to replace it due to lack of permissions. It complains about access denied to the path. (C:\Windows\System32\osk.exe) (Although the powershell is running as Administrator) It works if like bolino did you alter manually the permissions.

Not sure if that can be solved in the script, but if not it would be nice to add this in the readme.

mmarquezs avatar Dec 07 '22 09:12 mmarquezs

I think this issue should be reopened. Win 11 22H2 here with the same issue.

I had the same issue when running it it fails to replace it due to lack of permissions. It complains about access denied to the path. (C:\Windows\System32\osk.exe) (Although the powershell is running as Administrator) It works if like bolino did you alter manually the permissions.

Would you be so kind to explain what and how do we have to fix this? Tried adding permissions but the interface is horrible.

godoyLeonardo avatar Feb 09 '23 20:02 godoyLeonardo

I've run ReplaceOSK on many PCs running Windows 11 22H2 and can confirm everything is still working as of this date.

For cases where Windows denies automatically taking ownership of osk.exe, I've added instructions to the README. See "Known Issues" for details.

Lulech23 avatar Feb 09 '23 21:02 Lulech23