Muse not running after Creative Cloud Desktop app update

[DaveH5]

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.

[saraz943607]

@natashax4Thank you for that information. I checked out VEV and it doesn't seem like the right approach for my kind of content or design. I am new at this, but every plugin I have installed or which came preconfigured from my hosting account (a total of 7 so far) has an "enable autoupdate" option, so if you don't want to watch things every day, that could be one solution. However, I have already learned that some plugins can affect functionality, so I do not intend to let anything autoupdate except WordPress itself, through the Softaculous script that installed it. I will be in there every day anyway, and if a plugin needs updating, there's an alert in the plugins folder. I want to be able to run a manual backup before I update anything, just in case the update breaks something.

I looked into BLOCS that someone else mentioned in this thread and it's only for Macs, so I can't use that, either. I made the decision to go with an Optimized WordPress installation (includes LiteSpeed Cache and Quic.cloud CDN) in a hosting environment that meets my needs. It has 24/7 tech support by phone, and I think that if I am proactive in handling the plugins and do regular backups, their aggressive security measures should be enough for me.

I'd like to get away from Adobe altogether, but I'm heavily dependent on Acrobat, InDesign, Photoshop, and Illustrator for my print and web publishing, so I'm stuck with them for those. I waited four years for Muse to mature (I was using a simple HTML product before then) and then two years after I started using it, they announced the EOL. However, it wasn't until they cut off the Typekit connection that I had any problems, but I made it through that crisis. However, now their refusal to fix this problem with this latest Creative Cloud update pushed me past my limits of tolerating their insensitivity to their subscribers' needs and I made the decision to move on.

In addition, while I was looking around at how speed affects SEO performance, I did a few speed tests on my existing Muse-generated site and discovered that, among other things, the CSS was using old prefixes and the self-hosted web fonts were "overweighted" (which I think means too heavy).  So now I am even more convinced that I am making the right move in moving away from Muse once and for all. Yes, Muse did what I wanted to do, in a way that didn't require me to become proficient at coding, and it still gave me a beautiful responsive site. But times have changed and there are other ways of doing this that are more appropriate for my needs right now.  I probably should have moved on sooner, but was so close to finishing what I was doing (all static sites), I resisted having to learn something else. However, when it became evident it was time to start a blog, that pushed me into the WordPress world, and I'm just going to re-create the static pages in WordPress once I become proficient with it.

[Smooth Designs · Accepted solution]

hola esta es la solución a este problema 

https://community.adobe.com/t5/creative-cloud-services-discussions/solution-2024-adobe-muse-not-open...

[saraz943607]

I assume you are talking about a PC because of the x86 folder. Has anyone else tried this?

[Ribit]

Yes I have and it works AOK

[DaveH5]

hola esta es la solución a este problema 

https://community.adobe.com/t5/creative-cloud-services-discussions/solution-2024-adobe-muse-not-open...

By @Smooth Designs

Yes, this works perfectly, and thank you so much @Smooth Designs for finding it and telling us!

I did wonder whether it was just one part of CC Desktop which was causing the issue, and whether it could be identified and disabled.

As far as I can tell, CC Desktop still works fine with that file disabled.

Just to recap here, the file that needs to be renamed to disable it is, on Windows, in the

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

It's called AdobeIPCBroker.exe.

I disabled it the way I usually do when disabling a file, by putting a tilda in place of the middle character of the file extension, making it AdobeIPCBroker.e~e.

Any other change will work just as well though.

This is much easier than the other methods we've been using!

I'm afraid I don't know where that file is on a Mac, but it's presumably the same file so can just be searched for.

Cheers, Dave.

[kglad]

p.s. AdobeIPCBroker.exe is used by adobe cc to facilitate communication among its various parts.

[PunkPea Studios]

:). Awwesome works many thanks

[danielc39408068]

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]

@danielc39408068 

thanks for another confirmation 

[saraz943607]

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.

[kglad]

@saraz943607 

timing is important.  rename the file and then immediately open muse.

[saraz943607]

Are you saying that this is only a temporary fix and has to be repeated each time you want to run Muse? It doesn't stay fixed?

[kglad]

correct, everything so far is a temporary work-around, not a fix.

this is apparently incorrect.  see the next message.

[DaveH5]

Strange, this fix seems to work perfectly for me.
I renamed the file, rebooted, ran CC Desktop, which opened and appeared to still work normally.

Then I launched Muse from CC Desktop, and Muse opened and loaded normally.

Timing didn't seem to be an issue at all.

[kglad]

oh, i didn't know that.  i stand corrected.

[saraz943607]

@DaveH5  Did you install Muse from within CC Desktop BEFORE you did the fix? I want to try this one more time to see if I can replicate what you did.

[DaveH5]

@DaveH5  Did you install Muse from within CC Desktop BEFORE you did the fix? I want to try this one more time to see if I can replicate what you did.

By @saraz943607

I haven't reinstalled anything, it's the same installation of CC Desktop and Muse that I've always used.

[saraz943607]

I just had to reinstall my entire computer and lost my prior installation of Muse, which was working as long as I didn't allow Creative Cloud to update. Now I don't have a choice about which version of Creative Cloud to use, but Adobe tech support did give me a downloadable installation file. However, when I installed that, I ran into the same problem because I hadn't done the fix. I could try installing Muse from the downloadable file instead of through CC desktop and then do the fix on the file, reboot, and see what happens. I'll do that now and see if it changes anything for me.

[kglad]

there are some cc desktop app choices.

 use the alternative download links at page bottom here, https://helpx.adobe.com/in/download-install/kb/creative-cloud-desktop-app-download.html

[saraz943607]

@kgladTried that, too. Didn't change anything. Did everything, rebooted each time (cold boot after waiting 30 secs. for the RAM to clear, not restart, which is incomplete) and nothing will get Muse to stay open after it loads. It opens fully then immediately disappears. I'm glad the rest of you found a solution that works for you. Unfortunately, I am not in that group, so have a great year. Over and out!

[uservasavoir]

Hi everybody,

On my Mac (Hackintosh Sonoma) i changed (rename) with administror password teh file

->>Applications->Utilities->Adobe Application Manager->IPC->AdobeIPCBroker.app

By 

->Applications->Utilities->Adobe Application Manager->IPC->AdobeIPCBrokerSSSS.app

And it works ...

[kglad]

thanks for that @uservasavoir 

in summary, the easiest work-around is:

rename AdobeIPCBroker in

win:

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

mac:

->>Applications->Utilities->Adobe Application Manager->IPC

[Proit]

Thats great. It works. Thank you very much. It is the easiest way! Many Greetings from Germany.

[kglad]

on behalf of the users that did the real work of finding these solutions, you're welcome ( from the usa).

[CGI619]

THANK YOU!  THANK YOU!  THANK YOU!