Wps Office Macros Cannot Be Run Because The Vba Support Library Is Not Installed Hot Jun 2026
| Solution | Works in WPS Free | Works in WPS Pro | Requires purchase | |----------|------------------|------------------|--------------------| | Install VBA add‑in | ❌ | ✅ | ✅ (Pro license) | | Upgrade to WPS Pro | ✅ (by upgrading) | ✅ | ✅ | | Switch to MS Office | N/A | N/A | ✅ (unless already owned) | | View only (no macros) | ✅ | ✅ | ❌ |
This error occurs because the standard free version of WPS Office does not include the Visual Basic for Applications (VBA)
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later. | Solution | Works in WPS Free |
If the installer fails or you cannot find it, here are alternative ways to get macros working. A. Switch to WPS Office Professional
For professional users who rely heavily on VBA automation (financial models, data processing, legacy business macros), switching to Microsoft Office may ultimately be the most headache-free solution. However, for light to moderate macro usage, the steps above will get WPS running your VBA code without further issues. Can’t copy the link right now
You need the installation package (usually containing vba6.msi or vba71.msi ). These packages are widely hosted on tech forums, cloud drives, and software archives.
Navigate to C:\Program Files (x86)\Common Files\Microsoft Shared\VBA and delete all files in this folder. This removes the automatically installed plugin that causes conflicts. Then download and install a fresh VBA for WPS plugin. In rare cases
During installation, ensure you are installing the full version, which usually includes VBA capabilities.
In rare cases, you can point WPS to an existing Microsoft Office VBA installation. However, due to registry and DLL mismatches.
The error "Macros cannot be run because the VBA support library is not installed" is simply a missing component issue.
If macros run on colleagues' computers but not yours: