Investigating NS_E_PROPERTY_NOT_SUPPORTED without losing the first failure
This result (0xC00D32D2) marks the provider recognizes the request context but does not implement that property. The code belongs to the property unsupported metadata check, which is why a later network, codec or metadata error must be recorded separately instead of replacing it.
Where the failure occurs
Interpret the provider response
Retest result
Interpretation
The identical call still returns the code
The values governing the property unsupported metadata check are unchanged, or the caller is still using an older object generation.
A fresh object succeeds
Lifetime or cached state contributed to this result; correct object recreation instead of applying a machine-wide workaround while tracing the property unsupported path.
The call advances to another HRESULT
the property unsupported metadata check boundary was cleared. Diagnose the new code at its own format, graph, URL, network or metadata stage for evidence about property unsupported.
Only one resource fails
The evidence favors content, URL, publishing point, stream, attribute or object-specific state rather than a global outage before closing the property unsupported incident.
Attribute, schema and locale evidence
Capture
Why it matters
Owning call
Record the API method, object identity, thread or callback and timestamp for the property unsupported metadata check.
Decisive values
file or content identifier, metadata provider, stream number, attribute name and type, locale, read/edit capability and the first metadata API result when isolating the property unsupported case.
Object generation
Note when the reader, writer, graph, URL object, streaming session or metadata provider was created; stale state can reproduce this result after configuration has changed.
First nested result
Keep the earliest codec, COM, socket, DNS, parser or provider status before it; later UI messages are less specific.
Comparison case
Use one known-good resource that exercises the same the property unsupported metadata check while changing only the rejected precondition.
Read-only metadata experiment
Log 0xC00D32D2, it, the exact operation and the first failure time for evidence about property unsupported.
Preserve file or content identifier, metadata provider, stream number, attribute name and type, locale, read/edit capability and the first metadata API result before closing the property unsupported incident.
Do not reuse a graph, session, reader or metadata object created before the relevant configuration or resource changed in the property unsupported diagnostic record.
Perform one isolated test: enumerate the provider capabilities and repeat the operation on one known attribute before testing the disputed metadata item when isolating the property unsupported case.
Repeat through the same API and protocol path; a different player or local-copy test is useful only as a comparison, not as proof that the property unsupported metadata check is fixed.
Confirm the expected next state and retain any new HRESULT as a separate downstream result while tracing the property unsupported path.
Nearby results are not interchangeable
Main distinction: unsupported is a provider-capability result, whereas not-found is an absent value within a supported key space during a controlled property unsupported retest.
Nearby HRESULT
How to compare it
NS_E_INVALID_QUERY_OPERATOR
Compare the owning API and first rejected value; it belongs to a neighboring checkpoint, not automatically to the same cause as it.
NS_E_INVALID_QUERY_PROPERTY
Use object state and operation order to decide which code is authoritative when both appear in one trace before closing the property unsupported incident.
NS_E_SCHEMA_CLASSIFY_FAILURE
Retain it separately if it appears only after the condition has cleared.
Misleading actions
deleting metadata caches or tags before preserving the provider, attribute key, type and locale that produced the result when isolating the property unsupported case.
