Skip to content

Commit b2b569f

Browse files
Merge pull request #227698 from Heidilohr/work-agent-registry
Adding info about removing registry keys
2 parents 7f5f57b + 6480ad1 commit b2b569f

File tree

1 file changed

+19
-1
lines changed

1 file changed

+19
-1
lines changed

articles/virtual-desktop/troubleshoot-agent.md

Lines changed: 19 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Troubleshoot Azure Virtual Desktop Agent Issues - Azure
33
description: How to resolve common Azure Virtual Desktop Agent and connectivity issues.
44
author: sefriend
55
ms.topic: troubleshooting
6-
ms.date: 05/26/2022
6+
ms.date: 02/18/2023
77
ms.author: sefriend
88
manager: clarkn
99
---
@@ -371,6 +371,24 @@ By reinstalling the most updated version of the agent and boot loader, the side-
371371
> [!div class="mx-imgBorder"]
372372
> ![Screenshot of available session host](media/hostpool-portal.png)
373373
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:
377+
378+
- HKU:\DEFAULT\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\DisableRegistryTools = 1
379+
- HKU:\S-1-5-18\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\DisableRegistryTools = 1
380+
- HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\DisableRegistryTools = 1
381+
382+
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+
374392
## Next steps
375393

376394
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

Comments
 (0)