Fix the MSCOMCTL.OCX License Error in Office 365 VB6 Add-Ins
Question details
Resolve a licensing error affecting previously working VB6 COM add-ins that use MSCOMCTL.OCX in Office 365.

- Product
- Microsoft Office 365 and VB6 COM add-ins
- Device & OS
- not provided
- Scenario
- A user opens an Office application with a VB6 COM add-in after an Office Click-to-Run update.
- Observed behavior
- The add-in fails with runtime error 429 and a message that there is no appropriate license to use the functionality.
Record the full error message, the affected add-in name, and the Office version, build, and bitness. Note whether the problem began after an Office Click-to-Run update.
Check the MSCOMCTL.OCX Registry and Licensing Configuration
Compare the affected computer's configuration with applicable VB6 and add-in vendor guidance before making changes.
A registry or licensing configuration issue may be involved, but the error alone does not establish the cause. Registry changes should be made only with appropriate vendor guidance and a backup.
In the affected Office application, open File > Account and select About to record the version, build, and 32-bit or 64-bit edition.
Open the referenced OSIsoft article at https://techsupport.osisoft.com/Troubleshooting/KB/KB00682 and compare its applicability and licensing requirements with your add-in vendor's instructions.
Open Registry Editor by searching for regedit, then inspect only the locations specified in the applicable guidance. Compare the relevant MSCOMCTL.OCX registration and licensing settings without changing them.
If a setting appears incorrect, ask your administrator or add-in vendor to verify it. Back up the relevant registry keys before any approved modification.
Escalate the Add-In Failure to Microsoft or the Vendor
Use specialized support when the issue began after an Office update or the licensing configuration is unclear.
Work With Office Documents in WPS Office
WPS Office is a free, lightweight alternative with a familiar interface for working with Office documents. Its format compatibility can make moving everyday document work easier, but it does not fix Office's MSCOMCTL.OCX licensing error or guarantee support for VB6 COM add-ins.

Frequently Asked Questions
Why does the add-in report that there is no appropriate license?
The message can involve MSCOMCTL.OCX registration or VB6 licensing, but it does not identify the cause by itself. Compare the configuration with applicable vendor guidance and provide the full error to the add-in vendor.
Where can I find my Office build and bitness?
In the affected Office application, open File > Account and select About. Record the version, build, and whether Office is 32-bit or 64-bit.
Should I edit the registry to fix error 429?
Inspect the settings against applicable vendor guidance first. Do not modify the registry without a backup and confirmation from an administrator or the add-in vendor.
Will WPS Office repair the VB6 COM add-in?
No. WPS Office is an alternative for compatible Office documents; it does not repair Microsoft Office licensing or guarantee support for the affected VB6 COM add-in.




