Photo Corners headlinesarchivemikepasini.com
A S C R A P B O O K O F S O L U T I O N S F O R T H E P H O T O G R A P H E R
Enhancing the enjoyment of taking pictures with news that matters, features that entertain and images that delight. Published frequently.
Adobe Acknowledges Creative Cloud Desktop Bug
13 February 2016
Late yesterday Adobe acknowledged that the latest release of Creative Cloud Desktop "may incorrectly remove some files from the system root directory with user writeable permissions." The notice, posted by David Kastendick, referred to "the updater" rather than "the update" as the cause of the problem but that may only be a typo.
The issue was first brought to the company's attention by Backblaze, a cloud-based backup service that writes an invisible folder to the root directory of the hard drive. The company discovered that Creative Cloud Desktop 3.5.0.26, released on Feb. 11, deleted that crucial file. Blackblaze has subsequently posted a recap of the issue, which includes a link to Adobe's revised release (version 3.5.1.209).
Subsequently reports of other root directory files, some named with leading spaces, were posted on reddit.
The update itself, which has been withdrawn, featured a new Manage Account menu system and bug fixes.
We installed the update on Feb. 11 under OS 10.10.5 without issue but we don't add folders to our root directory so wouldn't have seen the problem.
For more information see the text of Kastendick's post from yesterday below.
Creative Cloud Desktop on Mac Update Issue
Earlier today we were notified of an issue with an update to the Creative Cloud Desktop application on Mac that we rolled out earlier in the week. In a small number of cases, the updater may incorrectly remove some files from the system root directory with user writeable permissions.
We have removed the update from distribution, and are in the process of deploying a new update which addresses the issue. When prompted for the update, Creative Cloud members should install it as normal.
If you have issues with the update, please contact customer support.
Much thanks to Backblaze for helping us identify the issue.