Anderton
For what it's worth, I NEVER use any beta or pre-release software of any kind, from any company, on my main desktop computer that I use for getting actual work done.

This right here ^^^^ is priceless advise.
 
When I know I have a project due or something important, I have waited on the Early releases.
Why take the chance ?
With all this said, Early release 2016.12 is running like a charm here (Windows 8.1 X64) and I have kicked the snot out of it 8 hrs a day since its release.
 
Is it possible your download got corrupt ?
I would remove the Installer from Program Data / CCC /Downloads folder and try to re download.
On the flip side, If you were being serious and have genuine work that needs to be done.. I would roll back and finish it and avoid experimenting / downloading ER's unless you have some free time. Roll back.
That's why the roll back feature was created.
 
Good luck

I watch this forum before I update. That's why I never bought X1 or X2. 
 
I see that this rolling update system will always have this issue. We are headed for a rollercoaster ride of good and bad releases. It used to take a year to find out what the good and bad were going to be. 
I'm going to Stay in October untill this blows over. I usually wait a few releases anyhow. 

chuckebaby

Anderton
For what it's worth, I NEVER use any beta or pre-release software of any kind, from any company, on my main desktop computer that I use for getting actual work done.

This right here ^^^^ is priceless advise.

agreed 100%
 
but it does leave us users in a slightly weird place - like, early access 11 came out literally 1 day before the full release - and look at all the showstopper issues with 11 proper release - what are we to do? how many versions to wait? i wonder if "monthly" is a bit too quick for updates, nevermind learning any new stuff, but for proper QA before release?
 
there's a school of thought that says agile-developed software never leaves beta...

As has been said many times, there is no requirement to immediately update as soon as an update becomes available.

BobF
As has been said many times, there is no requirement to immediately update as soon as an update becomes available.

of course, but then why bother with monthly updates? why no just stick to the "old fashioned" way of a major release followed by a couple of point release updates?

pwalpwal

BobF
As has been said many times, there is no requirement to immediately update as soon as an update becomes available.

of course, but then why bother with monthly updates? why no just stick to the "old fashioned" way of a major release followed by a couple of point release updates?

User choice and flexibility? 
 
Aren't you a Studio One user? 

Suggestion for CW: don't get hung up on monthly releases. It's soup when it's soup.
 
Suggestion for SONAR users: stop the "{month_name} is almost over! Where's the update?!?!?" threads. It's soup when it's soup.

pwalpwal

chuckebaby

Anderton
For what it's worth, I NEVER use any beta or pre-release software of any kind, from any company, on my main desktop computer that I use for getting actual work done.

This right here ^^^^ is priceless advise.

agreed 100%
 
but it does leave us users in a slightly weird place - like, early access 11 came out literally 1 day before the full release - and look at all the showstopper issues with 11 proper release - what are we to do? how many versions to wait? i wonder if "monthly" is a bit too quick for updates, nevermind learning any new stuff, but for proper QA before release?
 
there's a school of thought that says agile-developed software never leaves beta...

In my opinion its kind of a double edged sword. Yes we get newest updates every single month, but when you have a stable version, changing every month can be for some.. a recipe for problems. So im kind of in the middle to be honest. I like the rolling updates myself, however if I were having a lot of problems, I wouldn't .
 
But there always is the roll back feature.
It is really hard to compare an annual release to a monthly one, because with an annual, I agree, it should be tight as nuts+bolts. Monthly, that's always going to be difficult. but as I said, theres a perc with monthly. new features and new fixes.
 
But you know Pwal, its easy for me to say because ive been running smooth almost all year.
I didn't even have any of the Windows 10 issues people were having. (still on Windows 8.1)

As to monthly vs. yearly, think of how many months it took with X3 to nail down all the bugs that were introduced upon its release...I think it took 4-5 months? And some of the fixes caused issues that were dealt with in later updates. With the monthly releases, the good news is that bugs are fixed much sooner. The bad news it that they're also introduced much sooner. There doesn't seem to be a perfect model for software releases. 
 
That said, like Chuck I have not had the stability issues others report, and I'm using Windows 10. Maybe I'm just lucky, or maybe it's because I'm really attentive to the computer environment.

I have no issue with the monthly updates and the early access program.  You can update when a new feature that you want to use comes out or a particular bug that is affecting your workflow is squashed.  You can wait a few days/weeks/months to update or do it on day one.
 
Users should be mindful that early access = OPEN BETA/QA.  If you have a project that has a deadline or something critical, you probably shouldn't update when the early access comes out (and possibly even when the monthly release comes out.)
 
The user is in control here, and that's the best part.