Fix Word Event ID 300 When Saving to a Network Share
Question details
The user is experiencing a recurring save-dialog loop and Event ID 300 errors when attempting to save Word documents to network locations.

- Product
- Microsoft Word
- Device & OS
- not provided
- Scenario
- Saving a document to a mapped network drive or UNC path.
- Observed behavior
- Word generates an Event ID 300 error and repeatedly prompts the user with the save dialog without successfully saving the file to the network share.
Verify that your network connection is stable and ensure you have the appropriate read and write permissions for the target network share or UNC path.
Configure Word Trust Center for Network Locations
Enabling and adding your network share to Word's Trust Center can bypass security blocks that trigger the Event ID 300 error.
Launch Microsoft Word, click on the 'File' tab, select 'Options' at the bottom left, and then click on 'Trust Center'. Click the 'Trust Center Settings' button.
In the left pane, select 'Trusted Locations'. Check the box at the bottom that says 'Allow trusted locations on my network'.
Click on 'Add new location', enter the exact mapped drive letter or UNC path you are trying to save to, and check 'Subfolders of this location are also trusted'.
Click 'OK' to save the new trusted location, exit the Word Options menu, and restart Word to test saving your document to the network share.

Perform a Clean Reinstallation of Office
If the issue happens across all Windows user profiles on a single device, the Office installation or cache may be severely damaged.
Try WPS Office for Seamless Network File Sharing
If Microsoft Word continues to struggle with Event ID 300 errors and complex Trust Center issues, switch to WPS Office. It provides a lightweight, highly compatible, and free alternative that seamlessly handles saving to local and network drives without continuous prompt loops.

Frequently Asked Questions
Why does Word keep prompting the save dialog when saving to a network drive?
This save loop typically occurs when Windows security, restrictive antivirus software, or Word's Trust Center blocks write access to the specific network path (UNC or mapped drive). Word loops the dialog because the initial save attempt was silently rejected by the system.
Does Event ID 300 affect all users on the network?
Not necessarily. If the error is caused by a damaged Office installation, local registry corruption, or a specific endpoint security policy, it will often be isolated to a single computer, even if multiple Windows user profiles on that same computer experience it.
Can antivirus software cause Word Event ID 300?
Yes. Strict antivirus programs or endpoint protection software can intercept and block Office applications from writing temporary or permanent files to shared network locations, which directly triggers this error event.




