Fix the Cannot Create ActiveX Component Error in vMix When Adding a PowerPoint File
Question details
The user needs to resolve the "Cannot create ActiveX component" error that appears in vMix when adding a PowerPoint file.

- Product
- vMix and Microsoft PowerPoint
- Device & OS
- not provided
- Scenario
- The user is adding a PowerPoint file to vMix, likely for live video production or streaming, and needs the PowerPoint content to load correctly.
- Observed behavior
- vMix shows a "Cannot create ActiveX component" error when the PowerPoint file is added. Temporary remote assistance may have hidden the issue without fully resolving it.
Before troubleshooting, note your vMix version, the PowerPoint file format (.pptx or .ppt), and whether the file opens normally in PowerPoint or WPS Presentation. This helps you provide accurate details to vMix Support.
Contact vMix Support for vMix-specific ActiveX troubleshooting
Use this first because the error is generated by vMix when it tries to control PowerPoint through ActiveX, so only vMix Support can address application-specific causes.
The error is not a WPS Office failure. vMix uses Microsoft PowerPoint's ActiveX interface, and this error typically appears when vMix cannot create or communicate with the PowerPoint application object.
Go to https://www.vmix.com/support/ in your web browser.
Note your vMix version, Windows version, Microsoft Office or PowerPoint version, the exact error text, and the PowerPoint file format.
Use the vMix contact form or support portal to attach the details and describe the exact steps that reproduce the error.

Check Microsoft ActiveX settings guidance for Office files
Use this as secondary research when you want to understand the Office side of ActiveX, but do not rely on it as a full fix for a vMix-specific problem.
Use WPS Office as a Free PowerPoint File Alternative When vMix ActiveX Issues Block Your Workflow
While WPS Office cannot fix vMix's ActiveX automation error, it is a free, lightweight Microsoft Office alternative that opens, edits, and saves PowerPoint-compatible .pptx and .ppt files with a familiar interface, so you can prepare or convert presentation files without Microsoft PowerPoint.
- 1. Download WPS Office Free: Click "Download WPS Office Free" on the WPS Office website and install WPS Office on your Windows PC.
- 2. Open the PowerPoint file in WPS Presentation: Launch WPS Presentation and open the .pptx or .ppt file that fails in vMix.
- 3. Check and re-save the presentation: Review the slides for external links or legacy ActiveX objects, then save a clean copy as a .pptx file.
- 4. Add the saved copy in vMix: In vMix, remove the old PowerPoint input if present, then add the newly saved .pptx file and test again.

Frequently Asked Questions
Does WPS Office fix the vMix "Cannot create ActiveX component" error?
No. The error occurs in vMix when it tries to create or control a Microsoft PowerPoint ActiveX object. WPS Office is not part of that automation path, but you can use WPS Presentation to open, inspect, and re-save the PowerPoint file.
Can I use WPS Presentation instead of Microsoft PowerPoint for vMix?
vMix's PowerPoint input is designed for Microsoft PowerPoint ActiveX automation, so WPS Presentation cannot be used as the live PowerPoint automation source. You can still prepare or convert files in WPS, then load the saved .pptx file in vMix.
What information should I send to vMix Support?
Include your vMix build number, Windows version, Microsoft Office or PowerPoint version, the exact error message, the file format, and whether the file opens normally outside vMix.
Why does changing Microsoft Office ActiveX settings not fix it?
ActiveX errors in vMix can come from how vMix calls the PowerPoint application, not only from Office file security settings. The vMix Support team can check logs and reproduce the issue in the application context.
What PowerPoint file format should I use for vMix?
Use a standard .pptx or .ppt file saved from Microsoft PowerPoint or WPS Presentation, and avoid embedded legacy ActiveX objects or external automation dependencies that may trigger the error.




