| Previous | Next |
| NS_S_WMP_LOADED_PNG_IMAGE | NS_S_WMP_LOADED_JPG_IMAGE |
NS_S_WMP_LOADED_BMP_IMAGE
Windows Media Player loaded a BMP image
What must be true before accepting it
Verify that the bitmap layout and decoded resource size are acceptable for the UI or skin. The documented condition must be demonstrated so this result is not mistaken for an unrelated success state.
Any state transition preceding this result must be included in rollback, continuation, and retry planning.
Where the status is encountered
- This result can be returned during Windows Media source, reader, writer, or renderer callbacks; log the exact method and object state instead of interpreting the constant outside that contract.
- It can be returned during Windows Media Player SDK automation; log the exact method and object state instead of interpreting the constant outside that contract.
- It can be returned during media graph, playlist, image, rights, or buffering state; log the exact method and object state instead of interpreting the constant outside that contract.
Because it is informational, a language binding may expose it as success and hide the symbolic distinction. Keep the original HRESULT available until the code-specific branch has run.
Evidence and telemetry
- preserve bitmap header fields.
- preserve dimensions and bit depth.
- preserve decoded byte size.
- preserve source package.
- preserve target control.
Also record ns_s_wmp_loaded_bmp_image_operation, ns_s_wmp_loaded_bmp_image_state_before, ns_s_wmp_loaded_bmp_image_state_after, UTC time, process and thread identifiers, component version, and a correlation ID. Use redacted telemetry for this HRESULT, retaining only the stable technical identifiers that distinguish the operation.
Correct handling and recovery
Check dimensions, bit depth, and memory cost before displaying. BMP success does not remove the need for limits on uncompressed image size.
Retry it only when a documented input or state has changed. Use the code-specific next action for this HRESULT; avoid treating all informational HRESULT values as retry signals.
Practical scenario
A toolbar bitmap loads from a skin package. The host verifies bit depth and dimensions before creating the display surface.
A regression test should reproduce it, assert the relevant outputs and state, then change only the decisive condition and verify the expected neighboring result or ordinary completion.
Difference from nearby results
It must be distinguished from ordinary S_OK and from failure-severity values in the same API family; its documented state changes control the next action.
Comparing it with related statuses protects the caller from applying failure recovery to normal state.
References
- Microsoft: Windows Media Format SDK error codes — official Microsoft material used to interpret it.
- Microsoft: Windows Media Player SDK
- Microsoft: Windows Media Player buffering event
- Microsoft: HRESULT values
Looking for a different code? Search another status or error code.