I updated to Kontakt 5.8 from the previous version today, and now when I open a project, Kontakt is crashing and freezing Sonar, either the new bandlab version or my Platinum version. Starting a new project, I try to add a synth, but instead of showing my 64 bit Kontakt listed, it only shows two instances of Kontakt 32-bit version--this has never happened before. I tried rescanning the vST folders, didn't help. I checked the location of my .dll files for Kontakt and they are all there, in their usual and proper location , and indicate that my version of Kontakt is indeed the 64 bit version. I'm lost at how to fix this. I have contacted Kontakt support, but I fear that this is some new incompability with Sonar/Cakewalk, since the standalone of Kontakt seems to be fine. I'm going to tinker with the VST scanning again, but if seems that should have fixed the problem already. I hope someone has an idea, this is putting my work at a standstill. Thanks.

that is a worry... think I'll hold fire on the 5.8 update until there is some clarification from Bandlab... hope you can find a solution... Can you move back to Kontakt 5.7 by a system restore point?

I may indeed try and do a system restore, but not sure if I have one or it will work, but it's a decent idea. I'm trying to re-scan, but having some scanning-crashing issues, too. It's all very annoying and puzzling. But we'll see.
Thanks.

thepianist65
I may indeed try and do a system restore, but not sure if I have one or it will work,

By updating Kontakt to 5.8 a system restore point may have been generated automatically..if it was the last software update you did you maybe able to go back.. not guaranteeing of course!
 
Ive sent a msg to Bandlab to clarify... if your Kontakt 5.8 works OK in standalone ..sounds like Sonar/CbB has an issue...

Sounds like you got the 32 bit update. I'd try the D/L again.

Updated and running fine here in CbB.

Just to rule out any incompatibility, I updated yesterday and it's working properly.
 
Maybe it's like ampfixer said.
 
Good luck.

Well, I did finally solve it in a rather unconventional way. Since Cakewalk (nor Sonar) was "seeing" the new version's .dll's, even though they were present in the scanned directory, I decided to copy the .dll files to a couple other of the folders where some of my 64-bit vst's reside (some vst's put their .dll's in directories other than my default c:/program files/cakewalk/vst). Anyway, after doing that, I launched Cakewalk, and the scanned picked up my three kontakt plug-ins, and everything is back working as normal. I have no idea why or how this worked, but I had a hunch that copying the files into additional directories wouldn't hurt anything and might trigger a "discovery" of a "new" VST, and voila, it did!
BTW, I wasn't able to do a system restore, as it didn't indicate that the Kontakt changes would be affected either way, and I'm relieved I didn't have to go to those lengths.

5.8.0 running fine here, near as I can tell. Tested it standalone and as a plugin.

Yeah, it's funny that this problem surfaced out of nowhere, and the solution was even wackier. I definitely had the 64 bit version, but the update was not being scanned by Cakewalk properly until I copied it into another folder that is normally scanned for changes, and then it was fine again.