As you can check with procmon (http://live.sysinternals.com/procmon.exe)
TightVNC service is constantly flooding the OS with Registry and File access requests, hundreds by seconds.
(even when no session opened !)
This is not Hyper-V friendly, as a Hyper-V Windows is supposed to dedicate all resources to its VMs.
Could we expect that TightVNC do nothing, when it really is doing nothing ??
Log in to post a comment.