Office for Mac Issues

Fix PowerPoint for Mac Crashing When Running VBA Code

Ayan MasoodAyan Masood Nov 3, 2026 869 views

Question details

The user needs to resolve an issue where running VBA macros causes PowerPoint for Mac to crash unexpectedly, often returning an EXC_BAD_ACCESS error.

Fix PowerPoint for Mac Crashing When Running VBA Code
Product
Microsoft PowerPoint
Device & OS
macOS
Scenario
Executing VBA code in a presentation, particularly macros that interact with system UI components like AppKit or the Touch Bar.
Observed behavior
PowerPoint experiences a hard crash and shuts down immediately, generating an application-level memory access failure report (EXC_BAD_ACCESS).
Before you start

Make sure to save any unsaved work in other applications, as application-level memory crashes can occasionally disrupt system stability. Create a new, blank presentation to test your VBA code safely before applying fixes.

Solution 1Recommended

Isolate the VBA Procedure and Disable Touch Bar Integration

Identify the exact line of code causing the memory conflict and disable Mac hardware integrations like the Touch Bar that commonly trigger this crash.

The EXC_BAD_ACCESS error indicates that PowerPoint is trying to access restricted memory. This often happens when older VBA commands attempt to interact directly with macOS AppKit or Touch Bar providers, which are tightly restricted in newer macOS versions.

1
Test in a blank presentation

Open PowerPoint and create a new, blank presentation. Press Option + F11 to open the VBA editor, paste your macro, and run it. If it doesn't crash, the issue is specific to your original file.

2
Comment out UI-interacting code

In your VBA script, temporarily add an apostrophe (') before any lines of code that trigger custom dialog boxes, user forms, or external application calls. Run the code again to pinpoint the exact failure point.

3
Disable Touch Bar settings

If your Mac has a Touch Bar, go to Apple Menu > System Settings > Keyboard. Change the 'Touch Bar shows' setting to 'Expanded Control Strip' or 'App Controls' to prevent PowerPoint from dynamically triggering its own Touch Bar provider.

Isolate the VBA Procedure and Disable Touch Bar Integration
Code Modernization: Consider replacing native Mac API calls in your VBA script with built-in Office VBA equivalents, as cross-platform compatibility has become stricter in recent updates.
Free Microsoft Office alternative

Try WPS Office as a Stable Alternative for Mac

If Microsoft PowerPoint continues to crash on your Mac due to VBA or system integration bugs, consider switching to WPS Office. It provides a lightweight, highly compatible alternative with seamless formatting support and excellent stability on macOS.

  1. 1. Download the installer: Visit the official WPS Office website and download the Mac version.
  2. 2. Install WPS Office: Open the downloaded .dmg file and drag the WPS Office icon into your Applications folder.
  3. 3. Open your presentation: Launch WPS Presentation and open your .pptx files directly without losing any formatting or design layouts.
Highly compatible with Microsoft PowerPoint (.pptx) formatsLightweight architecture optimized for smooth macOS performanceFree to download with a familiar, easy-to-use tabbed interfaceFewer crashes related to complex system-level macOS integrations
microsoft office alternative - wps office

Frequently Asked Questions

What does EXC_BAD_ACCESS mean in PowerPoint for Mac?

EXC_BAD_ACCESS is an application-level memory access failure. It means PowerPoint tried to access a block of memory it didn't have permission for, often caused by conflicts between older VBA scripts and newer macOS security protocols.

Why did my PowerPoint VBA macro stop working after a macOS update?

Apple frequently updates system components like AppKit to enhance security and stability. If your VBA macro interacts directly with these updated components, the older code may no longer be compliant, resulting in a sudden crash.

Can I recover my presentation if PowerPoint crashed while running a macro?

Yes. Upon reopening PowerPoint, the AutoRecovery feature should prompt you to restore the last saved version of your file. However, you should avoid running the same macro until you have identified the line of code causing the crash.