MS Teams - latest licensed personal desktop app: no call/meeting audio on Windows 10; same account works in browser

No public Microsoft information confirms an audio regression specific to Teams personal build 26260.1717.5229.7049, so the supported next action is to reproduce the failure, collect the desktop media logs immediately, and submit them through Report a problem while continuing to use Teams on the web.

Collect call-audio diagnostics

The desktop support bundle includes media and signaling logs as well as platform logs; consumer accounts generate Life-Weblogs. Media/signaling files are encrypted and can only be interpreted by Microsoft Support, so an absence of readable audio errors in the ordinary Teams logs does not rule out a media-stack failure.^1^

1. In Teams, open Settings and more → Settings → Privacy.
2. Under Extended diagnostics data, enable optional diagnostics if available. This provides additional troubleshooting information.^2^
3. Start a meeting or run the pre-join speaker test and reproduce the silence.
4. Note:
   • Exact local time and time zone.
   • Selected output device.
   • Whether the notification chime still played.
   • Whether the sndvol Teams meter remained stationary.
5. Immediately press Ctrl+Alt+Shift+1. Alternatively, right-click the Teams system-tray icon and select Collect support files.
6. Wait until the Downloading web logs notification disappears.
7. Open Downloads, find the new folder beginning with MSTeams Support Logs, and compress it into a .zip file.
8. In Teams, select Settings and more → Feedback → Report a problem.
9. Include the build, Windows version, reproduction time/time zone, browser comparison, and completed troubleshooting. Select Upload files and attach the ZIP.^3^

If the feedback form offers Include Troubleshooting info, enable it. That control can be absent when connected experiences or optional diagnostic data are disabled.^2^

Avoid posting the ZIP publicly: logs from a client containing multiple signed-in accounts include diagnostic information for every logged-in account.^1^

Build status and practical workaround

Microsoft’s version-history page is a build history, not a deployment-status or known-issues report. It also states that builds can be incremented or replaced during rollout and recommends updating when the installed version is not listed.^4^

Therefore:

• There is no documented basis to label this a known 26260.1717.5229.7049 defect.
• The browser-versus-desktop result, two affected output devices, and stationary desktop-client mixer meter make the collected desktop media logs the useful next evidence.
• Continue using Chrome for meetings until another Teams build arrives or Microsoft diagnoses the submitted bundle. The working browser path is preferable to repeating repair, reset, reinstall, cache, routing, driver, or device-selection procedures already completed.

One remaining isolation test

Because an injected Norton module was observed—even though excluding WebView2 did not fix it—the remaining supported local discriminator is a Windows clean boot, which tests all non-Microsoft services and startup applications rather than one injected component.^5^

1. Run msconfig as an administrator.
2. On Services, select Hide all Microsoft services, then Disable all.
3. On Startup, open Task Manager and disable enabled startup items.
4. Restart, reproduce once in Teams, and collect another support bundle.
5. Restore normal startup afterward.

A clean boot temporarily disables third-party functionality. If audio works there, re-enable services/startup items in halves to isolate the conflict. If it remains silent, include that result in the report; it materially strengthens the desktop-client regression case.

References

1. Collect Teams client diagnostic logs for Microsoft support
2. Diagnostic data in Microsoft Teams for personal use | Microsoft Support
3. [Desktop](https://support.microsoft.com/teams/personal/troubleshoot/send-feedback-or-suggest-a-feature-in-microsoft-teams-personal)
4. Version update history for the new and classic Microsoft Teams app
5. [Windows 10](https://support.microsoft.com/windows/experience/startup-boot/how-to-perform-a-clean-boot-in-windows)