| Previous | Next |
| RO_E_MUST_BE_AGILE | RO_E_COMMITTED |
RO_E_UNSUPPORTED_FROM_MTA
Single-threaded runtime class cannot be activated from the MTA
RO_E_UNSUPPORTED_FROM_MTA is HRESULT 2147483677 (0x8000001D) from winerror.h. AllStat describes it as “Activating a single-threaded class from MTA is not supported.” In the Windows Runtime metadata, object lifetime, asynchronous operation, activation, and apartment model, the code identifies a specific failure boundary and should not be replaced by a generic COM exception.
The hexadecimal value and symbolic name this result should remain attached to the originating API and operation generation.
Where it is encountered
- C++/WinRT, WRL,.NET projections, or native WinRT ABI calls. Record the interface, method, component version, thread, apartment, process, and correlation ID.
- Runtime-class activation, WinMD reflection, asynchronous objects, observable state, or view lifecycle.
- Cross-thread and cross-apartment handoff between UI, ASTA, STA, MTA, broker, and background work.
The immediate focus for it is activation of a class whose threading metadata requires an STA while the calling thread is initialized as multithreaded. Keep it attached to that operation; the same numeric severity outside the owning API does not supply enough context.
Decisive interpretation boundary
Before choosing recovery, verify that the runtime class threading model and current COM apartment were read from metadata and thread initialization, not inferred from symptoms. The decisive boundary for it determines whether the same object can continue, a new object is required, or policy must change.
Also confirm that all observed objects, tokens, buffers, proxies, metadata files, or ACLs belong to the current operation generation and were not retained from an earlier attempt.
Correct handling and recovery
Perform activation on an STA with a message pump, use an agile alternative, or redesign the worker boundary. Do not reinitialize an already configured MTA thread as STA.
Repeat the operation after it only when the documented precondition, identity, apartment, object generation, buffer, or configuration has changed.
Lifetime, retry, and cleanup rules
After it, determine whether the current object, interface pointer, call context, token, stream, metadata reader, asynchronous operation, or access-control instance remains valid. Release only resources owned by the failing attempt, cancel callbacks through their documented mechanism, and avoid double close, double commit, repeated activation, or replay of a non-idempotent remote method.
The retry policy for it should state the trigger, maximum attempts, cancellation owner, and reconciliation step for effects that may have completed elsewhere.
Practical scenario
A service worker in the MTA activates a UI-oriented runtime class. The service moves activation to a dedicated STA and exchanges immutable data with the worker.
A regression test should reproduce it, assert the raw HRESULT and all relevant outputs, then correct only the decisive condition and verify the intended success or neighboring failure result.
Difference from nearby HRESULTs
It rejects class activation from the MTA; RPC_E_WRONG_THREAD usually concerns later interface use on a different thread.
Tests for it should force both results and verify that object lifetime, output use, and user messaging differ.
Developer and administrator guidance
Dashboards should classify it by its actual cause category—lifetime, timing, apartment, marshaling, identity, authorization, format, buffer, or storage—rather than grouping every COM failure under one counter.
After it, avoid broad permission grants or system-wide resets unless code-specific evidence proves a global configuration problem. Define who owns retry, cancellation, cleanup, policy changes, package repair, and user-facing messaging for it.
References
- Microsoft: C++/WinRT error handling
- Microsoft: concurrency and asynchronous operations
- Microsoft: WinMD files
- Microsoft: IAgileObject
- Microsoft: COM apartments
- Microsoft: HRESULT values
Looking for a different code? Search another status or error code.