As a (very very very) long time cakewalk user I've become accustomed to (every once in a while) a release being, uhmm, 'a bit of a chore to use', and yet, with the X-series, I've begun to 'believe' again... at least until X3(d) (Producer)...
 
Simply, it routinely keeps freezing.  Hanging for 30-60 seconds, to the extent that Windoze 8 (64) routinely notes it as 'not responding'.  This on the same rig, same everything in fact, that ran X2 'perfectly'.  This is clearly utterly unacceptable.  To the extent I'm genuinely and seriously considering regressing to X2.
 
It also cannot reliably remember MIDI ports, so I routinely get asked if 'MIDI Port A' is the same MIDI port as 'MIDI Port A'.  Particularly if I've turned on (or off) a device that has a USB MIDI connection before/after a software restart.  This suggests a problem in X3's underlying configuration/control/mapping files when working with a USB MIDISPORT 4x4 and (directly) USB MIDI connected devices.
 
I also note that when connecting a device (esp a direct USB linked device), despite it having been previously configured, I have to go back in to the MIDI configuration to re-enable the MIDI device and further, re-assign its MIDI instruments.  This further suggests a problem (aka sporadic corruption) in X3's underlying configuration/control/mapping files.
 
X3d has also completely forgotten/lost (initially mid session, but continuing after a total PC power-down & reboot) my connection to my Frontier Alphatrack.  This happened after I (USB) detached and reattached my Korg Nano Key2.  This has NEVER happened before.  Ever.  This confirms a problem (aka sporadic corruption) in X3's underlying configuration/control/mapping files - even when not changed by the user.
 
As an experienced IT developer (working in real-time zero-loss messaging systems) this is irritating.
 
X3d is also routinely immune to mouse/keyboard/all other inputs, or indeed any form of input - to the extent that I thought my keyboard/mouse/Alaphatrack had become faulty.  I assume this to be a minor variant of the whole 'application simply freezing' (as noted above).
 
Additionally, if I save 'project v1.2' as 'project v1.3' in X3, and then close X3 by shutting down Windoze (e.g. not shutting the application itself directly), the next time I start X3 it has no memory of '...v1.3' in its startup menu.  Yes I accept this is trivial, but it is still poor, and a further exemplar.
 
So for 70% of the time X3d works faultlessly....... but that's down from 95% with X2... and about 20% less than I'd expect from any software... even freeware.
 
Honestly I do genuinely hate to moan, and I really do appreciate that trying to develop software for a near infinite number of PC variants must be a bloody nightmare, but I'm really not happy at the moment.
 
So, in summary, if you want someone to beta test X3e (or X4), please do get in touch.  I'm happy to sign an NDA.
 
All of that said, thanks for sorting out the atrocious 'magnetic' drag and drop MIDI note (non)alignment debacle... albeit that should never have passed testing... and on the plus side, your email and phone support is actually pretty good + very friendly.

I had a very poor experience with X1producer and reasoned that it must be X1 because Sonar 8 and then Sonar 8.5 ran perfectly well. It wasn't until the X1c update was released that X1 would even run. That's right from day one of the X1 release which is when I bought X1, to the release of the c update I couldn't even run Sonar.

Comes X2 and it runs perfectly on the same laptop. Today with. X3d and since X3 was released this same laptop is running that version without a hiccup. Go figure.

You haven't specifically asked a question so I figure you just want to vent. I won't offer you any advice, but I'm sure you're going to get some fairly soon.

I only have this to offer. Why are you saving file project name 1.3? Since you're an IT guy you should know that saving a file with an extension after a . (period) denotes another file type.
 
If I'm wrong there then you'll have to enlighten me.

I would suggest that since none of the issues you mentioned have been posted by anybody else - to the best of my knowledge - I would think that your install/settings/usage are causing you this grief.
 
+1 on the notion that using a '.' is problematic in saving a file, and quite possibly why Sonar is not 'seeing' that project when you start Sonar back up.  It is likely confused by your naming convention.
 
You could quickly test that theory by renaming the folder and project file to something that included 1-3 instead of 1.3, then firing up Sonar, using the Open Project in the Quick Start dialog box to open that project, close it out again, close Sonar, start Sonar up again, and see if it NOW shows up as the most recent project.
 
As far as the rest of the things that are frustrating you, I would start by reviewing the download itself of X3.  Did you have antivirus software running during the download?  If so, you might try getting to the download page, then temporarily suspending your antivirus software, downloading X3 again, then comparing the hash values that Cakewalk supplies on the download page against what is in the newly downloaded files.  Make sure they match.  FURTHER, you can also use those same has values to check your ORIGINAL downloaded files, to see if they were properly downloaded.
 
Corruption DOES occur at times during downloads.
 
THEN, I would suggest you review your install of X3.  Did you have antivirus software running DURING the install?  If so, this CAN cause weird problems.  Did you launch the install using the EXPLICIT option of Run As Administrator?  This is different than simply using an account with administrative privileges.
 
Is your Windows up to current maintenance levels?
 
So, please review and respond to the above, and we will begin the process of digging into things, hopefully to emerge with a functional X3d.
 
Bob Bone
 

I know sometimes people say they are an IT guy to add credibility to their posts but you should know,
typically a freeze or hang up is due to bad HD and or Ram or a driver conflict.
I would look their first.
 
if even 50% of users were complaining of freezes I might agree there is a problem with sonar but I cant do that at this time.
the census here has been good.

It sounds possible that you have exceeded Windows' midi device limit. That would lead to lots of confusion when unplugging/replugging devices or switching them on and off, possibly also causing hangs. Also, have you tried a clean reinstall of Sonar?

Assuming windows update is fully up to date (Win8 had some USB fixes for example) then I agree with most of what has been said here. I would lean more towards device drivers and firmware, although I don't know the specifics of your hardware.

I have it on good authority a majority of HDD don't last more than 2 years at the best of outcomes and Power supplies get flakey all the time but I ain't an IT guy!
But you can blame SONAR for this if ya want too!
But it Doesn't seem to worry me
How old is your Hardware?????
 

For me X1 was reasonably solid most of the time but a bear to work with as far as intuitiveness and when it crashed it crashed HARD. X2 was a much nicer workflow for me and rarely crashed but it was glitchy as all fart which made it infuriating to work with. X3 has been all zippety zappety doo dah and a bag of dill pickle chips. Pretty much completely problem free so far (although there are few tests I have not run yet but 95% of my previous problems have disappeared). All this on exactly the same system using all the same hardware/OS/plugs.
 
Sorry you are having difficulties and I don't mean to sound cliche but I'm gonna say there might something else causing your issues. Perhaps the install went badly or you are encountering one of the known conflicts. You should contact support. They are a rather helpful bunch if you can get a hold of them (which is why I call instead of email).
 
Good luck.

May I suggest avoiding connecting and disconnecting USB devices all the time. Especially when Sonar is running. With anything other than a storage device, the registry and drivers are kept on a per port basis and as such you could end up with multiple drivers covering all ports. This is not an issue for storage devices as the USB ports do not remember or store info on these devices.

Also it may be worthy to note that if you plug a device in that the computer then has to recognise, you will find it opens up a new process or starts some CPU activity. If this is done whilst you are working on or currently in a project, you are likely to find high dpc spikes which will manifest in pops and clicks.

I personally think you problems may well lay more in your habits of connecting and disconnecting devices all the time.