> This would keep the behaviour consistent with how library thumbnail flagging/rating works... even if your mouse is not on a selected thumbnail and you right click to change rating etc. it only applies the change to the one you right clicked on. Which brings us back to my comments in these threads : https://feedback.photoshop.com/photoshop_family/topics/folder-favorite-setting-cannot-be-changed https://feedback.photoshop.com/photoshop_family/topics/lightroom-ui-not-managed-as-a-finite-state-machine-ijo0smp14hryw There's a frequent confusion in the Lightroom UI between selected folder and right-clicked folder that explains other long lasting bugs. ... View more

Sorry Bruce, but I disagree. Re-read my example. If folder A is selected and if I right-click folder B (which is not selected) A and B are marked as favorites. I never wanted A to be added to a non wanted favorites group. Now if I right-click A (which is still selected), the available command is "Mark Favorite". This doesn't make sense since it is already marked as a favorite. The unmarking process is not more logical. Now select both A and B, right-click B and select "Unmark favorites".  A is no longer a favorite and B is still one that you can no longer unmark from the Folders pane. You have to do this from the Grid View drop up menu. ... View more

Bump! ... View more

Not fixed in version 7.5. ... View more

Hi Rikk, Version 7.5 didn't fix the problem. This bug appears to be random but it is not. It is easily reproducible as I explained 3 weeks ago in the thread mentioned above : https://feedback.photoshop.com/photoshop_family/topics/folder-favorite-setting-cannot-be-changed Depending on how one uses this feature, the problem may seem to appear randomly. Actually, the problem shows up when the right-clicked folder is marked as a favorite while it is not the currently selected folder. I have given all details just in time and this could have been easily fixed before releasing version 7.5. There are some people on this forum (most of them software engineers or developers) who are spending time investigating problems, giving accurate technical details allowing to fix long lasting issues. Sometimes, I have the feeling that nobody cares at Adobe. ... View more

A note for the developers : https://feedback.photoshop.com/photoshop_family/topics/lightroom-ui-not-managed-as-a-finite-state-ma... But I guess that managing a finite state machine using LUA can be a challenge. ... View more

Hi  Ryecooder, You might want to join this thread on the feedback forum : Photoshop/Lightroom: Error 183 when updating CC Desktop from the Assets tab | Photoshop Family Customer Community Allegedly fixed but I guess we will have to install a new CC version before we're able to enjoy the fix. And this installation will fail as the previous ones. Kind of a chicken-egg problem. Anyway, the Assets update that was triggered today when launching CC desktop failed again with the usual error 183. The above mentioned thread explains the workaround that I'm using to install these updates : 1. Kill all Adobe related processes. 2. Rename C:\Program Files (x86)\Adobe\Adobe Creative Cloud to C:\Program Files (x86)\Adobe\Adobe Creative Cloud.old 3. Rename C:\Program Files (x86)\Common Files\Adobe\CoreSyncExtension to C:\Program Files (x86)\Common Files\Adobe\CoreSyncExtension.old 4. Download the Adobe CC Desktop installer (direct link) and install again (run the installer as an administrator). Good luck. ... View more

Hi Marco, This bug exists since the beginning of Lightroom and I have been experimenting with the Save/Read workaround a lot. AFAIK, this procedure is safe. Never had a problem with this. However, this fixes the problem only for a (sometimes very short) while. As soon as the files are accessed again (for example when rebuilding a discarded preview), the problem may appear even if you didn't make any change. Just viewing the images is enough. I am using a single rule dynamic collection (Metadata Status is no up to date) to regularly fix this mess. Open the collection / Select All / Save. As for a fix by Adobe, give up any hope. The usual rule applies : once a bug has survived one or two years, you can be assured it will never be fixed. They just don't care and this is a demonstration that the bug  doesn't  prevent the product from being sold anyway. High code quality and professional conscience are no longer a preoccupation at Adobe. ... View more

Thanks for the details. There are many Plug-ins folders and I doe not know the exact search orders Photoshop and Bridge versions use Actually, I'd like to obtain accurate instructions from Adobe about this. This a very messy situation. The PS SDK doesn't provide any information about what should go where (unless I missed something obvious). I have asked the same question in the Feedback Forum. Waiting for an answer... ... View more

Hi, To further discuss this issue, please join this thread in the Feedback forum : Photoshop/Lightroom: Error 183 when updating CC Desktop from the Assets tab | Photoshop Family Customer Community ... View more

Yes Knut additional functionality can not be added to Explorer without it being briefly suspended.  I would recommend contacting Microsoft if you would like to see this limitation adjusted in the Windows operating system. Are you kidding us ? A code module that is currently running cannot be replaced without being unloaded. However, there are mechanisms in Windows allowing this. So this is not an OS limitation but a limitation of the developers not being aware about what they can do with the Windows API. Anyway, I guess that most users would merely accept a reboot instead of being constantly bothered by an unstable and buggy installation package that is obviously able to damage their system. ... View more

Hi, While investigating the CC Desktop installer unending problems described here​, I discovered this issue by looking at the installation logs. As a former developer and software engineer, I have never seen an installer program daring to voluntarily kill the explorer.exe process without asking the user and without considering the possible side effects of such a questionable practice. This is just unacceptable. If a DLL that must be replaced is currently in use, there are two possibilities to handle this situation : 1. Register a system reboot. 2. Use the system provided DLL unloading and loading mechanisms in order to make the replacement transparent. This requires some clever coding but this is possible. Brutally killing the explorer.exe process might have negative side effects (especially on tasks currently running in Explorer) and, IMHO, is explaining why, with certain configurations, the rest of the installation often fails. Depending on which add-ons are currently running in Explorer, the consequences of killing the explorer.exe process can be severe. Such a bad programming practice just has to be stopped. Period. ... View more

Hi Sunil, Please unmark this as "not a problem". It's a reproducible bug. ... View more

Another remark : This bug and the 2 bugs that I mentioned above (https://feedback.photoshop.com/photoshop_family/topics/lightroom-selected-published-folder-or-collection-is-not-deselected-if-a-folder-is-selected https://feedback.photoshop.com/photoshop_family/topics/-7-3-new-bug-with-smart-collections) seem to point to the same design issue. Somewhere in the UI code, there's a confusion between currently selected folder and right-clicked folder. This now appears rather obvious. ... View more

When following the steps described above, note that if you unmark folder B by right-clicking it in the Folders panel (B not being selected), both A and B are unmarked. If you do the same while B is selected, neither A nor B are unmarked. ... View more

[Using Windows 10 - LR 7.4] Hi, It seems that there's actually something wrong with the favorites marking/unmarking. I recently marked a folder as a favorite. It was tagged with a small star in the Folders panel of the Library module. It also appeared as a favorite in the "drop up" list that is available under the Grid view (I'm using a dual monitor configuration, so I usually have the grid view on the second monitor). I unmarked that folder from that drop up list. The folder was actually removed from the drop up list but was still tagged as a favorite (with the star) in the Folders panel of the Library module. When I right-clicked it there, the Mark Favorite command was available, not the Unmark command. Gasp ! The bug is easy to reproduce (and obviously, this feature was not very well tested - I would say, not tested at all ) : assuming you have selected folder A and now right-click another folder B and mark it as a favorite, both folders A and B get the favorite star. If you right-click A in the Folders panel, the Mark Favorite command is available while the folder is already marked as favorite with the star. So it's not a favorite on this side of the UI. If you open the drop up list under the Grid view, A appears in the Favorites section but at the bottom of the drop up list you get the Add Favorites command although that folder is currently selected and already marked as a favorite. So, on this side of the UI, A is a favorite but you can't unmark it. Yet another inconsistency problem in the Lightroom UI. If someone had spent just a few minutes checking this code, the bug would have been detected immediately. That's the problem since a while at Adobe : design flaws letting inconsistency problems appear in the UI and non-existent QA dpt. This bug belongs to the same category as these ones (which are still not fixed): https://feedback.photoshop.com/photoshop_family/topics/lightroom-selected-published-folder-or-collec... https://feedback.photoshop.com/photoshop_family/topics/-7-3-new-bug-with-smart-collections https://feedback.photoshop.com/photoshop_family/topics/wrong-timestamp-stored-in-lightroom-catalog-c... Obvious coding mistakes and lack of testing. Back to the base problem here : https://feedback.photoshop.com/photoshop_family/topics/lightroom-quality-assurance-dpt-please-tell-u... The problem is not that such bugs appear. The problem is that they go undetected to public releases. They are so obvious that they should be immediately spotted by the developer himself before the QA dpt. have a look at the new code. Adobe, are you subcontracting coding to students or offshore developers ? ... View more

Also, I'm almost sure that there's a relationship with the bug reported here : https://feedback.photoshop.com/photoshop_family/topics/-7-3-new-bug-with-smart-collections?topic-rep... As mentioned earlier in this thread, I'm using Windows. ... View more

The following screen capture made in LR 7.4 shows that it is still possible to have a folder and a collection simultaneously selected in the Library module, exactly as before : https://www.dropbox.com/s/n06ab0zbxo06vm0/LR_UI_bug.jpg?dl=0 It should not be that difficult to add a step in the folder/collection tree management code : when a click is received, wherever it happens, first deselect the currently selected object . I certainly wouldn't need 3 years to achieve this. IMHO, there's a big UI design flaw here. It's easy to reproduce. I followed the same steps as Jetze. ... View more

Hi Sumeet, Please remove the Solved tag as the latest post from Jetze demonstrates that the problem is still there with version 7.4. ... View more

Hi Jetze, No problem with the files (OneDrive, not Dropbox). Thanks for making clear that this bug that has allegedly been "fixed" 2 or 3 times is still there with version 7.4. ... View more

Hi minpeachie, I always had this very old problem with other Adobe applications and the suggested changes to the permissions never helped. The only thing that work for me is to launch the application as an administrator. To make this change permanent (assuming you're running Windows) : - Navigate to the program folder and find the executable (after effects.exe). - Right-click that file and select Properties - Select the Compatibility tab - at the bottom, check "Run this program as an administrator" (or click on "Change settings for all users" if you want to apply this change to all users). ... View more

Hi, I have tried the steps described in this thread and in the linked pages (including full cleanup and re-installation) : Creative Cloud seems to be taking longer than usual to initialize. I'm running Windows 10 1709. No software is affecting performances on my system. Everything is running smoothly except CC Desktop. No software has been added since this tool was launching normally. However, I still have the same error code 184 when trying to update from the Assets panel. An old problem hitting many users and that was never fixed. ... View more

Thanks. While we are at it... This very old one sometimes causes some hair pulling sessions and processing mistakes in my workflow : https://feedback.photoshop.com/photoshop_family/topics/lightroom-selected-published-folder-or-collec... ... View more

> Do you have another bug you would like to ask about? One of the most annoying and irritating problem (for me and for those who have a similar workflow making use of the metadata status flag) is this one. It's there since the first versions of LR. https://feedback.photoshop.com/photoshop_family/topics/wrong-timestamp-stored-in-lightroom-catalog-c... With John Ellis, we have spent a lot of time characterizing this bug. We have determined what was wrong in the database. Given this information, any developer should be able to spot the problem in the code and fix this odd behavior within a few hours (to be generous). If this is still not fixed after all these years, this means that nobody looked at it. We never had any feedback about the detailed reports that we have posted here. Which leads to another problem in the way bugs are managed and that's why the current "conduit" is from far not satisfactory. I don't know exactly how the maintenance team is organized but one things is for sure : the longer a bug has been there, the lower the probability to get it fixed. The bug priority list obviously doesn't work as a FIFO stack. Of course, there is a need to assign a priority level  but there are problems that never had a chance to reach the top of the list. If a bug is marked as minor (who decides this ?) and lasts over about one year, it will never be fixed even if it could actually be fixed within minutes. The whole system is not working well (understatement). ... View more

Rikk, I think it's now time for the LR users to have access to some bug tracking system (in read-only mode, of course) that would allow us to exactly know if and when a problem has been taken into account. Or maybe I missed something ? There are too many problems that are lasting since years and that are still not fixed. Nobody knows if these problems are taken into account, ignored, still under investigation,... Giving (sometimes) this information via forum threads is obviously not satisfactory. I have some examples of severe bugs reported and documented here since years and nobody seems to care. This affects the confidence we have in the ability and/or willingness of Adobe to fix these bugs. I'm really tired of regularly reporting and documenting problems that are obviously ignored, I repeat, since years. Some would say this is only annoying, but annoyance is the open door to repudiation. If this attitude doesn't change, I'll bite the bullet and switch to another solution. Adobe now have credible competition but don't seem to care. ... View more

Problem not fixed in version 7.4. Is that so difficult ? ... View more