VBA & Macro Problems

Fix a PowerPoint PPAM Add-In Macro Blocked by Security Settings

Kushani NimanthikaKushani Nimanthika Nov 14, 2026 868 views

Question details

Identify why a private PowerPoint PPAM add-in works on one computer but reports a disabled or missing macro on another.

Fix a PowerPoint PPAM Add-In Macro Blocked by Security Settings
Product
Microsoft PowerPoint PPAM add-in
Device & OS
not provided
Scenario
A private add-in is installed on two computers after macro permissions and trusted locations have been reviewed.
Observed behavior
The add-in works on one computer but displays a macro-disabled or macro-not-found error on the other.
Before you start

Keep access to both computers so you can compare their PowerPoint installations. If you maintain the add-in, locate its editable source presentation and any external DLLs or controls it uses.

Solution 1Recommended

Compare Office bitness and test the add-in with a matching version

Use this check when the same PPAM works on one computer but not another, even though both run PowerPoint 16.

The Office version number does not identify whether the installation is 32-bit or 64-bit. VBA declarations or external dependencies designed for 32-bit Office can prevent an add-in from working in 64-bit Office.

1
Check the working computer

In PowerPoint, open File > Account > About PowerPoint and note whether the version is 32-bit or 64-bit.

2
Compare the affected computer

Open File > Account > About PowerPoint on the computer showing the error and compare its bitness with the working installation.

3
Test with matching bitness

If the installations differ, test the add-in in an Office installation with the same bitness as the working computer. For example, one reported case was resolved by installing 32-bit Office.

4
Review incompatible code

If you have the editable source, open it in PowerPoint and use Alt+F11 to inspect VBA declarations and dependencies. Update Windows API declarations for 64-bit VBA where needed, and check that external DLLs or controls support the installed Office architecture.

Compare Office bitness and test the add-in with a matching version
Changing Office architecture: Changing from 64-bit to 32-bit Office may require uninstalling and reinstalling Office. Check organizational requirements and other add-ins before making the change.
Free Microsoft Office alternative

Create and Edit Presentations with WPS Office

WPS Office is a free, lightweight alternative with a familiar interface for working on presentations. Its PowerPoint format compatibility makes it easier to move existing files into a new workflow, though it does not fix Microsoft PowerPoint PPAM add-in errors.

Create and edit presentations in a familiar interfaceOpen and save Microsoft PowerPoint PPTX presentation filesUse a free, lightweight office suite for everyday workMove presentation content into WPS without relying on the affected PowerPoint add-in
QA img-9

Frequently Asked Questions

How do I check whether PowerPoint is 32-bit or 64-bit?

Open File > Account > About PowerPoint. The About window identifies the Office installation as 32-bit or 64-bit.

Does a macro-disabled message always mean a security setting is wrong?

No. An add-in may also fail because of incompatible VBA declarations or external dependencies. Compare Office bitness on the working and affected computers before changing security settings.

Will signing the PPAM fix a 32-bit compatibility problem?

No. Signing can establish a trusted publisher when the relevant policy accepts the certificate, but it cannot make incompatible code or dependencies work in a different Office architecture.

Why does a Ribbon button say its macro cannot be found?

The add-in may not be loaded, or the Ribbon XML callback may not match an available public VBA procedure. Check File > Options > Add-ins and compare the callback name and signature with the editable source.