I have a major bug with the latest version of Sonar Platinum. I went to roll it back and -- to my surprise -- the rollback versions are NOT listed in simple, dated, reverse-chronological order. 

They appear to be alphabetical. 
 
Why can't I see the rollback versions in reverse-chronological order by release date? See what I"m talking about here:
 
[image removed]

I don't even know, based on this list, what the last version would be to roll it back to. 

This is a major, urgent, life-stopping software-failure for me now and it would REALLY help to know the chronological date-order of the software releases when rolling Sonar Platinum back.
 
edit: image removed - sc

Also, I would usually call Cakewalk and ask -- 
 
Cakewalk eliminating phone support for Sonar Platinum does not help in this situation. 

It's not really that cryptic. The rollbacks are listed chronologically. The oldest ones are on the top, the most recent ones are at the bottom. FWIW there is no preference for selecting reverse chronological order. The first update is listed first, the second update second, etc.
 
You're confused because in 2015, updates were named after towns in Boston, in alphabetical order (e.g., Allston preceded Braintree).
 
As to the numeric ones, 2016.03 precedes 2016.04, which precedes 2016.05, which precedes 2016.06, etc. etc. Based on your screen shot, the most recent update you can roll back to is the last one listed (2016.07).
 
Also you might want to give some details on your "major, urgent, life-stopping software-failure" because there might be a simple solution.

They are in chronological order, but reverse would be nice too.

tayzonday
 
I don't even know, based on this list, what the last version would be to roll it back to. 

First off, open the current SONAR About box. You will see a version there (2x.x.x.xxx).
 
Secondly, in the list you showed if you notice the top of the list starts with Alston (21.0.1.254) and proceeds thru 2016.09 Update (22.9.2.42).
 
Those numbers (2x.x.x.xxx) get prgressively higher with each release.
 
So your About box may show something greater than 22.9.2.42 and you'll want to select the next lowest number you want to roll back to.

Two people beat me to it while I was typing. DOH!!!
 

Please remove the serial number from the image in the initial post. For now, I am removing the link.

Anderton
Also you might want to give some details on your "major, urgent, life-stopping software-failure" because there might be a simple solution.

Please do give the users here a detailed account what is not happening on your system.

tayzonday
This is a major, urgent, life-stopping software-failure
 

  
Sorry just cleaning up some coffee off my keyboard..
 
Im sorry for your troubles. but just check the version your using now and rollback to the previous.
good luck.
 
 

chuckebaby

tayzonday
This is a major, urgent, life-stopping software-failure
 

  
Sorry just cleaning up some coffee off my keyboard..
 
Im sorry for your troubles. but just check the version your using now and rollback to the previous.
good luck.
 
 

A Sonar project file I use to record for an urgent-turn-around client would not open -- nor the autosave version -- nor prior versions of it.

Fortunately, I don't really rely on the VST FX signal chain on that track to process my vocals as much as the built-in DSP in my RME UFX interface . . . and I recently saved a track template of the track I used to record on with its "optional" VST FX chain. Adding that track template to a new project caused Sonar to crash.

I traced the problem down to a situational incompatibility between Sonar's latest version and Acon Digital's "Deverberate" plugin. As soon as I disabled that DLL, the track template I saved worked in a new project and I was able to deliver to the client today. 

I still have an old / corrupt Sonar project file that isn't opening, but the immediate disaster (e.g. failing to deliver for a client who needs 100% reliability) was averted.