Keep Custom Ribbon XML from Being Removed from Word Normal.dotm
Question details
Keep custom Ribbon XML and macros available when Word saves its global template.

- Product
- Microsoft Word
- Device & OS
- not provided
- Scenario
- The user has added CustomUI Ribbon XML and macros to Normal.dotm and wants the custom tabs to remain available.
- Observed behavior
- Word may remove the CustomUI XML when Normal.dotm is saved, causing custom tabs and their associated macros to disappear.
Locate the existing Ribbon XML and macro code you want to move, and check Word's configured Startup folder. On Windows, you can find it under File > Options > Advanced > File Locations.
Load Ribbon customizations from a separate Word Startup template
Use a separate macro-enabled template as a global add-in instead of relying on Normal.dotm to retain the Ribbon XML.
In Word, open a new blank document and choose File > Save As. Select Word Macro-Enabled Template (*.dotm) and give it a name other than Normal.dotm.
Open the Visual Basic Editor from Developer > Visual Basic, select the new template project, and choose Insert > Module. Copy the relevant macros and Ribbon callback procedures into the standard module, then save the template.
Close the template in Word. Open the .dotm file in a RibbonX editor, add the CustomUI XML, and save the file. Check that each XML callback name matches a procedure with the appropriate callback signature in the template.
Copy the .dotm file into Word's configured Startup folder. On Windows, check the folder under File > Options > Advanced > File Locations, then select Startup.
Close and reopen Word, then look for the custom Ribbon tab and test its buttons. If the tab or macros do not load, check the XML callback names and your organization's macro security settings.

Edit Word documents with WPS Writer
WPS Office is a free, lightweight alternative with a familiar interface for opening and editing Word documents. It supports common Microsoft Office formats for easier migration, but it does not fix Word's Normal.dotm behavior or guarantee compatibility with VBA macros and custom Ribbon XML.

Frequently Asked Questions
Why should I avoid putting Ribbon XML in Normal.dotm?
Word may remove the CustomUI XML when it saves Normal.dotm. A separate .dotm file in Word's Startup folder loads as a global add-in and keeps the customization separate from the Normal template.
Where is Word's Startup folder?
In Word for Windows, go to File > Options > Advanced > File Locations and select Startup to see the configured path. The location and menus can vary on other systems.
Where should the Ribbon callback macros go?
Open Developer > Visual Basic, select the add-in template project, and use Insert > Module to add a standard module. Place the callback procedures there and ensure their names and signatures match the Ribbon XML.
Why does my custom tab not appear after restarting Word?
Check that the .dotm file is in the configured Startup folder and that its CustomUI XML was saved correctly. Also check Word's macro security settings and verify that callback names in the XML match the procedures in the template.
Can WPS Office fix the Normal.dotm problem?
No. Normal.dotm and its Ribbon XML are part of Microsoft Word. WPS Writer can edit common Word documents, but VBA macros and custom Ribbon XML may not be compatible.




