Latest Avast Free Blocks mouse & keyboard input using TeamViewer on Vista, Win 7

[Spec8472]

I believe antirootkit monitor is starting after 10 minutes after Avast SVC load. Please tell your friend to try to disable "Antirootkit monitor" in troubleshooting settings. Thanks.

[REDACTED]

The fix is in form of microupdate, you can force delivery by: schtasks.exe /Run /TN "Avast Emergency Update"
Reboot is required to replace aswsp.sys. The version of aswsp.sys (after update and reboot) in System32\drivers should be 17.8.3705.249

Works! Thanks ideed!

[gneuner_2]

Sorry about this bug, it is caused by latest changes in self-defense, because of reported self-defense bypass using automatization SW using user input emulation. Will be fixed ASAP.

Just updated to build 7.9.3761.0  (32-bit, Windows 7).  Avast is still blocking input from VNC.  Can the aswsp.sys micro-update be re-applied to this version?  And when is the problem going to be fixed in release?

George

[Spec8472]

Can you please specify VNC app? Are VNC EXEs signed?

Sorry about this bug, it is caused by latest changes in self-defense, because of reported self-defense bypass using automatization SW using user input emulation. Will be fixed ASAP.

Just updated to build 7.9.3761.0  (32-bit, Windows 7).  Avast is still blocking input from VNC.  Can the aswsp.sys micro-update be re-applied to this version?  And when is the problem going to be fixed in release?

George

[REDACTED]

As the late great Yogi Berra said:  "It's deja vu all over again!"   

Latest Avast Free Antivirus 17.9.2322 (build 17.9.3761.0) blocks mouse and keyboard input using TeamViewer, VNC, and other remote access programs on a remote Windows PC when you open the Avast Free Antivirus program on the remote PC (to try and disable shields to install other programs, for instance).  Sending "Ctrl-Alt-Del" and running Task Manager gets me out.  Tried it on a couple of Windows 10 and Vista PC's.  Work-around is to disable Self Defense Module while at the remote Windows PC (not a good option and cannot be done remotely).

Please fix...again.  Thanks!

[REDACTED]

A half year later: The described problem still occurs using AVAST Free Antivirus (18.1.2326)!

VNC access is blocked when opening a window in AVAST.

UVNC Windows Symbol + R is blocked too! Disabling Self Defense mode is not possible using vnc so you have a big problem being away 100 km from your computer running a vnc server instance.

Regards
avasttestit

[bob3160]

Posting in an old topic is never a good idea. Many things change.
Start your own topic and describe the problem in detail. Thanks

[REDACTED]

A half year later: The described problem still occurs using AVAST Free Antivirus (18.1.2326)!

VNC access is blocked when opening a window in AVAST.

UVNC Windows Symbol + R is blocked too! Disabling Self Defense mode is not possible using vnc so you have a big problem being away 100 km from your computer running a vnc server instance.

Regards
avasttestit

Once again, the latest version of Avast is still blocking access to Avast settings when remoting in using Teamviewer. Every time I try to get into Avast settings, I get the "The screen cannot be captured at the moment. This is probably due to fast user switching or a disconnected/minimizedRemote Desktop session."

The whole reason I use Teamviewer is because I don't have physical access to the computer. I can't physically change settings in Avast to fix this problem.

Teamviewer forums say Avast are looking into the problem and will fix it. Really? Since 6 months and no resolution? Or, is the problem back again, after being fixed once already?

I need a remote solution! This has got to be fixed once and for all.

[bob3160]

Reported to Avast's developers.

[REDACTED]

Well, one month later and I still can't disable shields or input Avast program password via Teamviewer. I can't go through a "remote" v1803 update with Avast shields on. Guess Avast is just coming off completely, for good.

[igor]

I'm afraid there are two different things here.
The previous one - which we tried to solve - was the when AvastUI was opened, *nothing* could be controlled via Teamviewer or similar tool.
If you are talking about the Avast consent prompt (similar to Windows UAC prompt), that's something completely different. It's intentionally displayed on a different desktop so that it cannot be controlled/scripted by malware.

Are you able to handle UAC prompts with your setting normally, via Teamviewer?
Thanks.

[REDACTED]

UAC control is available for all other programs EXCEPT Avast Free. The Avast consent box is not available. The screen goes black through Teamviewer and no keyboard input works. I have to wait for the consent prompt to time out to get back to the desktop. I have another system here that I am trying to update to v1803 remotely using Teamviewer, and cannot get past the UAC to turn Avast shields off for the upgrade. I need a remote solution to this please. PLEASE!

[REDACTED]

still, the latest version of Avast is still blocking access to Avast settings when remoting,
remote input freeze after right click right bottom Avast tray icon,
remote machine is using ultravnc reverse connection, which is a dell windows 7 x64
aswSP.sys 18.6.3983.367
please let me control the AV remotely or give a workaround, thank you

[glnz]

 
Last week or so, on my Win 7 Pro 64-bit machine with Avast AV Free, on reboots, sometimes TeamViewer cannot access the machine, and other times the TeamViewer remote mousing into this machine is TERRIBLE.  This is new - I have been using TeamViewer to remote into this machine for more than two years without any problems.

In the AskWoody forum, there are some reports that recent cumulative Windows Updates (since June ±) are borking the drivers in certain NIC cards.  So when the above started for me about a week ago, I UNinstalled the September Windows Updates.  At first -- I thought -- this helped, but it started up again - some reboots no connection, others bad remote mousing, and others OK (like now).
 
My Avast Free is version 18.6.2349 (build 18.6.3983.371).
 
Could it be the Avast problem discussed here? 

UPDATE - SEE https://forum.avast.com/index.php?topic=222378.msg1478786#msg1478786