Inspiring

Answered

Muse not running after Creative Cloud Desktop app update

Forum|Forum|2 years ago
December 21, 2023
31 replies
65118 views

After the latest update to version 6.1.0.587 my copy of Adobe Muse will no longer open.

It partially loads, and then just closes.

In the Windows 10 logs I'm seeing -

Application: Muse.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 0000000000DEE917

Followed by -

Faulting application name: Muse.exe, version: 2018.1.1.6, time stamp: 0x5d3ed771
Faulting module name: Muse.exe, version: 2018.1.1.6, time stamp: 0x5d3ed771
Exception code: 0xc0000005
Fault offset: 0x000000000060e917
Faulting process ID: 0x3150
Faulting application start time: 0x01da33a19cf3e497
Faulting application path: C:\Program Files\Adobe\Adobe Muse CC 2018\Muse.exe
Faulting module path: C:\Program Files\Adobe\Adobe Muse CC 2018\Muse.exe
Report ID: 8266414e-2cfd-4801-b0e4-a5257678bd62
Faulting package full name:
Faulting package-relative application ID:

Anyone any idea why this is happening?

I have uninstalled and reinstalled Muse and that makes no difference.

This is a big problem as I need to update one of my Muse websites.

And please, DON'T just tell me that Muse is now unsupported and obsolete and I should be using something else, I'm well aware of that!

I have carried on using Muse until I can find something better, which I haven't yet, and it has always worked fine up until now.

I haven't knowingly made any changes which would prevent it from working, so why has it suddenly apparently failed?

Thanks, Dave.

File sync

Correct answer santiago p

hola esta es la solución a este problema

https://community.adobe.com/t5/creative-cloud-services-discussions/solution-2024-adobe-muse-not-open-after-updating-creative-cloud/m-p/14357536#M49903

N

nop77

Participant

Hello DaveH5, have you got Muse up and running again ? Best regards, nop77

kglad

Community Expert

@nop77

flagging is the best way to get a particular response, @DaveH5

I

itholland

Participant

Hi, I found this simple to fix by just renaming the Adobe IPC Broker. I just renamed it Adobe IPC Broker2 and hey presto Adobe Muse opens again.

kglad

Community Expert

Hi, I found this simple to fix by just renaming the Adobe IPC Broker. I just renamed it Adobe IPC Broker2 and hey presto Adobe Muse opens again.

By @itholland

and for others, rename AdobeIPCBroker in

win: C:\Program Files (x86)\Common Files\Adobe\OOBE\PDApp\IPC

mac: ->>Applications->Utilities->Adobe Application Manager->IPC (right click > show package contents)

o2centre

Participant

kglad and itholland,

THIS IS GREAT! I am on a Mac (Sequoia) and this saves me the steps on each Muse launch of first having to go to Applications > Adobe Creative Cloud > Uninstall Adobe Creative Cloud > enter my password in the Creative Cloud Uninstaller, and then finally launching Muse.

THANK YOU!

B

BZZT

Participant

I had this problem on my system (Win10 Home ver22H2), and following advice of others on this thread, closed all my Adobe programs, including Creative Cloud, but that wasn't enough. After experimentation, I figured out that you must keep two background programs from re-opening. I did this by temporarily renaming the execution files while using Muse, then naming them back when finished. The files are CCXProcess.exe and AdobeIPCBroker.exe. I found them through Task Manager by right-clicking on Creative Cloud Content Manager and Creative Cloud Interprocess Service (32-bit).

kglad

Community Expert

@BZZT

thank you for adding your suggestion.

DaveH5Author

Inspiring

Now updated to CC Desktop version 6.3.0.207.

Muse is still working for me.

deborahc84269408

Participant

Hola DaveH5

Pregunta: ¿Le cambiaste el nombre al archivo llamado AdobeIPCBroker el cual se encuentra en la carpeta IPC?

Saludos...

Deborah

DaveH5Author

Inspiring

No, none of the Creative Cloud Desktop files are now re-named.
It seems to be still working fine with Muse, which is now running normally for me, although I gather that this is not the case for some others. I don't know why this is I'm afraid.

D

dcutaneo

Participant

Unfortunately doesnt seem to be fixed on macOS. Adobe is updated to the latest 6.2.0.544

o2centre

Participant

Same here. On Mac (OS Monterey), I continue to have to use the Creative Cloud Uninstaller, sign in with my password, click Repair, and then launch Muse. At least it still works!

DaveH5Author

Inspiring

Still working fine here, and I am on Windows 10.

Are you all certain that you're now on the new version of CC Desktop?

anber

Participating Frequently

Yes. Unfortunately, I'm certain. I previously checked if I already had the latest version of the ACC Client App you mentioned (which is 6.2.0.554) before reinstalling Muse and restarting the system. And again, I saw what I saw before, which is 'Sign in to start your 7-day trial' (even though my account name, which I've been using with Adobe for 12 years, was displayed in this 'invitation' -> I was signed in).

kglad

Community Expert

what about the work-arounds, @anber ?

R

Robex

Participant

C:\Program Files (x86)\Common Files\Adobe\Adobe Desktop Common\IPCBox

rename AdobeIPCBroker for AdobeIPCBrokerSSS

DaveH5Author

Inspiring

Just today updated to CC Desktop version 6.2.0.554.

Delighted to say that the issue seems to now be fixed.

AdobeIPCBroker.exe is now intact again, but Muse is still running!

So glad that Adobe actually seem to have fixed it!

Cheers, Dave.

F

filmographie

Inspiring

Might be working on a Mac, but not in Windows10.

F

filmographie

Inspiring

Perhaps we need to cast a wider net to understand what might be happening: https://www.theregister.com/2024/02/01/windows_10_users_errors_hardware/?

DaveH5Author

Inspiring

I'm aware of that problem, I'm suffering it myself!

It's nothing to do with the Muse problem of course, but I suspect that the scenario is exactly the same, an update has been rolled out which has caused things to stop working, by accident not by design.

I hope Microsoft will fix their mistake on the next Patch Tuesday update. They should hang their heads in shame, as this will potentially have affected millions of people!

I don't believe they would suddenly drop Windows 10 support for some processors, as the theory seems to be in some places, without saying anything in advance.

Likewise with Adobe, I don't believe they would do something deliberately to stop Muse from working with no notice given, as they must know that many people are still using it.

It's just carelessness, nothing more, and I hope it will be fixed, both by Adobe and Microsoft.

saraz943607

Participating Frequently

@DaveH5I interacted directly with Adobe tech support several times on each of these issues-- first when they severed the connection with Typekit (with no notice to any of us) and this time, around the issue of severing the ability to open Muse anymore. On both occasions, the standard response was "Muse is EOL, and is no longer supported. Go to the community forum for an answer." In each case, they logged a support ticket and then closed it because my request could not be accommodated within their current policies. I think disconnected Typekit was a conscious decision, due to a change in their priorities. At that time, I was assured BY EMAIL by someone at Adobe that Muse would continue to be available to people who wanted to use it, and when I had it installed, it was recognized as being part of my plan. She pointed out that they continue to make other, older applications available, but this is not a question of availability. I can install it just fine from within Creative Cloud. I just can't open it and the fix of renaming that file doesn't work for me. In this case, I am quite sure they are aware of the problem and from what I was told in my exchanges with tech support, they have no intention of doing anything about it.

They are putting their resources behind emerging and ongoing needs, and those of us who still are using Muse have been left behind. We were given proper notice of the EOL, and it was put on us to adapt accordingly. For Adobe, it's just business. It's not personal to any of us, but we simply aren't enough of a factor in their balance sheet to matter very much. That's just how it is, under the present economic system.

johno69315311

Participant

If you have a Mac do this: On your startup disk go to: Applications > Utilities > Adobe Application Manager > IPC > AdobeIPCBroker. Now, add a random letter to this file name—for example, AdobeIPCBrokerx. Then launch Muse from the application, not from Adobe Creative Cloud.

J

jenh50541205

Participant

This has worked thank you so much!!

danielc39408068

Participant

I'm on the latest version of macOS Sonoma at the time of this writing, version 14.2.1. The repair creative cloud trick worked for me. If it is not working for you, remember that you must OPEN Adobe Muse. WHILE Creative Cloud is being "repaired". This causes the bad Creative Cloud Processes to end and not interfere with Muse opening on its own. To repair creative cloud on a Mac, go to Finder > Applications > Adobe Creative Cloud > Uninstall Adobe Creative Cloud. Click on that and it will give you the option to "Repair". Open Muse while the repair is happening, not after it has completed.

I can also confirm this works on MacOS Monterey.

kglad

Community Expert

@danielc39408068

thanks for another confirmation

saraz943607

Participating Frequently

Well, it still didn't work for me. Muse went further in opening, but when it was finally open, it just spontaneously shut down again. I tried both approaches to disabling AdobeIPCBroker (changing its name and/or putting a tilde in the extension), but for some reason, it just won't stay open on my computer. I also rebooted, to see if that helped, but it didn't. I tried putting in the old hack (three dll files) and that made things worse.

I'm glad the rest of you had success. I'm still going to have to move on from Muse, like it or not.

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded