Does Acrobat add-in cause word to crash?

Anonymous
2020-08-16T16:59:45+00:00

Split from this thread about the general release build of Word 2016 for Mac.

You are discussing the current Insider Fast beta build of Office 2019. Please use the special Insider forum for questions and comments about Insider builds. Your comments do not relate to Word 2016.

Your question has been moved to the Insider forum.

Thank you.

Wondering if anyone who has this problem also happens to have Acrobat DC installed as well. I'm on Insider Fast and upgraded to Build 16.41.20081200 without any issues.

But then I installed Acrobat and Word started crashing every time after opening a document. Did some searching around and found issues in the past with Acrobat plug-in. I uninstalled a template Adobe installs in Word (linkCreation.dotm), and this solved the issue. Although I lost the Adobe add-in functionality. This is the one along with the path:

Microsoft 365 Insider | Word | MacOS

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2020-08-22T13:34:19+00:00

Great find! Removed linkCreation.dotm and Word stopped crashing!

Was this answer helpful?

4 people found this answer helpful.
0 comments No comments

6 additional answers

Sort by: Newest
  1. Anonymous
    2020-08-15T11:39:42+00:00

    Thanks so much. This worked perfectly. Interestingly--at least to me--I installed Acrobat on July 30 for a project, and Word continued to work until the update I installed on August 13. Somehow the update "activated" a problem with a file that had been on the machine for a couple of weeks. In any event, thanks again.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-08-15T02:48:18+00:00

    Thank you - followed your instructions (deleted the linkCreation.dotm files) and Word is now back up and running.

    Still needs to be addressed by Microsoft and hopefully will be in the next update.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments