Just FYI if anyone else is having this problem.  This is a new one for me, after 23+ years using Cakewalk and Cake/BL.  The program crashed on opening 3 times in a row today after working perfectly late last night.  I'm still on the last release - (2018.09.0.25), not the one from October 4.  My only system change was installing the latest Melodyne Studio update - 4.2.0.020.  
 
I was able to open the (last) SONAR Platinum version fine, it scanned and found the new Melodyne plug-in and had no problem opening my Cakewalk project from last night.
 
So I uninstalled the latest Melodyne update but still got the Cakewalk/BL crash.  The I went back and uninstalled an old 2016 Melodyne Runtime installation showing in "Programs" and was able to open Cakewalk without a crash. Then I reinstalled the Melodyne update and I'm able to get back to work in Cake/BL.
 
MORAL of the story - When Melodyne says uninstall your old version first, it's for a good reason.

Please install the latest version of CbB. The crash was most likely due to a big we fixed that was more visible on some systems.

Thanks, Noel! Will do.  Just had the same thing happen when I installed Kontakt 6 alongside Kontakt 5.

Kontakt 5 and 6 should both co-exist without issues.

I reinstalled Kontakt 5 after doing the 2018.9 update and now it works fine along side Kontakt 6. Thanks, Noel.

I'm still having both the Crash when loading a project using Melodyne, and the issue where Melodyne doesn't open correctly... I updated CbB this morning to 2018.09 (Build 29, 64 Bit) I have let Melodyne know it's still an issue for me.

jlhawk
I'm still having both the Crash when loading a project using Melodyne, and the issue where Melodyne doesn't open correctly... I updated CbB this morning to 2018.09 (Build 29, 64 Bit) I have let Melodyne know it's still an issue for me.

Maybe I'm wrong here, but I saw exactly the same thing when opening projects with active Melodyne 2 region fx after upgrading to Melodyne 4.
 
I suspect that when a region fx is active, it saves the state of Melodyne along with the region fx. When you re-open the project, the state is reloaded into Melodyne.
 
I doubt if that state is compatible between different versions of Melodyne, although you may be lucky with a minor update.
 
This is one of the reasons I always bounce to clips after editing within Melodyne.
 
If for some reason I need the original, I'll duplicate the track and archive the original.
 

I'm not using groove clips. I also tried uninstalling Melodyne completely and reinstalling with no luck. CbB crashes hard when opening any project with Melodyne. If I keep trying it will eventually open, but it can take 4 or 5 tries or more to successfully open the file. I'm also seeing the issue where no algorithm is chosen when a Region FX is opened. The crashes started with the 2018.08 updates and continues with 2018.09 (Build 29, 64 Bit). Interesting note, The run time version of Melodyne reinstalls itself when Melodyne 4.2 installs. 

Another note on this... I have had rare occasions where all works fine for a time or two, and then the crashes return, so unless you've had several start ups with no incident, the problem may just be hiding...
 

And finally, since uninstalling and reinstalling Melodyne, I find the editor is not tracking properly with the project. it's ahead of the track by varying amounts...  so where the cursor is on number 2 on the track ruler, in the Melodyne Editor, the cursor is on 3 or 4 or 5. the tracks are correct, Melodyne is not correct, but why is this happening? I cannot edit this way... I'm wishing I'd never installed this last series of updates...