PowerToys Keyboard Manager With a Macropad

KM16 Macropad has sixteen keycaps, one large knob and two smaller knobs on anodised aluminium. Its confirmed VIA support pairs well with PowerToys Keyboard Manager because the pad can emit inputs the main keyboard rarely uses.

What does Keyboard Manager do well?

Microsoft's current Keyboard Manager can remap a key, change one shortcut into another, send text, start an application or open a URI. Shortcut mappings can target a process, while an unscoped mapping applies across Windows. Changes take effect while PowerToys runs in the background.

It is approachable for named Windows actions and application shortcuts. It is less suitable for password screens, reserved operating-system combinations or software running at a higher privilege level than PowerToys. Microsoft also notes that several system keys cannot be replaced.

Why can global remapping cause trouble?

Keyboard Manager does not currently distinguish the physical keyboard that produced a normal key event. Remapping the letter A therefore affects the built-in keyboard as well as a pad that sends A. That can orphan a key or change every shortcut containing it.

Closing PowerToys or disabling Keyboard Manager stops its remaps, which is a useful recovery route. Still, choose an uncommon source instead of relying on emergency shutdown. Microsoft documents F13 through F24 as mappable even though they are absent from many keyboards.

How do VIA remaps make PowerToys safer?

First make one pad position emit an unused function key in VIA. Verify it in a key tester or the Keyboard Manager selection dialog, then map that input to a Windows shortcut. The main keyboard remains unaffected unless it can also generate that same spare key.

Maintain a two-column record of VIA output and PowerToys action. Test with PowerToys stopped to confirm the hardware layer, then start it to check the Windows layer. Configure one position at a time and preserve the original VIA map.

How do you map a key to launch an app?

Keyboard Manager's shortcut editor offers a Start App action with executable, arguments, working directory, elevation, visibility and already-running behavior. The trigger must be a shortcut rather than a bare key for this action, so have VIA emit a deliberate uncommon combination.

Choose what happens when the app already runs, since starting a second instance is not always harmless. The KM16 Macropad has enough inputs for many launches, but begin with one non-elevated tool and a few reversible shortcuts. Avoid putting secrets in arguments or creating one-press shutdown commands. Recheck the target process and elevation behavior after application updates, because a correct trigger can still fail at the Windows boundary.