I tried to install Sonarworks - SoundID Reference v5.12.1.8 (there's only one distribution as far as I am aware). When I ran the Keygen registration prompt, which asks for a computer ID and an email, the program errored, "Cannot save license files!"

Antivirus is off, I used Admin rights, none of the files were blocked, and I am using Windows 10. What am I missing?

 

I think I've had this issue long ago. Try create a tmp folder on your desktop first. Then open kg, fill in the fields then try save to the new folder.

 

That 5.12.1.8 does not seem to be an actual R2R release, it just uses their keygen.
I'm not using it, so don't ask me

Spoiler: info

But this is a solution someone posted about 5.7.2 release from R2R, and so maybe it is the same, or you will find it helpful.

the right way to install it :
1.block access in host file to - C:\Windows\System32\drivers\etc (open with notepad ++ so youll can save it)
127.0.0.1 accounts.sonarworks.com
127.0.0.1 analytics.sonarworks.com
127.0.0.1 *.sonarworks.com
2.make sure to uninstall previous version if u have (do it with revo-uninstaller)
3.install SoundIDReferenceSystemwide then the VST\AAX
4. follow R2R txt:
1.Run SoundID-Reference app.
Quit.
2.Go to "%LOCALAPPDATA%\Sonarworks\Logs\".
Find latest log file.
Find the ComputerID (41 digits, start from 'g') from the log.
In the log file, you can find the line like this:
> [2023-01-01 00:00:00.000] [SoundIDReference] [info] ComputerId g0123456789abcdef0123456789abcdef01234567
In this case, your ComputerID is "g0123456789abcdef0123456789abcdef01234567"
3.Run our keygen on Windows.
Click "Registration" in the menu.
Fill the ComputerID and your Email.
Click "Register SoundID Reference".
Since profile files are encrypted by ComputerID,
you need to generate headphone profile with our keygen.
0.Make sure that your SoundID-Reference is already activated.
1.Run our keygen on Windows.
Click "Generate Profile".
2.Click "Load Current License File" or manually fill the ComputerID.
3.Click "Generate Profile for This ComputerID".
It asks you to open "Headphone Profile Source (*.swhpsrc)".
Those source files are included in this release. (they 2 in the R2R folder, just find your headphone type)
Open the source file you want to use.
Our keygen generates valid profile for your computer.
It asks you to save "Headphone Profile (*.swhp)".
Save the file to any location.
4.Run SoundID-Reference.
Import profile (*.swhp) which you generated.

 

Last edited by a moderator: Jan 6, 2026 at 8:50 PM

I've followed these steps meticulously, but the Keygen errors each time:

I don't imagine there's a way to get TeamR2R to see this? If anyone is able to help, please let me know. I can't mix well in headphones without this tool. I have additionally tried installing on a virtual machine to see if it could be an OS issue, but the installer crashes when running on a VM.
I would purchase a legitimate SoundID license if only they didn't require a constant internet connection for licesning.

 

Have cleaned the system from the previous version? I had to remove all the uninstalled files manually to get working well.

 

if the keygen, now has the correct information supplied to it; and it is saying "cannot save license files", there are not many possible causes.

Either the keygen is not being run by a user account with the correct privileges to save in that location, or there is already a file with the same name which it is trying to use and it cannot overwrite the file and keep the same filename.

People have posted that these work, and other sites show way more downloads than people commenting. It might be a little bit of a complicated issue, but it is still user error.

 

As I continue to work through this, I am noticing that installing from a different user account results in the application being activated immediately upon running. I still get the Keygen error, and I cannot import any headphones profiles created with my ComputerID, however. I suspect that uninstalling and clearing %localappdata%\Sonarworks and %programfiles%\Sonarworks isn't sufficient to fully remove legitimately installed SoundID Reference, and there is still some Sonarworks anti-piracy bloatware that needs to be removed. I'll try clearing the regkeys and running the aforementioned revo-uninstaller.

 

If you don’t remove previous version’s files manually as I described above, you will not be able to crack it properly.

 

I did attempt to remove all the files manually. I have also just manually scanned some key positions in my filesystem and registry, and used revo-uninstall to remove all related files. Then I did a reboot to clear out the RAM. Unfortunately, the problem persists, meaning there is possibly some stealthy spyware/bloatware embedded into Sonarworks SoundID Reference. Since I cannot reverse engineer the program on a VM, I am going to use my test laptop to diff the filesystem before and after a SoundID install to see if I can find where the residual files not being caught by revo-uninstall or me (if any) are located.

 

May be, it is just a problem of access to folders? That seems plausible as you are able to install it from another user. There is a tool 'Take ownership'. You install it as usual and then get an entry 'Take ownership' in the common Win context menu. Try to apply it to folders where SoundID installs files and license info. Or check permissions of these folders (right click, 'Properties'). Or try to delete all folders completely (installer must create them from scratch).

Sometimes admin rights aren't enough.

 

Please read here: https://support.sonarworks.com/hc/en-us/articles/23923145348370-Unable-to-activate-SoundID-VoiceAI

To inspect the startup type assigned to the service:

1. Click on Start, type in Services, and hit Enter to launch the utility
2. Locate Sonarworks License Service
3. Double-click on the service to open its properties
4. If the startup type is assigned to Disabled, click on the drop-down box
5. Select Automatic and click Apply to apply the change

If the Status column indicates that the service has been stopped, right-click on the Sonarworks License Service to start or restart it. The Status column should indicate the "Running" status of the service.

 

When I tried installing from another user account, I used the admin account. Sometimes files are owned by SYSTEM, but I doubt this is the case, because then there would be many more complaints similar to mine. I think, (though I am not certain) the Keygen writes to %appdata%/Local/Sonarworks/SoundID Reference/license.json. I'll try installing again in a moment and checking the permissions.

That said, the following are the results of the installation on my test laptop:

• SoundID Reference was NOT automatically registered without running the Keygen first- contrary to the result from installing on my PC on the Admin account.
• After running the keygen and inputting the ComputerID and email, the license files were successfully generated without an error, and SoundID Reference was registered and licensed to "Yamete Kudasai" - contrary to what I observed installing on my PC Admin account, where the licensee name was "Activated".

Now for the results of the diff: I opted to install the TEAMR2R 5.7.2 version instead of the official version. Files seem to be placed only in these locations, based on the snapshot data:

AppData\Local\Temp\
AppData\Local\Sonarworks
Program Files\Sonarworks
Program Files\Common Files\Sonarworks

The results of the registry modifications are significantly more concerning, as approximately 70,000 registry changes were made.

Note: My first post didn't go through, I think it was too long so I am attaching the results this time.

 

Last edited: Jan 6, 2026 at 10:02 PM

Okay boys, the plot thickens.

I skimmed over the 70k registry mods and all the filesystem mods that Sonarworks interacts with, deleted everything, REINSTALLED R2R 5.7.2, then uninstalled it with the uninstaller, then deleted everything for a second time, then double checked that everything was truly gone in revo-uninstall. I rebooted my PC a few times, and then followed the instructions again with extreme attention to detail.

As before, the Keygen cannot save the file. But I learned that "%localappdata%\Sonarworks\SoundID Reference" is indeed the proper path for the license file, and that is where the Keygen saves the file. I double checked the permissions on the folder, and I am able to read and write there no problem. Why the Keygen cannot on my PC but can on my laptop, I have no clue and I would like to know. Perhaps it is even a hardware architecture fluke. But I thought of an alternative solution since this seems to be a dead end.

I honestly thought I was wasting my time and I wouldn't find a solution, or even a workaround. Glad I stuck this one through, and I hope it helps someone else. I copied the Computer ID from my PC to my test laptop, generated the license.json and user.json files via the Keygen on the test laptop, and then transferred the files to the "%localappdata%\Sonarworks\SoundID Reference" on my PC. After re-opening Sonarworks SoundID, it appears this trick has succeeded, as the app is registered on my PC.



Hopefully I'm through the worst of it, because I've already spent 8 hours trying to solve this issue. I am worried I will have trouble importing the headphones calibration files on the next steps, wish me luck.

 

Final update: the headphones calibration worked without a flaw. I'm all set! Thank you all for your suggestions and ideas which guided me to a solution.

 

Did you get the v5.12.1.8 installed or did you just installed the v5.7.2?

 

It could be Windows Defender Controlled Folder Access blocking the keygen from creating the file in the app folder try disabling it and try again. you will find it under the Ransomware Protection.

 

Monitored Install with Revo Uninstaller Pro is one of the best solutions to this kind of situation. R2R always say to cleanly uninstall any prior version you have installed as one of the first steps in their instructions, especially when it really matters.

The Pro version is paid but maybe you can find a copy the usual ways. You start it monitoring, and it takes a snapshot of the system right before installation of a program begins, and then when you go to use it to uninstall that software; it has basically logged all of those changes by tracing. That way this manual hunting around for random file detritus is not so difficult. You will get the cleanest removal possible by any automated process.

 

I installed the v5.7.2 version and deleted the v5.12.1.8 one. I am not sure what was up with v5.12.1.8, but seeing as how clone mentioned that it is not an official R2R release, I didn't bother.

 

Good thinking, but I have Ransomware protection administratively disabled due to prior instances of running into things like this. Honestly, at this point I am thinking it might be a software bug in the keygen. My laptop CPU is Intel and my PC CPU is AMD, might be an architectural interface issue for example.