MicrosoftEdge / MicrosoftEdge/WebView2Feedback
[Problem/Bug]: Offline installer hangs for about 66 minutes
@LiangTheDev is already working on this.
Since Mar 25, 2024.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
What happened?
The WebView2 offline installer is hanging for about an hour and delaying the completion of an install script. The installer creates a child process MicrosoftEdgeUpdate.exe that terminates after about 66 minutes (PID 4032 in attached logs). The process seems to be executing the following:
"C:\Program Files (x86)\Microsoft\EdgeUpdate\MicrosoftEdgeUpdate.exe" /ping {with a bunch of Base64 data}
See attached data from ProcessMonitor and logs.
MicrosoftEdgeUpdate.log
msedge_installer.log
webview2_installer_PID4032.zip
Background: The offline installer is being launched by a Power Shell script during Windows setup in the Specialize phase using the following command:
Start-Process -NoNewWindow -Wait -FilePath ".\Microsoft\MicrosoftEdgeWebView2RuntimeInstallerX64.exe" -ArgumentList "/silent /install"
Importance
Important. My app's user experience is significantly compromised.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
122.0.2365.92
SDK Version
No response
Framework
Other
Operating System
Windows 10
OS Version
10.0.19045 Build 19045
Repro steps
On an offline system, install using offline installer using power shell command:
Start-Process -NoNewWindow -Wait -FilePath ".\Microsoft\MicrosoftEdgeWebView2RuntimeInstallerX64.exe" -ArgumentList "/silent /install"
I happen to be scripting this install during the Windows Setup specialize phase however I do not know if that is a factor.
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.