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
description: How to resolve common Azure Virtual Desktop Agent and connectivity issues.
4
4
author: sefriend
5
5
ms.topic: troubleshooting
6
-
ms.date: 05/26/2022
6
+
ms.date: 02/18/2023
7
7
ms.author: sefriend
8
8
manager: clarkn
9
9
---
@@ -371,6 +371,24 @@ By reinstalling the most updated version of the agent and boot loader, the side-
371
371
> [!div class="mx-imgBorder"]
372
372
> 
373
373
374
+
## Remove DisableRegistryTools
375
+
376
+
If you've performed all four steps but the agent still doesn't work, that may be because the DisableRegistryTools registry key is enabled in one of the following locations:
This registry key prevents the agent from installing the side-by-side stack, which results in an installMSIException error. This error leads to the session hosts being stuck in an unavailable state.
383
+
384
+
To resolve this issue, you'll need to remove the key:
385
+
386
+
1. Remove the DisableRegistryTools key from the three previously listed locations.
387
+
1. Uninstall and remove the affected side-by-side stack installation from the **Apps & Features** folder.
388
+
1. Remove the affected side-by-side stack's registry keys.
389
+
1. Restart your VM.
390
+
1. Start the agent and let it auto-install the side-by-side stack.
391
+
374
392
## Next steps
375
393
376
394
If the issue continues, create a support case and include detailed information about the problem you're having and any actions you've taken to try to resolve it. The following list includes other resources you can use to troubleshoot issues in your Azure Virtual Desktop deployment.
0 commit comments