When using COM Add-ins, common questions usually involve missing entries, empty lists, loading failures, and file formats; this FAQ covers 4 frequent questions.
FAQ
What should I do if the COM Add-ins list is empty?
- Confirm that the required third-party add-in has already been installed in Windows.
- Check whether the add-in has been properly registered in the system.
- Reopen the COM Add-ins management dialog and see whether the list refreshes.
- If the list is still empty, contact the add-in provider to confirm installation and compatibility details.
What should I do if a COM add-in fails to load?
- Check whether the add-in is compatible with your current Windows environment and WPS version.
- Close WPS Presentation, reopen it, and test the add-in again from the COM Add-ins dialog.
- If needed, register the add-in again.
- If the issue continues, temporarily disable the add-in and contact the provider for further support.
Could lag in WPS Presentation be related to COM add-ins?
- Open the COM Add-ins management dialog and check whether any third-party add-ins were added recently.
- Disable uncommon or suspicious add-ins one by one and observe whether performance improves.
- If a specific add-in updates or reinstalls itself automatically, manage it in the related external software as well.
- Keep only the add-ins you need to reduce the effect on startup and runtime performance.
What file format is commonly used for COM add-ins?
- Common COM add-in files are often in .dll or .ocx format.
- These files usually need to be registered in Windows before the app can recognize and use them.
- If the file exists but has not been registered, it may not appear or load correctly in the management dialog.
Glossary
| Term | Definition |
|---|---|
| COM Add-in | An extension component based on COM technology that adds extra functions to a desktop application. |
| Developer tab | A feature tab in WPS Presentation that is commonly used to access development-related or extension-related tools. |
| System registration | The process of writing component information into the system environment so that an application can recognize and call the add-in. |