I know this has been talked about and that it is said in the next version there will be the facility to tell ewido to not bother about vnc, but it is a showstopping problem for me. When the pc reboots, ewido comes up asking about winvnc and you can choose to clean or ignore. Fine. But if you are not at that pc and are trying to vnc in, you can connect remotely with the vncviewer, but cant get to the desktop or get any ui screen remotely because it seems ewido is holding up the process of winvnc 'working' until the user local to the pc takes some action (clean or none)... This would seem to be a showstopper, in that if you remotely reboot a pc with active ewido guard protection, you cant get back into it remotely until you locally tell ewido what to do with winvnc after it comes back up. Any ideas Ewido? Great product, but its tough to wait for some fix for this while it renders remote access useless... Thanks, Mark.