How to Fix 'Could Not Open Macro Storage' Error in MS Word
Question details
The user is unable to create, edit, or delete macros in Microsoft Word due to a persistent storage error.

- Product
- Microsoft Word
- Device & OS
- not provided
- Scenario
- Trying to manage, record, or edit VBA macros within a Microsoft Word document.
- Observed behavior
- Word displays a 'Could not open macro storage' error message, completely blocking any macro modifications. This issue persists even after attempting a standard reinstallation of the Office suite.
Ensure you have saved all open Word documents and completely exited the Microsoft Word application before applying these fixes. It is also recommended to temporarily disable any strict third-party antivirus software that might be blocking file access to your Office templates.
Reset the Normal.dotm Global Template
A corrupted global template is the most common cause of macro storage errors. Renaming it forces Word to generate a fresh, error-free copy upon the next startup.
Microsoft Word stores default settings and macros in a global template file named Normal.dotm. When this file becomes corrupted, it blocks macro creation and editing. Reinstalling Office often leaves this file intact, which is why manual removal is necessary.
Ensure that Microsoft Word and all other Office applications are completely closed.
Press the Windows key + R to open the Run dialog box. Type '%appdata%\Microsoft\Templates' and press Enter to open the folder where Word stores its global templates.
Locate the file named 'Normal.dotm' (or simply 'Normal'). Right-click the file, select 'Rename', and change its name to 'Normal.old'.
Launch Microsoft Word again. The application will automatically create a new, clean Normal.dotm file. Test your macros to see if the issue is resolved.

Verify Macro Security Settings and Folder Permissions
Strict Trust Center settings or restricted folder permissions can block Word from accessing the storage required for macros.
Identify Conflicts in Safe Mode and Repair Office
Faulty add-ins can interfere with macro storage. If Safe Mode bypasses the error, an add-in is the culprit. Otherwise, an Office Repair is necessary.
Try WPS Office for Seamless Document Management
If Microsoft Word continues to struggle with template corruptions, macro storage errors, or complex troubleshooting steps, consider switching to WPS Office. It provides a lightweight, user-friendly alternative for all your document creation needs while maintaining excellent compatibility with your existing files.
- 1. Download WPS Office: Visit the official WPS website and download the free installation package tailored to your operating system.
- 2. Install the Application: Run the installer and follow the simple on-screen instructions to set up WPS Office on your device.
- 3. Open Your Documents: Launch WPS Writer and open your existing .docx files seamlessly to continue working without interruption.

Frequently Asked Questions
Why does the 'Could not open macro storage' error occur even after reinstalling Word?
Reinstalling Word often leaves your personal configurations and the 'Normal.dotm' global template intact. If the template file itself is corrupted, the new installation will simply load the same damaged file, causing the macro storage error to persist.
Will renaming Normal.dotm delete my existing macros?
Yes, macros stored in your original global template will not appear in the newly generated template. However, because you renamed the old file instead of deleting it, you can later use the Word Organizer tool to copy salvageable macros from 'Normal.old' into your new 'Normal.dotm'.
Can my antivirus software cause macro storage errors in Microsoft Word?
Yes. Strict security software, such as Windows Defender's Controlled Folder Access or third-party antivirus shields, can falsely flag Word's attempts to write to the AppData folder. This blocks access and triggers macro storage errors.
Does disabling all add-ins permanently fix the macro issue?
If a specific COM add-in is directly conflicting with VBA execution, disabling that specific add-in will permanently fix the issue. You should re-enable your add-ins one by one to identify the exact culprit so you can keep the others active.




