Bonus: Remote desktop may have worked as I have seen strange things happen with some of my laptop keys that are remapped locally but behave differently when they go into a remote window. Same thing applies to the touch screen keyboard, if you have it enabled/available. Lastly, if this wasn't working with the onscreen keyboard, I have no idea what has happened: for years, I've used the On-Screen Keyboard and just confirmed that it's oblivious of the Windows remappng since it blissfully just turned-on caps lock, which is disabled on the physical keyboard.Not a thing can be done for that, as it's organizational specific. Or your company has some sort of add on masking that DreymaR has mentioned above, like a group policy or something. Again, the remapping entry is exclusive to HKLM which by its very nature should be visible to all users but requires admin rights to do so. Running SharpKeys from another account on the box would work, if the account has Administrator permissions.It's like saying that Windows spontaneously decided on its own to hold onto the remapping without instructions: either the key was restored by some process on the power down or the box was suspended, rather than rebooted. It must work because once Windows reboots, it has no instructions about how to remap keys. Removing the Scancode Map value or the entire Keyboard Layout Key in the Registry and rebooting will work.The only Registry Key that does the remapping lives under HKEY_LOCAL_MACHINE putting it under HKEY_CURRENT_USER does nothing. There is no "per user" setting that's available for mapping keys.I don't see that there is anything to look for in this.
0 Comments
Leave a Reply. |