![]() Note: Some articles also claim KB452941 will solve various display issues related to the XDDM vs WDDM driver as well but it did not in my case. ![]() Note that the machine must be restarted for this change to take effect. Reg add “HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services” /v “fEnableWddmDriver” /t REG_DWORD /d 0 /f Graphics display driver for Remote Desktop Connections] toĪlternatively, to use the modify the registry method, open the command prompt with administrator privileges and type Session Host->Remote Session Enviroment], set the Policy [Use WDDM I can also use mstsc /multimon as a command line to use multiple monitors. To get a list of monitors, I can run mstsc /l to LIST out all my monitors on my machine. Templates->Windows Components->Remote Desktop Services->Remote Desktop use multimon:i:1 selectedmonitors:s:0,1 I can put on selectedmonitors:s:x,y and then use the zero-based numbers to indicate my monitors. In [Local Group Policy Editor->Local Computer Policy->Administrative See here for instructions on how to implement: Remote Desktop black screen Using GPO or registry modification to eliminate the forced use of WDDM also resolved the intersession windowing issue (amongst other things), without needing a rollback. Since the rollback to 1809 resolved the issue with the first host I investigated further as to what was changed from 1809 to 1909 to try and find the root cause, and the issue seems to be the deprecation of the XDDM display driver and the forced use of WDDM. I also had a second host that I also discovered had the same issue that too was upgraded from 1809 to 1909 but this host was past the 10 day rollback window. The first solution I came up with is to do a rollback to 1809. Now it is like starting from scratch each time I connect via RDP even if there isn’t a local session between RDP sessions. I have a 12 monitor local computer and rdp into a host computer with only 1 monitor with the use all local monitor option and I was, prior to updating from 1809 I was able to use all 12 local monitors and it would remember the window locations between sessions prior to the latest windows update. but also the more recently released 1909) because I had the same exact issue that was resolved by rollback to 1809. I think this is a bug courtesy of the latest windows updates (1903 as is listed in the tags in the original post.
0 Comments
Leave a Reply. |