Muted participant remains muted after client shutdown and OS reboot

,

ID: TS6-2025-07-04-001
Status: New
Operating System and Version: Windows 11 Pro, 24H2
Environment: Teamspeak 6, Version: 6.0.0-beta2

Detailed Description & Context

When a participant is muted locally via the client’s UI and subsequently un‑muted, the state should reset immediately and persist as un‑muted. Instead, after an operating‑system shutdown/restart sequence without first closing TeamSpeak 6, the client reconnects with the participant still shown as muted. This indicates that the final un‑mute action is not flushed to persistent storage before the abrupt termination of the application.

Preconditions

  • TeamSpeak 6 installed and configured with default settings
  • Valid credentials and access to any TeamSpeak server & channel containing other users

Reproduction: Always possible

  1. Launch TeamSpeak 6.
  2. Connect to any TeamSpeak server.
  3. Join a voice channel with at least one other participant (User A).
  4. Mute User A via the participant list context menu.
  5. Un‑mute User A again (state in UI returns to normal).
  6. Shut down Windows directly (do not exit the TeamSpeak client first).
  7. Power the computer back on and log in.
  8. Launch TeamSpeak 6 and reconnect to the same server/channel.

Actual Result

User A appears as muted in the participant list, indicating that the un‑mute operation was not persisted.

Expected Result

User A should appear un‑muted. The last user‑initiated state change (un‑mute) must be preserved across client and OS restarts.

User Impact

This issue creates confusion and disrupts expected communication behavior. A user who was unmuted before rebooting the PC may unintentionally remain inaudible to others, or continue to be ignored due to being incorrectly shown as muted. In team-based or time-critical voice sessions (e.g., gaming, coordination, support), this leads to misunderstandings and delays, especially since the mute state appears client-side only and may not be obvious to the affected user.

The client saves the information only when being closed properly. Make sure before you turn off your system, that TS is being properly closed.

3 Likes

That is the issue Florian was talking about.
There is a significant portion of people, who just turn off their PC, without closing any application (some maniacs even hold the power button or cut the power directly).

Even tho it is not hard to fix on the users end, it is an annoying consequence of the current implementation.

1 Like