Here is Why You Should Stay Away from Adobe Creative Cloud

Here is Why You Should Stay Away from Adobe Creative Cloud Clapway

As if you needed another reason to hate Adobe, a recent Mac update has discovered a major inconvenience for the software’s users. By updating the Creative Cloud suite, Mac users can now rejoice in the addition of a surprise gift. This gift comes in the form of a bug and it will destroy all your files without warning. Nice feature right?

Here is Why You Should Stay Away from Adobe Creative Cloud Clapway

IF YOU’RE READING THIS, DON’T UPDATE ADOBE

When users download the latest Adobe creative cloud update (3.5.0.206) and then log into their account, they will be greeted with a nasty surprise. All contents of the first folder listed alphabetically in the root directory will be deleted without warning. Thankfully, Adobe has recognized the error and is making a strong effort to fix it. If you haven’t downloaded the update yet, hold off for now.

BACKBLAZE UNCOVERS DISCREPANCY

Thanks to the heroic efforts of Backblaze, many can be saved from the negative aspects this bug can offer. Unfortunately for users of the data backup services, they have felt the effects of this discrepancy the most. The Backblaze service uses a hidden root folder called .bvol. This folder contains a large amount of user data, which is now wiped out. Thanks, Adobe. If you think you’re safe because you don’t use Backblaze, think again. The folder named “.DocumentRevisions-V100” is the first in the root directory. This folder is used by Mac’s autosave feature and stores all kinds of significant data. Once deleted, the potential for system errors to occur is quite likely.

SOLUTIONS TO THE PROBLEM

While Adobe tries to fix the problem, there are some precautions that one can take. First of all, just don’t install the update. That is probably the easiest solution. If you have and haven’t logged in yet, don’t do it. A world of disappointment will only await you. If you absolutely need access to the software and have installed the update, there is hope for you yet. Start by creating a fake folder in the root directory. Start the name with .a to make sure it starts first in the alphabet. Since the bug deletes the first folder, this decoy should prevent any further damage.