Windows 10: 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

 

Close remote desktop session and launch an executable


Having a Windows 10 Enteriprise 2016 LTSB installed on an industrial PC for a totem with a touch screen.

This PC run a client application, for simple operations I need sometimes to access the PC with Remote Desktop from a remote location.

Finished my activity if I simply exit from Remote Desktop the PC will show a login screen to the users, obviously not what wanted

Using a .bat script with
Code:

Code:

tscon.exe 1 /dest:console

as administrator I'm able to leave the session and the PC didn't show the login screen, but shows the desktop, again not what I wanted.

Adding this command before the other
Code:

Code:

start "" "C:\Users\User\Desktop\BikeCube\BikeCube.exe"

it launch the client but didn't close the session.

There is a way to close the session and immediately launch the client, or the opposite.
The final status need to be the the touch screen with the client app opened.