microsoft / microsoft/microsoft-ui-xaml

Regression in 10.0.22621 Build 22621- setting ControllerToVKMapping/Enabled to 0 no longer has an effect

Open
#10,035 1 comment 0 reactions 0 assignees View on GitHub
area-External needs-triage
Dominant language
C++
Stars
8.4k
Forks
942
Avg merge
2d 7h
Merged PRs (30d)
105

Description

as of 10.0.22621 Build 22621, this solution no longer has any effect:

Good news! This fix made it into the next build which will be flighted on the dev channel of the Windows Insiders program.

Here is the new reg key you will need to create:

HKLM\Software\Microsoft\Input\Settings\ControllerProcessor\ControllerToVKMapping

Then add a DWORD value named `Enabled` set to `0`.

Note that if you remove the `Enabled` value or the `ControllerToVKMapping` key, the system will default to enabling the controller-to-virtual-key mapping for UWPs.

After setting this key you should not need to do anything else and the input system should automatically see the new reg key and disable the feature. If it doesn't work right away, double-check the spelling and restart your computer. If you are still having issues, feel free to reply to this thread and I'll see if I can help out.

_Originally posted by @jlnordin in https://github.com/microsoft/microsoft-ui-xaml/issues/1495#issuecomment-745586048_

Contributor guide

Open the contributing guide

Research direction

No repository file, test, or entry point is identified in the issue. Start by reviewing the referenced issue 1495 and reproducing the behavior on Windows 10.0.22621 with the documented registry setting; done would require a confirmed fix or a clearly documented resolution for the regression.

Written by the indexing model from the issue text.

Assessment

Domain
desktop, operating-systems
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.