| Previous | Next |
| NS_E_WMP_UI_OBJECTNOTFOUND | NS_E_WMP_UI_NOSKININZIP |
NS_E_WMP_UI_SECONDHANDLER
How to classify this WMP result
0xC00D0FE6 maps to NS_E_WMP_UI_SECONDHANDLER. Its actionable interpretation is a second handler is declared for an event that already has one, within the Windows Media Player skin, theme and control layout engine; the producing mechanism is the XML-based skin loader that opens a skin package, finds its.wms definition, constructs views and controls, applies attributes and attaches event handlers to artwork-backed UI elements.
The generated part of the What Is page already shows the standard AllStat description for this HRESULT. The additional test for the UI second handler condition is to record event name and both handler locations in the skin/script; that evidence is more useful than reinstalling the Player or changing several unrelated settings at once.
Evidence to capture before retry
Preserve the first occurrence before retry or fallback changes the UI second handler evidence. The following fields should identify the same object generation:
| Field | What to record |
|---|---|
| Decisive check | record event name and both handler locations in the skin/script |
| Artifact identity | resource path, decoded dimensions and transparency/mapping attributes for the UI second handler reproduction |
| Runtime state | event name, first handler and any duplicate handler declaration for the UI second handler reproduction |
| Owning object | skin archive path, member list and selected.wms definition for the UI second handler reproduction |
| Lower-level result | THEME/version declaration and currentViewID for the UI second handler reproduction |
| Correlation | control type, object ID and parent/child relation for the UI second handler reproduction |
How this layer works
A focused diagnostic sequence
- Start with the symbolic value this result; do not diagnose UI second handler from the final dialog alone.
- Record the bytes or object state that produced UI second handler before automatic recovery mutates it.
- Exclude a stale callback or superseded object generation as the source of the UI second handler event.
- Use this deciding observation for UI second handler: record event name and both handler locations in the skin/script.
- Apply the smallest supported remedy for UI second handler: merge the behavior or keep one authoritative handler.
Correct the producing condition
- Avoid renaming arbitrary XML to.wms or repacking a skin without preserving its relative resource paths while investigating UI second handler; it can destroy the artifact or state needed to explain this result.
Why the symbolic name matters
| Result | Different boundary |
|---|---|
NS_E_WMP_UI_NOSKININZIP | the skin archive contains no.wms definition file discoverable by the loader |
NS_E_WMP_UI_OBJECTNOTFOUND | attributes were parsed for a skin object that was never constructed |
NS_E_WMP_UI_PASSTHROUGH | the skin hit-test path returned its internal pass-through result rather than selecting a control |
What to search for in traces
Regression check
Technical references
- Windows Media Player skins — documentation used to identify the producing boundary of it.
- Skin definition file structure — normative or platform material relevant to it.
- Skin definition XML structure — API or format context for this HRESULT.
- Skin files and package contents — documentation used to identify the producing boundary of it.
Looking for a different code? Search another status or error code.