Macropad settings disappear after reconnecting
KM16 Macropad is sold as a configurable sixteen-key pad with three knobs. If yesterday's mapping disappears when you reconnect it, establish where that mapping was meant to live. A device profile, an editor shortcut and a desktop remapper rule can produce the same visible action. They do not have the same persistence requirements, so restoring one will not necessarily repair another.
Was the change saved to hardware or to the computer?
Open the utility originally used to create the mapping and review its save behaviour. Some interfaces apply supported changes to device configuration, while host remappers keep their rules on the computer. An export file on your desktop is a backup, not proof that the device is currently using its contents.
Choose one harmless key and record the intended output. Test it with the host remapper active, then with that rule paused if the utility provides a reversible pause. This helps distinguish a hardware assignment from a translation made later. Avoid factory reset or firmware replacement while you are still identifying the storage layer.
Could a different profile or layer be active?
Inspect the selected profile and any layer-switching key in the configuration. A familiar key can appear to revert because you are viewing a different layer, not because the saved data vanished. Compare the mapping shown by the tool with the event produced by the pad. Keep the diagnostic key away from any action that submits text.
If your utility identifies devices separately, check whether reconnecting changed which entry your rule targets. Do not assume every tool recognises the same device in the same way. Document the displayed identity without copying unrelated machine details into a public support request.
Did the host utility restart correctly?
A host-dependent configuration may stop applying when its background process closes. The official PowerToys reference explicitly says Keyboard Manager remaps require PowerToys to run. Relaunching the utility and seeing the mapping return is evidence of that dependency, rather than evidence of lost keypad memory.
Browser-based configuration tools introduce a separate distinction: access to the configuration interface and ordinary typing are not the same connection. If a configuration page cannot see the pad, follow its supported reconnect flow. Do not overwrite a working keymap solely because the browser session needs attention.
What should a recovery record contain?
Save the profile export where available, the utility name, the operating system and a short list of expected key outputs. Reconnect once and compare those outputs before restoring the full workflow. A successful result should be observable without launching an agent or sending a command. Consult KM16's product information for its stated setup support, then keep your own configuration backup alongside that reference.