Kontrol S MK3- There needs to be A Product Recall

bnsrowe
bnsrowe Member Posts: 4 Member
in Komplete Kontrol

Another firmware update, another time bricked. This is not normal, this is not acceptable and we shouldn't cringe every time we see the notification and wonder how much time is this going to cost me to fix it .

Yes I run 2 usb C cables, one for power and one for data.

Comments

  • Matthew_NI
    Matthew_NI Product Team Posts: 1,834 mod

    I'm not sure what exactly could have gone wrong - but could I ask that you open a support ticket so that we can properly diagnose and understand the environmental factors here?

    @Jeremy_NI

  • bnsrowe
    bnsrowe Member Posts: 4 Member

    I will, it literally happens EVERY update. doesn't matter if using a power supply and usb C to C directly on motherboard, external hub, added a internal PCI to usb card same result. This time I was able to get to work through the usually reinstall driver THEN using a Usb C to A cable. I shouldn't have to do all this just to updates to work.

  • BIF
    BIF Member Posts: 1,206 Guru
    https://community.native-instruments.com/discussion/comment/190219#Comment_190219

    Hey, I'm working on a little research project. "Some" computer hardware has issues with the MK3 update process, but we in the user community don't know which hardware has the trouble. So I'm building a little knowledgebase on it.

    Maybe you can help us all out by sharing some info.

    1. Mac or Windows? What version of OS?
    2. Details for #1 above. If it's a prebuilt, what's the make, model, and year? If you built it yourself, can you tell us the following:
      1. Motherboard
      2. CPU
      3. Memory (brand, how many GB, and how many sticks)
      4. Graphic Card
      5. Hard drive or solid state drive make and model
      6. Exactly which USB-C port is plugged into for the data to and from the MK3?
      7. What CPU BIOS is installed?

    That's a start; thanks!

Back To Top

Categories