Articulate Ribbon not working

Hi Jeanette,

Sorry to hear about the trouble!

I recommend confirming that you have a supported version of Office and PowerPoint installed:

Articulate Studio '13 requires a 32-bit desktop version of Microsoft Office. It won't work with:

• 64-bit versions of Office
• Browser-based (online) components of Office 365
• Click-to-run versions of Office 2010

Note: Visual Basic for Applications must be installed. It's part of the typical Office setup. If it wasn't included in your installation, here's how to install it.

Here's how to tell which desktop version of Office you have.

If the issue continues, please try the troubleshooting steps outlined in the following article:

The Articulate Tab on the PowerPoint Ribbon Is Missing

(This should also resolve an unresponsive Articulate Ribbon)

Also, please make sure that you're working with local project files:

• Work on your local drive (your C: drive). Working on a network drive or a USB drive can cause erratic behavior, including file corruption, loss of audio, and other unexpected behavior. 
• You should also make sure the directory path to your project files and your published output is less than 260 characters (for example C:\Articulate).
• Avoid using special characters, accents or symbols in your file names (this includes spaces and underscores).

Additional information regarding "Naming Files, Paths, and Namespaces" in Windows operating systems can be found in the following Microsoft article.

If that doesn't fix the problem, please try repairing Studio '13:

Articulate Support - How to Repair Articulate Studio '13

If you're still experiencing these issues, please try the following troubleshooting steps:

Unexpected or Erratic Behavior in Articulate Studio

Let me know if you try all of those suggestions and still don't see the ribbon in PowerPoint.

Best,

Christine

I'm running PowerPoint 2007

Thanks for that information, Jeannette!

However, I'm afraid that's not quite enough to go off of. Please make sure you've read through the information I've shared and attempted the troubleshooting steps I provided. 

Thanks!