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

[byungmeo]

What happened?

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.

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

[lflores-ms]

Hi @byungmeo -- it's hard to tell exactly what the specific issue is from just the error code, but some of the reasons creation might fail in this way are the following:

• There is an existing instance of the application running the WebView2 Runtime, with a mismatching configuration, including DPI awareness, GDI scaling and AdditionalBrowserArguments.
• There's another process running with the same User Data Folder which has set ExclusiveUserDataFolderAccess.
• There's an app compat setting forcing DPI awareness of the msedgewebview2.exe process to be of certain value, which doesn't match the app configuration.

It is possible that the machine has a User Data Folder override, leading to one of the conditions above. See GitHub #7688