Skip to content

Commit ffb7d55

Browse files
authored
Merge pull request #291157 from RoseHJM/mdb-troubleshooting-articles
MDB - troubleshooting articles
2 parents 5399a61 + 9a08d24 commit ffb7d55

File tree

7 files changed

+208
-6
lines changed

7 files changed

+208
-6
lines changed
Lines changed: 127 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,127 @@
1+
---
2+
title: Resolve Dev Box connectivity issues
3+
description: Learn how to resolve connection issues with dev boxes, including disconnections and sign-in problems, to maintain a stable workflow.
4+
author: RoseHJM
5+
ms.author: rosemalcolm
6+
ms.service: dev-box
7+
ms.topic: troubleshooting-general
8+
ms.date: 10/22/2024
9+
10+
#customer intent: As a developer, I want to troubleshoot my Remote Desktop connection issues with dev boxes so that I can maintain a stable and efficient workflow.
11+
---
12+
13+
# Resolve connectivity issues with dev boxes
14+
15+
If you're experiencing problems with your Remote Desktop connection to your dev box, this guide can help you find and fix the issues quickly. Whether it's frequent disconnections, latency, or sign-in problems, we've got solutions that can get you back on track.
16+
17+
## Prerequisites
18+
19+
Before you begin troubleshooting, ensure you have:
20+
21+
- Access to your dev box.
22+
- Administrative permissions if needed.
23+
- An understanding of your organization's policies related to dev boxes.
24+
25+
## Steps for troubleshooting
26+
27+
Remote Desktop connections are essential for accessing your Dev Box. However, connectivity issues can sometimes arise due to various factors. This guide provides a comprehensive step-by-step approach to troubleshooting common Remote Desktop connection problems, ensuring that your workflow remains uninterrupted.
28+
29+
Before proceeding with troubleshooting, ensure that your Remote Desktop app is updated and both your client computer, and Dev Box have the latest updates installed.
30+
31+
Any improper network configurations on your Dev Box can disrupt Remote Desktop connections.
32+
33+
Additionally, if you haven't accessed your Dev Box for some time, check whether your organization has a policy that removes users from Microsoft Entra ID due to inactivity. To regain access, contact your support team.
34+
35+
### Step 0: Preliminary Checks
36+
1. **Internet Connection:** Verify that your local machine has an active internet connection.
37+
1. **Dev Box Status:** Confirm that your Dev Box is running through the Dev Box portal.
38+
1. **Proxy Settings:** Incorrect internet proxy settings can interfere with the Remote Desktop experience, so ensure these settings are correctly configured.
39+
40+
### Step 1: Windows Update and App Restart
41+
1. **Pending Updates:** If Windows is updating, it can take up to 30 minutes, during which your Dev Box won't connect.
42+
1. **Restart Remote Desktop:** Close all instances of the Remote Desktop app, terminate any 'msrdc.exe' and 'msrdcw.exe' processes via Task Manager, and then to attempt reconnection, reopen the app.
43+
44+
### Step 2: Address App Hang and Authentication Issues
45+
1. **App Hang:** If the Remote Desktop app hangs, capture a process dump of MSRDC.exe and create a support request. Restart your computer and try connecting again.
46+
1. **Authentication Errors:** If denied sign-in despite correct credentials, check the join status using `dsregcmd.exe /status`. Resolve any errors with your support team and restart your computer. If authentication errors persist, unsubscribe and resubscribe to your Dev Box pool in the app.
47+
48+
### Step 3: Browser Client Connection
49+
1. **Browser Access:** Attempt to connect via the browser client by visiting https://DevBox.microsoft.com and selecting "Open in browser".
50+
1. **Black Screen Issue:** If the Remote Desktop Protocol (RDP) window is black, "Shutdown" or "Stop" your Dev Box via the portal and restart it.
51+
52+
### Step 4: Connection Drops During High CPU Load
53+
**Registry Adjustment:** If you experience frequent connection drops with the Remote Desktop app during high CPU load, ensure your Dev Box has the latest Windows 11 build. Set the `SetGpuRealtimePriority` registry value to DWORD 2 in the Dev Box and restart.
54+
55+
```
56+
key: HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations
57+
value name: SetGpuRealtimePriority
58+
value: DWORD 2
59+
```
60+
61+
You can set the `SetGpuRealtimePriority` registry value by using this command in an elevated shell:
62+
63+
```
64+
reg add "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations" /v SetGpuRealtimePriority /d 2 /t REG_DWORD
65+
```
66+
67+
### Step 5: Connection Drops During Low CPU Usage
68+
69+
If you experience frequent connection drops with the Remote Desktop app despite low CPU usage on the Dev Box, switch Remote Desktop to use TCP instead of UDP.
70+
71+
You can configure this setting through a registry edit, or through Group Policy.
72+
73+
#### Use TCP instead of UDP - Registry edit:
74+
Close the Remote Desktop app, apply the following registry setting on your client computer, and try reconnecting.
75+
76+
```
77+
key: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client
78+
value name: fClientDisableUDP
79+
value: DWORD 1
80+
```
81+
82+
You can set the `fClientDisableUDP` registry value by using this command in an elevated shell:
83+
84+
```
85+
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client" /v fClientDisableUDP /d 1 /t REG_DWORD
86+
```
87+
88+
#### Use TCP instead of UDP - Group policy:
89+
Alternatively, use Group Policy Editor on your Dev Box to set RDP transport protocols to "Use only TCP".
90+
91+
1. Open the Group Policy Editor on your Dev Box.
92+
1. Navigate to **Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections**.
93+
1. Open the policy setting **Select RDP transport protocols**.
94+
1. Set it to **Enabled**.
95+
1. For **Select Transport Type**, select **Use only TCP**.
96+
97+
If the preceding steps don't resolve your issue, contact your support team.
98+
99+
Include the following details in your incident report:
100+
101+
- The time the issue occurred
102+
- Impacted users
103+
- A detailed description of the problem
104+
- The Activity ID from your Remote Desktop session, if available. You can find this ID by clicking on the connection bar during your session.
105+
106+
:::image type="content" source="media/how-to-resolve-dev-box-connectivity-issues/troubleshooting-connection-bar.png" alt-text="Screenshot that shows the Remote Desktop connection bar.":::
107+
108+
- Include information from the connection dialog.
109+
110+
:::image type="content" source="media/how-to-resolve-dev-box-connectivity-issues/troubleshooting-connection-information-dialog.png" alt-text="Screenshot that shows the Troubleshooting connection information dialog box.":::
111+
112+
In macOS clients, use the terminal to change connections to TCP instead of UDP:
113+
114+
In the app:
115+
```
116+
defaults write com.microsoft.rdc.macos ClientSettings.EnableAvdUdpSideTransport false
117+
```
118+
119+
In the beta app:
120+
```
121+
defaults write com.microsoft.rdc.osx.beta ClientSettings.EnableAvdUdpSideTransport false
122+
```
123+
124+
125+
## Related content
126+
- [Troubleshoot and resolve dev box Remote Desktop connectivity issues](how-to-troubleshoot-repair-dev-box.md)
127+
- [Get support for Microsoft Dev Box](how-to-get-help.md)
Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,66 @@
1+
---
2+
title: Troubleshoot known Dev Box Remote Desktop issues
3+
description: Learn how to troubleshoot known Remote Desktop connection issues with dev doxes to maintain a stable workflow.
4+
author: RoseHJM
5+
ms.author: rosemalcolm
6+
ms.service: dev-box
7+
ms.topic: troubleshooting-general
8+
ms.date: 10/22/2024
9+
10+
#customer intent: As a developer, I want to troubleshoot my Remote Desktop connection issues with dev boxes so that I can maintain a stable and efficient workflow.
11+
---
12+
13+
# Troubleshoot known Remote Desktop connectivity issues with dev boxes
14+
15+
If you're experiencing problems with your Remote Desktop connection to your dev box, this guide can help you find and fix the issues quickly. Whether it's frequent disconnections, latency, or sign-in problems, we've got solutions that can get you back on track.
16+
17+
## Prerequisites
18+
19+
Before you begin troubleshooting, ensure you have:
20+
21+
- Access to your dev box.
22+
- Administrative permissions if needed.
23+
- An understanding of your organization's policies related to dev boxes.
24+
25+
## Does your Remote Desktop session disconnect frequently?
26+
Organizations can set a policy that disconnects dev boxes after a specified length of time.
27+
28+
## You see a window pop-up with message "You were disconnected from \<dev-box-name\> because your session was locked."
29+
You might see this message if your organization sets a policy to disconnect idle dev boxes after a specified length of time, and has the single-sign on (SSO) feature enabled. Select **Reconnect** to access your dev box again.
30+
31+
## My dev box is stuck at sign-in welcome screen when I try to reconnect after dev box is locked due to being idle.
32+
You might have to close the remote desktop session and connect again.
33+
34+
## Does your Remote Desktop session have a higher network latency and feel laggy?
35+
If you're using a VPN on your client computer or dev box, you might experience network latency. A forced-tunnel VPN, which routes all IP addresses, can increase this latency. Check with your network administrator.
36+
37+
## I can't enable the Windows insider channel in my dev box.
38+
Enabling Windows insider channel in your dev box isn't supported. Upgrading your dev box to a Windows insider build might result in unable to connect to your dev box.
39+
40+
## Windows update is taking a long time to install.
41+
Windows update might take 30 minutes or more to install. If you can't connect to your dev box immediately after Windows update, retry after 15 – 30 minutes.
42+
43+
## I disabled the network connection in my dev box and unable to connect.
44+
If you disabled the network connection in your dev box and are unable to connect, wait for up to 4 hours and retry. Our agent periodically checks and re-enable it every 4 hours.
45+
46+
## Teams calls don't work well in my dev box.
47+
If Teams calls don't work well in your dev box, open the About page in Teams and check that the **AVD Media Optimized** feature is installed. If this feature isn't installed, or if your dev box is running Windows Enterprise N or KN SKUs, contact your dev box administrator.
48+
49+
## I can't connect to my dev box from my client computer.
50+
If CPU profiling doesn't work on an AMD-based dev box, it's a known Windows issue. To fix it, go to **Turn Windows features on or off,** uninstall **Hyper-V** and **Virtual Machine Platform,** and reboot.
51+
52+
## Do an AMD-based dev box support nested virtualization?
53+
AMD-based dev boxes don't support Hyper-V VMs with nested virtualization. After setting `Set-VMProcessor -VMName <name> -ExposeVirtualizationExtensions $true`, VMs inside dev box won't boot. To avoid this issue, use Intel based dev box.
54+
55+
## When I try to sign in to dev box by using Windows Hello for Business based authentication, I get error code 0x8007013d.
56+
When you sign in to dev box via Windows Hello for Business based authentication method and it fails with error code 0x8007013d, it could be due to Windows Hello certificate not properly installed. To fix it, first make sure you remember your password. Run `certutil -DeleteHelloContainer` command on your client computer (not your dev box), sign out and log back in.
57+
58+
## My dev box has display issues.
59+
If you notice display issues like incorrect window scaling, blurry content, or broken screen paint, it might be due to a screen DPI rendering issue. These issues usually happen when using multiple monitors or switching between different physical machines. To fix it, disconnect and reconnect the dev box.
60+
61+
## My Remote Desktop connection is reporting UDP issues.
62+
If UDP port 3478 is blocked in your network (for example, on your home router), your Remote Desktop connection might have problems using UDP. For the best experience, keep UDP port 3478 open.
63+
64+
## Related content
65+
66+
- [Troubleshoot and resolve dev box Remote Desktop connectivity issues](how-to-troubleshoot-repair-dev-box.md)

articles/dev-box/how-to-troubleshoot-repair-dev-box.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,18 @@
11
---
2-
title: Troubleshoot and repair Remote Desktop connectivity issues
2+
title: Resolve connectivity issues with Troubleshoot and Repair
33
description: Having problems connecting to your dev box remotely? Learn how to troubleshoot and resolve connectivity issues to your dev box with developer portal tools.
44
author: RoseHJM
55
ms.author: rosemalcolm
66
ms.service: dev-box
77
ms.topic: troubleshooting
88
ms.date: 01/10/2024
99

10-
#CustomerIntent: As a dev box user, I want to be able to troubleshoot and repair connectivity issues with my dev box so that I don't lose development time.
10+
#CustomerIntent: As a dev box user, I want to be able to automatically troubleshoot and repair connectivity issues with my dev box so that I don't lose development time.
1111
---
1212

13-
# Troubleshoot and resolve dev box Remote Desktop connectivity issues
13+
# Resolve connectivity issues with the Troubleshoot and Repair tool
1414

15-
In this article, you learn how to troubleshoot and resolve Remote Desktop Connectivity (RDC) issues with your dev box. Because RDC issues to your dev box can be time consuming to resolve manually, use the **Troubleshoot & repair** tool in the developer portal to diagnose and repair some common dev box connectivity issues.
15+
In this article, you learn how to troubleshoot and resolve Remote Desktop Connectivity (RDC) issues with your dev box by using the Troubleshoot and Repair tool. Because RDC issues to your dev box can be time consuming to resolve manually, use the **Troubleshoot & repair** tool in the developer portal to diagnose and repair some common dev box connectivity issues.
1616

1717
:::image type="content" source="media/how-to-troubleshoot-repair-dev-box/dev-box-troubleshoot-repair-tool.png" alt-text="Screenshot showing the Troubleshoot and repair tool in the Microsoft developer portal." lightbox="media/how-to-troubleshoot-repair-dev-box/dev-box-troubleshoot-repair-tool.png":::
1818

articles/dev-box/index.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -70,8 +70,10 @@ landingContent:
7070
url: tutorial-configure-multiple-monitors.md
7171
- linkListType: how-to-guide
7272
links:
73+
- text: Use the Troubleshoot and Repair tool
74+
url: how-to-troubleshoot-repair-dev-box.md
7375
- text: Troubleshoot dev box connectivity issues
74-
url: how-to-troubleshoot-repair-dev-box.md
76+
url: how-to-troubleshoot-remote-desktop-connectivity.md
7577

7678
# Card
7779
- title: Provide secure access
6.77 KB
Loading
Loading

articles/dev-box/toc.yml

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -123,8 +123,15 @@ items:
123123
href: how-to-skip-delay-stop.md
124124
- name: Troubleshooting
125125
items:
126-
- name: Troubleshoot dev box connectivity issues
126+
- name: Automatically repair connectivity issues
127+
displayName: Troubleshoot & repair, troubleshooter, fix, wizard
127128
href: how-to-troubleshoot-repair-dev-box.md
129+
- name: Troubleshoot dev box connectivity issues
130+
displayName: Troubleshoot & repair, troubleshooter, fix
131+
href: how-to-troubleshoot-remote-desktop-connectivity.md
132+
- name: Resolve dev box connectivity issues
133+
displayName: Troubleshoot & repair, troubleshooter, fix
134+
href: how-to-resolve-dev-box-connectivity-issues.md
128135
- name: Troubleshoot Task view issues
129136
href: how-to-troubleshoot-dev-box-task-view.md
130137
- name: Get support for Microsoft Dev Box

0 commit comments

Comments
 (0)