KeyLab 49 doesn't work (update message all time)

[mcalf]

Hi

My KeyLab 49 doesn't work. When I turning on, is shows me message: "AnalogExperience KeyLab" for a second and then shows only "Update" message and staying like that all thee time.
MacBook doesn't see it. MIDI Studio Shows device as "USB MIDI Device"
Reset didn't help (Octave UP+Octave Down+Power)
Update mode doesn't work (SOUND+MULTI+EDIT+Power)

[Semaphore55]

Good luck with this, I had the same issue with my keylab 49 and I messaged arturia a few times and received ZERO response. Now I have a keyboard that just says "update" and doesn't do anything.

[Rockscientist]

I am having the same problem, I can't get the Keylab 49 to leave Update mode no matter how I turn it on/off or how long I wait. If I power it up using just the power switch (or plugging in the USB cable with the power switch on), the LCD says "Update" and the Sound, Multi, and Edit lights are illuminated. If I turn on the power switch with the Octave Down and Octave Up buttons held, I get the exact same result. If I turn on the unit with the Sound, Multi, and Edit switches held, the LCD says "AnalogExperience KeyLab" for just a second or two and several of the lights on the unit flash 2-3 times. Then, the LCD display changes to "Update", and the Sound, Multi, and Edit lights turn off.

I contacted Arturia support a few days ago, so I still expect to maybe hear something, but I wanted to lend my voice to this thread as well.

[staszkiewicz]

Have you received any reply from Arturia? Exactly the same has happened to me today with brand-new Keylab 49.

[Bradamantine]

Have you tried opening up Arturia's "Midi Control Center" software with your keyboard on?

I had the software walk me through an update (lots of very specific and odd sounding button combinations need to be pressed during an update) and my Keylab has been working.

[kinesko]

I am having the same problem, I can't get the Keylab 49 to leave Update mode no matter how I turn it on/off or how long I wait...

Hi, did you get this fixed? I’m having the exact same issue as you…