Windows 10: DWM.EXE High CPU (One Core) On Target System after Remote Desktop Disconnect on Windows 10...

Two systems,

• Intel NUC with Iris Plus Graphics 655 running latest drivers 26.20.100.6890
• the other with Intel HD Graphics 2500 running latest drivers 5.33.48.5069

On completion of a remote desktop session, the target system shows high CPU utilisation (one core running at 100%) for DWM.EXE - the newer machine (Intel Iris Plus 655) will eventually crash several hours later - I suspect a memory leak such as the previous one affecting QuickSync.



If I change the drivers to "Microsoft Basic Display Adapter" then things return to normal re: DWM.EXE. It's not a long term fix as one of the machines is my Media Centre PC and I lose audio output on it, the other is a headless Plex server and I lose "Quick Sync" hardware transcoding.



Anyone else seeing this ? If so after a bit of digging I've identified a short term workaround.


I believe there is a problem with the Microsoft RDP code in 1903 (an area which seems to have had a major internal overhaul), and I document a successful workaround.



For clarity,

• the behavior started with 1903
• one system is an Intel NUC NUC8I7BEH PC with 16Gb Corsair Vengeance Memory and an Intel 760p 256Gb SSD; the other is a Chillblast Fusion Vacuum PC based on a P8H77-M motherboard. However other machines with nVidia GPU's are also affected, so this is NOT an Intel problem.
• my testing consists of using a third machine running Windows 10 x64 1903 (fully patched) to run the Remote Desktop client software. The "targets" I refer to are the two machines I mention acting as RDP Host machines. Both demonstrate the high CPU DWM.EXE after taking them over and then disconnecting (the NUC has an 8 core CPU so shows 12.5% CPU) and the other machine based on an Intel P8H77-M motherboard.

It seems Microsoft has done significant engineering to Remote Desktop in Windows 10 1903 and I now believe a significant bug exists in the Microsoft code.

• https://answers.microsoft.com/en-us...een-with/23c8a740-0c79-4042-851e-9d98d0efb539

• https://www.groovypost.com/unplugge...d-and-deprecated-features-on-windows-10-1903/

In the first article a Microsoft employee mentions



<--------------------->

There’s a known issue with some of the old display drivers. <I believe the issue I am facing is related to this area>



Display drivers report some of their capabilities upon load. In previous Windows versions this reported data wasn’t used or verified. Because of that, some of the old versions of the legacy display driver may report invalid data and it would be ignored. Starting with Windows 10 1903 RDP uses this data to initialize the session.



The best option is to install an updated display driver from the hardware manufacturer. If the new version is not available, you can workaround this by disabling the problematic driver in the device manager.



Our team has identified the issue and we are currently verifying the fix that will dynamically switch to the software renderer if the problematic driver is detected.



I will this thread when the fix will be included to the Windows Insider release.

<---------------------->



Further testing in my environment has shown that machines without Intel integrated graphics are also showing the problem.



In the second article it mentions a change to the RDP driver area



<--------------------->

XDDM-based remote display driver: Starting with this release the Remote Desktop Services uses a Windows Display Driver Model (WDDM) based Indirect Display Driver (IDD) for a single session remote desktop. The support for Windows 2000 Display Driver Model (XDDM) based remote display drivers will be removed in a future release. Independent Software Vendors that use XDDM-based remote display driver should plan a migration to the WDDM driver model. For more information on implementing remote indirect display driver ISVs can reach out to *** Email address is removed for privacy ***.

<--------------------->



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.



This isn't a long term fix (to rely on a deprecated feature). I also don't understand why only a limited number of users are affected, but for now, I'm up and running again, and hoping for a Microsoft fix.

:)

 

DWM.EXE High CPU (One Core) On Target System after Remote Desktop Disconnect on Windows 10 x64 1903 (Fully Patched)

Two systems,

• Intel NUC with Iris Plus Graphics 655 running latest drivers 26.20.100.6890
• the other with Intel HD Graphics 2500 running latest drivers 5.33.48.5069

On completion of a remote desktop session, the target system shows high CPU utilisation (one core running at 100%) for DWM.EXE - the newer machine (Intel Iris Plus 655) will eventually crash several hours
later - I suspect a memory leak such as the previous one affecting QuickSync.



If I change the drivers to "Microsoft Basic Display Adapter" then things return to normal re: DWM.EXE. It's not a long term fix as one of the machines is my Media Centre PC and I lose audio output on
it, the other is a headless Plex server and I lose "Quick Sync" hardware transcoding.



Anyone else seeing this ? If so after a bit of digging I've identified a short term workaround.

I believe there is a problem with the Microsoft RDP code in 1903 (an area which seems to have had a major internal overhaul), and I document a successful workaround.



For clarity,

• the behavior started with 1903
• one system is an Intel NUC NUC8I7BEH PC with 16Gb Corsair Vengeance Memory and an Intel 760p 256Gb SSD; the other is a Chillblast Fusion Vacuum PC based on a P8H77-M motherboard. However other machines with nVidia GPU's are also affected, so this
  is NOT an Intel problem.
• my testing consists of using a third machine running Windows 10 x64 1903 (fully patched) to run the Remote Desktop client software. The "targets" I refer to are the two machines I mention acting as RDP Host machines. Both demonstrate the high CPU
  DWM.EXE after taking them over and then disconnecting (the NUC has an 8 core CPU so shows 12.5% CPU) and the other machine based on an Intel P8H77-M motherboard.

It seems Microsoft has done significant engineering to Remote Desktop in Windows 10 1903 and I now believe a significant bug exists in the Microsoft code.

• Windows 10 1903 (May update) black screen with Remote Desktop

• https://www.groovypost.com/unplugge...d-and-deprecated-features-on-windows-10-1903/

In the first article a Microsoft employee mentions



<--------------------->

There’s a known issue with some of the old display drivers. <I believe the issue I am facing is related to this area>



Display drivers report some of their capabilities upon load. In previous Windows versions this reported data wasn’t used or verified. Because of that, some of the old versions of the legacy display
driver may report invalid data and it would be ignored. Starting with Windows 10 1903 RDP uses this data to initialize the session.



The best option is to install an updated display driver from the hardware manufacturer. If the new version is not available, you can workaround this by disabling the problematic driver in the device
manager.



Our team has identified the issue and we are currently verifying the fix that will dynamically switch to the software renderer if the problematic driver is detected.



I will this thread when the fix will be included to the Windows Insider release.

<---------------------->



Further testing in my environment has shown that machines without Intel integrated graphics are also showing the problem.



In the second article it mentions a change to the RDP driver area



<--------------------->

XDDM-based remote display driver: Starting with this release the Remote Desktop Services uses a Windows Display Driver Model (WDDM) based Indirect Display Driver (IDD) for a single session remote
desktop. The support for Windows 2000 Display Driver Model (XDDM) based remote display drivers will be removed in a future release. Independent Software Vendors that use XDDM-based remote display driver should plan a migration to the WDDM driver model. For
more information on implementing remote indirect display driver ISVs can reach out to L: *** Email address is removed for privacy ***.

<--------------------->



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.



This isn't a long term fix (to rely on a deprecated feature). I also don't understand why only a limited number of users are affected, but for now, I'm up and running again, and hoping for a Microsoft
fix.

 

kill dwm.exe windows 10 pro 64bit


I found this link

What is dwm.exe and why is it using so much memory?

With this note: "The steps below only work for Windows Vista and Windows 7. Desktop Windows Manager is not displayed in the Services window on Windows 8 and Windows 10, and therefore cannot be turned off or disabled."

These links have suggestions for improving performance:

dwm.exe Desktop Window Manager High CPU on Windows 10 [Solved] - Driver Easy
Fix: Dwm.exe issues in Windows 10
I would start here:

 

Windows 10 - Remote Desktop

Hi,

We will surely assist you with the issue you are facing with Windows 10.
- Which version of Windows 10 Operating System are you using?

- Were you able to upgrade to Windows 10 successfully?

I suggest you to refer the below steps and see if this helps.

• 
  Enable remote desktop in settings
  
  • Control Panel\System and Security\System, Click "Remote Settings" on the left side
• 
  Verify my port forwarding settings were properly forwarding to my computers local IP address
  
  • run "cmd.exe" and then type "ipconfig". Find your IP from that list

[*]

• Make sure your firewall settings are open
• Go to "Control Panel\System and Security\Windows Firewall\Allowed apps"

• On the left, click "Allow an app or feature through Windows Firewall"
• Click "Change Settings"
• Find "Remote Desktop" in the list and make sure both "Private" and "Public" is checked.

Let us know if this helps.

Thank you.

Credits to : Jace_Sango.