FIXED - Issue with the Kontrol S mk3 new firmware/Hardware Connection Service

Jeremy_NI · 2025-08-14T08:02:15+00:00

There was an error rendering this rich post.

WINDOWS

Windows users cannot install Hardware Connection Service with Native Access 3.20.0 - The Native Access team is working on it.

MAC

The Hardware Connection Service update in Native Access fails to install the Cubase scripts, but doesn't uninstall itself. Only affects Cubase users.

SOLUTION

While we are working on fixing both issues, you can download and install the new version of the Hardware Connection Service (2.0.4) in your download Manager:

https://www.native-instruments.com/account/downloads

Our apologies for the inconvenience.

Find more posts tagged with

Accepted answers

timrae_NI

Should be fixed in the latest 2.0.5 update, I'm really sorry for the inconvenience. There was an incompatibility with Native Access introduced into the installers, which we missed in our testing, and had to work around the clock to get a fix out.

All comments

LostInFoundation

@Jeremy_NI For your interest, the linked page at the moment has issues

PoorFellow

Then people can use this link : Account downloads , then search for 'hardware'

Jeremy_NI

@LostInFoundation Thanks for the report, I've edited the post.

Skijumptoes

Mac users are affected too, as the DAW integration isn't being fully installed for Steinberg/Cubase unless you manually install the service.

Jeremy_NI

https://community.native-instruments.com/discussion/comment/237518#Comment_237518

I wasn't aware it was also an issue on Macs. I've seen only Windows reports. The Hardware Connection Service should be available in Native Access, I can confirm on my end:

Just like for every firmware update of the mk3 keyboard, the Hardware Connection Service should be updated as well.

Aberamenth

Something tells me this is somehow connected to my last post..

Skijumptoes

@Jeremy_NI we were discussing it in this thread:

https://community.native-instruments.com/discussion/comment/237372#Comment_237372

I can only presume that when we run the installer manually it pops up an additional dialog that we have to accept, whereas installing it from Native Access that doesn't happen - so perhaps there's some part of the install process that gets bypassed when installed silently?

Either way, fantastic update, really thankful for the work you've all put in for this! I see you guys get hate at times, but you really deserve a big pat on the back for this. 👍️

Jeremy_NI

https://community.native-instruments.com/discussion/comment/237527#Comment_237527

Yes, issue is confirmed on Mac and Cubase scripts. I'll update the thread accordingly.

Jeremy_NI

https://community.native-instruments.com/discussion/comment/237525#Comment_237525

It's an issue with the Hardware Connection Service. It's not the firmware update in itself being the issue. Your post relates to Maschine Plus, which is a different case.

PSYNUS

Thank you Jeremy_NI.

I was having trouble with this very issue. Thanks to your explanation and solution, I am now enjoying the new feature.

reytek1201

Thank you for this update. I've been struggling with this issue for 2 days. Everything is up and running now.

DunedinDragon

Thanks for alerting us, but it's very discouraging to see this happen after so many people have had so many issues with these keyboards. I'll say after the initial problems I had everything has been rock solid with these updates over the last year or so. Imagine my disappointment after everything working fine then…BOOM…a promising new update that forces me back to an old release just to get things working again.

I have to seriously question your in-house testing and release discipline in this case. I'm not on any strange or peculiar setup. Just Windows 10.0 Home edition on an Intel I7-6700 with 16gb memory. About as plain vanilla as it gets and still not adequately tested before release?

LostInFoundation

Testing and smooth releases are one of the weakest point of NI lately.

All we can hope for is that at least they’ll be acting responsibly AFTER the not so smooth releases and fix things (hopefully in a short time/immediately).

Lately I see some good (or let’s say decent) signs at least on that front.

It’s only sad that that front could be completely avoided by working better from start (I mean by making good testing and smooth releases).

Same is valid for the by now consolidated “release now and promise missing/not functional things will be added/fixed in the future” technique

Kymeia

https://community.native-instruments.com/discussion/comment/237616#Comment_237616

There is a huge difference between testing in a beta team and releasing software into the wild.

DunedinDragon

https://community.native-instruments.com/discussion/comment/237630#Comment_237630

Technically the regimen SHOULD be you complete internal testing successfully THEN open it to beta testing with trusted testers to isolate test cases you might not have uncovered in your internal test cases. It doesn't appear to me they're doing such things if they have failures in a simple configuration like mine after it's been released.

Quick links

Unanswered questions