Hi, Not only this bug still has not been fixed in version 9 after all these years but things now appear to be worse than usual. After installation, I found myself with hundreds of files with their metadata status allegedly marked as "not saved" which is plain wrong. When using the usual trick that temporarily fixes the problem (Ctrl-S, then Read Metatadata from file), I had to "read the metadata from file" multiple times for some of these images before the metadata status got the correct value. And as usual, the status returned to "not saved" for some files after a few seconds. I regret that the developers of LR have not enough self-esteem and pride to definitively fix this infamous bug lasting since the early versions of LR and disturbing the workflow of many users. I personally would be ashamed of this. ... View more

I totally agree. I just found gigabytes of useless temporary files in the above mentioned folders that should have been cleaned up after installation. This is very bad (lazy) programming practice. Adobe, you're not at home on my system. ... View more

By the way, the last two updates of PS are for MacOS only but under Windows, the whole thing has been reinstalled twice just to keep the version number in sync. And the second update failed with code 183, a classic error that survived the "re-design" of the CC Desktop App. How about a simple patch operation on the version resource of the executable ? ... View more

I agree that the development team responsible for the CC Desktop app disaster (whatever the version) and all the update machinery should be sent back to school and replaced with a more efficient team. ... View more

To uninstall the current version of CC Desktop, you could try this tool : https://helpx.adobe.com/creative-cloud/help/uninstall-creative-cloud-desktop-app.html I also had this sync problem between the app and the web page. After running the current version of CC Desktop, you could try to refresh the web page. This usually cures the update/open vs. get issue. Anyway, they have obviously replaced a buggy app with another bug nest. ... View more

Hi, The new app is actually a tiny web browser showing the contents of this page : https://creativecloud.adobe.com/apps/all/desktop . It's exactly the same thing and you can manage and update your apps from this web page. So, updating the CC Desktop app itself is not absolutely necessary. ... View more

> Try resetting your Photoshop preferences, which you can do under the General tab in Photoshop preferences. Which seems to be difficult since Negui14 told us that PS closes as soon as it is launched. Negui14, try to press and hold Alt+Ctrl+Shift (Windows) or Option+Command+Shift (Mac) as you start Photoshop. Maybe PS will have enough time to reset the Preferences before crashing. ... View more

Did you try the link I gave you above ? It's not a link to a dmg file but to a web page that is the exact replica of the new CC Desktop app (actually, things work reversely). ... View more

Oooops! There was a problem with that page in my browser (I should have a look at the cache). On the other hand, AdobeCreativeCloudCleanerTool is apparently the same as before. ... View more

> I guess you're using Windows Sorry ! But the suggested workaround should work as well. ... View more

Hi GilesHicks,   The tools mentioned above cannot work since they are older than the latest version of CC Desktop (v5). However, this "new version" is merely a lightweight interface to this web page : https://creativecloud.adobe.com/apps/all/desktop . So, if uninstalling from the Control Panel (I guess you're using Windows) doesn't work, just go to the page mentioned above and you should be able to update your apps. Actually, there's no "new version" of the CC Desktop app. The new Creative Cloud is just a mini app that opens a minimalist browser that brings you to that web page.   Note that the web thing doesn't seem to work that well today. Camera RAW no longer appears in the app list and I had to refresh it multiple times until it consented to list the apps installed on my system. ... View more

Thanks all for your remarks. However, as I mentioned above, the 32-bit version of Creative Cloud.exe is just doing one thing : it launches the 64-bit version and then immediately exits. Also, I don't see what plugins (which plugins for which app ?) have to do with the Creative Desktop app.   So, the only reason I can see for the existence of this 32-bit tiny program is when the user of an old 32-bit app uses the "Check for updates" menu, which generally results in launching the CC Desktop app since the old Application Manager no longer exists. But the installer should be able to detect that no 32-bit Adobe app is installed on the system and therefore avoid to install unnecessary code.   If absolutely needed, creating a hard link should be enough. ... View more

Thanks, the forum is back to normal now, that is, it behaves as terribly as before but without the slowness and without the errors mentioned above. ... View more

Should be rolled out in France today but I'm unable to download the new app. ... View more

Where did you get this information ? Thanks. ... Never mind. Got it! ... View more

> A better solution would be to eliminate the quick reply and add the ability to quote a post. Absolutely. This would be the first step toward making this incredibly bad code a decent forum software (however I doubt there's something that can be done about it). ... View more

> Very frankly, no I'll try to explain this statement...   By using some debugging tools and by looking at the log files, one can determine which files are causing the installer failure. In your case (and this time), the CoreSync_xxx DLLs were involved, probably because they were loaded while the installer was trying to replace them. As I mentioned above, I had the same problem lately, but this time it was CCLibrary.exe that I had to kill before the update could succeed. There's no need to open a remote debugging session with 4 engineers to obtain this information if you have some development or system knowledge. This is not the problem anyway.   Fixing the problem is understanding why we are regularly encountering such situations : files or code modules that have to be replaced by the installer and that are opened or loaded by CC Desktop itself or by a related Adobe service. This is not an uncommon issue for installers but usually there are 2 ways this problem can be worked around :   1. The installer detects that the files/code modules that have to be replaced are currently opened/loaded or running and it asks the user to close such or such program or tries to do this itself (and politely informs the user about what it is about to do).   2. If this can't be done, the new files are registered for a boot time move and the replacement will be made at the next reboot before any program has a chance to use these files.   The CC Desktop installer obviously excludes option #2. But it is unable to handle correctly a situation where a file needs to be replaced while it is in use. Instead of giving information to the user about that, it merely fails, displays an error code and that's it. Fend for yourself. Moreover, when the files that have to be replaced are used by the explore.exe process (probably because they are extensions of the Windows Explorer), the installer merely kills explorer.exe without any warning instead of registering the necessary boot time move. Which is absolutely unacceptable and dangerous for many reasons.   Since an update is not supposed to always replace the same files, the probability for the "fix" they suggested to you this time to work again is low. I have seen reports where the replaced files had nothing to do with those mentioned above. So the problem is repeating again and again. Until they decide to properly handle these replacement issues, the problem will last. ... View more

Also, maybe they switched to a new version of SQLite. ... View more

> Adobe seems to have a handle on it.   Very frankly, no. The first reports about these 183/184 error codes appeared 3-4 years ago. They have never admitted that there was a problem and most often, the only answer has always been uninstall everything Adobe/cleanup/reinstall. The problem is always on the user's side. Despite many suggestions, no effort has been made to make identifying the error cause easier. For example, error code 183 means that a file is currently in use and cannot be replaced. Is it difficult to indicate which file is in use and by which process ? No. Any skilled developer can do that. This would make solving the problem much easier. No way. Moreover, these errors may or may not appear depending on what other Adobe processes are currently running. Since there are a lot of Adobe processes that are totally out of user control, you can't do anything about it. Just undergo these time consuming issues.   Again, do no expect any permanent fix for these issues. Many users are not hit, many are. The bugs are there for everyone but they may or may not appear depending on how you are using the software. I insist, the design of this tool is flawed and it should be replaced. Actually, I'd prefer to be able to live without it. ... View more

Hi, The catalog status control now seems to be made another way : - When opening the catalog with LR, 2 files are created : <catalog_name>.lrcat.lock and <catalog_name>.lrcat-wal. Both files are deleted when LR exits. - When opening the catalog with an SQLite manager (SQLite Expert Personal v5 in my case), 2 files are created : <catalog_name>.lrcat-shm and <catalog_name>.lrcat-wal. Both files are deleted when SQLite Expert exits. Contrary to what happened earlier, I can no longer have the catalog opened in both LR and SQLite Manager simultaneously. So I guess that the lock is now the -wal file. ... View more

Hi J_Isner,   > They clearly knew how to fix the problem. This is not "fixing the problem". It's working around a bug in the code. Next time, you'll have to rename other files or kill such or such process. The last time I got an error 184, I had to kill CCLibrary.exe. I didn't have to rename Coresync_xxx.dll. And the next time, this will be another problem. This program is totally out of control. ... View more

> After the repair, a defunct CC window pops up displaying only a header line and a spinner. The application can only be terminated via Task Manager.   Please also note that if you wait enough before killing the process, you'll get the Quit/Repair window that I described in the first thread mentioned above. If this is the case, you are in the very same situation that I described in this thread. ... View more

Hi, Please have a look at these threads : https://feedback.photoshop.com/photoshop_family/topics/cc-desktop-app-stuck-in-an-endless-loop https://feedback.photoshop.com/photoshop_family/topics/cc-desktop-installation-failed-again   Hopefully, this will give you enough information to work around these never ending issues with CC Desktop. ... View more

A lot of people have various problems with CC Desktop. I guess many of them have given up complaining. I don't think that these problems are related to the system configuration, just because these issues may or may not happen while the system configuration didn't change. This program is merely extremely buggy. ... View more

Hi,   You should download the Adobe Log Collector tool (https://helpx.adobe.com/creative-cloud/kb/cc-log-collector.html). Then... - Run it. - Rename the created .zxp file to .zip. - Unzip it and then unzip the Zip file that was contained in the initial Zip archive. - Look for the InstallerLogs folder and have a look at the log files to hopefully find some information about the error.   You can also downlad the CC Desktop Uninstaller (https://helpx.adobe.com/creative-cloud/help/uninstall-creative-cloud-desktop-app.html). Before running it, logoff/login and kill any Adobe process possibly currently running. Then reinstall.   By the way, both Creative Cloud Uninstaller.exe and Creative_Cloud_Set-Up.exe delete themselves when terminating even if they failed. Ridiculous ? Yes. So, make a backup copy. ... View more

Hi, I agree with this. For example, when running Photoshop, I have 15 instances of CEPHtmlEngine.exe running. CC Desktop is also an invasive program. However, many of the Adobe processes that are running permanently are tied to CC Desktop. If you uncheck the "Launch at login" option in CC Desktop, your system memory space will be less invaded. You don't need to have CC Desktop running permanently. I launch it only when checking for updates. ... View more