The notion that members are posting wanting other members to tell them to do a Google search is to me a bit anti forum. People are here to answer questions and help one another not so much to tell people to search out the answer. Not everyone even knows what to search for. 
 
Years ago I use to tell people to read the manual. I don't do that anymore. The whole purpose of this forum is to answer questions. If we have an answer we should post it. 
 
I'm sorry this is off topic but I believe in helping directly not referring someone to a search engine.  

Learning SONAR, or any other modern DAW for that matter, is like learning a musical instrument. You learn by practicing, from teachers, by watching others, by sharing licks, etc. I don't think there is any one size fits all solution to learning, except for "learn anything you can, anywhere you can."
 
Clearly Cakewalk believes in providing education for customers, or there wouldn't be CakeTV, the Cakewalk blog, instructional videos, or Noel coming in here and helping out. But with a program as deep as SONAR, I think education has to be a shared process among users and the company.

Not sure if this post will go through (the forum seems to have dropped it's CSS page again) however...
 
Recently when I close a project it takes WAY longer before I can reopen Platinum. The length of time seems to be tied to how large/complex the project is. In previous versions I did usually have to wait a second or two before I could reopen Sonar but these days it can take as long as 30 seconds or more (on larger projects) and at minum around 5-10 seconds.
 
So I'm not sure if it is related to this but something is different and making me wait longer before I can reopen Sonar. Just to be clear the Sonar windows closes normally. It is just when I go to reopen Sonar I can't for a certain length of time. I click on the launch icon and nothing happens. I open and close projects often as I work (for various reasons) so it does kind of get annoying.
 
It has not gotten so bad that I have to use Task Manager though. I did have a bit of an issue the other day where I (accidentally) tried to open a different project while another one was open. This led to a severe hang and I eventurally had to use Task Manager to close SOnar (which did not work the first couple times). AFAIK I should be able to open another project while another one is open.
 
Anyway... just posting my experience in case it's related and leads to the Baker's fixing something. I was (and still kind of am) under the impression it was something on my end and was going to post a thread asking about it (eventually).
 
Cheers.
 
Hope this posts.

I had to use task manager in front of a client. Its embarrassing. Luckily I do this in a seek. But sonar should not do this. I also have the newer times of opening and closing. Opening a project takes ages, and closing is the same.

I suggest launching Task Manager while one of these projects that hangs on close is still open, and check to see if either BitBridge or JBridge is running, as that would indicate that a 32-bit plugin is being bridged to run in a 64-bit Sonar.
 
I used to have various issues like the above when I was still running with some 32-bit plugins, but since I deliberately made a conscious decision to move all the way to 64-bit third-party plugins, things have been WAY more stable.
 
If you can identify and swap out any 32-bit plugins for some 64-bit equivalent or upgrade, then you might see a lot more stability with your system, assuming maintenance and other environmental aspects are OK.
 
Sorry you are having these frustrations - on my exclusively 64-bit system, things have been very very stable for several years now.  Hope that helps you, and in any case, I hope you can get past these issues.
 
Bob Bone
 

John
The notion that members are posting wanting other members to tell them to do a Google search is to me a bit anti forum. People are here to answer questions and help one another not so much to tell people to search out the answer. Not everyone even knows what to search for. 
 
Years ago I use to tell people to read the manual. I don't do that anymore. The whole purpose of this forum is to answer questions. If we have an answer we should post it. 
 
I'm sorry this is off topic but I believe in helping directly not referring someone to a search engine.  

 
Next time quote me directly John.
 
If I knew what the OP's issue was the chances are I would have googled for the OP. Everybody knows I'm one of the most active members here trying to resolve others issues. But I don't know what to search for either.
 
As you know I mentioned Google as a direct response to:
 

LJB
It may well be worth Cakewalk's time to write some sort of a PC/OS debug tutorial then - even if it's not their bug. Where the heck do I even start looking - I make music!

 
Suggesting alternative tools that may be available for a person to find a solution isn't unhelpful at all, esp in the context of directly responding to the above quote. We all use it, esp to help people here in these forums, and if we don't we should.
 
Suggesting it is 'anti forum' is either hilarious or totally ridiculous and unnecessary overstatement (silly), I expect other motivations were at hand. 

Genghis
I haven't had this issue since I ditched my old MidiSport 8x8 MIDI device several versions ago.  I figured out then that it was the culprit and would simply shut it off when it hung, wait a few seconds for good measure, then turn it on again.  The process would die when I shut it off, and then the OS would pick it back up when I started it again.  Fortunately I don't use external hardware synths any more, so I sold the MidiSport and don't have the problem now.
 
The only advice I can give is to do some testing (Noel's method looks pretty sound) and figure out whether it's a bridged plugin or a driver.  Personally, I'd suspect hardware first, plugin second, unless you do a lot of bridged plugins. 

Same here with the early Delta drivers and MIDISport 2x2.  If Sonar ever got hung up, first step was to unplug the MIDISport.  That released the Sonar process 99% of the time.
 
 

Noel - would it be possible for SONAR to write a minidump when it sits in wait state for x number
of seconds? Give us the instruction its on and the driver/dll process its waiting for. Anything to make
the investigation go faster.
 
Ludwig - I'd be looking for a driver as the most likely cause, but I've also had this problem tracked
down to 1) a faulty memory module and 2) an aging BIOS on an older (+4 yrs) mobo. If all of your
drivers and library links are current, you might try memtest and a BIOS update if one is available.

Check windows event viewer.. paste errors here. That may speed things up.

We need steps to repro and full list of specs as well. Some good advice has already been given. We will simply need to go through the same troubleshooting steps we use for everybody else. And there is always Cakewalk support if OP needs help quicker. Ball in OP's court.

Ta.

I have this happen periodically...to often...maybe once every 4 to 8 hours...  Fortunately don't have clients... Task manager does not release Plt...I routinely re-boot.  I've just gotten use to accepting this as part of the world of "amazing daw"land...
 
Personally I don't have the brains to sort this out.  It IS frustrating, but balanced by the awesomeness of Platinum over older Sonar's... If I had clients, it WOULD be embarrassing.  As it is, I just live with it...
 
As I'm getting ready to try Win10 and will be updating graphic drivers and Forte drivers, I hope this helps... No 32bit anything that I am aware of.