CC Desktop app - Stuck in an endless loop

  • 1
  • Problem
  • Updated 1 month ago

[running Windows 10 1809]

Hi,

This 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 :

CCdesktop_sucksjpg

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 :

CCdesktop_sucks_2jpg

If 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 ?

Photo of Patrick Philippot

Patrick Philippot

  • 520 Posts
  • 157 Reply Likes
  • disgusted

Posted 3 months ago

  • 1
Photo of Geoff Walker

Geoff Walker, Champion

  • 223 Posts
  • 47 Reply Likes
I get this on my Macbook about once a week... the CC app has serious issues.
Photo of john beardsworth

john beardsworth

  • 1231 Posts
  • 319 Reply Likes
Photo of Patrick Philippot

Patrick Philippot

  • 520 Posts
  • 157 Reply Likes
Not exactly the same post because it's a new problem. Please leave the moderators alone.
Photo of john beardsworth

john beardsworth

  • 1231 Posts
  • 319 Reply Likes
Moderators, please note, it's an edited cut and paste.
Photo of Patrick Philippot

Patrick Philippot

  • 520 Posts
  • 157 Reply Likes
OK. Removing all the Adobe stuff (as described elsewhere) and re-installing everything didn't solve the problem but generated new ones. Since the new version of CC Desktop (4.9) still doesn't work, I could not re-install the latest version of  LR.

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 :

https://feedback.photoshop.com/photoshop_family/topics/bypassing-adobe-cc-desktop

Thanks.
Photo of Singleton

Singleton

  • 7 Posts
  • 1 Reply Like
When you say Adobe Desktop CC what are you talking about?,
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

Paranoid yet,?

Wipe and clean
Photo of Patrick Philippot

Patrick Philippot

  • 491 Posts
  • 143 Reply Likes
Adobe CC Desktop = Adobe Creative Cloud App for the Desktop. The central app you mentioned above. Which means I'm running CC versions of LR and PS, not legacy versions. My OS is protected against viruses. As a former developer/system engineer, I'm not inclined to use pirated versions of software. Regarding support, I'm already directly in touch with the development team. No, I'm not paranoid and you shouldn't improvise as a psychiatrist. As mentioned above, the "wipe everything Adobe, cleanup and reinstall" doesn't work. This approach is time consuming, has many side effects and eventually doesn't help.
Photo of Robert Somrak

Robert Somrak, Champion

  • 352 Posts
  • 116 Reply Likes
My OS is protected against viruses.
That doesn't mean you can't get a virus.  Virus checkers do not provide 100% protection.

 As mentioned above, the "wipe everything Adobe, cleanup and reinstall" doesn't work
As Singleton suggested its probably time to do a complete wipe(Reformat Disk, reinstall OS and all software from scratch), not just Adobe.   You have had these issues for 3 years from your other posts.  Your system collects a lot of cobwebs and a reformat cleans these up. It also seems to speed things up.  Its not fun but I do this at least every 2 years on my Mac.  If your data storage methods are well planned it is fairly easy to restore everything.

  Note:  It is a lot easier and quicker to do this on my Mac than on my Windows machine.  My Windows machine is not used much for internet or email although it is connected to the internet so I only reformat it if needed.
(Edited)
Photo of Patrick Philippot

Patrick Philippot

  • 491 Posts
  • 143 Reply Likes
Hi,

Reinstalling the whole system from scratch just to have the privilege of being able to update PS and LR from that useless tool while everything else on my system is working fine ? No, thanks. This would take a whole week with no insurance that CC Desktop would work afterwards. At least, I can run PS and LR for the moment.

A virus that would hit only Adobe CC Desktop ? No. Anyway, my system is clean, believe me. I'm running a lot of applications and everything is working nicely.

Thanks.
Photo of Patrick Philippot

Patrick Philippot

  • 520 Posts
  • 157 Reply Likes
Hi,

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.
Photo of Patrick Philippot

Patrick Philippot

  • 520 Posts
  • 157 Reply Likes
Still investigating this issue and I might have a fix...

On my system, I found 2 copies of AdobePCBroker :

C:\Program Files (x86)\Common Files\Adobe\Adobe Desktop Common\IPCBox\AdobeIPCBroker.exe (version 5.5.1.11)
and
C:\Program Files (x86)\Common Files\Adobe\OOBE\PDApp\IPC\AdobeIPCBroker.exe (version 5.5.0.66)

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.

(Edited)
Photo of Patrick Philippot

Patrick Philippot

  • 520 Posts
  • 157 Reply Likes
And the story continues...

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.
Photo of Patrick Philippot

Patrick Philippot

  • 520 Posts
  • 157 Reply Likes

Helping myself seems to be the only way to fix problems when using Adobe products. I eventually found out why the built-in updater of CC Desktop is failing with error code 184. It is trying to update files that it is indirectly using itself. This time, it was CCLibrary.exe that was indirectly loaded when CC Desktop was launched. So, the built-in updater fails because it is trying to replace an executable that it itself launched. And then it issues an error code 184 telling me that the executable that it wants to update is in use by another process (which is actually itself). Kind of a self generated chicken-egg problem.

After killing this process and clicking on Retry, CC desktop could update itself normally.

1. The installer should be able to clearly indicate to the user which file could not be replaced.
2. It should, like many other installers do, try to terminate the offending executable and try again to automatically replace it.
3. Note that others have mentioned similar problems with other files. So, my case is just an example. The actual error source can be determinated by running the LogCollector tool and looking at the contents of Install.log.
4. Diagnosing such situations is something that is possible only for power users, developers or software engineers. The designers of CC Desktop seem to be unable to imagine how confusing this is for non computer savvy users when they are facing such a situation.

 

Another indication that the design of this app is flawed. Time to replace it.