Fix Excel Macro Files Not Working on Mac Due to ActiveX
Question details
The user is unable to use an Excel macro-enabled workbook on a Mac because it contains Windows-specific ActiveX controls, resulting in errors.

- Product
- Microsoft Excel
- Device & OS
- macOS
- Scenario
- Opening and attempting to use a macro-enabled workbook created on Windows that utilizes interactive controls on a Mac device.
- Observed behavior
- The controls fail to function, and Excel may throw a Runtime Error 429 indicating that the ActiveX component cannot create the object, even when VBA macros are explicitly enabled.
To resolve this compatibility issue, you will temporarily need access to a Windows PC running Microsoft Excel to modify and replace the unsupported controls in your workbook.
Replace ActiveX Controls with Legacy Form Controls
Switching from Windows-only ActiveX controls to standard Excel Form Controls ensures that your workbook functions seamlessly on both Windows and macOS.
ActiveX controls are inherently tied to the Windows operating system framework. Because macOS does not support this framework, no amount of macro security adjustments or trusting VBA projects will make ActiveX controls function on a Mac.
By identifying and replacing these controls with legacy Form Controls, you can maintain the interactivity of your workbook across all platforms.
Transfer your macro-enabled workbook (.xlsm) to a Windows computer and open it in Microsoft Excel.
Navigate to the Developer tab on the Excel ribbon. Click on 'Design Mode' in the Controls group to allow selection and editing of the existing ActiveX controls.
Click on the problematic ActiveX control (such as a drop-down menu, checkbox, or command button) to select it, and press the Delete key on your keyboard.
Still on the Developer tab, click 'Insert' in the Controls group. Choose the equivalent tool from the 'Form Controls' section (do not select from the ActiveX Controls section) and draw the new control onto your worksheet.
Right-click the newly inserted Form Control and select 'Assign Macro' from the context menu. Select the appropriate VBA macro from the list, click 'OK', and save your workbook. The file can now be used on your Mac.

Try WPS Office for Seamless Cross-Platform Spreadsheets
Dealing with restrictive platform errors can slow down your workflow. WPS Office provides a highly compatible, cross-platform alternative to Microsoft Office. It natively supports standard Excel formats like .xlsx and .xlsm, allowing you to manage complex spreadsheets and data effortlessly on your Mac without expensive subscriptions.
- 1. Download WPS Office: Visit the official WPS Office website and download the installation package designed for macOS.
- 2. Install the application: Run the downloaded installer and follow the simple on-screen instructions to set up the software on your Mac.
- 3. Open your files: Launch WPS Spreadsheets and open your existing Excel workbooks to enjoy fast, highly compatible document editing.

Frequently Asked Questions
Can I enable ActiveX controls in Excel for Mac?
No. ActiveX is a proprietary Microsoft Windows technology. There is no setting, add-in, or security workaround in macOS that can enable ActiveX controls in Excel for Mac.
What is the difference between Form Controls and ActiveX Controls?
Form Controls are built-in, lightweight Excel objects that are fully compatible with both Windows and Mac operating systems. ActiveX controls offer deeper programmatic integration and specialized event handling but are strictly limited to the Windows environment.
Will my VBA code still work if I switch to Form Controls?
Yes, standard VBA macros can easily be assigned to Form Controls. However, if your existing VBA code specifically references proprietary ActiveX control properties or events, you may need to slightly modify the script to match standard Excel objects.
Why does macro security not affect Runtime Error 429?
Macro security settings only determine whether VBA code is allowed to run. Runtime Error 429 is an architectural limitation meaning the Mac operating system lacks the underlying Windows components required to render the ActiveX object, regardless of security permissions.




