I am remoted into a host machine (using RDP on Windows 10 Pro) where I need to update some software which requires Avast Shields to be temporarily disabled. As soon as I disable the shields the remote session becomes unresponsive. Not only that, but I can’t login to the remote machine again until the ten minutes passes, as Avast seems to be locking it up for that period of time. I’ve done a lot of searches, tried changing some settings in Avast, but to no avail. Why will Avast not let me disable the shields temporarily during an RDP session? And what might be the fix for this?
RDP is built into Windows and is proprietary to Windows. There is no other application aside from Remote Desktop. There are applications like RDP (Teamviewer, VNC, Bomgar), but they’re not RDP. They use their own protocols for connections.
It is an interesting problem though. This may be default behaviour. What version of Avast are you using?
OP is more then welcome to correct me obviously, but I suspect given the term usage “host” that he works in IT. The host in this case is likely some kind of server or workstation (as evidence by the “Pro” version), which would likely be using RDC (Remote Desktop Connection), not Quick Assist. Q.A was designed for end users to get help from a mate. Partial control over the remote system, nothing more. It’s worth noting that “home” users do not have access to Remote Desktop Connection. People using Enterprise/Pro/Education/Server versions of Windows do have access to it.
Remote Desktop Connection was built more or less for Sys Admins who (for example) need to manage servers with unlimited control. That server may not have a display or input devices. If you’ve ever been in a datacenter with one of those carts they push around… That’s what it’s being used for, “remote desktop connection”.
I do need to revise my previous statement though. RDP is a protocol designed by Microsoft and used by Microsoft. Both Quick Assist and Remote Desktop Connection are the only two applications who use it.
Reply 21 suggests installing the beta version but doesn’t state that that fixes the problem.
There’s also been no confirmation from the user as to the effect of installing the beta version.