Excel Error Codes

How to Fix Excel Run-time Error 53 on Mac (Windows XLSM File)

Muhammad TalhaMuhammad Talha Nov 3, 2026 870 views

Question details

The user encounters an external-link warning and Run-time error 53 when attempting to open an XLSM macro-enabled workbook on a Mac.

How to Fix Excel Run-time Error 53 on Mac (Windows XLSM File)
Product
Microsoft Excel
Device & OS
Mac
Scenario
Attempting to open and run a macro-enabled Excel workbook (.xlsm) originally created on a Windows computer.
Observed behavior
An external-link warning and Run-time error 53 appear, preventing the file from opening or running properly, regardless of whether the user clicks 'Update' or 'Don't Update'.
Before you start

Ensure you have access to a Windows PC or can contact the original author of the workbook, as editing the hard-coded VBA macro paths is often required to resolve this cross-platform compatibility issue.

Solution 1Recommended

Edit VBA Macros for Cross-Platform Compatibility

Modify the Visual Basic code to remove hard-coded Windows file paths and use dynamic commands that work on macOS.

Run-time error 53 occurs when VBA attempts to locate a file or path that does not exist on your Mac. This is almost always caused by hard-coded Windows directory structures (such as 'C:\Users\...') embedded in the macro code.

Updating the VBA code to use Mac-compatible path separators or dynamic path commands is essential to make the macros function properly on macOS.

1
Bypass the Macro on Startup

If the error prevents you from opening the file entirely, hold down the 'Shift' key while opening the file on your Mac to temporarily disable macros, or open the workbook on a Windows computer.

2
Access the VBA Editor

Navigate to the 'Developer' tab and click 'Visual Basic', or press 'Option + F11' on your Mac keyboard to open the Visual Basic for Applications (VBA) editor.

3
Locate Windows File Paths

Search the module code for any specific Windows file paths. Look for drive letters like 'C:\' or backslashes ('\') which are not recognized by macOS.

4
Update to Mac-Compatible Paths

Replace the Windows paths with Mac-compatible paths using forward slashes ('/'), or utilize VBA commands like 'Application.PathSeparator' to handle directory paths dynamically across both operating systems.

5
Save and Test the Workbook

Save the modified XLSM workbook. Close Excel and reopen the file normally on your Mac to verify that the Run-time error 53 is resolved.

Edit VBA Macros for Cross-Platform Compatibility
Developer Note: If you are the workbook author, consider using cross-platform VBA commands to check the operating system at runtime before executing file-handling scripts.
Free Microsoft Office alternative

Try WPS Office for Seamless Cross-Platform Work

If you frequently work with spreadsheet files shared across different operating systems, WPS Office offers a highly compatible, lightweight, and completely free alternative to Microsoft Office. It supports a wide range of formats and delivers robust features on both Windows and Mac.

Highly compatible with Microsoft Excel (.xlsx, .xlsm, .csv) formatsLightweight architecture ensures fast performance on both Mac and WindowsFamiliar tabbed user interface requires zero learning curveBuilt-in robust spreadsheet tools completely free of charge
QA img-9

Frequently Asked Questions

What causes Run-time error 53 in Excel for Mac?

This error is triggered when a VBA macro attempts to access a file or folder path that does not exist on your Mac. It typically occurs because the path was hard-coded for a Windows environment (e.g., trying to access a 'C:\' drive path).

Can I fix Error 53 without editing the VBA code?

If the error is directly caused by a hard-coded Windows path inside the macro, you or the author must edit the VBA code. However, you can bypass the error to simply view the spreadsheet data by disabling macros when you open the workbook.

Are XLSM files fully compatible between Windows and Mac?

While the .xlsm spreadsheet format itself is fully compatible, the VBA code embedded within it may not be. Macros that rely on OS-specific file paths, Windows-only libraries, or ActiveX controls will fail and require manual modification to work on a Mac.