PROCEDURE The following information may help resolve a challenge with RDS servers where the start menu random stops working. It has been found that registry bloat can exist with two areas in the registry with the FirewallRules key. The process is to delete the key (to delete the rules within) and then recreate it. This should have an instant effect. To be safe, it is generally best to have all users signed out before hand. See this link: https://docs.microsoft.com/en-us/answers/questions/204147/windows-server-2019-rds-start-amp-search-does-not.html and this link https://social.technet.microsoft.com/Forums/ie/en-US/c212e6d7-160d-4a54-bfc6-92bd720fc424/windows-2016-rds-start-menu-not-working-getappxpackage-returns-nothing?forum=winserverTS .
REQUIREMENTS
Review the link above.
STEPS
- Sign out all users on the SH servers you wish to fix. It would be good practice to then block sign in’s on said servers via the connection broker server.
- Open Powershell as an administrator and run the following commands verbatim including all ” symbols in the order listed.
Remove-Item “HKLM:\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\FirewallRules”
New-Item “HKLM:\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\FirewallRules”
Remove-Item “HKLM:\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\RestrictedServices\AppIso\FirewallRules”
New-Item “HKLM:\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\RestrictedServices\AppIso\FirewallRules”
The last step is to sign back in yourself and verify the issue is resolved. If so you can then set the servers in the connection broker to allow for logins.
REFERENCES