Elevation is required, better run the command from administrator’s console.
What I posted in pictures is what I ran. As you can see from the results,
the change happened.
Same problem using UltraVNC and Avast 17.8.2318 (3705). But I’m only having issues with 32-bit Win7 … 64-bit Win7 and Win10 machines are working fine. I have not yet found any workaround in Avast settings.
George
Thanks very much for the quick fix and clear instructions. Update those test plans! 
The workaround for this is to disable Self Defense Module but this issue should be fixed already by the microupdate. Same goes with other remote tools.
Hi All. Using XP Pro SP3 and cannot get Avast to update to the .249 release. Tried the schtasks command and, even though it indicates the task completed, the last digit in the build is .0 no matter what I try. A friend with 2 XP-based machines successfully updated them.
Why can’t I get the upgrade?
Please try to run “AvEmUpdate.exe /debug” from Avast program folder as an administrator and copy output.
Please try to run “AvEmUpdate.exe /debug” from Avast program folder as an administrator and copy output.
Prior to your response I tried "AvEmUpdate.exe /Run /TN “Avast Emergency Update” and that seems to have set the update to build version .249 and so and so far it is working. My friend who successfully updated Avast on his XP earlier is now having a different problem. After Avast is running for about 10 minutes, it will lock his computer so badly he has to power it off to regain control. Once it is up and running again, the same lock up scenario will happen again after a few minutes.
There is definitely a problem…
XP what SP 2 or 3 ???
XP SP3
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.
Works! Thanks ideed!
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
Can you please specify VNC app? Are VNC EXEs signed?
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!
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
Posting in an old topic is never a good idea. Many things change.
Start your own topic and describe the problem in detail. Thanks
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.
Reported to Avast’s developers.
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.