You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: diagnostics/gpu.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ On the device that is hitting the issue:
9
9
1. Share the `dxdiag.txt` file
10
10
11
11
## GPU Logs
12
-
1. Navigate your WV2 to `edge://gpu`
12
+
1. Navigate your WV2 to `edge://gpu`. This needs to be done programmatically inside the application, and can't be done via DevTools console or similar means.
13
13
1. Wait for the page to load content under the "Log Messages" header towards the bottom.
Installer logs include information about any errors that WV2's installer/updater hit when trying to install or update the WV2 runtime. There are a few different logs that we need to best look in to any issues.
3
3
4
-
## Registry Key
5
-
This registry contains important update information like when the last update occurred, recent error codes, and updater version information.
4. Name it `registryoutput.txt`, change "Save as Type" to .txt, and ensure "Selected branch" is the path from step #2.
10
-
5. Click Save.
4
+
## Installer History & File List
5
+
There are some registry keys that contain important update information like when the last update occurred, recent error codes, and updater version information. The list of installed files that actually exist the device is also helpful in case there are errors or other processes removing them.
6
+
7
+
1. Open a command prompt.
8
+
2. Run `reg export HKCU\SOFTWARE\Microsoft\EdgeUpdate\ClientState EdgeRegistryUser.txt`
9
+
3. Run `reg export HKLM\SOFTWARE\Microsoft\EdgeUpdate\ClientState EdgeRegistryMachine.txt /reg:32`
10
+
4. Run `dir "c:\Program Files (x86)\Microsoft\EdgeWebView" /s > EdgeFiles.txt`
11
+
5. Run `dir "c:\Program Files (x86)\Microsoft\EdgeCore" /s >> EdgeFiles.txt`
12
+
13
+
You should now have three files: `EdgeRegistryUser.txt`, `EdgeRegistryMachine.txt`, and `EdgeFiles.txt`.
11
14
12
15
## Installer Logs
13
-
There are three places where WV2's updater will write potentially important logs:
16
+
There are four places where WV2's updater will write important details about any install or update issues. If you don't have all of these that's not a problem, include what exists:
If you don't have all three of these, that's not a problem.
20
-
21
-
## List of Installed WV2 Files
22
-
Finally, including a list of all the files installed by WV2 will let us understand if there is something missing in your installation causing the issue.
23
-
1. Open a command prompt.
24
-
2. Run `dir /s /b "c:\Program Files (x86)\Microsoft\EdgeWebView\" > edgefiles.txt` this creates `edgefiles.txt` with the list of files.
25
-
26
-
Once you have all five of these files: `registryoutput.txt`, `msedge_installer.log`, `edgefiles.txt`, and the two `MicrosoftEdgeUpdate.log`s, share them with the WV2 developer who is helping you.
23
+
Once you have these files, share them with the WV2 developer who is helping you.
0 commit comments