MicrosoftEdge / MicrosoftEdge/WebView2Feedback

Allow Installing WebView2 Runtime as a Prerequisite from Microsoft Store

Open
#2,077 1 comment 0 reactions 2 assignees View on GitHub

@KomalPrasadMSPM is already working on this.

Since Mar 5, 2025.

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

Description

Is your feature request related to a problem? Please describe.
Yes. I have several apps on the Microsoft Store which I would like to upgrade from using Internet Explorer and Edge Legacy based WebViews to use Microsoft Edge Chromium ones, but because the runtime is not installed by default on Windows 10 I cannot guarantee that the user will have it installed already. Yes, I can prompt the user to it but I feel like this creates a poor user experience - users should be able to install an app and it should 'just work' without needing to downloading anything else. Other issue is that administrative privileges are required to install the Edge Chromium runtime, meaning that a standard user could download one of my apps from the Microsoft Store, only to be unable to use it due to not having the runtime installed and not being an administrator. There is also the fixed distribution mode but this is annoying to set up and doesn't get updated automatically. Also it dramatically increases the size of the app and many of my apps are big enough as it is as they use .Net Core fixed distribution mode since .Net Core is in a similar situation where it can't be installed automatically via the Microsoft Store.
Also at the moment, there is no documentation (At least that I can find) on distributing the Microsoft Edge WebView Runtime via the Microsoft Store.

Describe the solution you'd like and alternatives you've considered
I think if the Microsoft Edge WebView Runtime could be installed automatically by the Microsoft Store when an app that uses it is installed, similar to WinUI this would be good and allow many more developers to use it. I've talked about the alternatives I've considered in the previous section.

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.