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
- Launch TeamSpeak 6.
- Connect to any TeamSpeak server.
- Join a voice channel with at least one other participant (User A).
- Mute User A via the participant list context menu.
- Un‑mute User A again (state in UI returns to normal).
- Shut down Windows directly (do not exit the TeamSpeak client first).
- Power the computer back on and log in.
- 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.
