VBA & Macro Problems

Fix VBA Runtime Error 53 Caused by Adobe PDFMaker on Mac

Rana Garcia Sep 30, 2026 869 views

Question details

Users need to resolve a persistent VBA runtime error that appears when launching Microsoft Office applications on Mac due to an Adobe PDFMaker add-in issue.

How to Fix VBA Runtime Error 53 Caused by Adobe PDFMaker Add-In on Mac

Product: Microsoft Office (Word, Excel, PowerPoint)
Device & OS: Mac
Scenario: Opening Microsoft Office applications on a Mac where Adobe Acrobat is or was installed.
Observed behavior: A VBA runtime error 53 dialog box appears, indicating that the system cannot find the Adobe PDFMaker component at the specific path: /Library/Application Support/Adobe/MACPDFM/MacPDFM.framework.

Before you start

Ensure that all Microsoft Office applications (Word, Excel, and PowerPoint) are completely closed before you attempt to modify or delete any startup add-in files.

Solution 1Recommended

Remove Hidden PDFMaker Files using Terminal

This is the most reliable method, as the required Office startup folders and the linkCreation.dotm files are frequently hidden from view in the standard Mac Finder.

Adobe Acrobat updates sometimes place hidden add-in files into your Office Startup folder to enable PDF creation. Because these files can be hidden in Finder, using the Mac Terminal ensures you can successfully locate and remove them.

Launch Terminal

Press Command + Space to open Spotlight Search, type 'Terminal', and press Enter to launch the Terminal application.

Navigate to the Word Startup Folder

Copy and paste the following command into Terminal and press Enter: cd "/Library/Application Support/Microsoft/Office365/User Content.localized/Startup/Word/"

Delete the Word Add-in File

Type the command: rm linkCreation.dotm and press Enter. This will remove the problematic Adobe PDFMaker file for Microsoft Word.

Clean Up Excel and PowerPoint

Navigate to the Excel and PowerPoint startup folders within the same parent directory and run the command: rm SaveAsAdobePDF* to remove any similar PDFMaker files for those applications.

Restart Office Applications

Close Terminal and relaunch Microsoft Word, Excel, or PowerPoint to confirm that the VBA Runtime Error 53 is resolved.

Remove Hidden PDFMaker Files using Terminal

Permanent Fix Note: If you update Adobe Acrobat in the future, these add-in files may be recreated. Keep these Terminal steps handy in case the error returns after a software update.

Solution 2

Manually Delete the Startup Files via Mac Finder

If you prefer using a graphical interface and your system displays hidden files, you can manually navigate to the Startup folder and delete the PDFMaker files using Finder.

Free Microsoft Office alternative

Switch to WPS Office for a Hassle-Free Experience

Tired of dealing with broken add-ins and VBA runtime errors on your Mac? WPS Office offers a lightweight, highly compatible alternative to Microsoft Office. It natively integrates powerful PDF editing tools, eliminating the need for conflicting third-party startup add-ins.

1. Download the Installer: Visit the official WPS Office website and download the free version designed for Mac.
2. Install the Application: Open the downloaded file and follow the standard on-screen instructions to install WPS Office on your Mac.
3. Open Your Office Files: Launch WPS Office and directly open any of your existing .docx, .xlsx, or .pptx files to continue working immediately.

Completely free to use with a lightweight, fast-launching applicationSeamless format compatibility with Microsoft Word, Excel, and PowerPoint filesBuilt-in robust PDF creation and editing tools natively integratedFamiliar user interface requiring zero learning curve for Office users

microsoft office alternative - wps office

Frequently Asked Questions

Why did VBA runtime error 53 come back after I fixed it?

The error usually returns after an Adobe Acrobat software update. When Adobe Acrobat updates, it often automatically recreates the PDFMaker startup add-in files (like linkCreation.dotm) in the Office startup folders to restore its PDF features.

What exactly is the linkCreation.dotm file?

It is a Microsoft Word macro-enabled template file created by Adobe Acrobat. It runs in the background when Word starts to inject the 'Save as Adobe PDF' functionality into the Word ribbon. When its accompanying framework is missing or broken, it triggers Error 53.

Will deleting these add-in files prevent me from creating PDFs on my Mac?

No. Removing these specific startup files only disables the Adobe Acrobat shortcut tab inside Office. You can still create PDFs effortlessly using the native macOS 'Print to PDF' feature or the built-in 'Save As' > 'PDF' option in Microsoft Office.

What if Finder says the Startup folder does not exist?

The path is case-sensitive and often hidden by system permissions. If Finder cannot locate /Library/Application Support/Microsoft/Office365/User Content.localized/Startup/, it is highly recommended to use the Terminal method, which bypasses graphical hiding rules.

Excel & Data Problems