MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Problem/Bug]: Multiple WebView2 applications share the same Windows audio session, causing mute state to affect all apps using msedgewebview2.exe

Open
#5,667 0 comments 0 reactions 1 assignee View on GitHub

@krbharadwaj is already working on this.

Since Aug 14, 2026.

bug
Dominant language
PowerShell
Stars
526
Forks
67
PR merge metrics
No merged PRs in 30d

Description

What happened?

I muted Microsoft Teams in Windows Volume Mixer. Then I launched my application (which also uses WebView2). My app started in a muted state automatically, even though I never muted my app. Both apps use WebView2 for audio, and Windows treats them as the same application because they both use msedgewebview2.exe.

When I checked Volume Mixer after launching my app:
Two separate sliders appeared:

  • "Microsoft Teams"
  • "Microsoft Edge WebView2" (my app)

Expected Behavior

  • My app should start unmuted by default
  • Muting Teams should NOT affect my app
  • Each app should have independent audio control

Actual Behavior

  • My app inherited the muted state from Teams
  • Even though my app has its own slider in Volume Mixer, it started muted
  • I have to manually unmute my app every time I launch it after Teams was muted
Importance

Blocking. My app's basic functions are not working due to this issue.

Runtime Channel

Prerelease (Edge Canary/Dev/Beta), Stable release (WebView2 Runtime)

Runtime Version

151.0.4129.59

SDK Version

1.0.2210.55

Framework

Winforms

Operating System

Windows 11

OS Version

22631.7219

Repro steps

Step-by-Step Issue
What I did:

  • Opened Microsoft Teams (which uses WebView2 for audio)
  • Opened Windows Volume Mixer (right-click volume icon → Open Volume Mixer)
  • Muted Teams by clicking the speaker icon under "Microsoft Teams"
  • Closed Teams completely (optional)
  • Launched my application (which also uses WebView2 for audio)
  • My app plays audio, but no sound comes out (in volume mixer it's in mute state)
Image
Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

Don't know

Last working version (if regression)

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.