Adobe CC Bug Erases Data on Macs (UPDATED)

A bug in a recent Adobe Creative Cloud update is currently deleting a folder on the root drive (Macintosh HD, by default) of Macs upon installation. This issue is affecting Backblaze users disproportionately due to the fact that the bug results in the deletion of the contents of the alphabetically first hidden folder on the root drive, which is often the folder ".bzbol" for Backblaze users.

Of course, if you are not a Backblaze user, the bug can still delete files within whichever hidden folder in your directory is first alphabetically, which may or may not have extremely undesirable consequences on your system. For some readers, the first hidden folder may be one called, ".DocumentRevisions-V100," the files within which are necessary for proper file version mapping and recovery functions within OS X. Whether or not there may be a solution that undoes the deletion (or rather, replaces these files) is still unclear. Adobe said they have stopped distribution of the update that causes this issue, which began with version 3.5.0.206.

Backblaze posted a video (above) showing the deletion of the files, but also shared a temporary solution, which naturally involves creating a hidden folder in the root directory that comes before the one called ".bzvol". They have managed to fit a small bit of humor into their fix, but they undoubtedly find little of this situation funny, given the impact it's had on their users.

Temporary fix:

To correct this, please do the following:

Open Terminal, which is found in Utilities under your Application folder.

Copy and paste the below command, pressing enter after:

  • sudo mkdir /.adobedontdeletemybzvol

After you press enter, you will need to enter your Mac Admin password and hit enter to create the folder. 

This should protect your .bzvol folder from being emptied by Adobe Creative Cloud, as the new folder is now first alphabetically. 

 

**If the bzvol folder has already been wiped, you will also have to follow these steps after creating the new directory.**

1. Click the Backblaze icon and go to preferences.

2. Click the Settings button.

3. Check both boxes for the unplugged and plugged in internal Mac HDs. 

4. You may receive a message that one drive will replace the other -- this will not affect your backup with this issue.

5. Click OK

This should resolve the bzvol error and allow backups to resume, as scheduled. 

 

**If you have any hidden folders alphabetically before .bzvol, you may want to restore them from Backblaze.**


The latest 'beta' installer of the Backblaze software has been updated to create a folder named '/.aBackblaze/ at the root of your hard drive as a decoy folder. Running the latest installer will also prevent this issue, like following the above steps. The installer can be downloaded here: http://files.backblaze.com/

 

[via ArsTechnica]

 

UPDATE: Apparently, Adobe has resolved the issue with a new CC release. Of course, this will not fix or reverse the deletion issues in any way. The new version will not, however, cause the issues to begin with for those that are lucky to not have been affected.

Log in or register to post comments

43 Comments

Previous comments
Adam Ottke's picture

On many users' systems, the first folder there is one that messes with document versioning/autosave-type features built-in to OS X. So you might want to check that. You can show your hidden folders (and then look at the Macintosh HD) by following these steps (just be sure to undo it with the directions listed afterwards -- you don't want the hassle of constantly staring at all the hidden folders on your system):
http://www.macworld.co.uk/how-to/mac-software/how-show-hidden-files-in-m...

This will at least tell you what that first hidden folder is so you can know if it's something important. A simple Google search helps a lot if you don't know what that folder is once you see it...

Umar Junaid's picture

What do you we do if that folder's contents have been deleted by the CC update?

Adam Ottke's picture

#1, hopefully you have a backup and can restore the content that was there. But if you don't, the first step would be to find out which folder had its contents deleted on your system (and if this happened to begin with at all).
Also, you could save yourself time by confirming the version of CC that you have. If your system hasn't been updated for some reason, you might not have any such version that's causing this problem.
Once you find which folder's contents has been erased (if applicable), you can do research to see what was supposed to be in there. In some cases, these files might have been temporary files that are not too important and that will automatically be written again. In other cases, they might be system files that are the same across all systems, but that you'll have to put there yourself somehow (maybe with a reinstallation of OS X???). In other cases, it might be data that you just can't get back without a good hard backup... So it really varies for each user.

Umar Junaid's picture

Thanks Adam. The first folder was unfortunately the .DocumentRevisions-V100 folder. Haven't had any errors pop up yet, and my backups are mostly my pictures and data, not the system files.

Adam Ottke's picture

Glad to hear it (sort of, since I'm assuming you still had the problem). Were there files in there? In any case, that's the way it likely is for most Mac users. Still, I would recommend you save your documents often and continue backing everything up, since that folder contains files used for autosave/versioning as far as I have read (just be careful until you can be sure everything is working as it should). Sounds like you, at least, could get out of this without much issue. Hopefully that's the case indeed.

As someone who does a lot of hiring out of the same pool of candidates as Adobe (they're just up the freeway from us, along with Oracle), I am not the least bit surprised. You could get away with less than perfect developers or QA, but not both.

Ralph Berrett's picture

And how is the cloud better?
Adobe it's not a job.
It's a joke.

Geoffrey Badner's picture

I'm a Photoshop beta tester and communicate off and on with the guy in charge of PS's user experience (he designs where all the buttons go and how they work). I sometimes get pre-release versions to "try out". Anyway... from what I've heard through him, I'm not surprised in the least that this has happened with Adobe. Lots of smart people there, but it's also kind of a sh¡t show over there.

Why the Hell Adobe is deleting any Folders in the root node? And of course, why there is not a Shitstorm against Adobe in cause of this fatal Fail? Next damn Software piece, that has to be updated only every second Release.

Phil Stefans's picture

And what you hear is the sound of 100,000 users turning auto-update off...

Spy Black's picture

Although I know it's easier said than done, I think the graphic arts industry has to break this dependency on Adobe. They have a monopoly in graphic arts, and of course we are all contributors to that. The CC suite has become a production landmine field. Although this one is pretty bad, even the lesser problems with the CC suite are roadblocks and impedance to our day-to-day production routines.

I think that we need, on an individual and collective level, to find real-word alternatives to the Adobe suite. Some of those options already exist, we need to just push ourselves out of our comfort zone and start to integrate them into our production pipelines. I know we all have work to do, and this industry demands work done yesterday, but it really does need to be done. We need to free ourselves from this software heroin.

I have been looking at this on my own production routines, and trying to figure out what works for me. As a freelancer it's a bit harder because I have to show up to places knowing Photoshop because, after all, it rules the industry. But if I can work from home and all I have to deliver is a tiff or a jpeg than the game changes.

I know it's different for every person, but really, think about it. Our dependence on Adobe really needs to be expunged from our production lives.

Adam Ottke's picture

At the end of the day, it comes down to whatever is the most efficient/saves us the most time/is the overall best solution. That, still, is Adobe's CC suite (in most fields....). When you consider switching, there's just nothing with the same combination of features, the same level of advanced algorithms that really do work, etc... That's tough work to get right, and they do it 99% of the time. Then this happens, and we all get upset (again, rightly so).

We can get upset at technology every day. Every day SOMETHING doesn't work. But the question is, would we be more productive without it?

So it bugs us, but for the most part, we can deal with it, and so we do. And of course, the world in which we live now demands a new level of efficiency based on the availability of this technology. So there certainly is a limit to how many bugs/nuisances can be in be in the way before it makes sense to switch. But it's still hard to say Adobe doesn't provide the best product in most cases (at least the best integrated suite of products...but sure, you could go C1, FCP, etc., any day....but that still leaves others stuck on Illustrator, InDesign, etc.).

Jason Ranalli's picture

You can expect more of this in the future unfortunately.

As someone who has worked in software for nearly 20 years I can tell you this kind of stuff starts to become the norm when you move to a highly iterative model for development and subsequent production deployments.

Why? Because you no longer are going through full regression testing suites since your releases are considered to be of less scope than the mega-monster full version releases Adobe used to have. Instead your developers and QA end up cherry picking the scope of focus and testing and are more likely to miss the mark on collateral damage type items.