If you’re encountering Runtime Error 53 while using Microsoft Word, Excel, or PowerPoint on macOS, it usually means a missing or corrupt file is causing the issue. This error can often be linked to missing add-ins, corrupt preferences, or software conflicts. In this guide, we’ll walk you through step-by-step solutions to fix it and get your Office apps running smoothly again.
Common Causes of Runtime Error 53
- Missing or corrupt Office files – Essential program files may have been deleted or damaged.
- Problematic third-party add-ins – Some add-ins may conflict with Office applications.
- Outdated Microsoft Office or macOS – Compatibility issues can arise if software is not updated.
- Corrupt application preferences – Settings files may become corrupted over time.
- File system errors on macOS – Disk errors can cause missing dependencies.
- Incorrect file path references – The application may be looking for files in the wrong location.
Step-by-Step Fixes for Runtime Error 53
1. Disable or Remove Problematic Add-ins
Add-ins can sometimes interfere with Office applications, leading to Runtime Error 53.
- Open Word, Excel, or PowerPoint in Safe Mode:
- Close the application.
- Hold down the Shift key while opening the app.
- If the error does not appear in Safe Mode, an add-in is likely the cause.
- Disable add-ins:
- Go to Tools > Add-ins.
- Uncheck or remove third-party add-ins.
- Restart the application and check if the issue persists.
- If you suspect a specific add-in, you can try reinstalling it after verifying the issue is resolved.
2. Repair or Reinstall Microsoft Office
If the Office installation is corrupt, reinstalling it can resolve the error.
- Open Finder > Applications.
- Locate Microsoft Word, Excel, or PowerPoint.
- Right-click and select Move to Trash.
- Empty the Trash to completely remove Office.
- Reinstall Office from the Microsoft website.
- After reinstalling, restart your Mac and check if the error is resolved.
3. Update macOS and Microsoft Office
Running outdated software can cause compatibility issues.
- Update macOS:
- Go to System Settings > General > Software Update.
- Install any available updates.
- Update Office:
- Open Word, Excel, or PowerPoint.
- Click Help > Check for Updates.
- Install the latest updates.
- Restart your Mac after installing updates to ensure the changes take effect.
4. Reset Microsoft Office Preferences
Corrupt Office preference files can trigger Runtime Error 53. Resetting them can help.
- Quit all Office apps.
- Open Finder, then go to:
~/Library/Preferences/ - Locate and move these files to the desktop:
com.microsoft.Word.plistcom.microsoft.Excel.plistcom.microsoft.Powerpoint.plist
- Restart the application and check if the error is resolved.
- If this fixes the issue, you can delete the old preference files. Otherwise, move them back to their original location.
5. Check for Missing System Files
macOS file system issues can sometimes lead to missing files needed by Office.
- Open Terminal and run the following command:
diskutil verifyDisk disk1or
sudo fsck -fy - If errors are found, restart your Mac in macOS Recovery Mode:
- Restart your Mac and immediately press Command (⌘) + R.
- Select Disk Utility > First Aid and run a disk repair.
- Restart your Mac and check if the issue is resolved.
6. Verify File Path and Permissions
Sometimes, the error occurs if the application is unable to locate a required file due to incorrect file paths or permission issues.
- Open Terminal and check the file path of missing dependencies using:
ls -l /path/to/missing/file - If the file is missing, reinstall Office or restore it from a backup.
- Ensure the correct permissions are set:
sudo chmod 755 /path/to/missing/filesudo chown $(whoami) /path/to/missing/file - Restart your Mac and check if the error is resolved.
Final Thoughts
By following these steps, you should be able to fix Runtime Error 53 in Word, Excel, or PowerPoint on macOS. If the issue persists, consider reaching out to Microsoft Support for further assistance. Keeping your system and software updated, along with regular maintenance, can help prevent such errors in the future.
Have you encountered this error before? Let us know in the comments how you fixed it!
