On our farm of Windows Server 2016 RDSH (Remote Desktop Session Host) I've had seemingly random issues with the start menu stopping working. This likely correlates with a Windows update being applied, but it's hard to tell as you do not always know immediately that it's stopped working (users complain days later or never complain and you notice when doing other maintenance, etc).
Searching the internet you find a number of solutions, but the most crazy (in my opinion) solution I found was the one that actually worked!
In this post user MrManual says to delete and recreate a registry key dealing with the Firewall. One, like me, would think this crazy and continue on trying all the other solutions only to have the issue remain (or return shortly).
Finally, figuring it's best to try a crazy solution than rebuild the server I open powershell and give it a go:
Remove-Item "HKLM:\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\RestrictedServices\Configurable\System"
New-Item "HKLM:\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\RestrictedServices\Configurable\System"
Click start menu and GASP it opens!
Note: other ideas on the thread do work, but seemingly only temporary. I still suspect this to have something to do with the crappy UPD's.
On the note of UPD's one might ask "if you hate UPD's so much why not switch to fxlogic? I mean, it is free afterall..."
https://blogs.microsoft.com/blog/2018/11/19/microsoft-acquires-fslogix-to-enhance-the-office-365-virtualization-experience/
https://www.brianmadden.com/opinion/Microsoft-FSLogix-free-to-all-customers
Subscribe to:
Post Comments (Atom)
Thank you. been driving me crazy.
ReplyDelete