You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The automatic updating desynchronises Webview2 from Edge and so wastes 0.6GB of storage to duplication. I cannot find a reliable way to update Webview2 or to downgrade/disable automatic updates in Edge so that the two remain synchronised. It's fairly painful for storage space control and cleanup to have this variable 0.6GB. Help or remediation appreciated.
Did you run WebView2 Runtime installer as admin (elevated)? By default it tries to install per user and would refuse to do so if per machine install is already there.
Edge browser and Edge WebView2 Runtime are 2 different products, and have slightly different release and rollout schedule. While rollout schedules are different, the same version is normally released at the same time, and I would expect running installer as admin would install latest version. Note that there could be times that we release the two products at different times or skip a version for WebView2. Those should not be often though.
What happened?
The automatic updating desynchronises Webview2 from Edge and so wastes 0.6GB of storage to duplication. I cannot find a reliable way to update Webview2 or to downgrade/disable automatic updates in Edge so that the two remain synchronised. It's fairly painful for storage space control and cleanup to have this variable 0.6GB. Help or remediation appreciated.
I tried:
.\setup.exe --msedgewebview --delete-old-versions --system-level --verbose-logging --on-logon
: immediately exits with no output.Importance
Moderate. My app's user experience is affected, but still usable.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
130.0.2849.56
SDK Version
No response
Framework
Other
Operating System
Windows 10
OS Version
19045.5011
Repro steps
Bug is fully automatic and intermittent depending on versions.
Repros in Edge Browser
No, issue does not reproduce in the corresponding Edge version
Regression
No, this never worked
Last working version (if regression)
No response
The text was updated successfully, but these errors were encountered: