VBA & Macro Problems

How to Fix Word VBA Error 35010 and VBE Crashes in 64-Bit Office

Phi Hung Vo Oct 20, 2026 871 views

Question details

Users need to resolve Unexpected Error 35010 during VBA project compilation which causes the Visual Basic Editor (VBE) or Microsoft Word to crash.

How to Fix Word VBA Error 35010 and VBE Crashes in 64-Bit Office

Product: Microsoft Word (Microsoft 365)
Device & OS: Windows 11
Scenario: Compiling or executing VBA macros that contain Windows API callback procedures in a 64-bit Microsoft Office environment.
Observed behavior: The Visual Basic Editor or Word crashes unexpectedly, displaying Error 35010 due to threading conflicts with 64-bit VBA callback functions.

Before you start

Ensure you save backup copies of your VBA projects and documents, and close all active instances of Microsoft Word before making system changes or updating Office.

Solution 1Recommended

Update Microsoft Office to Version 2402 or Later

Updating Office installs the patched VBE7.DLL (version 7.1.11.33 or later) which officially resolves the 64-bit VBA threading conflict.

Microsoft introduced a fix for this specific VBA compiler error beginning with Microsoft 365 Version 2402 (Build 16.0.17304.20000). Updating your Office installation will replace the faulty VBA runtime file (version 7.1.11.31) with the corrected version.

Open Office Update Options

Launch Microsoft Word, navigate to 'File' in the top ribbon, and select 'Account' from the left sidebar.

Trigger the Update

Click on 'Update Options' under the Product Information section and select 'Update Now' from the drop-down menu.

Verify the Build Version

Wait for the update to complete, then check the 'About Word' section to confirm your build is 16.0.17304.20000 or newer.

Confirm the DLL Version

Open File Explorer and navigate to C:\Program Files\Microsoft Office\root\vfs\ProgramFilesCommonX64\Microsoft Shared\VBA\VBA7.1. Right-click 'VBE7.DLL', select 'Properties', go to the 'Details' tab, and confirm the version is 7.1.11.33 or later.

Update Complete: Once the runtime is updated to 7.1.11.33, the VBA compiler will correctly handle AddressOf callbacks without triggering Error 35010.

Solution 2

Conditionally Exclude API Callbacks for Diagnostics

Temporarily exclude callback-related code using conditional compilation to verify if Windows API callbacks are causing the crash.

Free Microsoft Office alternative

Switch to WPS Office for a Stable and Lightweight Experience

If persistent Microsoft Office VBA errors and crashes are disrupting your productivity, consider switching to WPS Office. It provides a lightweight, highly compatible alternative that natively supports Microsoft Word documents while offering a seamless and stable user experience.

1. Download the Installer: Visit the official WPS Office website and click the free download button to get the setup file.
2. Install WPS Office: Run the downloaded installer and follow the quick on-screen prompts to set up the software on your Windows PC.
3. Open Your Documents: Launch WPS Writer and seamlessly open your existing .docx files to continue working without interruption.

Fully compatible with Microsoft Word (.docx), Excel (.xlsx), and PowerPoint (.pptx) formats.Lightweight installation with significantly faster load times and fewer resource-heavy crashes.Familiar user interface requiring zero learning curve for users migrating from Microsoft Office.Free to use with built-in PDF editing, cloud sync, and advanced document management tools.

microsoft office alternative - wps office

Frequently Asked Questions

What causes Unexpected Error 35010 in Word VBA?

Error 35010 is typically caused by a threading conflict in the 64-bit VBA runtime (VBE7.DLL) when Windows API functions trigger callbacks (like TimerProc or WindowProc) within VBA's single-threaded environment.

How do I check my VBE7.DLL file version?

Open File Explorer and navigate to C:\Program Files\Microsoft Office\root\vfs\ProgramFilesCommonX64\Microsoft Shared\VBA\VBA7.1. Right-click the VBE7.DLL file, select Properties, and check the Details tab to view the exact file version.

Does VBA Error 35010 affect 32-bit versions of Microsoft Office?

No, this specific threading conflict and compiler crash is primarily observed in 64-bit versions of Microsoft 365 running on Windows 11. 32-bit environments generally handle these specific API callbacks without triggering Error 35010.

Excel & Data Problems