This article goes over the current workaround needed to resolve the "Failed to initialize Visual Basic" and "Runtime Error R6025" messages that prevent SOLIDWORKS from being launched on Windows 10.
Summary
When attempting to launch SOLIDWORKS on Windows 10, the user receives a "Failed to initialize Visual Basic for Apps" error, which is immediately followed by a "Microsoft Visual C++ Runtime Library" error. When these error windows are closed, the SOLIDWORKS splash screen will crash.
Solution
Currently, there are four known workarounds to resolve this issue. Each computer, however, may have a different way to repair the issue, please try one solution at a time. It is best to check the compatibility mode of the launcher first, as it appears to be the most common fix.
Compatibility mode of the launcher
- Right-click your SOLIDWORKS launcher shortcut on your desktop
- Click on Properties and go into the compatibility tab of the new window.
- Un-check the "Run this program in compatibility mode for:" box if it is selected.
- Apply the changes and click OK.
- Once you click OK verify if the shortcut begins to work again. If it does, repeat the steps above with your other SOLIDWORKS shortcuts.
Launching from the SLDWORKS.exe
- Navigate to the SOLIDWORKS install directory. By default, this is: C:\Program Files\SOLIDWORKS Corp\SOLIDWORKS
- Find the main SOLIDWORKS executable named "SLDWORKS.exe".
- Attempt to launch SOLIDWORKS via "SLDWORKS.exe". If the software successfully launches, proceed with the next steps.
- Create a new SOLIDWORKS shortcut using "SLDWORKS.exe". In Windows 10, the easiest way to accomplish this is to right-click on "SLDWORKS.exe" > Send to > Desktop (create shortcut).
- Confirm that SOLIDWORKS launches using this new shortcut.
Repair Microsoft Office
- Navigate to the Windows Control Panel then go to Programs -> Programs and Features
- Find what version of Microsoft Office is installed in the programs list and Modify the installation.
- Choose the repair radio button and click continue
- If this does not repair the issue re-try the "Launching from SLDWORKS.exe" again. It is possible that repairing Microsoft office allows the SLDWORKS.exe to work properly and launch SOLIDWORKS.
Creating a new Admin User Profile
- Click the Windows start button and select Settings. Next click Accounts -> Family & other People -> Add Someone else to this PC.
- Click on Change Account Type in the Family & Other People section and select the newly created profile.
- Under Account Type select Administrator for the user profile, then click OK to save it.
- Restart the machine and sign in as the new administrator account.
- Attempt to launch the SLDWORKS.exe located in C:\Program Files\SOLIDWORKS Corp\SOLIDWORKS again. If SOLIDWORKS launches successfully delete the old User Profile so the new Admin one is the main profile.
Re-installing SOLIDWORKS using the Installation Manager or Admin Image
Depending on the method SOLIDWORKS has originally installed another potential workaround is to uninstall SOLIDWORKS and re-install it using the other method.
If installed using an Administrative Image:
- On a computer where SOLIDWORKS is running properly create an Administrative Image. For instructions on how to create an administrative image please reference our guide.
- Copy the administrative image folder onto the computer with the VBA error, then uninstall the current installation of SOLIDWORKS.
- In the Administrative image folder navigate to the program SolidWorks.Msi located in \64bit\SOLIDWORKS folder.
This will install SOLIDWORKS using the source files within the administrative image, you can select what add-ins to install based on the license you will activate on it.
If installed using the Installation Manager, Source files, or Disks:
- Locate a copy of the SOLIDWORKS installation disks, source files, or installation manager for the version of SOLIDWORKS you wish to install.
- Follow the installation instructions outlined in our guide for standalone installations.
Comments
For me, this error started happening randomly (no Windows patches or even reboots between when it worked and stopped working), and the "Compatibility Mode" box was not checked, but when I check it and choose "Windows 7", that seems to work around this issue. I'm running Windows 10 (1809) and SW 2022 SP05.
Please sign in to leave a comment.