Fix Excel VBA Error 426 When Creating Outlook or Word Objects
Question details
Resolve an Excel VBA error that occurs when creating Outlook or Word automation objects on one computer.

- Product
- Microsoft Excel, Outlook, and Word
- Device & OS
- Windows 10
- Scenario
- A VBA macro creates Outlook and Word objects on one computer but fails on another with apparently identical Windows and Office versions.
- Observed behavior
- The affected computer reports error 426 or an ActiveX error when the macro attempts to create an Outlook or Word object.
On the affected computer, check the exact VBA error number and description, and identify the line that fails. Confirm that desktop Word and classic Outlook are installed and can each open normally.
Repair Office and test object creation in a new workbook
Use this approach when the same automation code works on another computer but fails on the affected installation.
Open Word and classic Outlook from the Windows Start menu. Complete any first-run prompts and confirm that each application opens normally.
Close Office applications, then open Windows Settings > Apps > Apps & features. Select Microsoft 365 or Office, choose Modify, and run Quick Repair.
Open Excel, create a blank workbook, and press Alt+F11. In the VBA editor, choose Insert > Module and test CreateObject("Word.Application") and CreateObject("Outlook.Application") separately to identify which application fails.
If the test still fails, return to Settings > Apps > Apps & features, select Office, choose Modify, and run Online Repair. Open Word and classic Outlook again, then repeat the Excel test.
If CreateObject still fails after repair, uninstall and reinstall Office, then open Word and classic Outlook and repeat the test from Excel.

Check and refresh VBA references
Use this when the macro relies on an Outlook or Word object library reference, especially if a reference is marked missing.
Work with spreadsheets and documents in WPS Office
WPS Office is a free, lightweight alternative with a familiar interface for working with Office files and moving everyday document tasks between suites. It does not repair Microsoft Office COM registration or guarantee compatibility with Outlook automation macros.

Frequently Asked Questions
Why does the macro work on one computer but not another?
Matching Windows and Office build numbers do not rule out differences in application installation, COM registration, or VBA references. Open Word and classic Outlook on the affected computer, then test each CreateObject call in a new workbook.
Does CreateObject require an Outlook library reference?
No. Late-bound CreateObject("Outlook.Application") does not require the Outlook library reference. Early-bound declarations such as Outlook.Application do require the appropriate reference under Tools > References in the VBA editor.
Where can I repair Microsoft Office on Windows 10?
Go to Settings > Apps > Apps & features, select Microsoft 365 or Office, and choose Modify. Try Quick Repair first; if the problem remains, use Online Repair.
Can I automate the new Outlook for Windows with Outlook VBA objects?
The new Outlook for Windows does not support traditional Outlook COM automation. Use classic Outlook when a macro depends on Outlook.Application, and confirm it opens normally before testing the macro.




