MicrosoftEdge / MicrosoftEdge/WebView2Feedback
[Problem/Bug]: After distribute with Evergreen Standalone x64-Installer (136.0.3240.50 and 136.0.3240.64), MSTeams doesn't start anymore
@KomalPrasadMSPM is already working on this.
Since May 23, 2025.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
What happened?
After deploy MicrosoftEdgeWebView2RuntimeInstallerX64.exe (Evergreen Standalone Installer) with the parameters "/silent /install" with System-Account, then MS Teams won't start and appears a window informing you that a problem has occurred and that you need to download “Edge WebView2”:
No possibility to distribute this software with system account so that MSTeams works.
If you start the installer with an administrator account, the installation works correctly and MSTeams starts and works normally.
Used client OS to deploy this package on it: Windows 11 Education x64 (23H2 and 24H2)
Used deployment software: Matrix42 Empirum v24.0.3
Importance
Blocking. My app's basic functions are not working due to this issue.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
136.0.3240.64
SDK Version
No response
Framework
Other
Operating System
Windows 11
OS Version
10.0.26100.3775
Repro steps
Run with system account (with deployment software): "MicrosoftEdgeWebView2RuntimeInstallerX64.exe /silent /install"
Try starting MSTeams
A window informing you that a problem has occurred and that you need to download “Edge WebView2”.
Solving this problem:
Run with administrator account: "MicrosoftEdgeWebView2RuntimeInstallerX64.exe /silent /install"
MSTeams works.
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.