Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: steelej on May 08, 2010, 02:39:14 PM

Title: Avast 5 with RDP totally locks up computer
Post by: steelej on May 08, 2010, 02:39:14 PM
Using Avast 5.0.545 with XP Pro (fully patched) and connecting to XP via RDP from Vista.

RDP completely locks up XP machine. I see a totally black screen on both the remote desktop and the XP machine. The only way I have found to recover  is the power off switch.

When I switch off the File Shield on XP then I can connect. The other shields can be left running. This is completely repeatable.

This is not a satisfactory state of affairs. I have been using and strongly recommending Avast for years. Do I have to look for an alternative?

Title: Re: Avast 5 with RDP totally locks up computer
Post by: RejZoR on May 08, 2010, 02:41:24 PM
Wait for confirmation. They can fix lots of bugs via regular daily updates in avast! 5. Maybe this one falls there and they can fix it fast.
Title: Re: Avast 5 with RDP totally locks up computer
Post by: doktornotor on May 08, 2010, 02:46:14 PM
Cannot reproduce here w/ 5.0.545 and XP Pro SP3
Title: Re: Avast 5 with RDP totally locks up computer
Post by: igor on May 08, 2010, 04:09:18 PM
We use RDP quite a lot... so it's certainly not a common problem.
Would you be able to create & upload a full memory dump at the moment the machine is frozen?
(provided there's a PS/2 keyboard on that machine, i.e. not USB, the description is here (http://support.avast.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=71).)
Title: Re: Avast 5 with RDP totally locks up computer
Post by: steelej on May 09, 2010, 06:26:08 PM
Thanks for the response. Following the request to send a sytem dump I have been unable to recreate the fault. RDP has started working correctly again.

Since I raised the problem the following changes have occured.


I don't know what to conlude from this but at least my RDP is working again. Could it have been some form of false positive in the signature file?