Forum Discussion
Windows Server 2022 App Compatibility FOD breaks Remote Desktop
- Feb 09, 2022
This is now fixed in OS Build 20348.524 (https://support.microsoft.com/en-gb/topic/february-8-2022-kb5010354-os-build-20348-524-c5355158-0f4d-4106-90f7-0a5a6c7376b9), available from Windows Update since February 8, 2022.
I will also try and raise this via my MS account team at work...
- JOHNPILLAROct 05, 2021Copper Contributor
I've been told by MS to log it in the feedback hub on a win10 or win 11 machine. I've done that so would be good for people to up vote.
- mauricewalkerOct 07, 2021Brass Contributor
Hey JOHNPILLAR, I just installed Feedback Hub to upvote the issue. But this seems to be just a steaming pile of rants about Facebook being broken and other nonsense. I was unable to locate your bug report. Could you post a link (if that's a possibility with Feedback Hub) or some keywords? I tried the obvious ones.
- JOHNPILLAROct 08, 2021Copper ContributorLink to bug report: https://aka.ms/AAe0l37
Title: Windows Server 2022 - App Compatibility FOD breaks Remote Desktop (RDP)
I used your well explained steps to re-produce, hope that was ok.
- mauricewalkerOct 06, 2021Brass Contributor
I just noticed that the Devices Tool in Windows Admin Center shows a "Critical" device while trying to establish an RDP connection:
SWD\REMOTEDISPLAYENUM\RDPIDD_INDIRECTDISPLAY&SESSIONID_0002
The drivers for this device are not installed. (Code 28)- JOHNPILLAROct 07, 2021Copper ContributorHi,
I do not have any unknown devices when attempting to connect via RDP. It passes auth but then there is something not being invoked. I suspect it's graphics driver related, but not sure why FOD would alter that! I've done everything from re-install graphics drivers, to reverting to the windows basic driver to disable Bitmap Caching, RemoteFX etc. Still no joy 😞