it asks to reboot and do a scan. i say ok, it finds nothing. I continue using computer, awhile later it pops up again warning of this rootkit infection. again it wants to reboot and do a scan. I say ok, again it finds nothing. The next day, it pops up that rootkit warning and wants to do…
When was this detected ?
e.g. on an on-demand scan or roughly 8 minutes after boot (anti-rootkit scan, see image example) ?
What is the full path to this file, e.g. c:\windows\system32\drivers\ filename ?
Given the comment that this comes back later I suspect it isn’t only the anti-rootkit scan, but also another one of the shields.
@ paulmars
The VPS 111206-2 should have resolved the sfloppy.sys detection, I don’t know if that is also the case for classpnp.sys, but I would suggest that you ensure you have the latest avast VPS version.
Once you have the latest version, reboot and see if anything is is detected, if so report what it was.
Then try a repair of avast:
XP - Add Remove programs, select ‘avast! Anti-Virus,’ click the Change/Remove button and scroll down to Repair, click next and follow.
You may need to reboot after the repair. This has in the past resolved this out of sync issue between reported and actual VPS version.