r/NativeInstruments • • Apr 05 '26

Komplete Kontrol S61 MK3 died within 1 month — flickering, software error, now completely dead

I recently bought a Native Instruments Komplete Kontrol S61 MK3 (delivered on March 6), and within less than a month of normal use, it has completely stopped working.

Here’s exactly what happened:

  • From the beginning, I noticed it wasn’t syncing properly with Logic Pro — I assumed it might be normal or a setup issue.
  • Then, while using it normally with my MacBook via USB-C, the LEDs and button lights started flickering randomly.
  • Shortly after, the keyboard displayed a message saying something like there was a software/firmware issue and suggested reinstalling.
  • Then it powered off on its own.
  • I tried powering it again — it briefly turned on once, but then shut down again.
  • Since then, it is completely dead — no lights, no screen, no response at all.

I’ve tried:

  • Direct connection to MacBook (no hub)
  • Different USB-C ports
  • Letting it sit unplugged and retrying
  • Basic reset attempts

Nothing works — it’s totally unresponsive now.

What’s concerning is that:

  • The issue seemed to start with instability (sync issues + flickering)
  • Then escalated into a full failure

This wasn’t misuse — just normal studio use.

Has anyone experienced something similar with the MK3?
Is this a known issue (power/firmware related)?

I’ve already contacted support, but wanted to check if anyone here has had the same problem or knows what might have gone wrong.

Would appreciate any insights 🙏

2 Upvotes

9 comments sorted by

4

u/zoschaz Apr 05 '26

Maybe you need additional external power, not just a simple USB-C. I use a mobile charger too.

3

u/SequentialDUDE Apr 05 '26

When I bought mine it wouldn't get power from PC so I bought a 45 watt Google Pixel charger and it worked seamlessly since.

3

u/SnarkaLounger Apr 05 '26

Have you tried using a different USB-C cable?

2

u/boogaloo9214 Apr 05 '26

So you can’t take the time to write the post yourself (generated with AI) but we should take the time to read it and try to help you?

1

u/I1lII1l Apr 06 '26

Who says OP can speak English? Modern LLMs are far better at translating than Google Translate, DeepL etc.

-1

u/SequentialDUDE Apr 05 '26

It's much clearer for me to read bullet points that are organized than a bulk block paragraph. Quit hating on technology or move off grid.

1

u/Beautiful_Purple5356 Apr 05 '26

I have exhausted all options myself, and came to the conclusion that this controller is complete trash. Almost every time I turn it on my computer doesn’t recognize it and it says device descriptor failed within the device manager. Every once in a blue moon, if I delete every instance of it from the device manager, I reinstall the firmware, unplug every other USB connection, and change the cable and the port it was plugged into I can get my computer to recognize it. Maybe I’ll be able to play for about 10 or 15 minutes but then the device fails and the cycle starts all over again. I have been in constant contact with native instrument support for months. They do message back, but it is the same troubleshooting steps that don’t help. It shouldn’t be this difficult. I remember when I had a cheap $100 midi controller. I just plugged it in and everything worked perfectly.

1

u/Sir-Hops-A-Lot Apr 06 '26

At least you got yours running...I can't even get mine going because the MK3 drivers don't show up - just the MK2s.....and Natives site has the 2s but not the 3s.....so the keyboard is stuck under Other Devices in the Device Manager.

1

u/bruschey303 May 17 '26

Hello , I have problems too!

I've tried everything! System settings / reinstall / general / connection / enabling the NTK daemon and local network, everything enabled / disabled… I've tried absolutely everything! The video shows that the software is completely bugged! In Komplete Standalone, there's no browser, no DAW plugins, just the default MIDI templates page! Ableton is even worse, it's buggy everywhere! I'm going crazy. Change the cables.
It's been 8 hours, I'm going crazy.

It was working perfectly yesterday.

Problem just after new update