You have to troubleshoot each issue to completion separately. Only then can you know what's due to:
 
1. An actual bug
2. User error or incorrect expectation
3. Preference setting
4. Project configuration
5. 3rd-party plugin defect or interoperability issue with SONAR
6. Corrupted project or session
7. Hardware or O/S problem
8. Other
 
DAWs are complex beasts. A lot can go wrong that has nothing to do with defects in the DAW software. Laundry lists of briefly summarized issues are of little value to anyone.

Sorry but I really do not think the OP is interested in any help - That obviously was not the point of his Post. IMHO
 

stratman70
Sorry but I really do not think the OP is interested in any help - That obviously was not the point of his Post. IMHO

 
True...he said he's going to purchase another DAW. However if he checks any of the support forums for any other DAWs that still maintain support forums, he'll find them populated with people who claim to have found bugs, some real and some imagined. 
 
If the problem is pilot error but someone assumes software is the problem, then the "problem" will never be fixed. For example...
 

4.19.16 - Double click on Synth icon in track on edit screen, no results

 
He's probably clicking on the icon below the track header; that icon is there for identification. The icon to click to open the synth GUI is the little one in the track header. This is logical. The little icon will always be visible, even if the track is minimized. 
 

Pro Channel not working. no audible changes on any module

 
Logic would dictate that if this was indeed a bug, the forum would be up in arms. The only other time I remember this being identified as a "bug" was by William Copper, because he didn't realize there was a ProChannel global FX bypass button. That's probably what's happening in this case. This functionality is also logical, so you can bypass the entire ProChannel with one click rather than having to disable each module independently.
 
Anyway, the reality is that today's DAWs are complex. It's not surprising that some people don't have the desire or discipline to study a DAW with the same intensity that's required to master any musical instrument. For these people, I believe - and I say this without any condescension, because I've heard some truly great music created on all-in-one studios - that something like a digital Portastudio is a better choice.
 
 

bgl1
Numerous Sonar Platinum errors.

Yup. Sonar is good training for anyone wanting to enter the Software Quality Control profession ;)

bgl1
4.28.16 - false midi trigger at 35 seconds. when i move the clip, the false trigger stays at 35 seconds and falsely triggers a different midi note now at that timecode

Is this one particular project? Or does it happen on every project?
If you create a new project, then copy/paste the midi clip to the new project, does the false trigger move, too?
1) You may be missing a tiny midi note, too small to see
2) You may have one note over another (depending on the nature of the false midi trigger)
3) You may have another track (cloned?) and it's triggering the same midi synth.

bgl1
4.29.16 - One Crash - False midi notes. Multiple midi notes where only one was written. - dropout in one midi section. deleting and reinstalling the track and copying midi data over solved the problem for about 10
minutes. dropouts resumed.

As azslow3 said, that sounds like the classic midi buffer size issue. Everybody runs into it once.
Go to:
Edit > Preferences, then click on:
MID/Playback and Recording
Under "Playback", set "Prepare using:" to 500 or even 1000.
 
Do try other DAWs and let us know your experience. Many of us here use more than one.
Other DAWs have bugs and limitations, too. But I find Sonar has features and depth that others lack.

+100 Wookiee's comment on McAfee - for the sake of whatever DAW the OP intends to use -  strongly recommend he uninstall it and exile it forever from his DAW. Highly recommend using the "McAfee Consumer Products Removal Tool" (MCPR, available on Bleepingcomputer.com) after a complete normal uninstall, then system restart. Before you uninstall, check your CPU and Memory levels (while running your DAW) in windows Task Manager, then again after completely uninstalling it. That'll help to dissuade you against reinstalling it should you want to use the remainder of your AV subscription.
 
 

Many helpful suggestions from the forum readers...however...
 
I was told by a Cakewalk Tech Support Rep that there would be a report created at Cakewalk to address one of the malfunctions: CWBRN-46239. This report was created on 2.15.16. As of 5.3.16, nothing has been done to address this or most other malfunctions
 
If cakewalk rep said I was going to receive information from a troubleshooting report and never did (info above) I think y'all need to understand that cakewalk does NOT support its customers. That's why I purchased a different DAW. I need to keep working.

bgl1
I purchased a PreSonus DAW 

 

bgl1
If cakewalk rep said I was going to receive information from a troubleshooting report and never did (info above) I think y'all need to understand that cakewalk does NOT support its customers. That's why I purchased a different DAW.

 
I really hope PreSonus customer support has improved from a couple of years ago. Back then, a couple of inquiry emails I sent to them were completely ignored.
 

bgl1
I was told by a Cakewalk Tech Support Rep that there would be a report created at Cakewalk to address one of the malfunctions: CWBRN-46239. This report was created on 2.15.16. As of 5.3.16, nothing has been done to address this or most other malfunctions
 
If cakewalk rep said I was going to receive information from a troubleshooting report and never did (info above) I think y'all need to understand that cakewalk does NOT support its customers. That's why I purchased a different DAW. I need to keep working.

I completely identify having to balance exchanging pleasantries here with getting a project finished.
 
From experience I can say it's impossible to know when or even whether a bug will be fixed. Usually it takes a year or two, so I guess you do what you gotta do.

icontakt
I really hope PreSonus customer support has improved from a couple of years ago. Back then, a couple of inquiry emails I sent to them were completely ignored.

Best support I got at PreSonus was from folks that are also members here! :)

jpetersen
From experience I can say it's impossible to know when or even whether a bug will be fixed. 

Bugs introduced in a new version are typically fixed within a month, sometimes less. However bugs involving old code are a crap shoot as to when they'll be fixed, depending on how deep they are in the code, and what else is going on. For example if CW is concentrating on automation or changing it, they'll try to fix automation-related bugs at that time; otherwise the automation bugs will wait until it's their turn.