New Workshop! Lighting 3 | Advanced Off Camera Flash

News & Insight

Adobe CC Deleting Mac User Data Insidiously

By Kishore Sawh on February 13th 2016

All press is good press, is the old chestnut, but my oh my Adobe seems to be trying to push it for all it’s worth. The past year has been filled with the beautiful, good, bad, ugly, and absolutely heinous. Boundary Warp, updated Bridge, and GPU assistance for Lightroom is all good, but those highs are thrown into sharp contrast with the troughs of a messed up LR import dialogue, broken Liquify tool, and now, possibly the most insidious of them all, the deletion of the alphabetically-first root file in your Mac Root directory.

Yes, this has thus far only proven to affect Macs, and only concerns the latest version of the Creative Cloud Launcher/Installer. The Root directory is not to be confused with the Root User account which simply provides a higher level administrative access. The Root directory is, by default, Macintosh HD, and is the highest level of filesystem hierarchy.


What seems to be happening is that upon installation of Creative Cloud Launcher version, the contents of the very first folder of your Mac’s Root directory is being deleted. It warrants saying that these files are listed alphabetically, so many probably have the same folders being erased. See BackBlaze’s video of the problem in action:

The sinister part of this is that depending on your familiarity with the ‘hidden’ file and root system on a Mac (and it does depend on what OS X you’re running), you may not know what has been deleted, or that anything has been deleted at all. You see, the majority of files and folders within the Mac Root directory are ‘hidden’ from view because the average person will not need access to these files. That, however, doesn’t mean they aren’t important – this isn’t an ‘out of sight, out of mind’ situation. Depending on what your first folder is you could be causing proper damage to your system, and that could mean important data corruption or loss.

The problem seems to have truly come to light much in part due to BackBlaze, who recently found themselves in the midst of another user issue regarding faulty Seagate HDD units. You can see that here. It seems to have been affecting Backblaze users because those users have a root file folder on their drives called .bzvol, which is higher in the alphabet than the folder most people would have which would be .DocumentRevisions-V100. ArsTechnica had this to say:

Many users who don’t use Backblaze (the reporter of this Ars story included) will find the first folder in their Mac root drive is .DocumentRevisions-V100, a folder that stores data required for Mac autosave and Version history functions to work properly. Deleting its contents could have negative consequences. The Adobe bug could also have dire consequences for users who have important folders with spaces in them, since those also assume a top alphabetically sorted spot on the Mac hard drive (which by default is labeled Macintosh HD).



So that’s the bad news, and there is good news. The good news is that since we understand how the problem works, it can be easily tricked, and there is a temporary fix. And in case you were wondering, Adobe is aware of the problem and have halted the release of any more of that specific update version ( So how do you trick it? If you have installed but not logged into the update, you may be able to create a folder that would, alphabetically, precede any of the real folders. Basically, creating something with a lot of ‘a’s in it would work, but Backblaze is assuming the role of jester recommending the creation should be ‘.adobedontdeletemybzvol.’ You would do this by opening Terminal, within the Utilities, and entering the following command:

sudo mkdir /.adobedontdeletemybzvol

This should ensure that it is this file’s folders that get deleted, and nothing useful. Still, the recommendation is – just stay away from that update. That said, Adobe says there is now the release of available which IS fine. Personally, I would wait it out for a week to make sure.

If you want to be able to see your hidden folders, once again turn to terminal and enter the following:

defaults write AppleShowAllFiles YES

Then you must relaunch Finder for the files and such to show up, and they will, though they will look faded. To reverse this command and re-hide the files, use the same command but replace the YES with NO, according to this source (note this is for those running El Capitan).


I hate saying that and I’m quite fond of Adobe generally, but it’s becoming harder and harder to defend them in these instances. This isn’t a virus, it’s a coding issue, and it’s not the first one. With all the benefits to CC, and the quick update to the 3.5.1 version shows how quick it can be, for many people, the trouble could be more than it’s worth. There’s a general dissent now in regards to how people feel about Adobe because many feel like the paid subscribers are being treated like beta testers. I’m still very much in the Adobe corner, though I haven’t been affected by this problem due to negligence that paid off. I truly believe CC is the way forward, and that it will be great, but it’s no longer in its true infancy, so come on Adobe, don’t let the side down.

Sources: Ars Technica, Fstoppers

This site contains affiliate links to products. We may receive a commission for purchases made through these links, however, this does not impact accuracy or integrity of our content.

A photographer and writer based in Miami, he can often be found at dog parks, and airports in London and Toronto. He is also a tremendous fan of flossing and the happiest guy around when the company’s good.

Q&A Discussions

Please or register to post a comment.

  1. Gareth Wignall

    Is this Adobe just showing that is human after all…
    “Its not the mistakes you make that define you! It’s how you act when a mistake is made!”

    Acknowledge, Apologise, Analyse… but above all just get it FIXED!

    | |
  2. Mark Romine

    Nice Adobe! So glad that I have untill now pushed back on updating to any CC products.

    | |
  3. John Cavan

    An update came out from Adobe a couple of hours ago. Apparently I got lucky, or didn’t have the conditions to trigger the delete, but my root filesystem was intact. I really do recommend that people have a backup solution, such as time machine, in the event of failures or other errors. That gives you a recovery strategy, if nothing else.

    | |
    • Eric Mazzone

      Having a backup is all well and good, unfortunately this killed my time machine causing an error that it couldn’t create a particular folder, thus damaging the partition the time machine was on on an external disk. Adobe had better come out with an update fixing their damage to my system!

      | |
    • Bob Keene

      My time machine hasn’t worked for quite awhile! How do you know Adobe broke it?

      | |
  4. Joseph Prusa

    Thanks for posting!

    | |
  5. Thomas Major

    I’m running OS X 10.11.3 on my macbook 15″ Retina with Creative Cloud and have not lost any of my directories in my root directory. FYI, I’m a highend IT professional and have root access to my full system and work in terminal quite a bit, so I’m very familiar with working in the OS. I don’t know if there is a major difference between how CC installs in 10.11.2 vs 10.11.3.

    | |
    • Kishore Sawh

      Hey Thomas, I’m glad to hear. I am still on a 3.4 variant, but as noted in the post, it’s that seems to be the problem, and your experience seems to be affirmation enough that 3.5.1 works fine.

      | |
    • Thomas Major

      Sorry about that, I miss read it. My bad……….

      | |
    • Kishore Sawh

      no no man. I’m by no means a Mac expert, and if anything you’ve given us all some assurance that the newer update has resolved the issue. Cheers Thomas

      | |
  6. Umar Junaid

    Any solution for what happens if the .DocumentRevisions-V100 folder is empty? Now I’m afraid to restart the computer! Haven’t had any error messages yet. Adobe needs to stop using paid users as beta testers!

    | |
    • Kishore Sawh

      Umar, I wish I was more versed as a back-end tech guy to advise you sensibly on what to do. I don’t like to speak about things I truly don’t know, and this I’m afraid, I don’t. My advice would be to contact Adobe directly, and if not, call Apple and see if they can tell you how to do it from a backup file or disk. Best of luck

      | |
    • Umar Junaid

      Thanks Kishore, hopefully a fresh install of the OS is not required. Thanks though :)

      | |
    • Scott Walter

      If the directory .DocumentRevisions-V100 is empty you most likely have not lost any data and restarting the computer will not cause any issues. The .DocumentRevisions-V100 is used by certain applications that allow you to retain a history of document changes and revert back to a previous version if needed. The latest version of your document is safe.

      Not all applications take advantage of document versioning. Some applications that support document versioning including Apple’s Pages, Numbers, and Keynote.

      Hope this helps.

      | |