- Adobe Acrobat 2017
- Office 2013, Office 2016, Office 365 Apps for Business, Office 365 Apps for Enterprise, and later.
Issue: Word or Excel pop up this warning 3 times upon opening a document or spreadsheet.
"The function you are attempting to run contains macros or content that requires macro language support. When this software was installed, you (or your administrator) chose not to install support for macros or controls.'
Cause: Acrobat PDFMaker Add-in
- PDFMaker add-in found in Office 2013 and later versions, select File > Options > Add-Ins. Next to Manage COM Add-ins select Go. You will see a dialog box that resembles the following screenshot:
- Incompatibility between Adobe Acrobat 2017 (Adobe Acrobat COM add-in) and Office apps.
- After installing/repairing Adobe Acrobat Standard, macro warning in Word "The function you are attempting to run contains macros or content that requires macro language support."
Solution: disable Acrobat PDFMaker Office COM Add-in
Manually disable Acrobat PDFMaker Office COM Add-in
If you have administrative permissions, you can disable the add-in by following these steps in each affected Office program:
- Open a Office program.
- Select File > Options > Add-ins.
- In the Manage drop-down list, choose COM Add-Ins, and then click on Go.
- Clear the check box for Acrobat PDFMaker Office COM Add-in (similar to the Office 2010 screen shot) and click OK.
Registry edit to disable Acrobat PDFMaker Office COM Add-in
Alternatively you may prefer to do this registry edit.
Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.
First, exit the Office program that you're having issues with when the PDFMaker add-in is loaded, and then use one of the following methods to start Registry Editor.
We had success with disabling the Acrobat PDFMaker Office COM add-in using this registry fix: https://github.com/itsolver/gsuitedev/tree/master/M365/Fixes/DisableAcrobatAddin
Note: we discovered that repairing or reinstalling Adobe Acrobat causes the issue to resurface, necessitating a repeat of one of the above fixes.