[running Windows 10 1809]
morning, the CC Desktop launched by itself and entered the endless
spinning wheel state. No way to stop it. After an hour, I killed the
process. Then I tried to relaunch. No way. I tried a repair from the Windows Control Panel and I got this :
which is ridiculous,
obviously. So I tried the AdobeCreativeCloudCleanerTool to uninstall CC
Desktop. It succeeded. I then downloaded and reinstalled Adobe CC
Desktop. The installation succeeded (apparently). But now I'm stuck in
an endless loop. When I try to launch CC Desktop, I get the following
message after a very long time :
I click on Repair, a new installation process begins, the existing CC
Desktop is wiped out and I get again the same message when I relaunch CC
Desktop. So, this time I clicked on Quit and tried the download link
provided in the message. It's a broken link. So, I used the previously downloaded package (from Adobe's site) and installed again.
And now I'm back to step #1.
When will Adobe ever decide to hire capable developers for the CC Desktop App team ?
This tool is a failure from the very beginning. Until now, I could
always find a way to reinstall and have it running properly but this
time, I'm stuck. Following the recommendations found here Adobe Creative Cloud, needed to resolve this problem, is missing or damaged didn't help in anyway. Using other tricks that had helped previously didn't help either.
Very frankly, is it that difficult to write an installation program that works ?
I eventually had to restore my system to the state it was in before Adobe CC Desktop updated itself yesterday. The previous version apparently works normally but now gives me no choice when I launch it: update to 4.9 or Quit. Updating brings me back to the Quit / Repair endless loop described above (I had no problem with the previous version).
I'm not alone with these long lasting problems. This should now stop. We need a way to update PS and LR directly and to get rid of CC Desktop. I have started a discussion about this issue here :
I upgrade all adobe software from Adobe Creative Cloud which has a dropdown menu and tells me which apps need updates.
This sounds like a virus or a possible attack upon a pirated version of the Adobe software.
What is Desktop? Never heard of that.
I know about Adobe Creative Cloud as a central app that basically works as a licensing system. So its no wonder you are geting tbd loop. If you are upgrading via the app then goimg to adobe cc and it tells you you need to update ypu are erasing in a loop.
Registry errors are going to persist.
I use a mac for this reason.
When i used a pc running win10 i ended up having to wipe the entire system. Reinstall via Microsoft then Adobe
Especially since you are getting loop errors
I would ask for support from Adobe
You are a subscription based model?
Or us this a serial older version?.
Again since the subscription model i have no more issues that are not handled or fixed via tghe Adobe Manager or Adobe Creative Cloud app or applet
Good luck and post your solution
The loop makes me think it's a hack because its looping and asking you with no choice to update to 4.9 even when you revert to earlier stable state. That means you are returning to a state when an operation is bugging you into the loop again
Wipe and clean
The latest news about this issue....
If I fully disable the Windows UAC, that is, if I set HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System | EnableLUA to 0, Adobe CC Desktop starts and executes normally. However, this has immediate side effects : Lightroom then crashes immediately upon startup and Photoshop misbehaves (it no longer loads extensions and obviously no longer reads all its preference files). As soon as I reset HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System | EnableLUA to 1 and reboot, Lightroom and Photoshop behaves normally but Adobe CC desktop returns to the Quit/Repair loop described above.
What on earth have CC Desktop, PS and LR to do with UAC ?
Obviously, this indicates yet another permission problem. Not a surprise. On many systems, PS, PSE and sometimes LR cannot run when not launched as an administrator. Also, this indicates that the CC desktop installer is doing things with permissions when running (that's probably why it’s not possible to install from a non administrator account). Since I had to kill the process after one hour because the update failed, some permissions probably were not restored to their initial state. Unfortunately, reinstalling CC doesn’t fix this and since I have no indication about which permissions have been changed, I’m stuck.
This is not the first time that the CC desktop installer shows such an unexpected and undue behavior. Another recent issue demonstrated that the CC installer was killing explorer.exe without any warning (search for “explorer process” in this thread : https://feedback.photoshop.com/photoshop_family/topics/error-183-when-updating-cc-desktop-from-the-a... ).
Now that the problem is narrowing down to this permission issue, I’d like to have more information about what is done by the installer and what permissions are required to successfully install and run CC, LR and PS (online documents about this are not enough). Obviously, the installer is not taking into account all possible configurations regarding UAC.
I have a message to Adobe : please leave my system alone. Installing apps like LR, PS and the CC Desktop app should not require such complex and undue manipulations. The CC Desktop app appears to be unnecessarily complex, very unstable, extremely buggy and implementing very questionable programming practices. A full re-design is in order, I think. Actually, most of us (photographers) don't need it. Allow us to update and use LR and PS like normal applications, check our subscription by whatever (simple) mean you want and that's it.
On my system, I found 2 copies of AdobePCBroker :
C:\Program Files (x86)\Common Files\Adobe\Adobe Desktop Common\IPCBox\AdobeIPCBroker.exe (version 126.96.36.199)
C:\Program Files (x86)\Common Files\Adobe\OOBE\PDApp\IPC\AdobeIPCBroker.exe (version 188.8.131.52)
By default, Creative Cloud is trying to launch the one in IPCBox. I renamed it and deleted the corresponding file in \Windows\Prefetch. Then I launched Creative Cloud. This time it used the version in PDApp and ran normally. Also, LR and PS are now also behaving normally again and both processes are terminating immediately when exiting LR or PS. Until I applied this fix, they were both waiting on AdobeIPCBroker and then exited after a timeout of 3-4 minutes (reported here : https://feedback.photoshop.com/photoshop_family/topics/ps-bridge-and-lr-processes-no-longer-terminat...).
Why 2 copies of AdobeIPCBroker ? This is rather inconsistent. Again, I think that Creative Cloud has grown overly complicated and things appear to slowly get out of control.
While investigating the case, I could observe that Creative Cloud is a very intrusive mechanism running a lot of processes even when LR and/or PS are not used, creating a lot of log files (why not an option to disable this ?) and constantly transmitting data to the Adobe servers at Amazon. I don't need this. I don't want this. Unfortunately, there is no way to stop AdobeIPCBroker. This was possible in the past but now, renaming the executable just generates a lot of trouble.
I'm working with PS and LR locally and I'm not interested in any Cloud activity. So, please Adobe, leave me alone with all these background processes and data transfers. I have been patiently waiting for bug fixes since years and I remained a loyal customer. I have been trying to fix the current issue since more than one week. This is too much. Now I'm seriously considering switching to another workflow. DxO Photolab + Affinity Photo would certainly be a good choice, even if I could miss some Lightroom features.
This morning I launched Adobe CC Desktop and it told me that 1) updates were available for Adobe CC Desktop itself and 2) that Photoshop also had an update waiting. I started with the Photoshop update which failed with error 183. I then tried to apply the CC Desktop update which failed with error 184.
OK. I cleaned up CC Desktop with the Cleaner Tool and reinstalled. But the version installed when downloading the installer manually is not the latest. So, when run, it immediately asked to apply the update and guess what, error 184. A new endless loop has been invented. Also, I had to apply the AdobeIPCBroker workaround described above to get CC Desktop running.
Once I got CC Desktop running (but still not updated), it told me this time that Photoshop was up to date. So, either the update process reported a failure but actually succeeded OR this was just an error and no update was available. I'll never know.
IMHO, the correct decision about CC Desktop is to send this crap code to the garbage can and to write a new tool to replace it (I guess a new development team should be formed to achieve this). We do need a more simple and stable way to update our Adobe applications. We don't need that useless beast.