Edit

SDK 1.0.4126-prerelease, for Runtime 151 (Jul. 7, 2026)

Release notes for Microsoft Edge WebView2 Prerelease SDK, release date: Jul. 7, 2026.

NuGet package for WebView2 SDK 1.0.4126-prerelease

For full API compatibility, this Prerelease version of the WebView2 SDK requires the WebView2 Runtime that ships with Microsoft Edge version 151.0.4126.0 or later; see Runtime 151.0.4129.50 (Aug. 3, 2026).

Detailed contents:

Experimental APIs (Phase 1: Experimental in Prerelease)

The following APIs are in Phase 1: Experimental in Prerelease, and have been added in this Prerelease SDK.

Crash Report in ProcessFailed event

The CrashReport API provides crash diagnostic data when a WebView2 process fails with a crash. When a ProcessFailed event is raised, the host application can access the CrashReport property on the ProcessFailedEventArgs to retrieve crash signature details, including:

  • The exception code.
  • The faulting module name and version.
  • The fault offset.
  • The crash report ID.
  • The bucket ID.
  • The time the crash was reported.

ProcessFailedEventArgs.CrashReport is null when the failure didn't produce a crash report, such as in these scenarios:

  • A normal exit.
  • An external kill of the process.
  • A launch failure.
  • A hang.

ProcessFailedEventArgs.CrashReport may also be null for certain crash-type failures where no report was produced. Host apps should always check for null before accessing properties.

Configure per-origin reputation checking (SmartScreen) settings

The ReputationChecking feature allows a WebView2 app to skip SmartScreen reputation checks for navigations and downloads from specific trusted origins. ReputationChecking is a member of the CoreWebView2OriginFeature enum.

When this feature is set to CoreWebView2OriginFeatureState.Disabled for an origin, phishing and malware reputation checks are bypassed for that origin. If this feature isn't configured for an origin, the CoreWebView2Settings.IsReputationCheckingRequired setting, which is global, applies; the preference at the browser-process level is applied for all the processes utilizing it.

If CoreWebView2Settings.IsReputationCheckingRequired is set to false, setting CoreWebView2OriginFeatureState.Enabled for an origin doesn't re-enable reputation checks for that origin; CoreWebView2Settings.IsReputationCheckingRequired takes precedence.

Older supporting APIs:

See also