HI lelumpolelum-3314 and Tjatte1336,
There are many different reason cause for this problem.
There are some suggestions for IT friends:
If you want to do any change for your registry, please full backup your registry of problematical server first.
1.Some issues are related device0 registry key missing.
Please check below registry key is existed on problematical server.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RDPUDD\Device0
"InstalledDisplayDrivers"=RDPUDD or other value hex(7):52,00,44,00,50,00,55,00,44,00,44,00,00,00,00,00
"VgaCompatible"=dword:00000000
"Device Description"="RDPUDD Chained DD"
additionally, in some cases the above registry location not corrupted then check the following : Check if value exist under HKLM\System\CurrentControlSet\Control\Terminal Server\VIDEO\RDPUDD\Device\Video0 (we can compare with working server, and non-working server)
2.Some issues be resolved by deleting the HKLM\System\CurrentControlSet\Enum\TERMINPUT_BUS\UMB\ key on problematical server.
3.Reduce rediected devices to problematical RD session host server then check result
4.Reduce firewall rules then check result
Windows Servr 2016 RDSH - Firewall rules created at every login
https://social.technet.microsoft.com/Forums/en-US/992e86c8-2bee-4951-9461-e3d7710288e9/windows-servr-2016-rdsh-firewall-rules-created-at-every-login?forum=winserverTS
5.Check if the issue happen on new created domain user (or test domain user)?
if the issue also happen on new created domain user (or test domain user), we can don't use UPD or roaming profile or Fslogix for the new domain user account (or test domain user). then monitor some time and check the result.
6.We can build a new test collection and add the same OS clean installed RDsession host server in it, logon both normal RDSH server and problematical RDSH server by using local admin account in console session, then run procmon on both normal RDSH server and problematical RDSH server respectively in local admin console session, and waiting issue the same issue user account to remote logon normal RDSH server and problematical RDSH server respectively.
then capture both normal procmon log and problematical procmon log then save all events.
Finally, we can compare both normal procmon log and problematical procmon log.
Process Monitor v3.70
https://learn.microsoft.com/en-us/sysinternals/downloads/procmon

7.Since There are many different reason causes for this problem and we need to analyze much more logs. Please open a ticket to Microsoft support. In forum, doing troubleshoot for this kind of issue is more difficulty. Thanks for your understanding.
For more information about our Premier support, please see below link:
https://www.microsoft.com/en-us/microsoftservices/support.aspx
https://hubstaticsite.z5.web.core.windows.net/
============================================
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.