MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Problem/Bug]: webview2 process running failed with log "[DllMain] Not SafeMode"

Open
#5,149 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

What happened?

Our application use webview2 to show html page.
It has been running normally on many users' machines.
But one custom report issue that can not display html page on his PC.
We remote this user's PC.
Found that process of webview2 running and exit soon,we got follow info

  1. In code, ICoreWebView2ProcessFailedEventHandler catch the exit event

    • kind:COREWEBVIEW2_PROCESS_FAILED_KIND_BROWSER_PROCESS_EXITED
    • reason:COREWEBVIEW2_PROCESS_FAILED_REASON_UNEXPECTED
    • exit code:-2147483645
      we added retry logic in ProcessFailed logic, but retry always meet process failed in 4 times.
  2. we use DebugView on this PC,got follow error.
    Image

  3. on this PC, webview2Sample demo always can not running succeed, follow popup

Image

  1. on this PC, MS Steam and Widget.exe always can not running due to webview2 process failed.
    Thirdtly Application Zoom always can not show web page due to webview2 process failed.

  2. we know this PC have follow hotfix through sysinfo command
    [01]: KB5049622
    [02]: KB5052093
    [03]: KB5052085
    [04]: KB5052915

We do not know why this issue happend on this PC, Please give us more support.

Importance

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

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

133.0.3065.82

SDK Version

1.0.2045.28

Framework

Win32

Operating System

Windows 11

OS Version

Windows 11 Pro(10.0.26100)

Repro steps

just running client,then reproduce every time on this PC.

Repros in Edge Browser

No, issue does not reproduce in the corresponding Edge version

Regression

No, this never worked

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.

Research direction

Reproduce the failure on the reported Windows 11 PC using the WebView2 sample, then review the ProcessFailed details, DebugView log, runtime version 133.0.3065.82, SDK version 1.0.2045.28, and listed hotfixes. A useful outcome would be identifying the cause or a supported workaround, but the issue does not define a specific code change or test for completion.

Written by the indexing model from the issue text.

Assessment

Domain
desktop, operating-systems
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.