What does HRESULT 0x88980422 (UCEERR_TRANSPORTOVERLOADED) mean?

 
Previous Next
UCEERR_TRANSPORTDISCONNECTED UCEERR_PARTITION_ZOMBIED

UCEERR_TRANSPORTOVERLOADED

UCEERR_TRANSPORTOVERLOADED is a Windows User Composition Engine (UCE) HRESULT. It indicates that the composition channel cannot keep up with the volume of pending graphics or visual-update traffic.

What to check for UCEERR_TRANSPORTOVERLOADED

  • Profile high-frequency property changes, animation, layout invalidation, and rendering callbacks.
  • Coalesce frequent updates and avoid generating work faster than the rendering channel can consume it.
  • Check for a blocked renderer or GPU issue if the workload is normally modest.

Microsoft guidance for WPF render-thread failures

Diagnostic interpretation of UCEERR_TRANSPORTOVERLOADED

UCEERR_TRANSPORTOVERLOADED has the HRESULT value 0x88980422. AllStat records the condition as “UCEERR_TRANSPORTOVERLOADED”. For UCEERR_TRANSPORTOVERLOADED, in practice, interpret that wording at the boundary owned by the Windows component or COM interface that returned the HRESULT, rather than treating the value as a generic Windows message.

Evidence to capture for UCEERR_TRANSPORTOVERLOADED

  • Record the exact COM method or Windows API, its input object, the calling thread, and the full 0x88980422 value before a wrapper converts it to an exception or Boolean result.
  • Capture any IErrorInfo text, activity identifier, event-log entry, and subsystem trace that mentions UCEERR_TRANSPORTOVERLOADED or the uceerr / transportoverloaded operation.
  • For UCEERR_TRANSPORTOVERLOADED, compare the failing machine with a working one at the same configuration boundary: component version, policy, registration, identity, and target resource.

Retry and recovery for UCEERR_TRANSPORTOVERLOADED

Retry UCEERR_TRANSPORTOVERLOADED only when the owning API documents a transient state or after the condition described as “UCEERR_TRANSPORTOVERLOADED” has changed. For UCEERR_TRANSPORTOVERLOADED, configuration, policy, format, and authorization failures normally require correction first; an immediate loop can hide the original call site and add secondary errors.


Looking for a different code? Search another status or error code.