| Previous | Next |
| STG_E_FILENOTFOUND | STG_E_TOOMANYOPENFILES |
STG_E_PATHNOTFOUND
Why this differs from a missing stream
STG_E_PATHNOTFOUND means that the requested storage operation could not reach its target through the path supplied by the caller. It commonly appears before the compound file has been opened at all: a directory was renamed, a UNC share is unavailable, a mapped drive is absent in the service session, or a component builds the path from an unexpected working directory. In a layered application, the same HRESULT can be wrapped around a failure to resolve a parent location for a structured-storage document.
Do not assume that the error proves a damaged OLE document. Compound File Binary Format describes the layout inside the container; it does not make an invalid external path valid. Conversely, a valid path only proves that the file can be reached, not that it contains the required storages and streams.
Useful checks
- Log the final absolute or UNC path after environment-variable, profile, and configuration expansion.
- Run the failing operation under the same service account and session type as production; mapped drives are often user-session specific.
- Separate “parent directory unavailable” from “container opened but child stream missing” in application logs.
- If the file is copied from removable or network storage, verify the share and reconnect policy before retrying a write.
References
- Microsoft: Structured Storage error values
- Library of Congress: Compound File Binary Format overview
- olefile: structure of OLE compound documents
Looking for a different code? Search another status or error code.