SOLVED: Komplete Kontrol 3.3.0 caused connection issues with Kontrol A, M and SMK2 series keyboards.

Jeremy_NI

What went wrong:

• Komplete Kontrol 3.3.0 shipped on 2024-08-01.
• Komplete Kontrol 3.3.0 broke connection for some A, M and S MK2 keyboards (MK3 was unaffected).

Why it went wrong:

• In certain circumstances, Komplete Kontrol 3.3.0 was inadvertently ignoring NIHardwareAgent, a service used by A/M/SMK2 keyboards.
• This service handles Komplete Kontrol's NKS integration for those keyboards, thus causing a failure to connect for affected users.

Severity and Symptoms:

• The A/M/SMK2 keyboards for affected users would still have functioned as generic MIDI and DAW Controllers, but experienced a failure to connect to Komplete Kontrol 3.3.

Please accept my sincere apologies for the incident.

Komplete Kontrol 3.3 was in beta for weeks, and passed all of our own internal tests as well –both manual and automatic. The variable that had to exist for the above incident to be true didn't surface until we released en masse to a much larger audience.

Solution:

We deployed Komplete Kontrol 3.2.1 rollback installers via the Community Forum overnight, solving the issue for any user who we were able to reach and had prepared an email to send to all users today, had the issue not been properly solved.

The good news is… Komplete Kontrol 3.3.1 contains a fix, has been deployed worldwide and should appear in your Native Access 2 accounts already, or within minutes.

Matthew_NI

@Jeremy_NI

Thanks for creating this post! I have updated it with a full report, and we can confirm the issue as resolved for all users.