Bug Description
On Windows, shortcut recording in Settings → Shortcuts never registers any key press. When clicking the pencil icon to edit a shortcut (e.g. "Push to Talk"), the field enters "Press a key..." recording mode, but pressing any key — including plain letter keys like A, and modifier keys like Ctrl — is never captured or displayed in the input field.
The amical.log file shows that WindowsHelper.exe is correctly detecting physical key presses and sending them to the Electron main process, but the native-bridge logs them as an unknown message type and appears to discard them instead of forwarding them to the shortcut recorder UI:
[warn] [(native-bridge)] Received unknown message from helper {
message: {
payload: {
altKey: false,
ctrlKey: true,
fnKeyPressed: false,
keyCode: 162,
metaKey: false,
shiftKey: false
},
timestamp: '2026-07-15T13:01:11.0087361+00:00',
type: 'keyDown'
}
}
The same warning appears for type: 'keyUp' and type: 'activeDisplayChanged' messages as well — every message coming from the native helper is logged as "unknown message from helper".
Steps to Reproduce
- On Windows, open Amical → Settings → Shortcuts
- Click the pencil icon next to any shortcut (e.g. "Push to Talk") to enter recording mode
- Press any key (tested: plain letter keys like
A, and Ctrl)
- Observe that nothing is registered in the shortcut input field, and the shortcut cannot be changed
Expected Behavior
Pressing a key while in shortcut-recording mode should display the key combination in the input field and allow saving the new shortcut.
Actual Behavior
No key press is ever registered, even though WindowsHelper.exe is confirmed running (visible in Task Manager) and is confirmed — via the log file — to be correctly detecting and forwarding keyDown/keyUp events to the main process. The main process logs every one of these messages as [warn] Received unknown message from helper and does not appear to act on them.
Environment
- OS: Windows 11 Home 10.0.26200
- Amical version: reproduced on both v1.10.0 and v1.11.0 (fresh clean install of v1.11.0 via the direct Windows installer — same behavior)
- Antivirus: Trend Micro Virus Buster Cloud (ruled out — temporarily disabling "unauthorized change monitoring" / behavior monitoring made no difference)
Troubleshooting already performed (no change in behavior)
- Restarted Amical fully (quit from tray, not just closing the window)
- Ran Amical as Administrator
- Restarted the Windows "Human Interface Device Service"
- Confirmed OS-level global shortcuts (e.g.
Win+Shift+S) work normally, ruling out a keyboard/OS-level issue
- Confirmed no keyboard remapping/injection software installed (no PowerToys, AutoHotkey, Logi Options, Razer Synapse, etc. present in Startup Apps)
- Temporarily disabled Trend Micro behavior monitoring ("不正変更の監視")
- Enabled "Allow injected keystrokes" toggle in Shortcuts settings (already on by default)
- Fully uninstalled and reinstalled the app (still on v1.10.0 at the time) — no change
- Upgraded to the newly published v1.11.0 pre-release (which includes
win-helper fixes) via direct installer download — no change; same "unknown message from helper" warning still appears in the log
WindowsHelper.exe is confirmed present and running in Task Manager throughout all tests.
Bug Description
On Windows, shortcut recording in Settings → Shortcuts never registers any key press. When clicking the pencil icon to edit a shortcut (e.g. "Push to Talk"), the field enters "Press a key..." recording mode, but pressing any key — including plain letter keys like
A, and modifier keys likeCtrl— is never captured or displayed in the input field.The
amical.logfile shows thatWindowsHelper.exeis correctly detecting physical key presses and sending them to the Electron main process, but the native-bridge logs them as an unknown message type and appears to discard them instead of forwarding them to the shortcut recorder UI:The same warning appears for
type: 'keyUp'andtype: 'activeDisplayChanged'messages as well — every message coming from the native helper is logged as "unknown message from helper".Steps to Reproduce
A, andCtrl)Expected Behavior
Pressing a key while in shortcut-recording mode should display the key combination in the input field and allow saving the new shortcut.
Actual Behavior
No key press is ever registered, even though
WindowsHelper.exeis confirmed running (visible in Task Manager) and is confirmed — via the log file — to be correctly detecting and forwardingkeyDown/keyUpevents to the main process. The main process logs every one of these messages as[warn] Received unknown message from helperand does not appear to act on them.Environment
Troubleshooting already performed (no change in behavior)
Win+Shift+S) work normally, ruling out a keyboard/OS-level issuewin-helperfixes) via direct installer download — no change; same "unknown message from helper" warning still appears in the logWindowsHelper.exeis confirmed present and running in Task Manager throughout all tests.