USB issues and Loss of DAW Communication with KK S61 MK2

Hello

I’m experiencing a new issue with my Komplete Kontrol S61 MK2 and Cubase, ableton, FL Studio etc… on Win11 , and I'm hoping someone here can help (or share the required file).

Problem:

DAW integration seems to be missing or corrupted – the transport buttons (Play, Stop, Record, Loop, Metronome) . Not the MIDI communication

System info:

- Komplete Kontrol S61 MK2

- Win 11

- All compatible DAWS

- Komplete Kontrol (tested via Native Access, latest version)

- Native Access running with admin permissions

What I’ve tried:

✅ Fully uninstalled and reinstalled Komplete Kontrol via Native Access

✅ Reset Cubase , installed fresh Ableton and FL Studio

✅ Checked All required services are running ok

****************************************************************************

I suspect a conflict between USB drivers event though Device manager is all ok. I had big issue with my miditech midiface 8X8 Bome Driver that forced me to change the parameters for USB Power settings and also forced me to run MSDT.exe (the repair tool under CMD)

All drivers are ok BUT STILL Cubase won't recognize these functions ..

MIDI is ok and cubase detects the S61.

BUT un Studio settings I must select s61 by myself and Cubase won't recall this choice which vanishes all the time…

Thanks for help

Find more posts tagged with

Accepted answers

Uwe303

Hello,

First you could try to install the Bome SDK from here it has helped in the past with similar issues:

https://www.bome.com/products/bmidi

if nothing helps, go to device manager and set it to show all devices, also the not currently connected ones. Disconnect all midi related devices. Then uninstall all midi related devices if asked for deleting the drivers, say yes (ok maybe not the one from your audio interface). Then reinstall the native instrument driver for your keyboard or just komplete kontrol. Test it and see if all works then. It could (!!) be the case that your midi interface with the bome driver caused an issue, native also uses bomes midi driver, but i guess you need it so you could try to install it after all that.

fur.thestudio

@Uwe303

You are my savior .Only a perfect knowledge and understanding of the issue could bring such a perfect solution and perfect fix .

I was helpless even though my focus on the problem was the good one.

Thank you so much 😁

fur.thestudio

PROBLEM SOLVED - DRIVERS CONFLICT DESPITE GOOD DIAGNOSTIC BY WINDOWS TOOLS

All comments

DunedinDragon

The first thing you should do is check your MIDI preferences in KK. My S49 MK2 works perfectly with the following preferences. That's on Windows 10 so there may be some differences. I'm shocked it's all still working since I haven't turned it on in over a year.

JesterMgee

If you open the MIDI preferences in one of the DAWs, does it show the "Komplete Kontrol DAW" port? That is the MIDI port that talks to the DAW so if that is not listed then that suggests an issue around the drivers or service that controls that.

Uwe303

Hello,

First you could try to install the Bome SDK from here it has helped in the past with similar issues:

https://www.bome.com/products/bmidi

fur.thestudio

@Uwe303

You are my savior .Only a perfect knowledge and understanding of the issue could bring such a perfect solution and perfect fix .

I was helpless even though my focus on the problem was the good one.

Thank you so much 😁

fur.thestudio

PROBLEM SOLVED - DRIVERS CONFLICT DESPITE GOOD DIAGNOSTIC BY WINDOWS TOOLS

Uwe303

https://community.native-instruments.com/discussion/comment/255706#Comment_255706

Thank you, hope you can now have fun again and make some noise.

Vocalpoint

Another key tip for this one - is to never have the actual device plugged in the PC BEFORE adding drivers.

When I build out a custom DAW - each device is treated as a separate install event. And the order of installation is critical.

First - the device itself is always powered off, it's cable is in place but NEVER actually plugged in the machine.

The drivers are installed first (and foremost). Once the install is complete (and depending on device) - there may actually be a restart here. Restart if prompted and once the OS is back up - the device cable is plugged in, THEN powered on and all of this is happening with Device Manager onscreen.

If all is well - you will be able to watch the device come on line in real time and will be able to see at an instant if the drivers are sound and the device is ready. Has never failed me yet

I see so many folks having these "connection" issues - mainly because the device is plugged in AND powered on well before the actual driver install - which (depending on device) will force Windows to deal with the device itself (using crappy inbox drivers and other oddball issue) rather letting the device be properly "introduced" to the OS environment with the correct drivers.

Learned this one years ago from an engineer at RME.

Quick links

Unanswered questions