Komplete Kontrol M32 MIDI Failure and Persistent Scan Loop on M1 MacBook Air

0 views
Skip to first unread message

Barry Toner

unread,
Mar 25, 2026, 10:54:48 PM (21 hours ago) Mar 25
to logic-acc...@googlegroups.com

I am seeking advice on a persistent setup failure with Komplete Kontrol and a Komplete Kontrol M32 keyboard on an M1 MacBook Air. Despite multiple troubleshooting steps, the system is in a deadlock.

System Specifications

  • Hardware: MacBook Air M1.

  • Keyboard: Komplete Kontrol M32.

  • Current Firmware: 0.3.4.

  • Target Firmware: 0.4.5.

  • Software: Komplete Kontrol (Fresh Install).

  • Library Location: Samsung T7 External SSD.

The Primary Issues

1. Persistent "Scan in Progress" Loop

The NI Accessibility Helper is stuck announcing "Scan in progress" indefinitely. I have already deleted the db3.cacheand komplete.db3 files and restarted the NTKDaemon. While I can browse instruments and hear audio previews through the MacBook speakers, the "Scanning" status never clears.

2. Silent Musical Keys (MIDI Failure)

Although the 4D Encoder (the wheel) successfully browses the library and triggers audio previews, the musical keys on the M32 produce no sound. I suspect this is due to the outdated 0.3.4 firmware, which is known for MIDI dropouts on Apple Silicon.

3. Unresponsive Firmware Updater

The KKMUpdater correctly identifies the keyboard and the current firmware version. However, the Update button is completely unresponsive. I have attempted:

  • Closing all browsers and background NI agents.

  • Using VO Cursor and VOCR to route the mouse.

  • Using VO + Shift + Space for a hardware-level click.

  • Standard mouse clicks via the trackpad.

Steps Already Taken

  • Full Disk Access: Granted to Komplete Kontrol, Native Access, and NTKDaemon.

  • Terminal: Used killall on NIHostIntegrationAgent and NIAccessibilityHelper to reset the hardware bridge.

  • Database: Performed a clean wipe of the App Support database folders.

  • Power: Conducted a full system shutdown and cold boot.

If anyone has successfully forced the 0.4.5 firmware update on an M1 machine when the UI buttons are unresponsive, or if there is a known fix for the MIDI input being ignored while the browser remains functional, please let me know.

Cheers,

Barry.

Reply all
Reply to author
Forward
0 new messages