Macropad shortcuts fail when an app runs as administrator
KM16 Macropad can trigger shortcuts through a Windows remapping utility. If a binding works in ordinary windows but fails in an application opened as administrator, the difference may be the process privilege level. That does not establish a problem with the keypad. Start by checking whether the elevated application actually needs that mode for the task you are doing.
Is the application running with different privileges?
Compare a harmless action in a normal instance of the application with the same action in the elevated instance. Use an empty file and avoid commands that modify system settings. Also test the unmodified shortcut from the main keyboard. This separates an unavailable app command from a remapping limitation.
Record how you opened the application. A pinned shortcut, launcher or terminal can change the way a process starts. If you cannot tell which privilege level it uses, inspect the application's launch settings and the operating system's process information rather than inferring it from the window's appearance alone.
What does the remapping utility support?
Microsoft states in its Keyboard Manager troubleshooting guidance that remapping will not work on an elevated window when PowerToys itself is not running as administrator. This is a documented software boundary. A shortcut profile that depends on that utility inherits the boundary, even if the pad's ordinary keys still arrive.
Do not treat this as a reason to run every desktop program with broader privileges. For a routine editing or browsing task, using a normal application instance may be the simpler answer. On a managed work computer, follow the organisation's approved process for software that genuinely requires elevation.
Could a direct application binding avoid the dependency?
If the hardware emits a supported key combination and the app can bind it directly, an application-level shortcut may remove the host-remapping step. Confirm the keypad's actual output before making this change. A text macro that types a sequence is not necessarily equivalent to a single shortcut event.
Keep the proposed binding limited to a reversible command during testing. Opening search or changing a view provides evidence without executing administrative work. If direct binding is unavailable, document the limitation rather than replacing it with a script that silently launches elevated processes.
What should you keep in the setup notes?
Record the hardware output, remapper name, target application and whether the workflow requires elevation. Retest the normal window afterward so the original shortcuts still work. This gives a colleague a clear explanation of the exception. The KM16 keypad's configuration is only one part of the route; Windows and the destination application's access model remain relevant.