Skip to main content
Participant
August 9, 2020
Answered

Error code 37 unable to run CC

  • August 9, 2020
  • 1 reply
  • 457 views

Every time I try to open my apps in CC I get the following message as shown in the attached .jpg. I follow the instruction re Task Manager, to no avail. Help please. This has only appeared as a problem in the last week.

Thanks

This topic has been closed for replies.
Correct answer Rowena Wolton

Hi there,

Thank you for your reply. I had restarted my computer several times and looked at what was running in Task Manager.

When I looked further down the list in "background processes" I found that "windows installer.exe" was there; admittedly only using minimal resources. I stopped the process and, hey presto, all OK. So it was Windows Update that caused my problem.

1 reply

kglad
Community Expert
Community Expert
August 10, 2020

restart your computer and retry.

 

if that fails, reset the cc app: To reset the Creative Cloud desktop app, make sure it's in the foreground, then press:

Win: Ctrl + Alt + R
Mac: Cmd + Opt + R

if that fails, do a clean cc install:

uninstall every cc app including preferences, https://helpx.adobe.com/creative-cloud/help/uninstall-remove-app.html
then uninstall the cc desktop app, https://helpx.adobe.com/creative-cloud/help/uninstall-creative-cloud-desktop-app.html
clean your computer of cc files per http://www.adobe.com/support/contact/cscleanertool.html
restart your computer (don't skip this)
reinstall the cc desktop app, https://creative.adobe.com/products/creative-cloud.
if you're unable to install the cc desktop app at this stage, use an administrator account (solution 4 here, https://helpx.adobe.com/creative-cloud/kb/creative-cloud-missing-damaged.html)
use the desktop app to install your cc programs/trials

Rowena WoltonAuthorCorrect answer
Participant
August 17, 2020

Hi there,

Thank you for your reply. I had restarted my computer several times and looked at what was running in Task Manager.

When I looked further down the list in "background processes" I found that "windows installer.exe" was there; admittedly only using minimal resources. I stopped the process and, hey presto, all OK. So it was Windows Update that caused my problem.