MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Problem/Bug]: Error When Initilize WebView2 (0x8007139F)

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

@vbryh-msft is already working on this.

Since Feb 26, 2024.

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

Description

What happened?

image

Message ---
The group or resource is not in the correct state to perform the requested operation. (0x8007139F)

StackTrace ---
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32 errorCode)
at Microsoft.Web.WebView2.Core.CoreWebView2Environment.CreateCoreWebView2ControllerAsync(IntPtr ParentWindow)
at Microsoft.Web.WebView2.WinForms.WebView2.InitCoreWebView2Async(CoreWebView2Environment environment, CoreWebView2ControllerOptions controllerOptions)


a particular user have reported that the program worked well in the past,
However, as of February 23rd, an error suddenly occurred and it did not work.

We have tried various measures such as
WebView 2 recovery, Edge Beta installation, and userDataFolder changes,
but they are still not resolved.

The user eventually solved it by window formatting,
but I want to know the source of this problem.

Importance

Important. My app's user experience is significantly compromised.

Runtime Channel

Stable release (WebView2 Runtime), Prerelease (Edge Canary/Dev/Beta)

Runtime Version

121.0.2277.128

SDK Version

1.0.1823.32 and 1.0.2277.86

Framework

Winforms

Operating System

Windows 10

OS Version

19045.4046

Repro steps

Initialize WebView 2 when running the program and loading the form, an exception occurs.
Sadly, this is only happening with some users, and I have never reproduced this error so far.
So, I'll upload the code for the initialization part.

image
image

The same symptoms occurred even if set the userDataFolder differently.
And I recognized that the data existed in that path.

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

  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.