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.
Season Greetings and A Prosperous New Year for 2021 - and a Big Thank You from Andy!
In what has become an annual Andy EE Tradition, Many Thanks to all the VMware and Virtualisation Questions I've answered this year and for making EE what it is, an Excellent Community of Technical Folk from around the World.
We all live in very trying times, with COVID-19 this year, and I hope you and your families are safe, and hopefully, with vaccines which have now been developed it will not be soon, and the World can return to normal without the fear of COVID-19, and hopefully this time next yeat COIVID-19 will be a thing of the past.
I've analysed the data, and here is a thank you.
Here's a pie-chart
Some familiar names, and I hope your VMware and Virtualisation issues are solved, I've included the Anonymous users as well!
Merry Christmas and Hope to see you in the New Year.
PSEXEC vulnerability! Must-read for admins who use it. Please note that you might not be aware that you use it since it is incorporated into some software products that interact with remote systems, so read it anyway!
0patch has issued a patch, Microsoft has not (yet). Only patches psexec v2.2!
Update: Microsoft released a new patched version. To use it against machines that you used the old version against, you need to launch this command 1st, or it will fail:
net stop psexecsvc & sc remove psexecsvc