Unfortunately, Adobe has once again made an unexpected change that can possibly break some plugins. This is the case for the very useful Keyboard Tamer plugin written by Timothy Armes. What change ? Until recently and since 2016, Lightroom was reading the keyboard shortcuts from this file :    C:\Program Files\Adobe\Adobe Lightroom Classic\Resources\fr\TranslatedStrings_Lr_xx_XX.txt (xx_XX being the standard language identifier i.e. fr_FR for french).   Now LR is reading the shortcuts from a file named TranslatedStrings.txt in the same folder. The Keyboard Tamer plugin does its magic by modifying / adding shortcuts in the  TranslatedStrings_Lr_xx_XX.txt file. So, the plugin is still working but the created / modified shortcuts are no longer taken into account because they are not stored in the correct file.   It's interesting to note that Lightroom is now back to the naming scheme that was active before 2016 (at this time, Keyboard Tamer was already broken once but the author fixed the problem). Well, they made the reversed change in 2025. The problem is that Keyboard Tamer doesn't seem to be still maintained although it was working fine until I installed LR 14.3.   If you are using KT, there's a temporary and awkward workaround (but after all, you're not changing you customized shortcuts everyday) :     Open the folder containing the shortcut definition : C:\Program Files\Adobe\Adobe Lightroom Classic\Resources\xx (xx being the language id - fr for french). Make a copy of TranslatedStrings.txt in the same folder and name it TranslatedStrings_Lr_xx_XX.txt if this file doesn't already exist. Skip this step if the file is already there (see above for the meaning of xx_XX - i.e. fr_FR for french). In LR, launch the Keyboard Tamer configurator and make your changes as usual (or don't make any change if you just want to get KT working again). TranslatedStrings_Lr_xx_XX.txt will be modified by KT. Quit LR after validating your changes. Don't directly copy back TranslatedStrings_Lr_xx_XX.txt  to TranslatedStrings.txt because it may contain only your changes while TranslatedStrings.txt contains all the standard shortcuts. Instead, use a comparison tool or a text editor, to copy the changes you made in KT from TranslatedStrings_Lr_xx_XX.txt to TranslatedStrings.txt. Beyond Compare is the right tool for the job. But any capable text editor will do. Since the shortcut file is stored in C:\Program Files\Adobe\Adobe Lightroom Classic\Resources, you'll have to run Beyond Compare or you text editor as an admin. Otherwise you'll not be able to save the fixed shortcut file. Launch Lightroom and check. That's it. This worked for me. I couldn't find any other way to fix the problem. The plugin code is obfuscated so I couldn't adapt the code itself. Only the author can do that but I didn't receive any answer to my emails.   Hope this helps. ... View more

Hi,   CC Desktop is trying to display in the home screen "recent" images that no longer exist. The results are empty thumbnails unnecessarily occupying real estate. How to cleanup ?   Thanks. ... View more

Hi, I have 2 questions about plugin management in LR (using the latest version of LR Classic)   #1 On my system, the Remove button in the Plugin Manager is always grayed out. It's OK for the plugins installed by default by LR but not for the third-party plugins. Is this related to the way they were installed ? Or is this a bug ?   #2 Assuming that this button would eventually work, what does it do ? Does it just remove the plugin folder ? What happens with the data inserted in the preference file by the plugin ? Are they cleaned up or should they be, as I suspect, manually removed in the Preference file ?   Thanks in advance. ... View more

Hi,   Like many others, the CC updates are (were) extremely slow on my system although I have a decent ADSL connection. I gave this some thought and found the following...   Adobe are distributing their software through the Akamai CDN (this can be observed with a network monitor while updating). For those who are not aware of this technology and to make things simple, a CDN is a system that is able to make the downloaded package available to a myriad of servers all over the world and to connect you to a server near your location (which is detected from your IP).   This works automatically but not always, especially when you are using a DNS server that is not able to provide localization information to the CDN system. In which case, you are systematically downloading from the central server. If you are living far from Illinois, this can slow down operations a lot. A good example is when using the Google DNS servers (8.8.8.8 and 8.8.4.4). This can also happen for some internet providers. I made some tests and I could observe that indeed, I was always downloading from the central server in the US (I'm based near Paris in France).   Given this information, I thought to myself that if I could use the Akamai DNS servers instead, I may have more chances to download from a nearer server. Fortunately I could find the IP addresses of the Akamai servers :   - IPV4 88.221.162.120 and 88.221.163.120 - IPV6 2620:119:35::35 and 2620:119:53::53   I changed the network settings on my system to make it use these DNS servers and I could immediately observe that I was now downloading from a server in Frankfurt (Germany). And the update was significantly faster. I wouldn't say lightning fast (I only have a 10 Mbps ADSL connection) but this was more acceptable.   I cannot guarantee that this will work for everyone but there's no risk trying. I didn't observe any side effect since I have changed the DNS servers.   Hope this helps. ... View more

Hi, This is an old problem but it could now become a show stopper if not solved.   When run as an administrator PS runs without a hitch on my system. But I shouldn't have to do that for obvious reasons. If I run it normally (not as an admin, even under an admin account), it misbehaves and strange things are happening :   #1 When specifying scratch disks, only C: is listed. All other disks/partitions are ignored (not listed). No problem when running as an admin. Of course, these disks/paritions are recognized by any other app running at the same time under Windows. All these disks and partitions have a lot of free space available. I'm very curious about how PS decides what disk can be listed as a possible scratch disk. Moreover, PS is also unable to create and write to the system's and user's TEMP folders (although full rights have been given to all users - other apps can access these folders without any problem). This problem could explain issue #2. #2 It seems unable to read or write its preference file. Any preference changed in the preferences dialog is not retained when exiting. No problem when running as an admin. Needless to mention that all necessary permissions have been checked. #3 It is unable to write any edited image file to any other disk than C:. No problem when running as an admin. Any other app can read from and write to these disks. #4 When exiting PS, the photoshop.exe remains active forever after the main window has been closed. It is waiting something from the network, permanently sending TCP/IP requests. When run as an administrator, photoshop.exe terminates within a few seconds after the main PS window has been closed.   I went through all the recommendations made on this page : https://helpx.adobe.com/photoshop/kb/basic-troubleshooting.html . Really. To no avail. However, it's worth noting that if I launch PS while pressing the famous Ctrl+Alt+Shift key combo and answer NO to the question about deleting the preference file, everything is working fine. But if I relaunch PS normally, the problems are back.   I have also created a new standard account, a new admin account and tried to run PS under the system admin account. No difference.   Additionally, I also checked the Windows Defender settings, just in case. Since there's no problem when running PS as administrator, it's obvioulsy a permission problem. No other application on my system needs to be run as an administrator. I have checked all the permissions that have been listed in various articles coming from Adobe. So, obviously again, these documents are not accurate enough. Something is missing in the list of system objects to which full access must be given. I should also mention that I have a similar problem with Bridge and Lightroom, but let's focus on PS for now. Please refrain from telling me to re-install everything Adobe (already done) or to point to a possible system misconfiguration. My system is well maintained and works fine with the many applications installed on it and as many of us already know, I'm not alone with these kind of problems lasting since years.   Thanks in advance for any idea. ... View more

Hi,   Many of us are unable to run CC Apps (especially Photoshop, Lightroom and Bridge) unless launched as administrator. This problem is lasting since years but nobody seems to care about it. The usual anwers (checking permissions, re-installing apps, re-installing Windows, creating a new user account, talking about corrupted files or system - that many corrupted data or systems, really ? - etc.) don't help. They are just a loss of time. The error messages emitted by the app about denied access to a folder or a file are stupid enough to not specify which file or which folder. A lot of users have spent hours following the above mentioned advice without any result. Trying to examine the many log files spread by Adobe CC on our disks is just a nightmare.   There's another related problem that also needs to be fixed : Photoshop will not list as possible scratch disk any other drive than C: ... unless run as admin.   I have noticed that similar problems exist on the Mac.   Forcing us to run apps as an admin is a nonsense. So, after all these years, someone at Adobe should take over these problems and work on it seriously :   - We need a tool that would automatically check all the required permissions needed to run CC apps. I really mean ALL because the list of permissions made available by Adobe on various web pages are obviouslyt not enough (and never updated anyway). - We need more informative error messages. A message saying "You don't have enough rights to access this file" without giving the file's name and path is merely some kind of a provocation. Not professional at all. - We need that Adobe stop telling us that the problem is on our side. These problems are specific to the CC Apps. There's obviously a bug that doesn't take into account some (legitimate) configurations. I suspect UAC problems on Windows but I'm not sure. There's probably another problem when the TEMP and TMP environment variables folders point to another drive than C: on Windows. When Photoshop fails to recognize any other disk drive than C: as a possible scratch disk when there's no similar problem with any other non Adobe app and when all these drives are recognized by the system, it becomes obvious that this is a PS bug. Fix it ! Or explain us how PS enumerates the disk drives that are candidate for being a scratch disk. Let's be serious : PS doesn't see the drives on my system unless run as admin ? Come on ! It's just a joke.   Adobe should now consider that they are no longer alone on the imaging software market, especially regarding photography. We now have excellent RAW processors (DxO Photolab) and imaging software that is enough powerful for photography (Affinity Photo). Adobe software still have some advantages but I'm really tired spending so much time fixing problems with Adobe Apps and with CC Desktop. The CC Desktop machinery is slow, messy, is spreading a lot of files everywhere on our disks, running a lot of programs and services on which we don't have any control and sending data over the internet even when all sync operations are disabled. Enough is enough. All this stuff should become more simple, cleaner and more user controllable.   So, Adobe, if you don't want to fix these problems, you should at least give us accurate information about the permissions required by your apps and the way you discover drive disks on our system. At least, we could try to adapt our system configurations if needed.   Thank you in advance for handling these problems more seriously.   Patrick ... View more