VBA & Macro Problems

Fix Word VBA Changes Not Saved to Normal.dotm in Office 365

WPS Editor Oct 1, 2026 868 views

Question details

Users are unable to save VBA macro changes directly to the Normal.dotm template in recent Microsoft Word updates, resulting in lost code when the application closes.

Fix Word VBA Changes Not Saved to Normal.dotm After Office Updates

Product: Microsoft Word 365
Device & OS: not provided
Scenario: Writing or editing VBA macros in the Visual Basic Editor and attempting to save the changes to the default Normal.dotm template.
Observed behavior: Changes made to VBA macros are saved to temporary files (such as ~WRLxxxx.tmp) instead of Normal.dotm, causing all recent edits to disappear after Microsoft Word is closed.

Before you start

Before applying any workarounds, manually export your current VBA modules from the Visual Basic Editor to a local folder to ensure your macro code is safely backed up.

Solution 1Recommended

Use a Custom Macro to Force Save Normal.dotm

Run a specific VBA workaround macro to manually force Word to save changes directly to the Normal template, bypassing the bug caused by using the Ctrl+S shortcut.

In affected versions of Word (such as 2405, 2406, and 2408), using Ctrl+S in a Normal.dotm module can cause subsequent changes to be written to a temporary file. Running a manual save macro overrides this behavior and ensures the actual template file is updated.

Open the Visual Basic Editor

Press Alt + F11 in Microsoft Word to open the Visual Basic Editor (VBE).

Insert the Workaround Macro

Create a new module and paste the following code: Sub NormalTemplateSave() \n Application.NormalTemplate.Saved = False \n Application.NormalTemplate.Save \n End Sub

Run the Macro to Save

Instead of pressing Ctrl+S, run this NormalTemplateSave macro every time you finish modifying your Normal template or VBA code.

Use a Custom Macro to Force Save Normal.dotm

Avoid Ctrl+S: Do not use the Ctrl+S shortcut in the Visual Basic Editor while this bug is present, as it triggers the temporary file glitch.

Solution 2

Enable Prompts to Save the Normal Template

Configure Word settings to explicitly prompt you to save the Normal template upon closing the application.

Solution 3

Roll Back Microsoft Office Version

Revert your Microsoft Office installation to a stable version prior to the 2405 update to avoid the temporary file saving bug completely.

Free Microsoft Office alternative

Try WPS Office for Stable and Reliable Document Editing

Experiencing persistent bugs and lost macros after recent Microsoft Office updates? WPS Office provides a lightweight, highly compatible alternative for your document editing needs. It handles Word files seamlessly without the update-related saving glitches.

1. Download WPS Office: Visit the official WPS website and download the free installation package for your operating system.
2. Install and Launch: Run the installer and follow the on-screen instructions. Once installed, open WPS Writer.
3. Open Your Documents: Drag and drop your existing Word documents or templates directly into WPS Office to continue editing without interruption.

Fully compatible with Microsoft Word formats (.docx, .doc, .dotm)Stable and lightweight alternative avoiding recent Microsoft update bugsFamiliar user interface for a seamless transitionFree to download and use for essential office tasks

microsoft office alternative - wps office

Frequently Asked Questions

Why are my VBA macros disappearing when I close Word?

In recent Word 365 updates (versions 2405, 2406, and 2408), a bug causes the Visual Basic Editor to save changes to a temporary file rather than the Normal.dotm template. Because the main template is not updated, your changes are discarded when the program closes.

Where does Word save Normal.dotm temporary files?

When the saving bug triggers, Word writes your VBA changes to a temporary file, typically named similar to ~WRLxxxx.tmp. These files are usually located in the same directory as your original Microsoft templates or in your system's standard temporary folders.

Does pressing Ctrl+S in the Visual Basic Editor still work?

If you are using an affected Office update, pressing Ctrl+S in the Visual Basic Editor can trigger the temporary file issue on subsequent saves. It is highly recommended to use a custom save macro or rely on the 'Prompt before saving' exit feature instead.

Will Microsoft fix the Normal.dotm saving bug?

This issue has been widely reported via Microsoft's feedback portal by the user community. Until an official patch is rolled out in a future Office update, users must rely on custom VBA save scripts or revert to a previous stable Office version.

Excel & Data Problems