Add ttd and procmon and correct memory dump

Author: Chetan Pandey

diagnostics/README.md

@@ -2,7 +2,7 @@
 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.md): Crash dumps are used to better understand why a WV2 process is crashing and firing a [ProcessFailed](https://learn.microsoft.com/dotnet/api/microsoft.web.webview2.core.corewebview2.processfailed) event.
-- [Crash Dumps from Task Manager](task_manager_dump.md): There are cases where crash dumps aren't automatically generated and need to be collected manually.
+- [Memory Dumps from Task Manager](task_manager_dump.md): Sometimes a user might need to manually gather a memory dump, normally for unresponsive processes.
 - [ETW Trace](etw.md): 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](install.md): 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.md): GPU logs include details on the user's GPU and any potential graphics or rendering issues.

diagnostics/code_integrity.md

@@ -9,7 +9,7 @@ and exit code -1073740760 or STATUS_INVALID_IMAGE_HASH.
 
 Users may see error page in the WebView2:
 
-![Compatibility problem](compatibility_problem.png)
+![Compatibility problem](resources/compatibility_problem.png)
 
 ## Update antimalware software
 Starting versions 118 and 119 the options to disable Code Integrity in WebView2 are deprecated and the guard is always on.

diagnostics/crash.md

@@ -11,4 +11,4 @@ By default the user data folder is created in the app's folder by default with a
 
 If you do not have crash dumps - please navigate your webview2 control to `edge://crashes` to see if there are new reports. Copy necessary data to Clipboard and share with us.
 
-![crashes](crashes.png)
+![crashes](resources/crashes.png)

diagnostics/etw.md

@@ -1,13 +1,13 @@
 # Gathering an ETW Trace
 [Event Tracing for Windows (ETW)](https://learn.microsoft.com/en-us/windows-hardware/test/wpt/event-tracing-for-windows)traces include detailed events on system state and the activities WV2 was doing before and when an issue occurs.
 
-This repo has a WV2 recording profile - [WebView2_CPU.wprp](WebView2_CPU.wprp) that includes the events that we find most useful.
+This repo has a WV2 recording profile - [WebView2_CPU.wprp](resources/WebView2_CPU.wprp) that includes the events that we find most useful.
 
 ETW traces can get fairly large, so try to keep the amount of extra time spent when recording as small as possible. If you need a longer trace, ask the WV2 developer that you're working with if `WebView2.wprp` will suffice (it gathers less data).
 
 1. Close Edge and any other apps using WV2 to make the trace more clear. Common apps using WV2 may include `widgets.exe`, `msteams.exe`, and Microsoft Office products.
-2. Download [WebView2_CPU.wprp](WebView2_CPU.wprp) from this repo.
-3. If your app has a specific profile, merge it with [WebView2_CPU.wprp](WebView2_CPU.wprp) to ensure all events are captured in a single ETL file.
+2. Download [WebView2_CPU.wprp](resources/WebView2_CPU.wprp) from this repo.
+3. If your app has a specific profile, merge it with [WebView2_CPU.wprp](resources/WebView2_CPU.wprp) to ensure all events are captured in a single ETL file.
 4. In an elevated command prompt run `wpr -start WebView2_CPU.wprp -filemode` (wpr.exe is included in Windows).
 5. Reproduce the issue.
 6. In an elevated command prompt run `wpr -stop trace.etl "trace"`.

diagnostics/procmon.md

@@ -0,0 +1,26 @@
+## Procmon
+
+Process Monitor is an advanced monitoring tool for Windows that shows real-time file system, Registry and process/thread activity. Read more [here](https://learn.microsoft.com/en-us/sysinternals/downloads/procmon).
+ 
+Procmon logs can be helpful for cases where we get file not found error or access denied.
+
+
+### Steps to collect Procmon logs 
+
+1.	Download Procmon from [Microsoft Learn](https://learn.microsoft.com/en-us/sysinternals/downloads/procmon)
+
+2.	Extract the zip file  and copy **Procmon.exe** ( or **Procmon64.exe** for 64-bit systems) to the target machine.
+
+3.	Launch **Procmon.exe** and accept the license agreement
+
+4.	By default, Procmon starts capturing events immediately. 
+
+5.	Stop the capture by clicking the **Play button**.
+
+6.	Before capturing the logs, one can add filters using the Filter button. 
+
+7.	After applying the filters, start capturing the log by clicking the **Play button**.
+
+8.	After your repro, again click the **Play button** to stop the capturing and then using the save button, save the logs as .PML file to any location.
+
+9.	Compress these logs and share the zip file.