Windows 10: After exiting a remote desktop session, cpu load goes up dwm.exe until next login REVISITED

For the record, the original post https://answers.microsoft.com/en-us...da0-9a64-4a14-a671-b7cb1b61f66e?auth=1&page=1 which has become a cult classic and is referred to by many is now locked.


I'm forced to ask though: Has regression testing failed? Has the fix that worked for a while KB4522355 been lost? I'm at Windows 10 1909 now


To me and my experience, the problem is back. After having the exact problems listed in the original thread, after temporarily using the workaround, and after later, when it came out applying KB4522355, the problem went away for the longest time.


But a few windows updates later, including from 1903 to 1909, it's baaaaaack, at least the freeze of the remote computer part. In my case the computer is hard-frozen, so I can't confirm that dwm was to blame.


Anyone else?

:)

 

After exiting a remote desktop session, cpu load goes up (dwm.exe) until next login

When I access another Windows 10 PC via remote desktop and then exit the remote desktop session, the CPU load goes up. It is DWM.EXE that causes it.

What I did to exclude other causes:

- scanned for viruses (yes, DWM.EXE is the original one from MS)

- made sure no magnifier was active (Google proposed this)

- made sure no screen saver is active and nothing else is on my lock screen

- made sure the gfx driver (Intel integrated) is up to date

dism /online /cleanup-image /checkhealth

dism /online /cleanup-image /scanhealth

sfc /scannow

chkdsk c: /f

do not show any problems.

Today I tried a second system as RDP target: Same problem! Could this be a bug? Can anyone else please try it, too? I don't know since when the problem occurs. Could be since 1903 (this is the version I use on both systems).

This is how it looks when I log the CPU loads:

 

dwm failure on rdp session in win 10

When logged in to a Win 10 pro system remotely from a Win 7 pro system, two instances of the dwm process are created. Only one appears when logged into the same system locally.

One of the two processes in the rdp session seems to be dormant, accumulating no cpu usage. However, the second dwm process seems to have an event processing thread in the dwmcore DLL that is hung in a tight loop, thus consuming a core of a multicore processor.

dwm version is 10.0.10240.16384...interesting versioning!

 

Remote Desktop - Screen resolution in remote session

I have connected to a remote desktop session and the windows in the remote session are all too small for me to see.

I have edited the remote desktop connection settings and cannot seem to make anything larger.

I am using a new Dell Inspiron Laptop which has a very high screen resolution 3840 x 2160

Any suggestions appreciated

Thank you