История

vbryh-msft 729ea6c1b6 Update antimalware (#4134 )		2023-11-08 13:02:07 -08:00
..
README.md	Code intergrity diagnostics (#3729 )	2023-08-23 11:29:53 -07:00
WebView2.wprp	PR Feedback.	2022-11-17 11:32:34 -08:00
WebView2_CPU.wprp	PR Feedback.	2022-11-17 11:32:34 -08:00
code_integrity.md	Update antimalware (#4134 )	2023-11-08 13:02:07 -08:00
compatibility_problem.png	Code intergrity diagnostics (#3729 )	2023-08-23 11:29:53 -07:00
crash.md	Expand all docs.	2022-11-16 13:15:01 -08:00
etw.md	Switch to WebView2_CPU.wprp by default.	2023-05-15 14:37:26 -07:00
gpu.md	PR Feedback.	2022-11-17 11:32:34 -08:00
install.md	Update install.md	2023-02-08 14:45:59 -08:00
network.md	Expand all docs.	2022-11-16 13:15:01 -08:00
version.md	Create version.md	2023-09-27 13:30:07 -07:00

README.md

Gathering Diagnostics and Logs

This folder contains directions for gathering various detailed diagnostics/logs when reporting WV2-related issues. There's generally no need to proactively get any of these diagnostics before opening an issue, but if one seems obvious feel free to get it before opening an issue. Otherwise, a WV2 developer might link you to one of these pages to help them investigate an issue:

Crash Dumps: Crash dumps are used to better understand why a WV2 process is crashing and firing a ProcessFailed event.
ETW Trace: Event Tracing for Windows (ETW) traces include detailed events on system state and the activities WV2 was doing before and when an issue occurs.
Installer Logs: Installer logs include information about any errors that WV2's installer/updater hit when trying to install or update the WV2 runtime.
GPU Info: GPU logs include details on the user's GPU and any potential graphics or rendering issues.
Network Logs: Network logs include the network requests, responses, and details on any errors when loading files.
Code Integrity: how to root cause STATUS_INVALID_IMAGE_HASH errors.