MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Problem/Bug]: Webview2 create second webview failed with hr 0x8007139f

Open
#5,356 2 comments 2 reactions 1 assignee View on GitHub

@prija-microsoft is already working on this.

Since Oct 23, 2025.

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

Description

What happened?

I'm developing an app base on Webview2, it works well for years, however, one customer recently reposrted that the app did not work well, I nalyst the log and found only the first webview created, from the second, all creation failed with hresult 0x8007139f(-2147019873), in caallback ICoreWebView2CreateCoreWebView2ControllerCompletedHandler, and the controller is null in this callback.
Not all customers have this issue but only this one, thus it's not easy to reproduce, but this customer are using Windows server 2016, in his machine it happens every time, this made him very upset.

Importance

Blocking. My app's basic functions are not working due to this issue.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

139.0.3405.125

SDK Version

1.0.3065.39

Framework

Win32

Operating System

Other

OS Version

Windows Server 2016

Repro steps

Iadd callback CoreWebView2CreateCoreWebView2ControllerCompletedHandler, Create an environment and create a webview, then create another, this iseeue happens.

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.