From: Bullwinkle on 1 Jun 2010 07:40 They only drop Apple malware. "~BD~" <.BoaterDave(a)hotmail.co.uk> wrote in message news:htmsl4$kep$1(a)news.eternal-september.org... "FromTheRafters" <erratic(a)nomail.afraid.org> wrote in message news:htljju$dev$1(a)news.eternal-september.org... | "~BD~" <.BoaterDave(a)hotmail.co.uk> wrote in message | news:htl7dt$gdj$1(a)news.eternal-september.org... | > | > "FromTheRafters" <erratic(a)nomail.afraid.org> wrote in message | > news:htkjgv$9m3$1(a)news.eternal-september.org... | > | > | He's edited the registry and moved on... | > | > | > Surely that's the *only* way to 'fix' things if malware has caused a | > registry alteration? | | If the program was out of date and perhaps misidentifying a malware | instance, what other settings might it have missed correcting? It would | be better to confirm or deny the use of the most recent version of the | removal program. What if version 'b' edits the registry *and* drops | another malware item and version 'a' gets identified and removed? Sure, | he can manually edit the registry entry he finds amiss back to what it | should be, but it would be better to execute an updated version of MBAM | or another removal tool such as SAS. What if MBAM itself was dropping a malware item after cleaning a machine? Who would ever know? SAS might do likewise! Just a thought! -- Dave |