Ableton Forum

So far I'm getting instant crashes with:

Antares
Celemony
Kush Audio
Lexicon (Reverbs are fine (MPX and LXP). Just the chorus crashing - must try a reinstall tomorrow)
NI Replika was crashing yesterday. Gotta confirm again later.
Slate Digital
SONiVOX (all except TimewARP2600)
Drumagog5

Very time consuming just narrowing it down to this little list.

Windows 7. Live 9.2 32bit.

Too tired to add any more detail right now (or ever maybe).

I bumped into some issues as well; 9.2 crashing due to some failure during startup VST scanning (one particular plugin seemed to cause the problem) or having difficulties with opening projects made with 9.1.x. (loading samples would freeze Live)...

Then I remembered something I have read a while ago about deleting the Preferences.cfg file in the \AppData\Roaming\Ableton\Live 9.2\Preferences folder, gave it a shot, and it looks like it cured my pains at least...

My update to v9.2 Suite was automatic, so I eventually uninstalled it, downloaded a fresh copy, and installed that instead. The reply I got from Ableton today would indicate that if you're having a problem, then the problem is with the Developer of the Plugin and not Live. No surprises there.

The list above is my current list of woes. I know of others who are having crashes with Celemony Melodyne (at least).

I'll attempt reinstalling any other troublesome Plugins to see if I can shorten my own list a bit more and then start contacting Developers. But first, I'll take advantage of that glorious sunshine outside my window.

I've been having the same problem since the 9.2 and it seems to affect any tracks I've made using Sonivox so far. Any word of fixes on the horizon yet?

Sometimes Live crashes when I load a set that has been made with the previous version 9.1, and when 3rd party plugins are used
The crash happens only when I try to change something in the set. As long as I leave it alone, nothing happens.
Not sure if this is related to previously reported crashes: Live just stops working and I get a windows message that the program has to close.

A work around is to open the old set and immediately save it again. After that: no more crashing.
I guess Ableton has changed some things in the file format of the saved sets.
Perhaps this could help some of you guys.

anyone having problems with fm8?

all my plugins are up to date with the latest updates. OS = win7 32bit

also, i'm getting intermittent crashes.

maybe the windows 10 upgrade will make for a more stable operating system for the new Live... and then again, maybe not.

can anyone report how 9.2 is running on win 8?

FM8 is working as expected for me on Win7, 32bit Ableton.

yeah - reinstalled ableton from scratch and it seems to work again with fm8


it all seems to be a rather crashy affair overall, through - requiring restarts etc. the whole system feels quite unstable. hopefully a new update is due out to tighten the whole thing up or i find it's something straightforward that i've just missed.

Well despite the initial reply from Ableton Support:

I got an email from Nathan at Kush Audio. Kush UBK-1 is crashing Live 9.2 Suite 32bit on

Windows 7 64bit.

Ableton (in their own words) have ''just deployed a new beta which contains a fix for the crashes

affecting Kush plugins on Live 9.2 32-bit.''

Feel free to rely your users (Kush Audio Users) to the following page, which instructs on how to

take part to the beta program: https://www.ableton.com/en/beta/

So I did. And guess what?

All of the Plugins which were crashing Live 9.2 work perfectly in ''ableton_live_beta_921b1_32''.

The only exception being Replika by Native Instruments which is a POS and doesn't work

anywhere anymore.

So I guess I'll be waiting for the next official update to Live. I don't like the idea of saving my

current projects with a BETA version.

I have had fun and games for the past couple of days with Ableton 9.2.2 (32 Bit) constantly crashing after reinstalling Windows 7 followed by all the tons of music software afterwards.

After much trial and error I discovered that Replika.dll (v1.2.2) was the culprit which then drew me to this forum to discover it is an issue already.

Following some advice here I uninstalled/reinstalled Replika with an earlier version I have (v1.2.0) and I am just ignoring the Replika update in the Service Centre. To date I have had no further issues