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: microsoft-edge/devtools-guide-chromium/remote-debugging/windows.md
+39-26Lines changed: 39 additions & 26 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.author: msedgedevrel
6
6
ms.topic: conceptual
7
7
ms.service: microsoft-edge
8
8
ms.subservice: devtools
9
-
ms.date: 04/23/2021
9
+
ms.date: 03/03/2025
10
10
---
11
11
# Remotely debug Windows devices
12
12
@@ -26,19 +26,13 @@ This tutorial teaches you the following tasks:
26
26
27
27
The host or debuggee machine is the Windows 10 or later device that you want to debug. It may be a remote device that is hard for you to physically access or it may not have keyboard and mouse peripherals, making it difficult to interact with the Microsoft Edge DevTools on that device.
28
28
29
-
To set up the host (debuggee) machine:
30
-
31
-
1. Install and configure [Microsoft Edge](https://www.microsoft.com/edge)
32
-
33
-
1. Install the [Remote Tools for Microsoft Edge (Beta)](https://www.microsoft.com/store/apps/9P6CMFV44ZLT) from the [Microsoft Store](https://www.microsoft.com/store/apps/windows)
34
-
35
-
1. Activate [Developer Mode](/windows/apps/get-started/enable-your-device-for-development) and enable [Device Portal](/windows/uwp/debug-test-perf/device-portal)
29
+
To set up the host (debuggee) machine, use the following sub-sections, in order.
36
30
37
31
38
32
<!-- ------------------------------ -->
39
33
#### Install and configure Microsoft Edge
40
34
41
-
1. If you haven't already, on the Windows 10 or later device that you want to debug, install Microsoft Edge from [this page](https://www.microsoft.com/edge).
35
+
1. If not already installed, on the Windows 10 or later device that you want to debug, install Microsoft Edge, from [Get to Know Microsoft Edge](https://www.microsoft.com/edge).
42
36
43
37
1. If you're using a pre-installed version of Microsoft Edge on the host (debuggee) machine, verify that you have Microsoft Edge (Chromium) and not Microsoft Edge (EdgeHTML). A quick way to check is to load `edge://settings/help` in the browser and confirm that the version number is 75 or higher.
44
38
@@ -52,33 +46,43 @@ To set up the host (debuggee) machine:
52
46
<!-- ------------------------------ -->
53
47
#### Install the Remote Tools for Microsoft Edge (Beta)
54
48
55
-
Install the [Remote Tools for Microsoft Edge (Beta)](https://www.microsoft.com/store/apps/9P6CMFV44ZLT) from the [Microsoft Store](https://www.microsoft.com/store/apps/windows).
49
+
1. Install the [Remote Tools for Microsoft Edge](https://apps.microsoft.com/detail/9p6cmfv44zlt) from the [Microsoft Store](https://apps.microsoft.com).
50
+
51
+
The **Download** or **Get** button for that page might be disabled if you are on Windows 10 or later version 1809 or earlier. To set up the host (debuggee) machine, it must be running Windows 10 version 1903 or later. Update the host (debuggee) machine, to acquire the Remote Tools for Microsoft Edge.
56
52
57
-
The **Get** button for the [Remote Tools for Microsoft Edge (Beta)](https://www.microsoft.com/store/apps/9P6CMFV44ZLT) may be disabled if you are on Windows 10 or later version 1809 or earlier. To set up the host (debuggee) machine, it must be running Windows 10 version 1903 or later. Update the host (debuggee) machine to acquire the [Remote Tools for Microsoft Edge (Beta)](https://www.microsoft.com/store/apps/9P6CMFV44ZLT).
53
+
58
54
59
-
55
+
1. Launch Remote Tools for Microsoft Edge and, if prompted, accept the permissions dialog in the app.
60
56
61
-
Launch the [Remote Tools for Microsoft Edge (Beta)](https://www.microsoft.com/store/apps/9P6CMFV44ZLT) and, if prompted, accept the permissions dialog in the app. You can now close the [Remote Tools for Microsoft Edge (Beta)](https://www.microsoft.com/store/apps/9P6CMFV44ZLT) and you don't need to have it open for future remote debugging sessions.
57
+
1. Close Remote Tools for Microsoft Edge. You don't need to have it open for future remote debugging sessions.
62
58
63
59
64
60
<!-- ------------------------------ -->
65
61
#### Activate Developer Mode and enable Device Portal
66
62
67
-
If you are on a WiFi network, make sure the network is marked as either **Domain** or **Private**. You can verify the state by opening the **Windows Security** app, selecting **Firewall & network protection** and checking if your network is listed as a **Domain** network or **Private** network.
63
+
1. Activate Developer Mode; see [Enable your device for development](/windows/apps/get-started/enable-your-device-for-development).
64
+
65
+
1. Enable Device Portal; see [Windows Device Portal overview](/windows/uwp/debug-test-perf/device-portal).
66
+
67
+
1. If you are on a WiFi network, make sure the network is marked as either **Domain** or **Private**. You can verify the state by opening the **Windows Security** app, selecting **Firewall & network protection** and checking if your network is listed as a **Domain** network or **Private** network.
68
+
69
+
1. If your network is listed as **Public**, go to **Settings** > **Network & Internet** > **Wi-Fi**, click on your network, and toggle the **Network profile** button to **Private**.
68
70
69
-
If your network is listed as **Public**, go to **Settings** > **Network & Internet** > **Wi-Fi**, click on your network, and toggle the **Network profile** button to **Private**.
71
+
1. Open the **Settings** app. In **Find a setting**, enter `Developer settings` and select it. Toggle on **Developer Mode**. You can now turn on the **Device Portal** by setting **Turn on remote diagnostics over local area network connections** to **On**. You can then optionally turn **Authentication** on so that the client (debugger) device must provide the correct credentials to connect to this device.
70
72
71
-
Now, open the **Settings** app. In **Find a setting**, enter `Developer settings` and select it. Toggle on **Developer Mode**. You can now turn on the **Device Portal** by setting **Turn on remote diagnostics over local area network connections**to **On**. You can then optionally turn **Authentication** on so that the client (debugger) device must provide the correct credentials to connect to this device.
73
+
1. If **Turn on remote diagnostics over local area network connections.**was previously turned on, you must turn it off and turn it on again for **Device Portal** to work with the [Remote Tools for Microsoft Edge (Beta)](https://www.microsoft.com/store/apps/9P6CMFV44ZLT).
72
74
73
-
If **Turn on remote diagnostics over local area network connections.** was previously turned on, you must turn it off and turn it on again for **Device Portal** to work with the [Remote Tools for Microsoft Edge (Beta)](https://www.microsoft.com/store/apps/9P6CMFV44ZLT). If a **For developers** section isn't displayed in **Settings**, **Device Portal** may already be turned on, so try restarting the Windows 10 or later device instead.
75
+
If a **For developers** section isn't displayed in **Settings**, **Device Portal** may already be turned on, so try restarting the Windows 10 or later device instead.
74
76
75
-
77
+
76
78
77
-
Note the machine IP address and connection port that are displayed under **Connect using:**. The IP address in the image below is `192.168.86.78` and the connection port is `50080`:
79
+
1.Note the machine IP address and connection port that are displayed under **Connect using:**. The IP address in the image below is `192.168.86.78` and the connection port is `50080`:
78
80
79
-
81
+
80
82
81
-
You enter the information on the client (debugger) device in the [next section](#step-2-set-up-the-client-debugger-machine). Open tabs in Microsoft Edge and [Progressive Web Apps (PWAs)](../progressive-web-apps/index.md) on the host (debuggee) machine that you want to debug from the client (debugger) machine.
83
+
You enter the information on the client (debugger) device in the next section, "Step 2: Set up the client (debugger machine)".
84
+
85
+
1. Open tabs in Microsoft Edge and [Progressive Web Apps (PWAs)](../progressive-web-apps/index.md) on the host (debuggee) machine that you want to debug from the client (debugger) machine.
@@ -120,13 +124,22 @@ If you want to connect to the host (debuggee) machine using `https` instead of `
120
124
121
125
1. If prompted, confirm that you want to install this certificate to the **Trusted Root Certification Authorities** store.
122
126
123
-
1. Now, when connecting to the host (debuggee) machine from the client (debugger) machine using the `edge://inspect` page, you must use a different `connection port` value. By default, for desktop Windows, the Device Portal uses `50080` as the `connection port` for `http`. For `https`, the Device Portal uses `50043` so follow this pattern: https://`IP address`:`50043` on the `edge://inspect` page. [Read more about the default ports used by Device Portal](/windows/uwp/debug-test-perf/device-portal#setup).
127
+
1. Now, when connecting to the host (debuggee) machine from the client (debugger) machine using the `edge://inspect` page, you must use a different `connection port` value. By default, for desktop Windows, the Device Portal uses `50080` as the `connection port` for `http`. For `https`, the Device Portal uses `50043` so follow this pattern: https://`IP address`:`50043` on the `edge://inspect` page.
128
+
129
+
To see the default ports that are used by Device Portal, see the table in [Setup](/windows/uwp/debug-test-perf/device-portal#setup) in _Windows Device Portal overview_.
124
130
125
131
126
132
<!-- ---------- -->
127
133
###### Default ports
128
134
129
-
The default port for `http` is `50080` and the default port for `https` is `50043`, but this isn't always the case, because Device Portal on desktop claims ports in the ephemeral range (\>50,000) to prevent collisions with existing port claims on the device. To learn more, see the [Port Settings](/windows/uwp/debug-test-perf/device-portal-desktop#registry-based-configuration-for-device-portal) section for Device Portal on Windows desktop.
135
+
The default port for `http` is `50080` and the default port for `https` is `50043`, but this isn't always the case, because Device Portal on desktop claims ports in the ephemeral range (\>50,000) to prevent collisions with existing port claims on the device.
136
+
137
+
To see the default ports that are used by Device Portal, see the table in [Setup](/windows/uwp/debug-test-perf/device-portal#setup) in _Windows Device Portal overview_.
138
+
139
+
For information about port settings, see [Windows Device Portal for Desktop](/windows/uwp/debug-test-perf/device-portal-desktop).
140
+
141
+
See also:
142
+
*[Registry-based configuration](https://learn.microsoft.com/en-us/windows/uwp/debug-test-perf/device-portal-desktop#registry-based-configuration) in _Windows Device Portal for Desktop_.
* The **Event Listeners** pane in the **Elements** tool is blank on Windows 10 version 1903. The team plans to fix the **Event Listeners** pane in a servicing update to Windows 10 version 1903.
198
+
* The **Event Listeners** pane in the **Elements** tool is blank on Windows 10 version 1903. The team plans to fix the **Event Listeners** pane in a servicing update to Windows 10 version 1903.<!-- todo: done? -->
186
199
187
-
* The **Cookies** pane in the **Application** panel is blank on Windows 10 version 1903. The team plans to fix the **Cookies** pane in a service update to Windows 10 version 1903.
200
+
* The **Cookies** pane in the **Application** panel is blank on Windows 10 version 1903. The team plans to fix the **Cookies** pane in a service update to Windows 10 version 1903.<!-- todo: done? -->
188
201
189
-
* The **Audits** tool, the **3D View** tool, the **Emulated Devices** section in **Settings**, and the **Accessibility tree** pane in the **Elements** tool aren't currently working as expected.
202
+
* The **Audits** tool, the **3D View** tool, the **Emulated Devices** section in **Settings**, and the **Accessibility tree** pane in the **Elements** tool aren't currently<!-- todo: fixed? --> working as expected.
190
203
191
204
* The file explorer doesn't launch from the DevTools in the **Sources** tool or in the **Security** panel when you remote debug.
0 commit comments