Zakaria Acharki is an analyst developer from Tangier, Morocco who joined Experts Exchange as a certified professional in November of 2018. He started his career early and was unafraid of a busy schedule. His experience in the field has taught him some important lessons, mainly to give the kind of help and advice you hope to receive in return.
An easy and light-hearted read about some experiences of John Hurst - a Microsoft certified Most Valuable Professional - about working alone. Give it a read and share your own experiences in the comments section of the article.
RDP Bug in Win10 v1903 - disconnecting RDP sessions WITHOUT LOGGING OFF causes one CPU core to spike https://www.reddit.com/r/Windows10/comments/c0agnb/1903_dwmexe_goes_to_100_cpu_on_remote_host_after/
As a workaround on all of my affected machines I have used Group Policy Editor to set
Local Computer Policy - Computer Configuration - Administrative Templates - Windows Components - Remote Desktop Service - Remote Desktop Session Host - Remote Session Environment
-> Use WDDM graphics display driver for Remote Desktop Connections to DISABLED
This forces RDP to use the old (and now deprecated XDDM drivers)
After rebooting, behaviour returns to normal and after disconnecting from an RDP session the RDP host (target machine) no longer shows DWM.EXE consuming CPU.
To my knowledge, this problem is not yet confirmed by Microsoft, although anyone can reproduce it on any hardware and any VM.