MicrosoftEdge / MicrosoftEdge/WebView2Feedback

`COMException` 800705b4 during `EncureCoreWebView2Async`

Open
#2,400 11 comments 0 reactions 1 assignee View on GitHub

@champnic is already working on this.

Since Apr 29, 2022.

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

Description

Description
We have noticed that some users encountered the following error when initializing WebView2

System.Runtime.InteropServices.COMException: This operation returned because the timeout period expired. (Exception from HRESULT: 0x800705B4)
  ?, in void Marshal.ThrowExceptionForHRInternal(int errorCode, IntPtr errorInfo)
  ?, in async Task<CoreWebView2Controller> CoreWebView2Environment.CreateCoreWebView2ControllerAsync(IntPtr ParentWindow)
  ?, in async Task WebView2.EnsureCoreWebView2Async(CoreWebView2Environment environment)+Init(?)
  ?, in async void MainViewModel.Initialize(WebView2 webView2)
  ?, in void AsyncMethodBuilderCore.ThrowAsync(Exception exception, SynchronizationContext targetContext)+(object state) => { }
  ?, in object ExceptionWrapper.InternalRealCall(Delegate callback, object args, int numArgs)
  ?, in object ExceptionWrapper.TryCatchWhen(object source, Delegate callback, object args, int numArgs, Delegate catchHandler)

Version
SDK: 1.0.1020.30
Runtime: >=95.0.1020.30
Framework: WPF (.NET Framework 4.8)
OS: >=10.0.22000.0

Repro Steps
We're unable to reproduce the issue but we can observe the occurrences of ^ from our logs.

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.