Smart Tool keymap config disappears after PC restart — only works on first install
After a successful first-install where the Smart Tool keymap applies and CODM controls work correctly, restarting Windows resets the keymap state. The next CODM launch shows default touch UI without the imported keymap. Reapplying via Smart Tool sometimes works, sometimes also fails. Reported framing:
"Una pregunta gente! porque no me cargan las config de teclas. Ya borre DB desde la app pero continua sin aparece... Solo me han aparecido la config cuando lo instale, luego me fui, prendi la pc nuevamente y ya no funcionaba"
Symptoms:
- Keymap works perfectly after fresh Smart Tool install + Apply Keymap.
- After Windows restart: keymap is gone — CODM uses TAC's default touch overlay.
- Restoring DB and re-applying keymap via Smart Tool sometimes works, sometimes also fails.
- Closing all TAC processes via Task Manager and reapplying with Smart Tool TWICE fixes it temporarily — but it disappears again on the next reboot.
Root cause: TAC's keymap database file requires write permissions that aren't preserved across restarts on certain Windows configurations. After a reboot, TAC starts with a fresh AppData state and the customized keymap row gets overwritten by the bundled default.
Solutions
Solution 1
Always run Smart Tool as Administrator. The keymap persistence problem reproduces only when Smart Tool runs in standard user mode — without admin rights, Smart Tool's writes to TAC's database go to a virtualized AppData copy that Windows reverts at logon:
- Right-click the Smart Tool desktop shortcut → Properties.
- Compatibility tab → check "Run this program as administrator" → OK.
- Re-launch Smart Tool. From now on it always elevates.
- Apply Keymap once.
- Restart Windows — keymap should persist.
Solution 2
Grant your user account explicit write permission on TAC's AppData folder. Some Windows configurations apply file virtualization to subfolders even when the parent is user-writable:
- Win+R →
%LOCALAPPDATA%\AOWEmulator(or wherever TAC installed). - Right-click the folder → Properties → Security tab.
- Click Edit → select your user → check Full control.
- Apply, OK.
- Reboot, retry keymap apply.
Solution 3
If OneDrive is redirecting your AppData folder, disable redirection. Microsoft 365 / OneDrive sometimes redirects "Documents" and adjacent folders to OneDrive cloud storage, which breaks TAC's local-write expectations:
- Right-click OneDrive tray icon → Settings.
- Backup tab → Manage backup → uncheck "Documents" if it's in the redirect list.
- Apply, sign out and back into Windows.
Solution 4
Recovery dance for stuck-keymap state. Per Feddee's diagnostic conversation with WhyBeKing — when the keymap silently fails to load on launch:
- Open Task Manager → kill every "tac", "gameloop", "AndrowsConnect" process.
- Open Smart Tool.
- Click Apply Keymap.
- Click Apply Keymap AGAIN immediately.
- Now click Launch CODM via Smart Tool.
Per WhyBeKing: "Reinicia gameloop, todos los procesos o con la herramienta dos veces." The double-apply trick works because the first attempt restores the database, and the second attempt actually writes the new keymap rows on top of the now-clean state.
Comments (0)
Sign in to_leave_comment