Forum Discussion
mauricewalker
Oct 01, 2021Brass Contributor
Windows Server 2022 App Compatibility FOD breaks Remote Desktop
When installing the App Compatibility FOD on Windows Server 2022, Remote Desktop connections to the server seem to be no longer possible. I think this is a bug, but haven't found any other reports. Can someone confirm?
How to reproduce:
- Install Windows Server 2022 Standard Core (physical and virtual installs are equally affected).
- In SConfig, enable Remote Desktop.
- Connect to the server via Remote Desktop using the default 'Administrator' account. Works fine.
- Install the App Compatibility FOD and reboot:
Add-WindowsCapability -Online -Name ServerCore.AppCompatibility~~~~0.0.1.0
Restart-Computer
- Try establishing a Remote Desktop connection again. Doesn't work. You either get a blank screen or get disconnected immediately.
- Install all applicable Windows Updates and try again. No change.
- Remove the App Compatibility FOD and reboot:
Remove-WindowsCapability -Online -Name ServerCore.AppCompatibility~~~~0.0.1.0
Restart-Computer​
- Try again. Remote Desktop functionality is now restored.
This did work fine in Server 2019.
This is now fixed in OS Build 20348.524 (KB5010354), available from Windows Update since February 8, 2022.
- mauricewalkerBrass Contributor
This is now fixed in OS Build 20348.524 (KB5010354), available from Windows Update since February 8, 2022.
- dmutsaersIron ContributorKB5008353: Releasing Windows 11 Build 22000.466 to Beta and Release Preview Channels
"We fixed an issue that causes a remote desktop protocol (RDP) session to disconnect or the screen to be blank for Server Core. This issue occurs when you install the AppCompat feature."
Let's hope this fix will be publicly available for Windows Server 2022 soon.
https://blogs.windows.com/windows-insider/2022/01/14/releasing-windows-11-build-22000-466-to-beta-and-release-preview-channels/- Obi_YoannCopper Contributor
Issue is now fixed with the CU released yesterday, KB5009608, build 20348.502.
I have tested it on 3 vms, all of which are WS2022 core based, with app compat FOD.
I can connect to them fine with RDP! 🙂Addresses an issue that causes a remote desktop protocol (RDP) session to disconnect or the screen to be blank for Server Core. This issue occurs when you install the AppCompat feature.
- mauricewalkerBrass ContributorGreat to hear! How did you install the update? Can't see it in Windows Update using WAC.
- ticktokCopper ContributorAt last Microsoft have acknowledged the problem and promised a fix in a 'future' cumulative update.
Let's hope the 'future' is measured in weeks or months and not years.- mauricewalkerBrass ContributorThanks ticktok for letting us know. Can you provide a link to Microsoft's statement?
- NikwonkCopper Contributor
mauricewalker I've the same issue.
- JR_TayschrennBrass Contributor
mauricewalker l'd like to add as well how horrible of a choice it was to force us to use a Feedback Hub app for bug reporting. Come on Microsoft.
- sysadminRigaCopper Contributorsame. rdp not working.
but in version with no graph interface it works.- polaticusCopper Contributor
sysadminRiga yes, same situation. I have hybrid ambients, some with Desktop Experience, some with Server Core. With Desktop, no problems, RDP works fine...but with AppCompatibility, RDP crashs
- JOHNPILLARCopper ContributorsysadminRiga thanks and interesting. Can you share install params/changes to any settings etc.
Thanks
- polaticusCopper ContributorI have the same problem without a server core. Any news?
- DruidiusCopper Contributor
I have the same issue and didn't find any solution yet
- JOHNPILLARCopper Contributor
Same here.
Using windows admin center to remote manage but sometimes you still need RDP.
- mauricewalkerBrass ContributorThanks for confirming. Hard to believe no-one at Microsoft noticed this. Without RDP, the App Compatibility FOD is pretty much useless, isn't it?
WAC is also my preferred management tool, but it's still missing some Hyper-V features (like attaching physical disks to a VM). So I would like to use the Hyper-V Manager (virtmgmt.msc) via RDP.
What's the best way to escalate this?