UltraVNC

FYI, I bypassed this issue by disabling the uvnc_service (starts winvnc.exe as a service) and creating a scheduled task to start winvnc.exe at logon as the logged on user.

When a UVNC 1.2.1.2 client (Windows 10) connects to a UVNC 1.2.1.2 server (Windows XP), a memory leak is started on the server. Disconnecting the client stops the memory leak. Killing the winvnc process (running as SYSTEM), restarting winvnc as the logged on user, and then reconnecting the client ...