I saw a previous post on this topic that was started in december, but when someone added to it today, poster was told to start a new topic. This is happening on my machine windows 7 64bit. Tried the “emergency update”, uninstalled, reinstalled, but every time an avast window pop ups, I lose mouse and keyboard inputs. Also uninstalled reinstalled uvnc, tried 32bit and 64bit versions, went back to older versions of uvnc, still same behavior. Cannot send ctrl/alt/del with the Avast window open.
If I open the chat window and press the send key about 10 to 20 times, i get one shot to close avast window, but as soon as another Avast pop up window opens, same thing happens, lose mouse and keyboard control. It looks like this has been an issue since back in November. Does anyone have a fix, besides disabling Avast (not really a fix).
And what is up with these verification images, have to reset that 5 to 10 times before it can be read?
Sounds like you have a case of the Avast blocking stuff! I had to completely uninstall my paid version of Avast so I could actually use software on my computer. Not even disabling the shields helped, a complete disable/uninstall was the only fix.
Avast isn’t listening, and obviously doesn’t care. It’s the bigger player in this matter of incompatibilities. UltraVNC doesn’t care, or is helpless to remedy this.
“What we have here is a failure to communicate!”
Can anyone tell us if Windows 10 Remote Desktop remains free of this problem that so severely affects UltraVNC?
We haven’t been able to reproduce the described issue, sorry.
For any report, please pack the main executable of the blocked tool (if unsure, the whole folder) and upload it somewhere - so that we can check how Avast classifies it. However, I’m afraid we haven’t found any problem so far.
Remote Desktop certainly isn’t affected by self-defense, it works differently (if you have Avast firewall, you may have to allow RD connections first though.)
I have this problem also. I use Splashtop Business to remote into about 75 computers. These pc’s have a variety of Window’s OS’s.
If I try to disable Avast shields by right clicking on the Avast icon in the taskbar, I get the pop-up menu, then I can’t do anything with the mouse or keyboard. The way out is to use the Splashtop interface on my end to send control-alt-delete and then log off or switch user on the remote end.
Disabling the Avast self defense module can’t be done remotely. Several of the pc’s I monitor are headless servers and are hundreds of miles away.
Splashtop does have a command to restart the remote pc in safe mode with networking and also starts Splashtop in this mode. Avast can be removed and Avast Clear can also be run from this mode. This is what I have done on the servers and will remove Avast from the others as well.
I have the same problem as well. I manage multiple clients using Splashtop Business and for clients that use Avast free and Avast Premier, initiating any user interface from Avast apps completely kills remote keyboard or mouse input. There was a similar issue back in November (see: https://forum.avast.com/index.php?topic=210715.0) that was supposedly remedied, but its now May and this problem affects my clients with the latest versions of Avast supposedly installed.
System Information
Windows Server 2012 R2 Standard
Avast Business Security 18.4.2534 (build 18.4.3895.327)
Virus definition 180702-0
TeamViewer Host 9.0.32494 (http://www.teamviewer.com)
UltraVNC Server 1.2.2.1 (http://www.uvnc.com)
UltraVNC is a code-signed executable.
It seems that UltraVNC is not in the list of trusted files because Team Viewer is working properly.
Thank you, Peter427, for the encouragement. I have another “distant” Windows computer, this time it’s a Windows 7 Pro host/server for UltraVNC, which is stymied as soon as the Avast control panel is raised. But TeamViewer host/server works on that same computer without any snags whatsoever.
I’ll put my name in the ring here, too. Using UVNC 1.2.2.1, windows 7 ultimate, Avast Free, everything up to date as of this posting. See, for instance:
This workaround seems to work for now. Open Ultravnc and connect to the remote machine.
If the Avast window pops up, you can no longer control the remote computer. CTRL/ALT/Delete will not work.
Open the chat window. Click “send” (no need to enter text, just click send).
For some reason, you can now use CTRL/ALT/DELETE from the UltraVNC window (top left icon).
Start Task Manager. You should see Avast in the list of programs. End Avast. The pop up Avast window should disappear. This does not stop the Avast program from running, but it just closes the Avast Pop up and you should have control of theremote machine again.
Thanks. It seems to be all about that chat window. Nevertheless, it’s still only a partial work-around in that, in the end, one still can’t interact with Avast remotely. In my role as remote administrator, I’d sure like to be able to interact with the AV software!!
Hi,
Avast is blocking all emulated user input coming from an unsigned process when an Avast window is the foreground window (the window which is receiving user input). This change was required, because there was an attack reported to avast bug bounty program, which was using user input emulation API to deactivate protection completely. TeamViewer has signed executables, so there shouldn’t be problem with TeamViewer unless you are using a warez (modified) version of TeamViewer. Also please use latest Avast 18.5 version as there were some bugs in previous releases related to this issue. I have tested latest UltraVNC 64bit and it contains signed executables too, but it is possible that afflicted computers have obsolete (unsigned) version of UltraVNC.
Thanks
Spec8472: thanks. That makes a lot of sense. Here’s the rub: I’m using UltraVNC 1.2.2.1 (the latest version) and Avast 18.5.2342. So the problem is appearing even with the latest version of software. Thoughts?
charlierainbow, can you please verify that “C:\Program Files\uvnc bvba\UltraVNC\winvnc.exe” executable really has digital signature? Is your UltraVNC 32bit or 64bit version? Thanks.