Audio subsystem restart lifecycle reference

Restart is a boundary event

A subsystem restart is a transition in which one or more audio services, endpoint representations, or driver relationships are stopped and established again. It is not synonymous with replacing a package, changing a format, or changing the physical device.

Several objects can be involved

The audio engine, endpoint manager, user-mode services, and device-facing driver each have different lifetimes. A restart may affect one service boundary while leaving package identity and hardware enumeration intact. The observed state depends on which component owns the restart.

Streams have independent lifetimes

Applications can hold stream objects that are separate from endpoint publication and service state. A stream may be closed, reopened, or renegotiated as the surrounding audio graph transitions, while its package and device records remain unchanged.

Read restart records precisely

Terms such as reload, reinitialize, restart, and reconnect can name different boundaries in different documentation. The useful reference question is which component stopped, which interface was recreated, and which records were preserved.

Questions and answers