Benches macOS

10

Why won't Microsoft Word launch after rei…

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

Hello

Apologies for the slightly off-topic question - I realize that Word isn't Apple's purview. However, I have a Mac and need to use Word on it, and until now I have been able to. But recently I've had some problems with Leopard and I've had to reinstall it. Ever since, Word won't launch. I've tried reinstalling Office from the disc but still no luck. Any ideas?

10 replies

Sign in or join Beachball Help to reply.

  1. 0

    geoffco85

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Do you an error message when you open Word?

    Also try in a new user see if it will open there.

    Let me know if it opens in the new user.

  2. 0

    Ian Leslie

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    It just says - after bouncing quite a few times - the application MW has quite unexpectedly.

    Can you explain what you mean by new user?

    Thanks

  3. 0

    kwolson

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I'm in the same situation - no other problems with Leopard to date except MS Office 2004 won't open. Each program gives the following and then closes:

    "The Application Could Not Be Launched because of a shared library error: "<Microsoft Word><Apple;Carbon;Multimedia><CFMPriv_QuickTime>"

    I've already run TechTool Pro and Disc Utility to check permissions and such. Any further troubleshooting is above my ability when I see something like this!

    Anyone have ideas?

  4. 0

    Donald Palmer

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Try this.

    Goto your user/library/preferences/ and trash the
    com.microsoft.Word.plist

    Start Word and see what happens.

    If it works, go back to the same location and trash the plist of excel and so on.

  5. 0

    dechamp

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    How did you uninstall Office? Did you just drag the folder to the trash or did you run the Office Uninstaller in the "Remove Office" folder?

  6. 0

    kwolson

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    No luck, but thanks for the suggestion.

    Anyone have another idea?

  7. 0

    eekfreak

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Same thing happened to me after upgrading Quick Time last night, Word is now dead. I tried trashing the file as recommended above and it did not work, same error message:

    The application "Word" could not be launched because of a shared library error: "><Microsoft Word><Apple;Carbon;Multimedia><CFMPriv_QuickTime>"

    I don't have the original office disc so this is really tragic. Any help Mac?

  8. 0

    JoeJoetheDivo

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I'm having the same situation; the message:

    The application "Word" could not be launched because of a shared library error: "<Microsoft Word><Apple;Carbon;Multimedia><CFMPriv_QuickTime>"

    appears every time I try to open Word. Mine, too, seems to have started after I upgraded Quicktime. I'm a college student and my university basically lives off of Word. How do I fix this? Thank you!

    Joseph

  9. 0

    Gareth Alexander

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    The application "Word" could not be launched because of a shared library error: "<Microsoft Word><Apple;Carbon;Multimedia><CFMPriv_QuickTime>"

    One of our offices have reported this error this morning. It would be good to get an answer to this.

    Matthew Boyle

    Technical Assistant

    Sense Scotland

    Message was edited by: SenseScotland

    - clarifying the error we are getting.

  10. 0

    James Engelby

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Go to http://www.apple.com/downloads/

    Click to download Quicktime 7.4.5 for Tiger or Leopard.

    Install / Reboot

    This is usually what fixes it for me.