Looks like something went wrong

Seedy eyes · April 10

I really wish I didn't have to post about this again, but I've had THE MOST absolute awful experience with an s61 keyboard that I've coveted for at least 6 years before recently purchasing one a month ago. Since then, I've had nothing but problems on top of problems with this thing. They've finally agreed to fix it but I've yet to hear back about the process. Then yesterday I try to do an update (from Native Access) and now this (images). I cant even use the equipment anymore. Does anyone know how to get around this, yet another issue with this thing? Any help would be appreciated. Mac OS

Screenshot 2025-04-09 at 11.13.14 PM.png

Seedy eyes · April 11

Is there anyone that can provide information on this issue? I cant get past the "Looks like something went wrong" screen. I have never had any issue with a piece of music equipment in 20 years until this NI s61. What can I do about this? Anyone please?

Sunborn · April 11

https://community.native-instruments.com/discussion/comment/221126#Comment_221126

Hello,

There are already 2 discussion with exactly the same issue as yours,

here:

https://community.native-instruments.com/discussion/44006/kontrol-s61-mk-firmware-update-failed-keyboard-now-unresponsive

and here:

https://community.native-instruments.com/discussion/44291/keyboard-kontrol-s61-mk3-firmware-update-failed

Please first check the troubleshooting steps provided on those threads and if you still have trouble to solve it, then please contact NI Support, here:
https://support.native-instruments.com/hc/en-us/signin?return_to=https%3A%2F%2Fsupport.native-instruments.com%2Fhc%2Fen-us%2Fsections%2F360000091538

Seedy eyes · April 11

Thanks so much for the links. I actually have followed the steps, and nothing. No fix. Has anyone had success with the steps provided? Although I do appreciate the community of NI users helping, this is beyond terrible customer service on the part of NI. I'll be making a report to the Better Business Bureau if I cant get this resolved soon.

Looks like something went wrong

Comments

Categories