Sharza

I digress - and history has proven that many times. In the event of a stability issue, then yes, an update may fix that. Any update is however a risk to stability, regardless of how vigorous testing the update has been subjected to - but that is not really the subject of the debate here. The point I am making is, I want to be in control of what happens on my system. As far as I see it - that is the main concern for others in the thread as well. We can nitpick the technical details of various client/server combinations, and the attached security implications all we want, but none of that justifies Evernote not adhering to acceptable life cycle and deployment principles. A client workstation is not Evernote domain, and as such it's bad practice to update without confirmation. In my opinion that is not debatable. It would be reasonable, acceptable, and most importantly forthcoming to implement a policy of the last x versions being able to connect to cloud services and sync data. If you are outside that policy, you can use the software, but not sync data online. That satisfies the need for an updated codebase in relation to cloud service security, and at the same time satisfies users demand for control over their own device. It really isn't that hard to reach a reasonable compromise. Being unwilling to do so, but instead muddy the discussion with strawman arguments is not exactly constructive in my opinion.

Hi I'm on the disable auto-update bandwagon. I've read through all the replies in this thread, and sees comments like "where is the problem? Does it not update ok? It should load in the background, etc etc.". While I appreciate being given updates to software and operating system components, I can't but wonder if no-one considers it is a matter of being in control more than anything else. Fact is any update is a risk to stability, and where Evernote - or another affected application or operating system component - being negatively impacted by a software installation, on a personal computer may pose a lesser impact, it is not necessarily the case, and definetely not in the case of a coorporate pc. We do updates in maintenance windows for a reason. I personally update my PC when I see fit for the very same reason. Just to be clear, this is not the same as being security unaware, but rather a matter of careful planning, intended to minimize the risk of data loss and loss of work (and ultimately profit). This is something software vendors should appreciate and respect, and neglecting to do so, is imho a matter of unprofessional conduct. It would be far better, and magnitudes more appreciated, to acknowledge this lacking feature, and plan it for implementation in the near feature, rather than discourage updating the product, and locking customers into the software vendors update regime... we are being troubled enough in that department already, courtesy of Microsoft - no need to join that team. So while it seems we have a workaround, which unfortunately involves editing files, verging on the duct tape scale, I would much prefer an actual option to put updates back under my own control. Just my 2 cents.