> Could CC be causing this? Yes, CC Desktop is the cause of a lot of trouble. You should be aware that under some circumstances, especially when updating itself, CC Desktop merely kills the explorer.exe process in order to avoid a reboot after replacing currently running modules (this has been proven by some tests I and another user have made). This is why your desktop "blinks". Explorer.exe is no longer running for a while, so you no longer have any desktop. This happened again to me this morning when CC Desktop updated itself.   This is absolutely insane and has already been discussed elsewhere. This an unacceptable and incredibly bad programming practice. Just because explorer.exe could be executing some important tasks when it was brutally killed. This is also why you lose access to some devices because explorer.exe is not relaunched correctly. Logging out and logging in again should fix the problem. ... View more

You can also try this FTP link : ftp://ftp.adobe.com/pub/adobe/legacy/lightroom/win/5.x/Lightroom_5_LS11_win_5_7_1.exe (Windows) ... View more

Cela dit, vous n'êtes pas du tout dans le bon forum. Utilisez soit https://community.adobe.com/t5/Lightroom-Classic/bd-p/lightroom-classic , soit https://feedback.photoshop.com/photoshop_family/categories/photoshop_family_photoshop_lightroom?topic-list[settings][type]=problem. ... View more

Bonjour,   Fermez Lightroom, allez dans le dossier où se trouve le catalogue et supprimez le fichier portant le nom du catalogue et ayant l'extension .lock. Relancez Lightroom.   Ce problème survient quand LR ne s'est pas terminé normalement. ... View more

- I have to sign in each time I return to the forum. I don't see any option allowing to avoid this. ... View more

- I forgot to mention the lack of quoting options. ... View more

> Hi, that’s strange, I see a few options under "more"   You're an ACP, I'm not. ... View more

Hi, This seems to describe another kind of problem. The log can be rather big and I think that you should look for the last occurrences of "184" and "locked" in the log file.The log files are cumulative, so make sure that you are looking at the records corresponding to your latest operations.   If this doesn't help spot an actually locked file, then read on... What you're describing reminds me of known issues I had (and still have regularly) that were resulting in error code 183 and also sometimes error code 184. See https://feedback.photoshop.com/photoshop_family/topics/error-183-when-updating-cc-desktop-from-the-assets-tab . The problem is that the update starts but then stops for some reason after it has started deleting files and folders from the previous version. This issue can take different forms but the result is that the existing version can be partially or totally wiped out. There's no reliable recovery mechanism in the updater/installer.   One of the first things that you should try is to run CC Desktop as an administrator. This sometimes fixes these issues (on my system, CC Desktop doesn't run at all if not launched as an administrator).   Then you should check whether the updater has created a temporary folder for the new version. It should have the following form : C:\Program Files (x86)\Adobe\Adobe Creative Cloud.<version_number>. If it exists, it contains the new version. In that case, just delete or rename the old version folder (which requires killing any Adobe process or service). Then rename C:\Program Files (x86)\Adobe\Adobe Creative Cloud.<version_number> to C:\Program Files (x86)\Adobe\Adobe Creative Cloud   >  The C:\adobeTemp folder is empty. This folder is always empty after a CC Desktop update operation, be it successful or not.   That's all I can say for the moment. I can have a look at your install.log file if you want. Just make it available from Dropbox or whatever cloud location or attach it to a message if it's not that big.   CC Desktop is merely a failure. It's too complex, unreliable and extremely buggy. It is unable to give the user clear informations about what caused the failure and nobody at Adobe seems to be able to support it (beside always repeating the same magic spell : uninstall everything Adobe/cleanup/reinstall). I wish it could disappear and be replaced with a more simple way to update our Adobe applications. ... View more

The menu appearing when clicking on ... or More are pulldown menus. They only contain one single item : Edit Message. Which is curious because in that case, no menu is needed. A button is enough. ... View more

The Edit message command is available in the ... drop-down menu AND in the More drop-down menu. Sometimes it works, sometimes it returns a "message not found" error (which is rather funny). ... View more

And if you edit the reply made with the one line editor, you get the full editor. Very consistent, indeed. So, the trick is to post only the beginning of your reply and then edit it immediately to add the rest. Very practical. ... View more

> So Khoros isn't all bad. It just needs lots & lots of tweaking.   Really ? If a software is unable to work decently with the default settings, I think there's a problem. Some basic features expected from a forum software are missing, bugs are ubiquitous and I'm not sure that this depends on tweaking even more. I'm wondering how Adobe could decide to let that thing go online before testing it internally at least a few hours (which would have been enough to detect all current major problems). ... View more

> It's produced by a 3rd party called Khoros (formerly called L1thium) Good to know this. Just to avoid installing it on a server for testing. ... View more

Hi, Before applying the usual and most often useless and time consuming "uninstall/cleanup/reinstall" procedure, you should have a look at the end of this thread : https://community.adobe.com/t5/Get-Started/Back-to-Adobe-CC-Desktop-App-hell/td-p/10580751   In order to determine which file is locked, you should run the Adobe Log Collector tool, unzip the ZXP file created by the Log Collector (this file is actually a Zip file - just change the extension from ZXP to ZIP), look for the Install.log file, open it in Notepad or any text editor,  and search the text for "184". You'll see which file is considered as locked. Uploading the ZXP file as suggested by the Collector tool is not necessary. Just hit Cancel when requested. The Log Collector tool can be downloaded from https://helpx.adobe.com/creative-cloud/kb/cc-log-collector.html . Using this tool in order to determine which file is locked should be the first recommendation made by the support in case of error 184. Good luck by taming the CC desktop beast. ... View more

Hi,   Prodesign Tools Site   Good luck. ... View more

> New Forum format a little frustrating An understatement, certainly. https://community.adobe.com/t5/Community-Help/This-new-forum-software-is-driving-me-nuts/td-p/10606153 https://community.adobe.com/t5/Community-Help/New-forum-please-replace-the-one-line-editor-with-a-full-editor/td-p/10606069 ... View more

Ricky, I know this. I'm just saying that these design choices are ridiculous. Moreover, when you edit a "Quick Reply", you get the full editor. Absolutely inconsistent. ... View more

Hi,   I second this request. I can't even understand how a forum software where that feature is missing could be installed by a company like Adobe. Not serious. Things seem to be totally out of control. I didn't think that one day I could say "Please, back to Jive". ... View more

Hi,   Some problems that I have identified :   Replying to the initial message in a thread is not the same as replying to a reply. In the first case, there are 3 possibilities : clicking on the (blue) Reply button just refreshes the page and does nothing OR it does nothing else than displaying (once again) the Community Guidelines OR it opens the full message editor.   Clicking on the (white) Reply button next to any message not being the initial post either does nothing OR opens a ridiculous one line editor. If the user has more than one line to insert in his reply, he has to first post a one line answer and then use the Edit command which will open the full editor. Ahem, maybe. Very often, clicking on the Edit command brings you to a page notifying the infamous 404 error (message not found).   When the user eventually succesfully writes and formats a reply, he should copy the whole text before clicking on Post because too often, this button has no other effect than to refresh the page : message lost.   Beware : when clicking on Preview, you'll only be able to Cancel or Post. I could not find a way to further edit the message. Or does Cancel bring me back to the editor ? Checked : no, it doesn't.   Same problems under Firefox and Chrome.   Usually, when a new forum software is installed, there are some difficulties related to settings that are not correctly adjusted. Fixing this is a matter of 2 or 3 days. This one is more problematic : just full of bugs. I didn't like Jive but I think that we should go back to it for a while until the new software has been correctly tested.   Another solution would be to use a well-known, well tested forum software like the Lightroom Queen forum or the one used for the Adobe Photoshop Family feedback forum. I'm wondering why Adobe need 2 different forum software. ... View more

Hi, I'm referring to this : When clicking on Reply I get this one line editor. To create this answer I had to first enter text in the one line editor and then edit the message to insert the image and format the text. I get the fulll editor only when editing the message. Tested in Firefox and Chrome. ... View more

Axel,   When the usual recommendation made when problems appear in a software is "please reinstall everything", this is a clear indication that this software is too buggy and that nobody is able to fix these problems. I'd like to spend time using the Adobe software, not reinstalling it each time something is updated or changed.   Regarding the error 16 configuration error page, I already checked all this many times. Doesn't help. There's probably a permission problem but not one that is listed there. I already asked many times more accurate information about all the permissions that are needed to run PS but I never got any answer. ... View more

This new forum software is driving me nuts. ... View more

Axel, When the usual recommendation when problems appear in a software is "please reinstall everything", this is a clear indication that this software is too buggy and that nobody is able to fix these problems. I'd like to spend time using the Adobe software, not reinstalling it each time something is updated or changed. Regarding the error 16 configuration error page, I already checked all this many times. Doesn't help. There's probably a permission probelm but not one one that is listed there. I already asked many times more accurate information about all the permissions that are needed to run PS but I never got any answer. ... View more

To resolve Error 16 please take a look here... I already checked this many times. There's obviously a permission problem but the solution is not in this document. ... View more

As far as I can remember, I always had to run Photoshop and CC Desktop as an administrator.   But this is not the actual problem. The problem is that CC Desktop tells me that I'm running it in compatibility mode and that is plain wrong. ... View more

Hallo, Which versions of Adobe CC programs do you use? I'm running the latest versions of Lightroom Classic and Photoshop   Which type of operating system and which version do you use? Windows 10 Pro 1903   It is unusual that you have to run CC client as an Administrator. Which what type of user your are logged in into your system, normal user, Adminstrator, user with Admin rights? Not that unusual. As far as I can remember, I always had to run Photoshop and CC Desktop as an administrator. Otherwise the CC Desktop process is loaded but no window is opening and with Photoshop, I get the well-known error 16, a problem that is hitting many users when not launching PS as an administrator. I'm using an administrator account.   MfG. ... View more

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 has 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. ... View more