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

PeterRonick-5589 0 Reputation points
2026-10-26T19:16:39.3866667+00:00

PROBLEM The new Microsoft Teams desktop app for personal use plays no audio in meetings or in the pre-join "Test mic and speakers" check. The Teams notification/meeting chime does play. The microphone appears to work. Teams in a web browser (Chrome) on the same PC, same account, same Focusrite Scarlett output, plays meeting audio and works correctly (I completed a live interview in it with no issues).

ENVIRONMENT - Windows 10 Home 22H2 (Dell XPS 8700) - Latest Teams (personal), version 26260.1717.5229.7049 - Microsoft Edge WebView2 Runtime 155.0.4283.62 (standard install path) - Audio: Focusrite Scarlett 2i2 3rd Gen (USB), driver and Focusrite Control reinstalled during troubleshooting. Also tested on the PC's Realtek output: same result. - Other audio works through the Scarlett: Windows test sound, YouTube, Spotify, Reaper.

KEY EVIDENCE - In the classic Volume Mixer (sndvol), the Teams level meter does not move during the pre-join speaker test, so Teams does not appear to be sending call audio to Windows. - Windows Application and Audio event logs show no errors or warnings at test time (only "MMDevAPI: Audio device state changed" information events). - Teams logs show nothing audio-related.

ALREADY TRIED (no change) - Windows default device, volume mixer, per-app device preferences, exclusive mode off, privacy permissions - Teams repair, reset, and full uninstall/reinstall - Renaming the Teams local data folder to test a fresh profile - Ending the Teams WebView2 Audio Service process (it respawned; still silent) - Third-party injection check: Norton's aswhook.dll was loaded into the Teams audio process; excluding the WebView2 folder in Norton removed it, with no change in audio - Equalizer APO: all devices unchecked and the Windows Audio service restarted; no change - Reinstalling the Focusrite driver

REQUEST Is this a known issue with this build on Windows 10 22H2? Is there a supported way to collect Teams call-audio diagnostics from the personal client, or a fix other than the steps above? I can supply further logs on request.

Microsoft Teams | Microsoft Teams Free | Calls
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Ruwim.B 7,325 Reputation points Volunteer Moderator
    2026-10-26T20:03:38.0466667+00:00

    Have you checked if Focusrite Scarlett is selected as the Speaker device in Teams -> Settings -> Devices? Have you tried to connect this audio device to another USB port?

    Unfortunately, the "Test mic and speaker" option is not working as expected. No sound is produced for the selected speaker device even when the speaker is known to work perfectly well with Teams.

    User's image

    Nevertheless, if you press the "Yes, I can hear it" button, a window with Microphone test will open.

    User's image

    Proceed with the microphone test, i.e. say something and then pause. If you hear your voice played back after the beep, then both your microphone and speaker are working.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-10-26T19:17:58.0366667+00:00

    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)
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.