Skip to content

Latest commit

 

History

History
58 lines (40 loc) · 2.89 KB

icorewebview2processfailedeventargs3.md

File metadata and controls

58 lines (40 loc) · 2.89 KB
Raw
description title ms.date keywords topic_type api_name api_type api_location
A continuation of the ICoreWebView2ProcessFailedEventArgs2 interface for getting blocked file for code integrity process failures.
WebView2 Win32 C++ ICoreWebView2ProcessFailedEventArgs3
04/22/2024
IWebView2, IWebView2WebView, webview2, webview, win32 apps, win32, edge, ICoreWebView2, ICoreWebView2Controller, browser control, edge html, ICoreWebView2ProcessFailedEventArgs3
APIRef
ICoreWebView2ProcessFailedEventArgs3
ICoreWebView2ProcessFailedEventArgs3.get_FailureSourceModulePath
COM
embeddedbrowserwebview.dll

interface ICoreWebView2ProcessFailedEventArgs3

[!INCLUDE deprecation-note]

interface ICoreWebView2ProcessFailedEventArgs3
  : public ICoreWebView2ProcessFailedEventArgs2

A continuation of the ICoreWebView2ProcessFailedEventArgs2 interface for getting blocked file for code integrity process failures.

Summary

Members Descriptions
get_FailureSourceModulePath This property is the full path of the module that caused the crash in cases of Windows Code Integrity failures.

Applies to

Product Introduced
WebView2 Win32 1.0.2420.47
WebView2 Win32 Prerelease

Members

get_FailureSourceModulePath

This property is the full path of the module that caused the crash in cases of Windows Code Integrity failures.

public HRESULT get_FailureSourceModulePath(LPWSTR * value)

Windows Code Integrity is a feature that verifies the integrity and authenticity of dynamic-link libraries (DLLs) on Windows systems. It ensures that only trusted code can run on the system and prevents unauthorized or malicious modifications. When ProcessFailed occurred due to a failed Code Integrity check, this property returns the full path of the file that was prevented from loading on the system. The webview2 process which tried to load the DLL will fail with exit code STATUS_INVALID_IMAGE_HASH(-1073740760). A file can fail integrity check for various reasons, such as:

  • It has an invalid or missing signature that does not match the publisher or signer of the file.

  • It has been tampered with or corrupted by malware or other software.

  • It has been blocked by an administrator or a security policy. This property always will be the empty string if failure is not caused by STATUS_INVALID_IMAGE_HASH.

The caller must free the returned string with CoTaskMemFree. See API Conventions.