'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Word Macro System Error H80070057
Question details
The user is unable to run or edit existing Word macros due to an H80070057 system error.
- Product
- Microsoft Word
- Device & OS
- not provided
- Scenario
- Attempting to execute or edit VBA macros in Word, or using the 'Bring to Front' option on an inserted shape within a document.
- Observed behavior
- A system error H80070057 is triggered, actively preventing macros from running or allowing the user to edit the VBA code.
Before proceeding with any template resets, ensure you copy your existing macro code into a basic text editor like Notepad so you do not permanently lose your scripts.
Reset the Normal.dotm Template
Deleting and regenerating the global template file can resolve underlying corruption that triggers the H80070057 error in the VBA editor.
The Normal.dotm file serves as the core template for all new Word documents. If this file becomes corrupted, it can cause catastrophic failures within the Visual Basic module, rendering macros inaccessible.
Open Microsoft Word and press Alt+F11 to open the Visual Basic Editor. Copy your existing macro code and paste it into Notepad as a backup.
Completely exit Microsoft Word and close any other running Microsoft Office applications.
Navigate to your system's template folder and either rename or delete the existing Normal.dotm file.
Restart Microsoft Word. A fresh Normal.dotm file will be generated automatically. Press Alt+F11 to open the Visual Basic Editor and paste your saved macro code back in.
Record a Dummy Macro to Reactivate Scripts
Recording a new, simple macro can force the system to refresh its VBA module, subsequently reactivating all other macros.
Experience seamless document creation with WPS Office
If you frequently encounter system errors or macro issues in Microsoft Word, consider switching to WPS Office. It provides a lightweight, highly compatible alternative with familiar formatting tools and a smooth user experience.
- 1. Install WPS Office: Download and run the free installer from the official WPS website.
- 2. Open Your Documents: Launch WPS Writer and open your existing Word documents seamlessly without losing formatting.
- 3. Enable Macros (Optional): If you require VBA capabilities, you can enable the VBA module in WPS Office to continue running your existing scripts.
Frequently Asked Questions
Where is the Normal.dotm file located in Windows?
The Normal.dotm file is typically located in the hidden AppData folder. You can access it directly by opening the Windows Run dialog (Win + R), typing %appdata%\Microsoft\Templates, and clicking OK.
Why does 'Bring to Front' trigger macro system errors?
This occurs when there is an underlying corruption in the document's drawing layer or the global template. Manipulating shapes can cause conflicts with a corrupted Visual Basic component, throwing the H80070057 system error.
How can I recover macros if I already deleted my template file?
If you did not back up your macro code before deleting Normal.dotm, you may only be able to recover them if you have a recent system backup, or if the macros were specifically saved within an individual .docm file rather than the global template.
