Keyboard Mappings Issue with PowerToys in Cloud/Dev Boxes
Microsoft PowerToys version
v0.82.1
Installation method
Other (please specify in "Steps to Reproduce")
Running as admin
Yes
Area(s) with issue?
Keyboard Manager
Steps to reproduce
I am encountering an issue where keyboard mappings set via PowerToys on my local system do not carry over to cloud/dev boxes. When I set up the same settings on PowerToys in the cloud/dev boxes, they don't work if the local system keyboard manager settings are enabled.
Steps to Reproduce:
- Set up keyboard mappings using PowerToys on the local system.
- Connect to a cloud/dev box.
- Attempt to use the same keyboard mappings in the cloud/dev box.
Alternatively, if I set up the keyboard mappings directly on the cloud/dev box, they still don't work if the local system keyboard manager settings are enabled.
Workaround: If the keyboard manager on the local system is turned off, the mappings work correctly in the cloud boxes. This requires manually turning off the keyboard manager on the local system while using the dev box and turning it back on afterward.
Impact: This issue is a significant inconvenience and impacts the usability of dev boxes, as it requires constant toggling of the keyboard manager on the local system.
Additional Information:
- PowerToys mappings work correctly in the cloud box when the keyboard manager is disabled on the local box.
- This issue prevents seamless switching between local and cloud/dev environments.
Request: Please investigate and provide a solution that allows for consistent keyboard mappings across local and cloud/dev boxes without needing to manually toggle the keyboard manager. Ideally, I should be able to set up the keyboard mappings on my local box once and not have to configure them in both places.
✔️ Expected Behavior
The keyboard mappings should work seamlessly in the cloud/dev box as they do on the local system.
❌ Actual Behavior
The key mappings trigger functions like Sticky Keys or Start instead of the intended mappings.
Other Software
No response