MicrosoftEdge / MicrosoftEdge/WebView2Feedback

WebView2 Runtime 109.0.1518.61 is not installing when there is a process using WebView2.exe

Open
#3,162 3 comments 0 reactions 1 assignee View on GitHub

@LiangTheDev is already working on this.

Since Jan 26, 2023.

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

Description

Description

WebView2 Runtime 109.0.1518.61 is not installing when there is a process using WebView2.exe.
We are seeing multiple machines not getting WebView2 installed because of this issue. Our users are running multiple applications that uses wsedgewebview2.exe
When they recieve the installation centrally, which installs with SYSTEM, it uninstalls WebView2 but is unable to re-install it because of the locking of WebView2-processes. The symptom also shows as the Application-folder is empty:

image

When running following PS-command we see that if you have, for an example, Outlook open then WebView2 will not be installed.

$instance = Get-WmiObject Win32_Process -Filter "Name='msedgewebview2.exe'"
$parentProcess = Get-Process -Id $instance.ParentProcessId | Where ProcessName -NotLike 'msedgewebview2'
$parentProcess

Handles  NPM(K)    PM(K)      WS(K)     CPU(s)     Id  SI ProcessName                                                                                               
-------  ------    -----      -----     ------     --  -- -----------                                                                                               
   5670     121   287984     414852      81,80  30900   1 OUTLOOK    

If we close down Outlook then WebView2 installs and the folder is populated. OBS it is not only Outlook blocking for WebView2 installation, but several other processes like Explorer, Photoshop and more...

This problem started with 109.0.1518.52 and is still active in the latest version 109.0.1518.61.

Version
Runtime: WebView2 Runtime 109.0.1518.61
OS: Win 10, Win 11

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.