Edit

Runtime 148.0.3967.48 (May 11, 2026)

Release notes for Microsoft Edge WebView2 Runtime, release date: May 11, 2026.

Bug fixes

  • Fixed an updater issue where the currently used WebView2 Runtime is deleted after installing a new version, causing a crash during new controller creation in an already running app.

  • Breaking change: Supplemented the CoreWebView2ProcessFailedReason.Unexpected enum member by adding more granular values, for the CoreWebView2ProcessFailedReason enum that's returned by the CoreWebView2ProcessFailedEventArgs.Reason property. This is a breaking change. See Breaking change: Granular process failure reasons for the ProcessFailed event, below.

  • Fixed Print dialog dropdown selection issues in WebView2CompositionControl. (Issue #5195)

  • Disabled the Domain Actions component for WebView2.

  • Disabled WebUSBDetector notification for WebView2.

  • Fixed stale ICoreWebView2Profile3::get_PreferredTrackingPreventionLevel.

  • Fixed WDP clients being unable to connect to a remote debugging server.

  • Fixed an issue for the WPF sample app, where closing the window left a lingering WPF process.

Breaking change: Granular process failure reasons for the ProcessFailed event

The ProcessFailed event fires when a WebView2-associated process (such as a renderer or GPU process) exits unexpectedly, allowing apps to respond with recovery logic or diagnostics.

Before this change: The CoreWebView2ProcessFailedEventArgs.Reason property returned Unexpected for three distinct exit scenarios (normal exit, abnormal exit, and code integrity failure), making it impossible for apps to distinguish between them.

After this change: When the msWebView2GranularProcessFailedReason feature flag is enabled, the CoreWebView2ProcessFailedEventArgs.Reason property returns the following new, granular CoreWebView2ProcessFailedReason enum values, instead of Unexpected:

  • NormalExit — The process exited normally (exit code 0).

  • AbnormalExit — The process exited abnormally (non-zero exit code), but did not crash or get killed.

  • IntegrityFailure — The OS terminated the process due to a code integrity failure, such as when a DLL fails Windows Code Integrity verification.

The msWebView2GranularProcessFailedReason feature flag is disabled by default in releases 148 and 149, giving apps two releases to proactively test. Starting in release 150, the feature will be enabled by default, and apps will receive the granular values. To validate your WebView2 app's behavior, enable the feature flag, as follows:

set WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS=--enable-features=msWebView2GranularProcessFailedReason

This is a bug fix for the Runtime and SDK. These enum members are a modification of an existing stable API, and are available as part of this Prerelease SDK.

See also:

See also

  • Last updated on