| Previous | Next |
| STG_E_SEEKERROR | STG_E_READFAULT |
STG_E_WRITEFAULT
Why a write fault is more than a save-dialog error
STG_E_WRITEFAULT means a write operation failed at the storage layer. In a compound-file workflow, that failure can happen while updating a stream, writing allocation data, or committing a transacted root storage. The visible document may have been open and editable for some time; the failure only becomes apparent when pending changes must reach the backing file.
The immediate cause can be an I/O error, a disconnected share, removable-media failure, antivirus or backup interference, or a storage implementation that can no longer complete a write. It is not interchangeable with STG_E_MEDIUMFULL, which specifically concerns lack of space.
Response and evidence
- Do not assume the document was saved merely because the application accepted edits; check the result of the final commit operation.
- Write diagnostic output to a different volume or location if the original path may be unavailable.
- Collect file-system and device events around the time of failure, including network-share disconnects.
- Keep a pre-write backup or use an application-level save-as-new-file strategy when data durability matters.
References
- Microsoft: IStorage::Commit and error handling
- Microsoft: Structured Storage HRESULT values
- Library of Congress: CFB format overview
Looking for a different code? Search another status or error code.