Author Topic: thousands of Error 42100  (Read 3139 times)

0 Members and 1 Guest are viewing this topic.

dbl2

  • Guest
thousands of Error 42100
« on: May 10, 2006, 03:40:09 AM »
didn't do anything different from last 6 stand alone scans.

operating system:  XP Pro version 2002 SP2
version of avast!  4.7.827  May2006
version of VPS file:  0619-9  5/08/2006
basic hardware configuration:  AMD Opteron 148 1M 2.22MHz, 2 Gig RAM
connection to Internet:  dial-up
e-mail client:  Outlook
other security software:  None (so far)
steps to reproduce the bug:  stand alone scan
error messages: (thousands of)  Error 42100 Error in polymorphic viruses code
 ???
« Last Edit: May 10, 2006, 03:44:50 AM by dbl2 »

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67194
Re: thousands of Error 42100
« Reply #1 on: May 10, 2006, 03:55:18 AM »
If I remember correctly (you can search the board for the 42100 keyword) you shouldn't worry that much about this error.
But I'm not fully sure...

Welcome to forums  8)
The best things in life are free.

CharleyO

  • Guest
Re: thousands of Error 42100
« Reply #2 on: May 10, 2006, 04:08:33 AM »
***

Click the link below for answers ......

http://forum.avast.com/index.php?action=search2


***

Offline Lisandro

  • Avast team
  • Certainly Bot
  • *
  • Posts: 67194
Re: thousands of Error 42100
« Reply #3 on: May 10, 2006, 04:20:49 AM »
http://forum.avast.com/index.php?action=search2
Charley... the link (of any avast forum search) gives you nothing  :P
Only the own user could see the results  :'(
The best things in life are free.

CharleyO

  • Guest
Re: thousands of Error 42100
« Reply #4 on: May 10, 2006, 04:42:11 AM »
***

Sorry ... I was not thinking about that.    :-[    :'( 


***

dbl2

  • Guest
Re: 42100 question: THE ANSWER
« Reply #5 on: May 10, 2006, 06:30:40 AM »
I just redid the boot scan with NO 42100 errors
Only two things different
   1) I had just done a scan
   2) I did an immediate VRDB just before the second scan

I'm guessing the latter did the trick.  I had installed Visual Studio since the last auto VRDB and Visual creates piles of files all over the place, which would therefore not have been included in the VRDB yet.  I was doing the scan before doing a cloning of my system disk because of the major changes.  I expect this to be the norm not the exception.  I think error 42100 does not qualify as a "feature".

?Any dissent?  I'd be real curious to hear.  All the many, many times this question has come up, this answer hasn't been offered.