Compartir a través de

interface ICoreWebView2ProcessFailedEventArgs3

  • Artículo
interface ICoreWebView2ProcessFailedEventArgs3
  : public ICoreWebView2ProcessFailedEventArgs2

A continuation of the ICoreWebView2ProcessFailedEventArgs2 interface fot 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 1.0.2470

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.