Mike Conway wrote:
In the event that you ever have to re-authorize your Kronos, because you reformatted the hard drive or something, you can find the DOWNLOAD RE-AUTHORIZATION CODE FILE link, right above your library authorization codes.
Hello Mike,
The authorization codes are based on the Public ID.
So, what happens in case of changing the motherboard. Do wee loose the Public ID and all our sound codes ? Or, is the re-authorization code file sufficient ?
The public ID seems to be stored in a microchip (AM1806B) welded on the motherboard.
So, in case of motherboard crash and replacement, we loose the Public ID. Since the re-authorization file is based on the Public ID, we consequently loose all the sounds banks purchased on shop korg.
Do you know what is the Korg policy in case of motherboard replacement ?
I purchased a used Kronos X on Facebook Marketplace and purchased a Bolder soundset. Korg asked me to register my Kronos which I did and, not knowing it's history I filled it in as best I could. Korg sent me a re-authorization code but it is only fourteen characters long and I can't download the new soundset because I haven't installed the re-authorization code. I have also updated to the most recent OS update 3.1.3.
I'm afraid if I install this new code, I'll have to start from scratch or, even worse I will be locked out of this keyboard. Any input would be greatly appreciated.
By the way, Bolder or whoever took my money anyway.
The public ID seems to be stored in a microchip (AM1806B) welded on the motherboard.
So, in case of motherboard crash and replacement, we loose the Public ID. Since the re-authorization file is based on the Public ID, we consequently loose all the sounds banks purchased on shop korg.
Do you know what is the Korg policy in case of motherboard replacement ?
I have no idea what the updated 'policy ' is , if it changed since 2011.
I know what Korg " should " do.
If you have a Mobo replacement for your K, keep a receipt of that component purchase. Send it to Korg support as proof and request the reissuance of all auth #'s.
Hi all. SSD drive in my Kronos (1st gen) become broken, so i replaced it with a new one. I installed an operating system from factory disks, but got a "Re-authorisation needed" message. I download a reauthorisation code from my Korg account, put it to a root of usb-flash, but Kronos can't find it. I tried a couple of usb-sticks, tried FAT32, FAT. But every time i got the same: "Re-authorisation file not found". I don't know what to do...
I suppose you also made sure that the file extension suffix is .reauth. Did you install the correct OS for your unit, in other words the data from DVDs for the Kronos 1 (and not for the Kronos 2) ? Just trying to help.
Of course, correct file with correct extension, installed from original DVD which come with the unit. I did this procedure not first time. I made the same a few years ago, when i replaced stock ssd with a new one. All went flawlessly, without any issues. It was ask for an authorisation, but it could find a file and register successfully.
But this time i got this error, and do not know what to do.
I even plugged vga monitor to a Kronos MB. All i see during authorisation process - that Kronos wait for an exact file name, which is correct im my case.
But i have a strange thing: Kronos looks for auth file on path "/mnt/cdrom/*filename.auth". But Kronos display says about plugging usb flashdrive, not a cd/dvd disk.
I'll try a few things:
- give it an authorisation file on cd-disk
- replace ssd drive and make a fresh installation
But if this will not help - I don't know what to do.
One more thing i need to check: Korg have a new web page with all libraries and authorisation data stored in user account. But the old web page also exists. I hope, it will be possible to generate auth data via the old site.
Finally i got my Kronos authorized. Authorisation file from new korg shop
(https://korg.shop/customer/account/) doesn't work for me. I re-download the same file from the old site (https://shop.korg.com/REGISTERKRONOS) and it works. Same flash drive, same account, same Kronos ID, but different results.
