'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Excel VBA Error 35010 and VBE7.DLL Crashes
Question details
Users experience Excel crashing during long-running tasks, returning error 35010 associated with the VBE7.DLL file.
- Product
- Microsoft Excel
- Device & OS
- Windows
- Scenario
- Running long VBA tasks or compiling code that involves 64-bit VBA callbacks and AddressOf statements.
- Observed behavior
- Excel VBA crashes with error 35010, the VBE7.DLL module fails, and it may corrupt other open files.
Close all running instances of Excel and ensure you have administrative permissions on your Windows PC to check system file properties and install updates.
Verify VBE7.DLL Version and Update Microsoft Office
Microsoft has released a patch for this bug in VBE7.DLL version 7.1.11.33. Updating Office is the most permanent fix.
The root cause of error 35010 is a confirmed bug within the 64-bit VBE7.DLL file, specifically version 7.1.11.31. By updating to version 7.1.11.33, the compilation crashes are resolved.
Open File Explorer and navigate to C:\Program Files\Microsoft Office\root\vfs\ProgramFilesCommonX64\Microsoft Shared\VBA\VBA7.1.
Right-click on the VBE7.DLL file, select 'Properties', and navigate to the 'Details' tab. Check the file version to see if you are running the problematic 7.1.11.31 build.
Open Excel, click on 'File' in the top-left corner, and select 'Account' from the sidebar. Click 'Update Options' and choose 'Update Now' to download the latest fix.
Troubleshoot AddressOf Statements and Disable Compile on Demand
If updating Office is not immediately possible, modifying your VBA code and editor settings can significantly reduce the frequency of the crash.
Try WPS Office for a Stable Spreadsheet Experience
Since Excel Error 35010 is deeply tied to Microsoft's 64-bit VBA compilation engine, consider switching to WPS Office. WPS offers a robust, highly compatible spreadsheet tool that handles complex data smoothly.
- 1. Download WPS Office: Visit the official WPS website and download the free installation package.
- 2. Install the software: Run the installer and follow the on-screen instructions to set up WPS Office on your Windows PC.
- 3. Open your workbooks: Launch WPS Spreadsheet and open your existing Excel files directly with full formatting compatibility.
Frequently Asked Questions
What causes Excel VBA Error 35010?
Error 35010 is caused by a bug in the 64-bit version of Microsoft's VBE7.DLL file (specifically version 7.1.11.31), typically triggered when the compiler processes AddressOf statements and callback functions.
Where can I find the VBE7.DLL file to check its version?
The file is typically located at C:\Program Files\Microsoft Office\root\vfs\ProgramFilesCommonX64\Microsoft Shared\VBA\VBA7.1. You can check the version by right-clicking the file, selecting Properties, and viewing the Details tab.
Does disabling Compile on Demand completely fix the crash?
No. While disabling Compile on Demand in the VBA Editor settings (Tools > Options > General) can significantly reduce the frequency of the crashes, it does not completely eliminate the root cause.
Can unused AddressOf callbacks trigger this error?
Yes. Even if the AddressOf callback procedures are not executed during runtime, simply having them present in your VBA code can trigger the compilation error in the affected VBE7.DLL version.
