Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Computer Learning -- Ignore unavailable to you. Want to Upgrade?

To: thecow who wrote (35230)	7/17/2003 12:02:18 PM
From: Esteban	Read Replies (1) \| Respond to of 110653

tc, How would he get reinfected after a successful restore? I'm not following the logic of that. By later restoring to the specific system restore point (by chance I assume) that was made as a safeguard prior to restoring to pre fxxx backup? Is that the only way through system restore? I'm asking because when I've restored my system, I've paid no attention to turning System Restore off and on again. Esteban System Restore creates a restore point before a restore as a safeguard so if your restore is successful you should disable System Restore to get rid of the offending fxxx backup or you will probably end up being reinfected. After destroying all the restore points you can turn System Restore back on.

To: thecow who wrote (35230)	7/17/2003 12:04:05 PM
From: Martin E. Frankel	Read Replies (1) \| Respond to of 110653

Thanks, TC, for the info and link. If I understand correctly what I read, if my son hasn't installed any new programs or drivers after the restore point he chooses, then the registry will be restored to its condition as of the restore date and all entries from that "fxxx.com.exe" will be deleted. I still think it's a good idea to search for the file as per Mr. Mark's suggestion and delete it. Do you think deleting the file (if he can find it) and using system restore at a restore point prior to this occurring will solve the problem? Many thanks again, Marty