This discussion was created from comments split from:
FIXED - Issue with the Kontrol S mk3 new firmware/Hardware Connection Service
.
I have now reinstalled 2.0.5 and after launching K.K.Software Standalone, I confirmed that the "NativeInstruments_Kontrol_S_Mk3.js" file appeared. It also works without any problems in Cubase. Thank you, timrae. It's been a long journey this time.
Does the 2.0.5 update not include Windows Cubase?
It does, the files get copied over to the correct location when the hardware connection service runs.
There are no files in my windows 11 PC, and the device cannot be found in Cubase 14 Pro. There is no problem downloading from the Hardware Connection Service link.
I originally downloaded and installed via the separate installer. And that worked fine.
Once 2.0.5 became available on Native Access, I did the 2.0.5 update via Native Access.
And that promptly killed the Cubase integration - i.e. it had disappeared from the Cubase MIDI Remote.
So just in case (it's Windows after all!) - I rebooted my Win10 system. And then it worked fine again.
Environment: Cubase Pro 14.0.32 on Win10 22H2. Native Access up-to-date.
That's not work for me. I tried rebooting after installing 2.0.5, but the file still doesn't exist.
Cubase Pro 14.0.32 Windows 11 24H2 Kontrol S61 mk3
Is Komplete Kontrol standalone working correctly for you? When the HCS starts it copies the javascript file from here:
C:\Program Files\Common Files\Native Instruments\Hardware\Hardware Connection Service\Kontrol_S_MK3
To here:
Documents\Steinberg\Cubase\MIDI Remote\Driver Scripts\Local\NativeInstruments\Kontrol_S_MK3
So if the Cubase file isn't in the correct location then that implies the hardware connection service wasn't able to copy the file for some reason. My assumption would be that the hardware connection service crashed, and your S61mk3 can't connect with Komplete Kontrol standalone. Can you please confirm this?
As for why the file fails to be copied on your system, these are the most likely reasons according to AI, does anything ring a bell?
Windows has a built-in feature called Controlled Folder Access to protect your Documents folder from unauthorized changes (like ransomware). This is the most likely culprit. Your security software (Windows Security, Norton, Bitdefender, etc.) might be stopping our app from writing the file.
Documents
If you use OneDrive, Dropbox, or Google Drive to back up your Documents folder, the sync client can sometimes lock the folder while it's syncing. This prevents other apps from writing files to it.
While uncommon, it's possible the permissions for your Documents\Steinberg folder have been changed, preventing new files from being created. The app might not have the rights to write to that specific location.
Documents\Steinberg
Steinberg
This is rare, but if your Windows username is very long, the total length of the destination path could exceed a limit that some older applications have trouble with.
Finally could you try opening a cmd shell and manually copying the file with the following command?mkdir "%USERPROFILE%\Documents\Steinberg\Cubase\MIDI Remote\Driver Scripts\Local\NativeInstruments\Kontrol_S_MK3" 2>NUL & copy "C:\Program Files\Common Files\Native Instruments\Hardware\Hardware Connection Service\Kontrol_S_MK3\NativeInstruments_Kontrol_S_Mk3.js" "%USERPROFILE%\Documents\Steinberg\Cubase\MIDI Remote\Driver Scripts\Local\NativeInstruments\Kontrol_S_MK3" I hope you can help us to identify the root cause of the problem to help other users (and us), while also getting your problem resolved ASAP
mkdir "%USERPROFILE%\Documents\Steinberg\Cubase\MIDI Remote\Driver Scripts\Local\NativeInstruments\Kontrol_S_MK3" 2>NUL & copy "C:\Program Files\Common Files\Native Instruments\Hardware\Hardware Connection Service\Kontrol_S_MK3\NativeInstruments_Kontrol_S_Mk3.js" "%USERPROFILE%\Documents\Steinberg\Cubase\MIDI Remote\Driver Scripts\Local\NativeInstruments\Kontrol_S_MK3"
Thank you for all your suggestions Tim. Komplete Kontrol standalone working correctly now. I was able to download "NIHardwareConnectionService Setup PC.exe" from the link and it works fine, so I'll wait a little longer about this things.
Are you saying that everything is working fine with Cubase 14 now? Your problem is resolved?
By the way, 2.0.5 works fine with Native Access now. It's not necessary to manually download the installer.
If it's working for you now, it'll be the starting of Komplete Kontrol software that fixed it. When you start Komplete Kontrol it starts the hardware connection service in the background which then copies the Cubase script.
For future reference, Make sure to install NI software using the same user windows account that you use Cubase. As i've seen people who run some apps in Windows "as admin", which can lead to permission and default folder mapping issues - especially when the MIDI mappings going into user documents folder.
In fact, in general, if you're ever having to run software "as Admin" then there's an underlying issue that you're best to fix rather than continue like that for general use,
Thank you for the advice Skijumptoes. I only install it on one PC using one user account. Looking to the future, it would be great if NI could align the behavior of the program downloaded from the download link with that of the Native Access installation so that we don't have to go through this again. I thought that the Kontrol S-Series MK3 2.0 had added the Midi Controll function, so I couldn't imagine the idea that important files would not appear unless I started K.K.Software afterwards.
Usually the hardware connection service is meant to start straight after the installer, but sometimes a reboot or running KK software might be required for this to happen. We have over 100 Cubase users up are running successfully, but it seems there's a small minority that are still experiencing issues like this
OK, Thank you Tim.
