UltraVNC

Problem Statement: we have encountered a problem when disabling/enabling input (keyboard/mouse) when an operator takes control of a user’s system. Today we have incorporated this into our existing application and when the operator connects (takes control) we successfully disable input however when w ...

This is FANTASTIC news - can you clarify a few things: - Does it have any dependencies on the version of Windows10? My deployment is still 1603 (old) and not at 1903 or the latest 21H2; is this something Microsoft re-introduced support for in a later version (which won't help me) or something that ...

Not being an expert in the area myself I've taken a quick look and not sure I fully understand what you mean - I've asked one of my partners to see if this clarifies a possible area of confusion - in parrallel I wanted to ask if you had an example to illustrate how the hooks could be different?

While the approach of the UVncVirtualDisplay64 solved a great many problems it requires a later version of Windows10 then most of our applications run on - meaning we have a sizable deployment on Win10 1603 which does not support the virtual display (1903 and above) - which means we are back to the ...

We continue to struggle with this item and it has caused many issues where users are pressing on the screen (when it goes blank) thinking something s broken but really someone has simply taken remote control - and seeing as there is no way to SHOW a screen to the user (like DO NOT TOUCH) this has ...

That actually seems to have worked - we are going to validate if this is a solution we can move forward with but there is a lot of risk in hat complete package replacement (as we have lots of custom code over the past decade in VNC Server/Client which is at risk with he approach of taking the .EXE ...

We attempted to rename/remove schook.dll and it did not change the touchscreen issue - so we did a bit of trial and error ... - If we use 1.3.4 as-is your fix seems to work (mouse, keyboard, AND TOUCH are disabled) - but if we take 1.2.1 and drop only VNCHook.dll (as recommended) we see the issue ...

Our VNC Server configuration looks a bit different from yours - but here are the properties in the ultravnc.ini and it looks as if EnableHook (towards the bottom) is set to 1; if this was failing would there be a log/trace evidence we could check? Could it maybe be a side effect of the version we ...

We've attempted to simply drop-and-replace the VNCHook.dll with the one you recommended and it did not resolve the issue - we can still clearly see that TOUCH is enabled and responsive when the screen is black. Could there be some configuration or options we need to set to disable touch for example ...

Subsequently - doing some research about the Virtual Display you mentioned - can it be persistent (always there) so we can move windows/applications to it at boot of operating system (Windows10) and VNC to it when needed or does it only get create upon connect of the VNC Client (and each time we ...

This response is very interesting and promising - and it may resolve much of my concerns if I am understanding it correctly. In Windows XP/7 we used a VirtualDisplay Adapter (3rd party SW) which created a 2nd display (virtual) and we would VNC to that screen (worked like a charm for decades ...

This is fantastic news - we are for sure using a much older version (and mixed) - does this fix require us to upgrade both the CLIENT and SERVER or could we simply upgrade one of them to the latest (1.3.3)? Obviously best to upgrade both to be consistent (know that) but we added custom-code to the ...

I was reviewing UltraVNC and before Windows 7/10 you could (when you take control) bring up a screen - something like a PLEASE WAIT MAINTENANCE IN PROGRESS with a picture (or something - does not need to be fancy) - but it seems to have been tied to functionality which no longer works for Windows10 ...

The goal is to disable user INPUT on the SERVER SIDE when someone has connected remotely ... - works great to disable keyboard/mouse - works great to disable the screen (goes blank) But for some strange reason if the screen is a TOUCH SCREEN enabled device (which most of our kiosks are) even if the ...