Photoshop/Lightroom: Error 183 when updating CC Desktop from the Assets tab

  • 1
  • Problem
  • Updated 2 days ago
  • In Progress
  • (Edited)
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 CC Desktop. After launching it, I saw a red dot near the Assets tab. I clicked on it and after "Checking for updates...", it proposed to update Adobe CC Desktop ( ? ? ? I had 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, with and without AV running. Nothing helps.

This program is just a failure. Always new problems, failed updates, uninstallations and re-installations,... 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 (or rather rewriting it because it never worked correctly).

Details about these 2 errors :

Error 184


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 but I immediately switch to error 183... It's rather strange that the updater is trying to update a DLL that is already in use by Explorer.exe.

Error 183


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.
Photo of Patrick Philippot

Patrick Philippot

  • 351 Posts
  • 63 Reply Likes
  • upset

Posted 1 year ago

  • 1
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3850 Posts
  • 730 Reply Likes
Greetings Patrick, 

I've researched your issue a bit (not one I've seen before) and it looks like there was a similar problem for a user of Illustrator a while back. Fortunately there were instructions on how they fixed it that I think you can adapt to Lightroom if you are willing to give it a go: https://forums.adobe.com/thread/2131478 
Photo of Patrick Philippot

Patrick Philippot

  • 351 Posts
  • 63 Reply Likes
Thanks Rikk,

I already read the document mentioned in this thread but the error code 183 is not even mentioned there.
Photo of Patrick Philippot

Patrick Philippot

  • 351 Posts
  • 63 Reply Likes

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. I thought this bug was fixed. It's back.

Photo of Patrick Philippot

Patrick Philippot

  • 351 Posts
  • 63 Reply Likes
My fix did not last very long. The problem is back. In the Assets tab, CC Desktop tells me that an update is available and I'm getting the same message in Install.log  :

...
09/08/17 23:36:27:792 | [INFO] |  | HDSetup | HDPIM | TaskManager |  | HDPIM | 5668 | Completed 'EXTRACT' task for Package (Name: CoreSync-mul Version: 2.4.2.61), Time taken '0' sec

09/08/17 23:36:29:439 | [WARN] |  | HDSetup | HDPIM | RunProgramCommand |  | HDPIM | 2552 | Program "C:\Program Files (x86)\Adobe\Adobe Sync\CoreSync\customhook\CoreSyncCustomHook.exe" failed with exit code: 105

09/08/17 23:36:29:439 | [FATAL] |  | HDSetup | HDPIM | InstallHelper |  | HDPIM | 2552 | Error (Code = 183) executing in command 'RunProgramCommand' for package: 'CoreSync-mul', version:2.4.2.61

09/08/17 23:36:29:439 | [FATAL] |  | HDSetup | HDPIM | InstallHelper |  | HDPIM | 2552 | Error occurred in install of package (Name: CoreSync-mul Version: 2.4.2.61). Error code: '183'

09/08/17 23:36:29:656 | [INFO] |  | HDSetup | HDSetup | AppContext |  | HDSetup | 16016 | Exit Code: 183
-------------------------------------- Summary --------------------------------------
 - 2 fatal error(s), 0 error(s), 1 warnings(s)

FATAL: Error (Code = 183) executing in command 'RunProgramCommand' for package: 'CoreSync-mul', version:2.4.2.61

FATAL: Error occurred in install of package (Name: CoreSync-mul Version: 2.4.2.61). Error code: '183'
WARN: Program "C:\Program Files (x86)\Adobe\Adobe Sync\CoreSync\customhook\CoreSyncCustomHook.exe" failed with exit code: 105

According to this page error code 105 means that hdpim.db is corrupt or has wrong permissions. Since it's a SQLite database, I checked its validity and it is OK. Regarding the permissions, Everyone and Administrators have full rights. So I'm wondering what additional rights it may need. On my system hdpim.db was automatically re-created 2 ago because CC Desktop was out of sync and wanted to update products that were already up-to-date. So I renamed it and checked for updates again which solved the problem in the Apps tab.

I also noticed an error and a warning in CoresyncInstall.log :

[09.09.2017 18:53:20]: Always: **** Log Opened ****

[09.09.2017 18:53:20]: Info: customhook: Invoked with args: '--install --component=CoreSyncExtension' (CoreSyncCustomHook.cpp.main.700)

[09.09.2017 18:53:20]: Info: customhook: Component given: CoreSync (CoreSyncCustomHook.cpp.main.714)

[09.09.2017 18:53:20]: Error: customhook: Either Mode tag is absent or has invalid value (CoreSyncCustomHook.cpp.main.723)

[09.09.2017 18:53:20]: Info: customhook: Successfully elevated process privilege (CoreSyncCustomHook.cpp.elevateProcessPrivilege.893)

[09.09.2017 18:53:20]: Info: customhook: Install path doesn't exist, defaulting! (CoreSyncCustomHook.cpp.getDefaultPath.283)

[09.09.2017 18:53:20]: Always: **** Closing Log ****

I think there is something wrong with the message line in bold. From what I have observed when monitoring the program, there are 3 possible modes : --install, --uninstall or --kill. In my case --install was used. So it is present and I don't see why it could be invalid.
Photo of Patrick Philippot

Patrick Philippot

  • 351 Posts
  • 63 Reply Likes
Actually, I'm wondering whether this is not the same error as mentioned above for the Apps tab. It's not that difficult to intercept the zip file downloaded from the Adobe server when CC Desktop tries to update from the Assets panel (the file has a short lifetime but it's possible to make a copy if you are quick enough). It is trying to update only one package : CoreSync-mul. I opened the ZIP file and compared the binaries it contains to the ones that are already installed : all files are binary identical. So I guess CC desktop is also trying to update something that is already up-to-date. This appears to cause the crash because it considers this as an error and as a corruption of the database.

Renaming hdpim.db was enough to fix the same problem in the Apps tab but obviously, this was not enough to re-sync the CC Desktop status itself. Maybe there's another database that should be reset...
Photo of Patrick Philippot

Patrick Philippot

  • 351 Posts
  • 63 Reply Likes
Up!

Problem still not fixed.
Photo of raden adams

raden adams

  • 3 Posts
  • 0 Reply Likes
Hi Patrick, Have you heard from anyone about how to resolve the error 183 when updating the creative cloud app? Thank you, Raden Adams
Photo of Patrick Philippot

Patrick Philippot

  • 351 Posts
  • 63 Reply Likes
Hi Raden,

I thought I had found a fix by modifying the properties of all executable in the CC desktop folder (Run as an administrator) but the fix was temporary. The problem is back and I can't find a way to fix it. Resetting (renaming) the hdpim.db database didn't help either. This just forced me to reinstall Photoshop and Bridge.
Photo of raden adams

raden adams

  • 3 Posts
  • 0 Reply Likes
I am having the same error 183 when trying to update the creative cloud app: creative cloud failed to update error 183 is all it says. I, too, would like very much to get this issue resolved as it has been a while. Please reply with instructions on how to fix this error. Thank you, Raden Adams 
Photo of Patrick Philippot

Patrick Philippot

  • 351 Posts
  • 63 Reply Likes
Raden,

I tried again something that I had already done without any success but this time, it worked :

1. I killed all Adobe related processes.
2. I renamed C:\Program Files (x86)\Adobe\Adobe Creative Cloud to*.old
3. I renamed C:\Program Files (x86)\Common Files\Adobe\CoreSyncExtension to *.old
4. I downloaded the Adobe CC Desktop installer and installed again (run the installer as an administrator).

When I clicked on the Assets tab, an update was proposed and this time, it installed correctly. No error for the moment. I already fixed similar problems this way in the past but these problems were back after a while (generally when a new CC Desktop update was released. So I'm not too confident...

Hope this helps.
(Edited)
Photo of Patrick Philippot

Patrick Philippot

  • 351 Posts
  • 63 Reply Likes
This issue is marked as solved but it is not. There are workarounds that may or may not work but the problem itself is not solved. It just re-appeared on my system.
Photo of Patrick Philippot

Patrick Philippot

  • 351 Posts
  • 63 Reply Likes
Bump !

Problem still there.
Photo of Patrick Philippot

Patrick Philippot

  • 351 Posts
  • 63 Reply Likes
If this can help...

The failure always occurs at 90% after Adobe CC Desktop has created the c:\adobeTemp folder in which it stores the CoreSync installation files. That installation always fails and error 183 (or sometimes 184) is issued.
Photo of Patrick Philippot

Patrick Philippot

  • 351 Posts
  • 63 Reply Likes
As described above, the only way I can get Adobe CC Desktop (almost) to install properly is as follows :

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).

Then, when clicking on the Assets tab, an update should be triggered and will install correctly.

However, during this process, I have observed multiple times that explorer.exe crashes (no more desktop / only application windows). It is then automatically restored by Windows.

Really fed up of this.

Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3850 Posts
  • 730 Reply Likes
Patrick: This doc details error codes and causes: https://helpx.adobe.com/creative-cloud/kb/troubleshoot-download-install-logs.html

I spoke to some people in the Creative Cloud Support and their reply was " It looks like something on their computer is blocking the installation process.  I would recommend they try temporarily disabling any installed security software during the next update." 

Are you running any unique security software?
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3850 Posts
  • 730 Reply Likes
Patrick: This doc details error codes and causes: https://helpx.adobe.com/creative-cloud/kb/troubleshoot-download-install-logs.html

I spoke to some people in the Creative Cloud Support and their reply was " It looks like something on their computer is blocking the installation process.  I would recommend they try temporarily disabling any installed security software during the next update." 

Are you running any unique security software?
Photo of Patrick Philippot

Patrick Philippot

  • 351 Posts
  • 63 Reply Likes
Hi Rick,

Re: error codes :
183, C183     Unable to install the product.    Click Retry to download and install it again.
184, C184     File locked by another process.    Restart the system and try the installation again.

Very informative. Thanks, I did notice that the installation failed  :-) . Regarding error 184, the file appears to be locked by the installer itself which doesn't terminate properly after a failure.

> their reply was " It looks like something on their computer is blocking the installation process.  I would recommend they try temporarily disabling any installed security software during the next update."

This problem has been reported for the first time about 2 years ago (1 year ago by me in this forum). A lot of information has also been given here :

https://forums.adobe.com/thread/2364652
https://forums.adobe.com/thread/2486246
https://forums.adobe.com/thread/2377547
https://forums.adobe.com/thread/2291219

Since then, I (we) tried all recommendations published by Adobe, all tricks published by other users and all the system settings changes I thought could interfere, including disabling the antivirus and antimalware software (ESET Nod32 and Malwarebytes), of course. Nothing helped. I'm not alone with this issue. Could someone at Adobe start considering that there's a problem with the Coresync Extension module installer instead of always answering that our system configurations are the cause of the problem? It seems that nobody at Adobe is able to make another answer than "Please uninstall and re-install" (which is not that easy because the uninstaller is not clean). This is not the way I want to spend time on my system just to be able to use Adobe's software.

Since the update works when I use the procedure described above and since a full re-installation also sometimes works, it seems that nothing is preventing the installation of this software. It's Adobe CC Desktop that is unable to update itself under certain circumstances.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3850 Posts
  • 730 Reply Likes
I see your logs are no longer available at the above link (not surprised considering how long ago it was). Any chance we could get a new set of logs from you, Patrick?
Photo of Patrick Philippot

Patrick Philippot

  • 351 Posts
  • 63 Reply Likes
> Any chance we could get a new set of logs from you, Patrick?

https://www.dropbox.com/s/6qoffanl9ylpuq5/InstallLogs.zip?dl=0

Could you please unmark this case as solved ? It has never been.

Photo of Cristen Gillespie

Cristen Gillespie

  • 1268 Posts
  • 325 Reply Likes
I get the message on launch that I must repair, etc. I began to get it frequently when I subscribed to Amazon Prime and it's loading Amazon Music — if it's any help to know that. I figured the two were competing on startup, and sometimes CCApp just can't handle delays on my old computer (don't have Music on my laptop).  I quit, finish the launch process, open the CC app and relaunch. I never uninstall and reinstall for that message. I tried that once  for some issue it thought it was having and it proved useless.
Photo of Patrick Philippot

Patrick Philippot

  • 351 Posts
  • 62 Reply Likes
I get the message on launch that I must repair, etc. I began to get it frequently when I subscribed to Amazon Prime and it's loading Amazon Music
Interesting. I also got this message recently when launching Adobe CC Desktop. I'm not running anything from Amazon upon startup although I'm also a Prime subscriber. Clicking on Repair triggered a full re-installation and, as usual, clicking on the Assets tab after the installation ended triggered itself an update... which failed as usual with error 183.

By the way, one can wonder why, after a re-installation, the program needed to be updated. Is not the installer supposed to download the latest version ?

I'm still wondering why Adobe needed to invent such a complicated and messy/unstable tool just to maintain installed applications.

Photo of Patrick Philippot

Patrick Philippot

  • 351 Posts
  • 63 Reply Likes
If someone could explain how updates triggered when opening the Assets tab differ from standard updates, I would be grateful.
Photo of Patrick Philippot

Patrick Philippot

  • 351 Posts
  • 63 Reply Likes
A few additional remarks about this issue...

- It's now clear that the problem occurs when installing the CoreSync-mul package, version 2.4.4.71. Since this version number has never changed since the problem started to appear, why is it necessary to install it again with each update ? It's already there.

- I looked at CoreSyncInstall.log and eventually understood that the CoreSync installer is voluntarily killing the Explorer process, without asking the user and without considering possible negative side effects (this is why each time I thought that Explorer had crashed - nope, the process was just killed). This is a very questionable practice. I have never seen any installer daring to do this. No surprise that things can go wrong on certain configurations, depending on what components attached to Windows Explorer might be currently running.

If this is to avoid a system restart because some DLL is in use, I suggest to the installer developer to have a look at how a DLL can be unloaded and reloaded transparently. A good design would allow to avoid killing the explorer.exe process. So instead of telling us that our configurations have something wrong, the developer of this aggressive piece of code should ask himself what's wrong with his programming skills. Just incredible.
(Edited)
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3850 Posts
  • 730 Reply Likes
Thanks for the additional log, Patrick. The engineers are digging into it. 
Photo of Patrick Philippot

Patrick Philippot

  • 351 Posts
  • 63 Reply Likes
Rikk,

Could you please unmark this issue has solved ?
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3850 Posts
  • 730 Reply Likes
Patrick,

I just heard back from engineering and with your help, they've identified the issue and it should be fixed in an upcoming release. Thanks for your help.
Photo of Avner Kornfeld

Avner Kornfeld

  • 2 Posts
  • 0 Reply Likes
Would you find out what your engineers say the root cause for the "Error 183" issue reported? Also, please clarify when will be the upcoming release. I do not understand why Creative Cloud Desktop App attempts to update its program when it is up to date already. Also why new creative cloud program updates (the one couple of days ago, PhotoShop 19.1.6 release) revert back the "Error 183" state. After more than 20 hours, trying to follow every suggestion related to this error - after "fixing" the issue, I am back to the same message. What I am doing is:

(1) Creative cloud desktop app does NOT start at power-up. I, as a user decide to start it if I need it.
(2) Under "Preferences", "General" -- I turn off the "Launch at login" and turned off the "Always keep Creative Cloud desktop up to date

Since I know when there are updates, I will apply them on my will and not Adobe's. Again, these updates are not daily, weekly. So, why to test for updates at every startup, login, etc.
Sometimes, it is MUCH better to admit that a piece of software was not written, tested as it should. And really FIX it. 

Thanks,
-AK
Photo of Patrick Philippot

Patrick Philippot

  • 351 Posts
  • 63 Reply Likes
It seems that things are getting better since the last update (4.7.0.400).
Photo of Avner Kornfeld

Avner Kornfeld

  • 2 Posts
  • 0 Reply Likes
When is this release due?
It is a problem that persists, multiple users report this "update failures".
Thanks,
AK
Photo of Patrick Philippot

Patrick Philippot

  • 351 Posts
  • 63 Reply Likes
Hi,

By the way, there's a (maybe) related problem that appeared about one month ago (using Windows 10 1709). The first time I launch Adobe CC Desktop after Windows has booted, the app starts and I get the spinning wheel while the program is trying to login. This never happens. I get the spinning wheel forever or until it issues a message saying that it's taking unusually long to login ("Creative Cloud seems to be taking longer than usual to initialize."). Retrying doesn't help.

The only thing I can do to stop this is to log out my Windows session and to login again. This time Adobe CC Desktop logs in almost immediately.

Photo of Patrick Philippot

Patrick Philippot

  • 351 Posts
  • 63 Reply Likes
While I'm still not seeing any progress with the update failure problem, I can confirm that the new issue described above now appears systematically. If I want to successfully launch CC Desktop for the first time in a Windows session, I have to logoff from Windows first and then login again. Otherwise, CC Desktop will never login.