Software Version Mismatch - right out of the box

  • The Profiler Model referred to in this thread is ...
    ☑️ Profiler Player



    Brand new kemper profiler player, right out of the box, followed the instructions, and got this.

    Anybody else had this issue?

    I haven't had a USB stick in years, so I'm not very happy about this.

    Mike - NYC & Woodstock, NY

    Fender(esqe) Telecasters > Budda Superdrives & Kemper Profiler Stage
    http://www.eviljake.com

    Edited once, last by mikeyjake (June 25, 2026 at 9:59 PM).

  • Your KPP might have been new but in a warehouse for a bit. They were released last year and there have been a few updates since. Once caught up you can use the computer connection via usb.
    It’s good practice to backup your KPP onto a USB stick. They are inexpensive to buy

  • I have the same issue...

    So I put the latest rig manager download on a USB? and then to the player?

    It says to unzip the OS and extract the chaos.bin? When I download the file to my Mac there is not an option to unzip and extract the chaos.bin?

    or am I missing something?

    Edited once, last by Ccunningham99 (June 28, 2026 at 5:49 PM).

  • Yes, we already all know KAOS 14 and Rig Manager 4 are a matched set. That's not what I was asking about.

    The question I asked is: under what circumstances is the Rig Manager unable to update the KAOS? I would expect it to always be able to do such an update, but occasionally, like the OP here, I've seen reports that it fails. It is much easier to update the firmware from RM than from a USB stick, so I'm asking G String: under what circumstances is that easy method not available?

  • Yes, we already all know KAOS 14 and Rig Manager 4 are a matched set. That's not what I was asking about.

    The question I asked is: under what circumstances is the Rig Manager unable to update the KAOS? I would expect it to always be able to do such an update, but occasionally, like the OP here, I've seen reports that it fails. It is much easier to update the firmware from RM than from a USB stick, so I'm asking G String: under what circumstances is that easy method not available?

    I will let G string answer with specifc's but there are 2 questions here:

    1) When can it fail - that can be with any version, sometimes it just doesn't work and you have to revert to USB stick. This is now rare but occasionally happens so I don't think this is version related - more frequent with Beta's of course.

    2) Incompatibility between RM and OS's - generally main versions but not always the case. Not sure how useful a list is when the alternative is clear but hopefully G string has the info needed.

  • In the vast majority of cases, you'll never need to update using a USB stick. However, when updating from a old firmware version, a USB stick may be required for technical reasons. For example, the way the Profiler communicates with Rig Manager has changed over time, and older versions may not support the direct update path.

    As I said, if you need help, please contact support.

  • In the vast majority of cases, you'll never need to update using a USB stick. However, when updating from a old firmware version, a USB stick may be required for technical reasons. For example, the way the Profiler communicates with Rig Manager has changed over time, and older versions may not support the direct update path.

    As I said, if you need help, please contact support.


    Thank you. I'd like to know how I can avoid that situation, so can you explain what you mean by "older"? By definition, the firmware version you are updating from is always "older". Are you saying this problem no longer occurs with firmware versions 13 and up? Or 14 and up?

  • As i understand it, its really if RM is out of sync with the OS.

    So if you are a number of versions behind, I would always update the OS first via RM which usually works. Then you can update RM independently. If you do it the other way round RM, won't talk to the OS and so you have to revert to a USB.

    GString - would you agree?

  • So if you are a number of versions behind, I would always update the OS first via RM which usually works. Then you can update RM independently. If you do it the other way round RM, won't talk to the OS and so you have to revert to a USB.

    That's not what the OP is experiencing and that contradicts what G String seems to be saying. He seems to be saying there are old versions of firmware that lack the ability to update from RM. If that's true, then this problem should only happen with firmware that is older than a specific version. If so, what is that version? Seems like this should be a simple question for Kemper to answer.

  • That's not what the OP is experiencing and that contradicts what G String seems to be saying. He seems to be saying there are old versions of firmware that lack the ability to update from RM. If that's true, then this problem should only happen with firmware that is older than a specific version. If so, what is that version? Seems like this should be a simple question for Kemper to answer.

    Sorry I assumed that was known.

    It was RM v3 and after that RM can update the firmware ( according to Google), prior to that it was always via USB.

  • Sorry I assumed that was known.

    It was RM v3 and after that RM can update the firmware ( according to Google), prior to that it was always via USB.

    No. In my post that you quoted, you can clearly see I'm referring to the firmware version that G String mentioned, not the RM version. G String made it clear he's referring to firmware version, not RM version. The OP obviously needs to update his firmware, not his RM.