Activation serial codes and such should not be posted on a public forum so it was hidden by a moderator. This is a users forum, forum members and moderators cannot view or change email addresses, serial codes and other personal information.

When you tried to activate Sound Forge, did you use the same email address that Magix sent to you with the serial code. Your email address and activation serial code are paired. If you wish to use a different email address for Sound Forge, you can change it in the service center. The log-in email address for this forum and the email address for activating SF can be different.
btw, welcome to the Magix Sound Forge users community @Ben-Brunsson.

Hi. I have used the same email address, when I bought this Soundforge 17, and I have recieved all the emails from Magix, on the same email address. Still I get the faultcode error 24, when I try to open the program. I have never used any other email address, to Magix. Besides, I don't even have any other email address, on the net. So for me, it looks that Magix have written a wrong email address, when they made this package with Soundforge 17 for me, or the whole business with Magix, is a hoax.

@Ben-Brunsson Where did you buy the software? If you got it from another vendor and did not buy it at Magix.com it could be that the vendor sold you a copy that was already used or returned from a previous owner. In that case, the error message with error code 24 would make sense, because even if the software was returned, the previous owner kept the license.

Hi SP. I bought the software directly from Magix yesterday and recieved links directly from Magix also.

@Ben-Brunsson Have you checked whether the software is already listed in your customer account at Magix.com under 'My Products'?

Does anyone know how to get a resposne from Magix technical support? I have now contacted them 5 times in the last 2 weeks, quoting the ticket code generated from my initial query. My initial query received an AI-generated response which was of no help, and all I have had since is an auto-reply.
My copy of Audio Studio 16 was working OK, but the next day it became unusable as it crashes immediately on launch; I even bought an upgrade to Audio Studio 17 to see if that would work, but it has the same problem.
So I have unusable Magix software, an unusable paid-for upgrade, and I cannot get a human response from Magix support - not good enough.
Is there any other way to contact them, or a way to raise a complaint with the company outside of the ticketed support system? I've looked on their website and can't find anything.

@Les-Wilkins Sadly, we don't know how to get a response from Magix support. I'm waiting for six weeks for a response. It looks like there is no longer any support staff active at Magix.

I haven't tried to contact some higher-ups. Current CEO of Magix is Robert Rutkowski. At the beginning of 2025 Magix was acquired by Russmedia Equity Partners: https://www.rmep.com/news/rm-equity-partners-acquires-magix-software-gmbh-and-appoints-a-new-management-team-led-by-robert-rutkowski

Maybe you can get in contact with somebody over there: https://www.rmep.com/imprint

Besides that, crashes at startup point towards the Magix Low Latency ASIO driver.

If you want to uninstall Magix Low Latency you can click on the Windows start button in the bottom left corner and type regedit. Then click on the Regedit app.

Then navigate to: HKEY_LOCAL_MACHINE > SOFTWARE > ASIO > Magix Low Latency 2016:

Now, simply right click the Magix Low Latency 2016 folder, and delete it. Make sure to not delete anything else by accident, except you know what you are doing!

Then restart your computer. Please select the Restart option and not the Shut down option.

If you have trouble deleting the folder, try starting Regedit as administrator via the right click option.

Sorry to hear that you have been suffering a similar problem with Magix support - seems to happen with companies in many different fields once 'equity partners' get involved, and their frequent cost-cutting in search of short-term bigger profits starts taking effect.

But ... THANKS! Your suggestion has worked!

Before installing the newly-downloaded v.17 I had searched through the registry and thought I had removed all references to Magix; maybe I had missed one, or maybe the Magix Low Latency 2016 folder was installed with the new version of v.17. Whichever, I now have my software back, and am very grateful.

Out of interest, do you, or anyone else on here, know why that folder causes the problem? Is it something in itself, or is there a conflict with other ASIO drivers on the computer?