Office Settings & Configuration

Restore a Custom Ribbon in Word 2016 Templates

Nimra MalikNimra Malik Nov 14, 2026 868 views

Question details

Restore custom Ribbon controls from a Word 2010 template in Word 2016.

Restore a Custom Ribbon in Word 2016 Templates
Product
Microsoft Word 2016
Device & OS
not provided
Scenario
A template or add-in contains Ribbon XML and possibly VBA macros that should be available in Word 2016.
Observed behavior
The custom Ribbon controls do not appear, potentially because of the XML schema, template deployment, or Startup-folder configuration.
Before you start

Locate the original template or add-in and identify whether it contains VBA macros. You will need access to its Ribbon XML and to Word's configured Startup folder.

Solution 1Recommended

Check the Ribbon XML and load the template from Word's Startup folder

Use this method when a template-based custom Ribbon should be available globally in Word 2016.

Store the Ribbon XML and any associated VBA code in the template or add-in rather than relying on an OfficeUI file. OfficeUI files are mainly intended for customizations made through Word's user interface.

Word 2016 supports the Word 2007 and Word 2010-and-later Ribbon XML schemas. If you need compatibility with both generations, use the appropriate separate custom UI parts; do not combine both namespaces in a single root element.

1
Inspect the template's Ribbon XML

Open the template in an Office Ribbon XML editor and check the customUI root namespace. Use http://schemas.microsoft.com/office/2009/07/customui for the Word 2010-and-later schema, or http://schemas.microsoft.com/office/2006/01/customui for the Word 2007 schema.

2
Check callbacks and macros

In the Ribbon XML editor, check that callback names match the procedures in the template's VBA project. If the customization uses VBA, save it in a macro-enabled template such as a .dotm file.

3
Find the Startup folder

In Word 2016, open File > Options > Advanced. Under General, select File Locations, select Startup, and choose Modify to view the configured folder path.

4
Deploy and reload the template

Close Word, copy the template into the configured Startup folder, and reopen Word. Check the Ribbon for the custom tab or controls.

5
Check macro security if needed

If the Ribbon appears but macro-driven controls do not work, review File > Options > Trust Center > Trust Center Settings. Enable macros only for a template you trust, following your organization's security policy.

Check the Ribbon XML and load the template from Word's Startup folder
Template-specific customizations: Placing a template in Startup makes it a global add-in. If the Ribbon is needed only for documents based on that template, open a document attached to the template instead.
Free Microsoft Office alternative

Edit Word Documents with WPS Office

WPS Office is a free, lightweight alternative with a familiar interface for editing Word documents. Its Microsoft Office format support helps you move existing files into your workflow, although it does not repair Word's template-based Ribbon customization.

Open and edit Microsoft Word DOC and DOCX filesUse a familiar Ribbon-style interface for document editingMove existing documents into WPS Office without starting from scratchWork with a free, lightweight office suite
QA img-9

Frequently Asked Questions

Where is the Word 2016 Startup folder?

In Word, open File > Options > Advanced. Under General, select File Locations, select Startup, and choose Modify to view the configured path.

Should I distribute the custom Ribbon through an OfficeUI file?

For a template-based Ribbon, keep the Ribbon XML in the template or add-in. OfficeUI files are mainly intended for customizations made through Word's user interface.

Which Ribbon XML schema should I use for Word 2016?

Word 2016 supports both the Word 2007 schema and the Word 2010-and-later schema. Check the customUI root namespace in an Office Ribbon XML editor and use the schema appropriate for the features and Word versions you need to support.

Why do my Ribbon buttons appear but fail to run macros?

Check that the XML callback names match the VBA procedures in the template. Then review File > Options > Trust Center > Trust Center Settings; macro security may block code from running.