Office Settings & Configuration

Troubleshoot a Missing Ribbon Separator in Office 2016 Custom XML

Algirdas JasaitisAlgirdas Jasaitis Nov 22, 2026 868 views

Question details

The user needs to determine why a separator in a custom Ribbon XML group is not visible in Office 2016.

Troubleshoot a Missing Ribbon Separator in Office 2016 Custom XML
Product
Microsoft Office 2016 Ribbon Custom UI
Device & OS
not provided
Scenario
A custom Ribbon group includes a separator alongside built-in controls such as Paste, Cut, Copy, and Find.
Observed behavior
The separator does not appear in the Office 2016 Ribbon.
Before you start

Identify the Office 2016 application hosting the Ribbon and locate the complete Custom UI XML, including its namespace. Note how the customization is loaded, such as through a document or an add-in.

Solution 1Recommended

Validate the Custom UI XML and Test a Minimal Ribbon Group

Use this approach to isolate whether the separator definition, its placement, or the host application is responsible.

Ribbon control types and valid parent elements depend on the Custom UI schema and the Office host. A menu separator is not necessarily valid as a direct child of a Ribbon group.

1
Check the namespace

Open the Custom UI XML in your XML editor and inspect the namespace on the customUI element. Use the corresponding Office Custom UI schema when validating the file.

2
Validate the separator placement

Run your XML editor's schema validation and check whether the separator element is supported inside its parent group. If you need a separator inside a menu, check the schema for the menuSeparator control instead.

3
Create a minimal test

In a test copy of the customization, reduce the XML to one custom tab, one group, a simple button, and the separator definition. Load it in the same Office 2016 application and check the Ribbon.

4
Check UI errors

If the host offers the setting, go to File > Options > Advanced > General and enable Show add-in user interface errors. Reload the customization and review any reported XML or control errors.

5
Reintroduce built-in controls

Add the Paste, Cut, Copy, and Find control references back one at a time, reloading the customization after each change to identify any interaction.

Validate the Custom UI XML and Test a Minimal Ribbon Group
A separator may require a different layout: If the schema does not allow the requested separator in a group, consider using separate groups or a supported menu layout. Exact behavior depends on the host application.
Free Microsoft Office alternative

Work With Office Documents in WPS Office

WPS Office is a free, lightweight alternative with a familiar interface and support for common Microsoft Office formats, making it easy to move everyday document work. It does not diagnose or fix Microsoft Office Ribbon XML.

Use a familiar interface for everyday office tasksOpen and edit common Microsoft Office formats, including DOCX, XLSX, and PPTXMove routine document work to a lightweight office suiteAccess common editing commands without configuring Office Ribbon XML
microsoft office alternative - wps office

Frequently Asked Questions

Can I place a menuSeparator directly inside a Ribbon group?

Do not assume it is supported there. Validate the XML against the schema matching the customUI namespace and check the allowed children of the group and menu elements.

How can I see Ribbon customization errors in Office 2016?

If available in your Office application, open File > Options > Advanced > General and enable Show add-in user interface errors. Reload the customization to check for messages.

Why should I test the separator without the built-in controls?

A minimal group helps distinguish a separator placement or schema issue from an interaction with other control definitions. Add the built-in controls back one at a time after the test.

What information should I include when asking for developer help?

Include the Office host and version, the complete minimal XML and namespace, how the customization is loaded, and any schema validation or UI error messages.