Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Exit
Samoreen
Advisor
Samoreen
Advisor
Activity
‎Oct 02, 2017
09:10 PM
Hi, I posted a message about this issue one year ago and the discussion was closed despite the number of "me too". Don't know why. Anyway, I'm somewhat stubborn... In LR, there's absolutely no possibility to edit the custom cropping ratios. Which is already a problem that should have been fixed since a long time. Now let's assume that the stacking mechanism managing these custom ratios (5 entries max and first in first out management) is corrupted and stuck. What can you do ? If you are a user with no database management skills, nothing. Period. Strangely enough, these settings are not stored in the preference file where they could at least be manually edited but in the catalog, a SQLite database. If you can deal with an SQLite management tool, you will be able to fix the problem. The relevant information can be found in the table named Adobe_variablesTable, entry named Adobe_customCropAspects. Maybe it's time for Adobe to make this feature more usable ?
... View more
‎Oct 02, 2017
03:06 PM
Bump!
... View more
‎Oct 02, 2017
03:02 PM
OK. It seems that the good ol' Adobe rule also applies for this issue : once a bug survived one or two years, it becomes a feature. This will be never fixed.
... View more
‎Oct 02, 2017
06:04 AM
Unfortunately, this problem is still not fixed after 2 years +. I guess it will never be as for all bugs that have a lifetime over one year. It's an Adobe tradition : once a bug a survived more than one year, it automatically becomes a feature.
... View more
‎Sep 12, 2017
09:55 AM
I eventually fixed the problem by chance when trying to fix an unrelated Windows issue. I applied the fix described in this thread (4th message about WMI) because I had a problem with the Security Center. After applying this fix, CC Desktop stopped failing when updating from the Assets tab. I had already noticed a few WMI error messages when investigating the CC Desktop case but I thought they were unrelated. NB : The fix description mentions that the WMI service must be stopped in order to be able to delete or rename the Repository folder. Actually, the service must be temporarily disabled and then stopped. Otherwise, it's impossible to rename or delete the Repository folder. Once this is done, the service must re-enabled in Automatic mode and the system should be rebooted.
... View more
‎Sep 08, 2017
04:46 PM
Although the instructions in that thread are for a Mac, I renamed all hdpim.db files I could find on my system, launched CC desktop and ran the Check for updates... command. The hdpim.db file in C:\Program Files (x86)\Common Files\Adobe\caps was re-created. Strangely enough, Lightroom was still marked as installed but Photoshop was now considered as uninstalled. So I clicked on Install (although this was normally not necessary) and this fixed the problem for Adobe Camera RAW. When updating CC desktop from the Assets tab, I still have an error but it's no longer code 105 but 183. I already got this one in the past and I had fixed it by changing the properties of all executable in Adobe Sync and checking the "Run as an administrator" option in the Compatibility tab. These executables are still set to run as an administrator but this no longer fixes the problem. Yet another problem to fix... Anyway, thanks for the pointer to the related thread.
... View more
‎Sep 07, 2017
11:42 PM
kglad, I renamed C:\Users\<user>\AppData\Local\Adobe\AAMUpdater. The AAMUpdater folder was re-created but this didn't change anything. Same error : Exit Code: 105 -------------------------------------- Summary -------------------------------------- - 1 fatal error(s), 1 error(s), 0 warnings(s) FATAL: Error occurred in uninstall of package (Name: CameraRawRIBSCoExistPackage Version: 9.6.0.126). Error code: '105' ERROR: Error in deleting package records for sapCode:ACR, version:9.12, package:CameraRawRIBSCoExistPackage, packageVersion:9.6.0.126 -------------------------------------------------------------------------------------
... View more
‎Sep 07, 2017
11:09 PM
>> Mac OS Thanks kglad, As stated in my OP, I'm running Windows 10.
... View more
‎Sep 07, 2017
03:19 PM
Actually, when I try to update ACR anyway the error is Exit Code: 105 -------------------------------------- Summary -------------------------------------- - 1 fatal error(s), 1 error(s), 0 warnings(s) FATAL: Error occurred in uninstall of package (Name: CameraRawRIBSCoExistPackage Version: 9.6.0.126). Error code: '105' ERROR: Error in deleting package records for sapCode:ACR, version:9.12, package:CameraRawRIBSCoExistPackage, packageVersion:9.6.0.126 ------------------------------------------------------------------------------------- So it tries to uninstall a version that is no longer there instead of recognizing that the latest version is already installed. So it really needs to be reset.
... View more
‎Sep 07, 2017
02:53 PM
Hi, [running Windows 10 Creators] The CC Desktop app is telling me that Adobe Camera RAW needs to be updated although the latest version (9.12.1) is already installed (I checked the plugin version number in PS). It is also telling me, in the Assets tab, that CC Desktop itself needs to be updated although I'm running the latest version (4.2.0.211) according to this page : Release notes for the Adobe Creative Cloud desktop app . If I accept to update ACR, the update fails anyway (without any error message), as well as the CC Desktop update (error 105) So something is out of sync in this tool (which has always been generating trouble since it was released for the first time - I guess it's time to replace it with something more stable). How do I reset the database used by CC Desktop in order to make it re-scan my installed CC apps ? Thanks in advance.
... View more
‎Aug 14, 2017
02:24 AM
Up!
... View more
‎Aug 08, 2017
03:16 AM
Hi Simon, So, if I understand you well, you are telling me that LUA doesn't have Structured Exception Handling (actually, I already know that). Therefore a routine for catching unhandled exceptions cannot be inserted in the code and assertions are used instead. I will not discuss the choice of LUA for developing LR (especially for a program that needs performance). There's no chance to change anything about that anyway. However, since LUA has limited capabilities regarding error handling, LR should have its own built-in mechanisms instead of relying on DbgView (or at least use DbgView in a transparent way). Unless I'm missing something obvious, I have never seen any directive about the use of DbgView when a user reported an "assertion failed" message. When LR crashes with such a message, it should display instructions as described in the thread you mentioned. This would be the bare minimum. Also, a built-in log mechanism would be easier for the user. Instead of asking the user to add an argument on the command line, a key combo (like the one used to reset the preferences) should be available in order to launch LR in debug/tracing mode. DbgView could be a part of the distribution and could be launched as soon as that key combo has been detected, when the process begins to execute. In other words : don't think developer, think user. If you want information about the cause of the assertion failure, you need to make the reporting easy for the user. That's not something that is difficult to implement. [NOT OFF-TOPIC] By the way, now that someone from the development staff is talking to us, I have a question about those bugs that are lasting since years and that are still waiting for a fix. A good example is this one which is lasting since version 1 : Lightroom: Wrong timestamp stored in catalog causing wrong metadata status (all Windows versions) | Photoshop Family Cus… This bug has been reported multiple times, is identified and probably easy to fix. But we continue to be bothered by these endless warnings about the metadata status allegedly not up-to-date. This is just an example, we have a lot of such bugs waiting to be fixed since years (like the bugs related to a failed assertion as discussed above) and not only in Lightroom. I'm questioning the way bugs are managed at Adobe. Once a bug has been declared as "minor", we can rest assured at 90% that it will never be fixed. I have already suggested to handle the priority list another way : the "todo" list should be worked on from both ends. The majority of available development/maintenance resources should be dedicated to the most urgent bugs but some developers should work on the low priority bugs which are most of the time very easy to fix. Or the maintenance developers should spend a part of their time looking at these low priority bugs what they obviously never do. If you think "customer satisfaction", you know that these allegedly minor but unfixed bugs are those who are giving a bad feeling about code quality. So they should be handled seriously. [MODERATOR Hi Samoreen. You have cross posted to the feedback forum. It is more appropriate to continue the discussion of the issues raised in that space rather than in this community] https://feedback.photoshop.com/photoshop_family/topics/-assertion-failed-messages-strange-programming-practice-at-adobe
... View more
‎Aug 07, 2017
05:06 AM
Just to be clear : this thread is not about the problem I'm trying to fix for this user. The actual problem is that the LR6 delivered code is still emitting these "assertion failed" messages and that it should not. I can't see any good reason for this. Debug assertions are a development tool and should not survive in the delivered code.
... View more
‎Aug 07, 2017
02:53 AM
Hi, There's something that is bothering me with Lightroom. I'm currently trying to help a user who has problems when launching LR. He gets an "assertion failed" message and that's it. We'll certainly fix that but this kind of message just raises a question... Assertions are small tests inserted in a program's code in order to verify that some condition is met when reaching a given part of the code during execution. If the condition is not met (the assertion failed), then the program immediately stops. Assertions are used by developers when testing and debugging their code. Assertions are useless when the code is considered OK. During development, the program is compiled in "debug mode" and the assertions are embedded. When the program is considered ready, the compiler is switched to "release mode" and the assertions in the source code are ignored and not embedded in the final code. Why ? Because this code needs to be executed only during development. Since the Lightroom users are sometimes getting these "assertion failed" messages, this means that the delivered code was compiled in debug mode, not in release mode. Since this code contains tests that are useful only during development, this more or less affects performance (because the assertion code is executed although it's not necessary). Conclusion : - If the distribution of code compiled in debug mode is a programming mistake, there's something to fix in the project management. - If this is done voluntarily, this is strange programming practice. The "assertion failed" message doesn't give any indication about what caused the program crash (because the assertion can only be handled in debug mode when the program is run under the control of a debugger). So the embedded test code is useless anyway (from a user's point of view). It's important to note that when an assertion fails, this doesn't always mean that something went wrong. The assertion was inserted by the developer because he wanted to check something at some moment during the development phase. The assertion may fail when the program runs in the field because the test was related to the developer's environment. So a debug assertion may fail in the field while there's absolutely no problem (but the program will stop anyway). This is why the distributed code should always be compiled in release mode. Since performance problems are a hot topic in LR, I'm wondering why the developers would want to make things even worse by distributing a version of a program containing non functional code. It's a common mistake among junior developers to forget to switch to release mode when the code is considered ready for delivery. But since these errors have been reported so many times, the project managers are certainly aware of this. So why are Adobe still distributing code compiled in debug mode ?
... View more
‎Aug 01, 2017
07:48 AM
1 Upvote
https://forums.adobe.com/people/Jeff+A+Wright wrote What installed security software, and versions do you utilize? These details could be helpful to see if other individuals affected by this error are using similar titles. I'm using ESET NOD32 antivirus (10.1.219.0) and Malwarebytes Premium (3.1.2), both with real time protection. I must mention that I also tried with real time protection disabled in both programs, which didn't change anything.
... View more
‎Aug 01, 2017
07:38 AM
Jeff, I had already created a clean local admin account which I only use for testing purposes. Of course I tried to run CC Desktop under this account to see whether this fixed the problem. No way. Anyway, this doesn't explain why I sometimes need to "run as an administrator " some CC apps. They should run normally, even under a standard user account. I have started a thread in the feedback forum about this issue. Photoshop: CC apps needing administrator rights | Photoshop Family Customer Community
... View more
‎Aug 01, 2017
04:49 AM
1 Upvote
Sheena, Thanks. I have eventually fixed the problem which was related to CoreSync. I had to change the properties of all executables in the Adobe Sync folder and to enable the "Run this program as an administrator". Then CoreSync could update normally (the update always failed before doing this) and the Sync option buttons were enabled. I already had similar problems with Photoshop and Lightroom which suddenly refused to launch unless I ran them as an administrator. The problem disappeared after the upgrade to Windows 10 Creators but now, it is showing up again in Adobe CC Desktop and Adobe Sync.
... View more
‎Aug 01, 2017
03:51 AM
1 Upvote
OK. I have fixed the problem by changing the properties of all executables in the Adobe Sync folder and subfolders. I have enabled the "Run this program as an administrator" in the Compatibility tab. Problem gone. This is not something new. It already happened in the past that Lightroom and Photoshop refused to launch unless I run them as an administrator.
... View more
‎Aug 01, 2017
02:42 AM
Now some more fun... When trying to uninstall CC Desktop from the Control Panel, before you get the message mentioned above, you have the choice to "Uninstall" (which will fail, of course) or to Repair. When selecting Repair, you get the following error message LOL. I'm running Windows 10 Creators. Yet another bug in the routine retrieving the Windows version number...
... View more
‎Aug 01, 2017
02:23 AM
By the way, the instructions on this page Use the Creative Cloud Cleaner Tool to solve installation problems are clearly out of date. You can't uninstall Adobe CC Desktop from the Control Panel because the uninstaller refuses to launch : "Couldn't uninstall Creative Cloud for desktop. You still have Creative Cloud applications installed on your computer that require it.". Which means that you have to uninstall all CC apps before being able to uninstall / reinstall CC Desktop. The only way to uninstall is to do this manually and then use AdobeCreativeCloudCleanerTool. This just doesn't make sense.
... View more
‎Aug 01, 2017
02:15 AM
Not yet. I have spent too much time trying to fix this and now, I have some urgent work to do. For the moment, I can't spent hours uninstalling, re-installing, etc. just to get a program installed correctly. This should be a simple process but this is overly complicated.
... View more
‎Aug 01, 2017
02:09 AM
Hi Sheena, Could you please try to connect to a different network and check if that helps? I don't know what "connecting to a different network" means. I only have one home network connected to the Internet. Am I missing something ? Additionally, let me know if you are on a windows machine or Mac? I'm running Windows 10 Creators.
... View more
‎Jul 31, 2017
04:16 PM
Since I didn't have this problem before, I guess it's a new bug introduced by version 4.2.0.211. I think I'm losing my time trying to fix this. Just waiting for the next release which might fix this new bug and introduce other ones... as usual. Regression testing is something that appears to be totally unknown at Adobe.
... View more
‎Jul 31, 2017
03:24 PM
Hi, Any known reason for this ? Thanks.
... View more
‎Jul 31, 2017
12:12 PM
I mean I implemented the steps successfully but this didn't fix the problem
... View more
‎Jul 31, 2017
11:08 AM
https://forums.adobe.com/people/Jeff+A+Wright wrote Samoreen did you implement the suggestions offered by Atul in message #3 of I can´t install CC apps ? Did you have any questions on how to implement the steps listed? Yes, Jeff, I did.
... View more
‎Jul 31, 2017
09:10 AM
Actually, there are 2 recurrent errors : FATAL: Error (Code = 184) executing in command 'MoveFileCommand' for package: 'CoreSync-mul', version:2.4.1.35 FATAL: Error occurred in install of package (Name: CoreSync-mul Version: 2.4.1.35). Error code: '184' WARN: Unable to move file at "C:\adobeTemp\ETR233F.tmp\1\CoreSyncExtension\CoreSync_x64.dll" to "C:\Program Files (x86)\Adobe\Adobe Sync\CoreSyncExtension\CoreSync_x64.dll" Error 32 The process cannot access the file because it is being used by another process.. Try setting correct permissions to the specified file/folder or parent folder, so that admin has rights to modify it. Indeed, if I kill the Windows Explorer process while the update is running, I don't get this error and I immediately go to the error below... It's rather strange that the updater is trying to update a DLL that is already in use by Explorer.exe. FATAL: Error (Code = 183) executing in command 'RunProgramCommand' for package: 'CoreSync-mul', version:2.4.1.35 FATAL: Error occurred in install of package (Name: CoreSync-mul Version: 2.4.1.35). Error code: '183' WARN: Program "C:\Program Files (x86)\Adobe\Adobe Sync\CoreSync\customhook\CoreSyncCustomHook.exe" failed with exit code: 105 This one is unclear. No idea about what RunProgramCommand is trying to do.
... View more
‎Jul 31, 2017
08:57 AM
Thanks but same answer as the last message in the referenced thread. The advice given in this thread doesn't seem to be relevant since Adobe CC Desktop must be running in order to launch and update from the Assets tab. Anyway, I can't spend my time uninstalling / re-installing / cleaning up the Adobe CC stuff each time Adobe CC Desktop is updated. This doesn't make sense. The developers of this program should spend their time fixing it.
... View more
‎Jul 31, 2017
07:43 AM
Hi, Today, Adobe CC Desktop refused to start telling me that I either had to Quit or to Repair. I selected Repair which resulted in a failed operation and an empty folder for the CC Desktop app. Thank you, Adobe. So, as usual, I uninstalled and reinstalled. After launching CC Desktop, I saw a red dot near the Assets tab. I clicked on it and after a "Checking for updates", it proposed to update Adobe CC Desktop ( ? ? ? I just downloaded and re-installed it so I'm wondering what it wanted to update). Anyway, this operation systematically fails with either error 184 or error 183. Log file here : Dropbox - Install.zip . I'm using Windows 10 Creators. I tried in Safe Mode and under a clean Admin account. Nothing helps. This program is just a failure. Always new problems, failed updates, uninstallations and re-installations,... Time to clean this code.
... View more
‎Jul 30, 2017
02:04 AM
Your best chance of getting a particular bug fixed — if it is doable and not the sort of deep rooted code that Chuck mentioned — is to start a thread on the Feedback forum... Done since a long time for all bugs that are bothering me since years. Requests supported by many people. Absolutely no effect. Problems still there. By the way, as a developer, I don't know what a "deep rooted bug" is. If that means that nobody can access (possibly using a modern debugger) or understand the source code related to that bug, then it's a project management defect. This clearly means that the product is no longer under control and that nobody can anticipate side effects when modifying or adding features. Which is exactly what is happening with Photoshop and, surprisingly enough, with Lightroom. Tracking down a bug is just a matter of expertise and time. If you want to fix it, you can. I observe that Adobe don't want to spend time fixing non critical bugs. It's their vision of customer service. Not mine.
... View more
Copyright © 2025 Adobe. All rights reserved.
AdChoices