Skip to main content
Known Participant
June 19, 2014
Answered

Autosave to Creative Cloud

  • June 19, 2014
  • 46 replies
  • 50761 views

I cannot add autosave to Creative Cloud 2014, get an error message when checking the box on preferences Auto Save - "Savie backup project to Creative Cloud."

Error message:

"Saving backup projects to Creative Cloud requires a Creative Cloud Files directory. Please install the Creative Cloud desktop application on your computer to enable this feature."

Choice to use Creative Cloud then greys out.

However,  I do in fact have Creative Cloud installed on computer and do in fact have a Creative Cloud Files directory.


Thanks in advance for any help you can provide.


-James Edmunds

New Iberia, LA


[Please choose only a short description for the thread title.]

Message was edited by: Jim Simon

This topic has been closed for replies.
Correct answer SK321

The workaround of creating a folder for each project in my Creative Cloud Files folder, then using that folder as the autosave folder for the project I'm working on, is currently working for me.  It would be nice if they could get the integrated CC autosave fixed once and for all, though.

46 replies

December 3, 2015

This was working initially on the new version, but now I'm having the same problem as before. Uugghh!!

Has anyone else experienced this problem?

turnleftkr
Participating Frequently
December 1, 2015

Has this been fixed in the new update or are we still SOL?

Legend
December 2, 2015

Working for me.

Participating Frequently
December 2, 2015

Working for me.

How did you get it to work for you?

chrislohar
Participant
October 14, 2015

I'm having the same problem. CC 2.3.0.151 and PP CC 2015.0.2 release. OSX El Capitan v. 10.11

I save the files to their appropriate project folders on various harddrives. And I keep the autosave files in the "same as project" folder. I don't want to create an autosave directory in the cloud. I want to create a backup directory in the cloud.

Is this solved yet?

Participant
October 11, 2015

Nearly bought a new macbook today on the back of this feature, so glad I didn't bother!

Participating Frequently
September 14, 2015

Same problem here!

Edited by Kevin Monahan. Please see community guidelines for allowed content.

Participant
September 12, 2015

I have a better workaround for anyone who isn't afraid to edit their Windows registry.  Yes, it's possible that you could screw up your whole system by editing your registry, but on the other hand you could get electrocuted while changing a light bulb.  Just be careful.

Thanks to the wonderfully useful utility Sysinternals Process Monitor, I was able to determine that Premiere Pro is looking to find your Creative Cloud folder path in the registry key "HKCU\Software\Adobe\CreativeCloud" in a string entry named "CloudFolderPath" that does not exist.  When I examined the other entries in that registry key, I found one called "ActiveCloudFolderPath" which suggests to me that the Creative Cloud developers changed the name of the entry and the Premiere Pro team didn't get the memo.

Anyway, if you add the missing string entry "CloudFolderPath" and set it to the same folder as "ActiveCloudFolderPath" it solves the problem.  Undoubtedly, if you were to change your Creative Cloud folder location afterwards, you would need to remember to update this entry manually to match, since only the "ActiveCloudFolderPath" is going to get updated automatically by the Creative Cloud program.

Now, this comes with the usual disclaimers: try it at your own risk, I'm not responsible if your mouse explodes, etc.  It solved the problem for me, and as someone who has been involved with IT and programming since the eighties, I can't see any way that adding this entry would cause any major problem -- and if it did you could certainly solve it by removing it again.  If Adobe releases an official update that solves this issue, it might be best to go back in and delete the key before installing it, but as long as it's pointing at the correct folder even that would be unlikely to cause a problem.

irinal55445615
Participant
September 20, 2015

Thanks for this. It solved the problem for me.

SK321
SK321Correct answer
Inspiring
September 10, 2015

The workaround of creating a folder for each project in my Creative Cloud Files folder, then using that folder as the autosave folder for the project I'm working on, is currently working for me.  It would be nice if they could get the integrated CC autosave fixed once and for all, though.

Kevin-Monahan
Community Manager
Community Manager
September 10, 2015

Hi SKendall,

The workaround of creating a folder for each project in my Creative Cloud Files folder, then using that folder as the autosave folder for the project I'm working on, is currently working for me.  It would be nice if they could get the integrated CC autosave fixed once and for all, though.

Nice workaround. Thanks for posting that. I'll add this info to the bug.

Regards,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
cowboycoffee
Participating Frequently
September 1, 2015

Same problem here. Making me crazy. Please fix this!

Participating Frequently
September 3, 2015

I too am having the same problem. And when I go try to see if my files manually moved to my creative cloud folder are live on the web I get this message....

Just moved over from FCP 7 and guess i am still learning that every rose has its thorn... (go ahead, click it, I dare ya...)

giorgioc84379275
Participant
August 31, 2015

I'd expect the cloud aspect of a product named creative cloud to work better. Oh well.

Nice one, adobe.

Participant
August 24, 2015

Any update on this?  Running Yosemite 10.10.3 and I've been having this backup issue for a while.  I "think" I've tried everything mentioned here so far.  Shame to have lost my presets...