Skip to main content
dv8kiwi
Inspiring
November 19, 2016
Question

Some error occurred during cloud switching - syncing paused, will not restart

  • November 19, 2016
  • 1 reply
  • 2428 views

I keep getting this message briefly every time I sign into Windows 10. "Some error occurred during cloud switching" and syncing fails.

I have no idea what this message means.

The cloud icon has a blue "paused" button and when I try to restart syncing it just gets stuck "syncing" and nothing happens.

The only solution is to quit Creative Cloud, then go into task Manager and close all the instances of Creative Cloud related apps, then restart Creative Cloud.

This is not a useful solution. This is just getting very frustrating.

This topic has been closed for replies.

1 reply

David__B
Adobe Employee
Adobe Employee
November 21, 2016

Hi Dv8kiwi,

Sorry to hear about your difficulties. As a test could you create a new admin user then uninstall and reinstall the Creative Cloud app when logged in under that account? This document explains how to remove the Creative Cloud app. Uninstall the Adobe Creative Cloud desktop application

Also, another test would be try temporarily closing any anti-virus or other cloud storage syncing software (GoogleDrive, Dropbox, etc.) to see if that makes any difference.

Please let me know if these help,
Thanks,

- Dave

dv8kiwi
dv8kiwiAuthor
Inspiring
November 21, 2016

Thanks David,

I have disabled it in the Startup list in Task Manager and launch it manually after Windows starts which works so I'm living with that for the time being. I will try disabling Google Drive One Drive and Drop Box and set CC back to start at some point as a test when I have the time.

Why do I need to create a new admin account? What would be wrong with uninstalling and reinstalling CC in the current account?

dv8kiwi
dv8kiwiAuthor
Inspiring
December 22, 2016

If you highlight over my name there should be a message option which goes to me only


Hello David, have you heard anything back about this? I can now confidently report that disabling Dropbox in startup doesn't stop the problem as I mentioned previously. It is ongoing.