| Previous | Next |
| STG_E_DOCFILECORRUPT | STG_E_DOCFILETOOLARGE |
STG_E_BADBASEADDRESS
OLE32 loaded at an unexpected base address
STG_E_BADBASEADDRESS is HRESULT 2147680528 (0x80030110) from winerror.h. The documented description is “OLE32.DLL has been loaded at the wrong address.” The result belongs to legacy structured-storage initialization that depends on a specific OLE32 image layout. A reliable diagnosis preserves the raw value and reconstructs the state that made this true: the runtime detected OLE32.DLL at an address incompatible with the expected implementation.
Where the result appears
- Preserve storage path or identity, STGM mode, stream or storage name, transaction generation, file hash, and backing provider before releasing or replacing the object that returned this result.
Typical causes and interpretation
Common cause branches include the following:
- Legacy binaries depend on obsolete fixed-address assumptions.
- The runtime image is mismatched or modified.
- Process injection or loader configuration changes module placement.
Confirm the cause branch that explains why the runtime detected OLE32.DLL at an address incompatible with the expected implementation by using call arguments, object state, metadata, device information, or provider traces.
Correct handling and recovery
The primary recovery is to repair the operating-system image and remove unsupported binary assumptions or injected components. The failure report should capture the relevant state during legacy structured-storage initialization that depends on a specific OLE32 image layout so it is clear why the runtime detected OLE32.DLL at an address incompatible with the expected implementation.
When it follows cancellation or replacement, create a new generation before applying the recovery: repair the operating-system image and remove unsupported binary assumptions or injected components.
Practical scenario
A historic automation host ships with a private incompatible OLE component; system-file repair and removal of the private copy restore normal loading.
Difference from related HRESULTs
CO_E_INIT_* results describe COM initialization stages; it is a legacy storage-family loader-layout failure.
Developer and administrator guidance
Exercise direct and transacted modes, read-only and writable paths, cancellation, malformed input, and cleanup after partial output.
A runbook should preserve the original artifact and logs before the proposed recovery—repair the operating-system image and remove unsupported binary assumptions or injected components—changes evidence.
References
Looking for a different code? Search another status or error code.