Excel ActiveX Controls on Windows 11 — What Breaks and How to Fix It

January 22, 2026 · 6 min read

ActiveX controls add interactivity to Excel worksheets — buttons, dropdown lists, date pickers, progress bars. They were the standard way to build UI in Excel for decades. They're also the most common thing to break when upgrading to Windows 11 or 64-bit Office.

Why ActiveX Controls Break on 64-bit Office

Most ActiveX controls are COM components compiled as 32-bit DLLs or OCX files. A 32-bit COM object cannot load inside a 64-bit Office process. When Excel (64-bit) tries to instantiate the control, it fails — sometimes silently, sometimes with an error dialog.

The symptom: you open an Excel file on a Windows 11 machine and see grey boxes where controls used to be, error messages about controls that can't be loaded, or buttons that appear but don't respond to clicks.

How to Identify Your ActiveX Controls

In Excel: go to the Developer tab (enable it in File > Options > Customize Ribbon if not visible). Click Design Mode. ActiveX controls will show a small handle when selected. Right-click a control and choose Properties — the "ProgID" or control class name tells you exactly what you're dealing with.

Common controls and their 64-bit status:

ControlFile64-bit?Resolution
CommandButton, TextBox, CheckBox (Forms 2.0)FM20.DLL✓ AvailableUsually works; re-register if not
ListBox, ComboBox (Forms 2.0)FM20.DLL✓ AvailableUsually works
TreeView, ListView, ProgressBar (MSComctl)MSCOMCTL.OCX✗ No 64-bit versionNo 64-bit version available. Use 32-bit Office or replace with modern alternatives
Calendar ControlMSCAL.OCX✗ 32-bit onlyReplace with date-picker workaround
Masked Edit ControlMSMASK32.OCX✗ 32-bit onlyReplace with Input Mask on text box
Rich TextboxRICHTX32.OCX✗ 32-bit onlyReplace with scrolling text box
Windows Media PlayerWMP.DLL✓ AvailableRe-register if missing

Fix 1: Re-register the OCX File

For controls that have 64-bit versions but aren't loading, the fix is re-registering the OCX file. Open Command Prompt as Administrator and run:

regsvr32 "C:\Windows\SysWOW64\MSCOMCTL.OCX"

For 64-bit controls in System32 instead of SysWOW64, use that path. You'll see a dialog confirming successful registration.

Fix 2: Replace 32-bit-only Controls

For controls with no 64-bit version (Calendar, Masked Edit, Rich Textbox), replacement is the only option.

Calendar Control replacement: Use a standard text box with a Date Picker. In the Developer tab, click Insert > More Controls and look for "Microsoft Date and Time Picker Control" — this has a 64-bit version. Alternatively, create a simple date input text box with format validation in VBA.

Masked Edit replacement: Select the text box where the Masked Edit was, go to Format Cells or the control's Properties, and set an Input Mask directly — this handles formatting without the 32-bit OCX dependency.

Fix 3: Stay on 32-bit Office (Temporary)

If immediate replacement isn't feasible, installing 32-bit Office on 64-bit Windows 11 allows all 32-bit ActiveX controls to continue running. This is a deferral, not a fix — 32-bit Office has worse performance on 64-bit Windows and will eventually need upgrading. But it buys time for a planned replacement effort.

Multiple files with ActiveX issues?

LegacyLeaps's scan identifies every ActiveX control in your files and flags which ones need replacement before you convert. Free scan, no commitment.

Scan My Files

Related Resources

Get tips like this in your inbox

Practical fixes for legacy Excel and Access problems. No spam.

← Back to all posts