Fix Word 365 System Error &H8000FFFF When Running Macros
Question details
The user is experiencing System Error &H8000FFFF (-2147418113) when attempting to run existing macros or access the Visual Basic editor in Word 365.

- Product
- Microsoft Word 365
- Device & OS
- not provided
- Scenario
- Running older macros or launching the Visual Basic for Applications (VBA) environment.
- Observed behavior
- Word 365 displays System Error &H8000FFFF, preventing macro execution and blocking access to the Visual Basic editor.
Before attempting to modify system templates or registry configurations, ensure that all active Word documents are saved and the Microsoft Word application is completely closed.
Rename the Normal.dotm Template
Resetting the global template resolves corruption issues that block the VBA editor and cause macro execution errors.
The Normal.dotm file is Microsoft Word's global template, which stores default styles, customizations, and standard macros. When this file becomes corrupted, it can trigger severe VBA errors like System Error &H8000FFFF. Renaming the file forces Word to generate a fresh, uncorrupted version on its next startup.
Ensure all Word documents are saved and the application is fully closed before proceeding.
Press the Windows Key + R on your keyboard to open the Run command window.
Type %appdata%\Microsoft\Templates into the Run dialog box and press Enter.
Locate the file named Normal.dotm (or just Normal if extensions are hidden). Right-click it, select Rename, and change the name to Normal.old.
Open Microsoft Word again. A new, clean Normal.dotm file will be generated automatically. Try recording or running a simple macro to confirm the error is resolved.

Recreate Macros from a Text Backup
If specific legacy macros are triggering the error, recreating them in a clean module can resolve underlying syntax or compilation problems.
Utilize AutoText or AutoCorrect as Alternatives
For macros solely designed to insert standard text snippets, using native Word features is more reliable and avoids VBA complications entirely.
Experience Stable Document Editing with WPS Office
If Microsoft Word 365 continues to display persistent system and macro errors, consider switching to WPS Office. It offers a highly compatible and lightweight environment for your daily document needs, allowing you to edit and format text effortlessly without complex VBA troubleshooting.
- 1. Download the software: Visit the official WPS website and download the free WPS Office installation package.
- 2. Install WPS Office: Run the downloaded installer and follow the quick on-screen instructions to set up the suite on your computer.
- 3. Open your existing documents: Launch WPS Writer and directly open your existing Word files to continue working seamlessly in a stable environment.

Frequently Asked Questions
What primarily causes System Error &H8000FFFF in Word 365?
This specific system error is most commonly caused by a corrupted Normal.dotm global template, incompatible legacy macro code from older Word versions, or a broken Office configuration that prevents the Visual Basic engine from initializing.
Will renaming or deleting the Normal.dotm file delete my saved Word documents?
No. The Normal.dotm file only acts as a template for new documents and stores default customizations (like custom toolbars, styles, and global macros). Renaming or deleting it will not delete or alter any of your previously saved .docx or .doc files.
How can I retrieve my macros if the VBA editor completely refuses to open?
If the VBA editor is entirely inaccessible, you will need to rely on previously exported .bas files or plain text backups. Alternatively, if the macros are saved in a specific document rather than the global template, you might be able to open that document on a different computer to export the code.
Are AutoText and AutoCorrect viable replacements for Word macros?
Yes, if your macros were exclusively used to generate predefined blocks of text, automated signatures, or repetitive phrases, using Word's built-in AutoText or AutoCorrect features is highly recommended. These features are native, faster, and not susceptible to VBA-related corruption.




