Avast error in Eventlog

Avast Free Antivirus / Premium Security
1

Hi! I have two errors in eventlog. I’ve made a copy&paste here:
(everything after → is my translation of oryginal info. I’ve never worked onan english Windows so I don’t know if this is as in original…)
Config: WinXP Pro SP1 + Avast! HE 4.1.418. First pasted error (15.07) occured (I’m not sure) on first boot after changing VRDB database format from ODBC to XML.
Finnaly ;D, here comes my question: Do I have to worry about them?
-------------start of ctrl+c, ctrl+v-----------------
Typ zdarzenia: Błąd → Event type: Error
Źródło zdarzenia: avast! → Event source: …
Kategoria zdarzenia: Client → Event category: …
Identyfikator zdarzenia: 90 → Event id: …
Data: 2004-07-15 → Date
Godzina: 17:59:55 → Time
Użytkownik: ZARZĄDZANIE NT\SYSTEM → User: NT Authority\SYSTEM
Komputer: XXXX → Computer
Opis: → Description
During the parsing of C:\Program Files\Alwil Software\Avast4\DATA\avast4.xml
XML document, following error occurred: C.

Typ zdarzenia: Błąd
Źródło zdarzenia: avast!
Kategoria zdarzenia: Client
Identyfikator zdarzenia: 90
Data: 2004-07-14
Godzina: 20:00:42
Użytkownik: ZARZĄDZANIE NT\SYSTEM
Komputer: DOMOWY
Opis:
AAVM - scanning error: x_AavmCheckBootDirectEx: avscanScanReal of *BOOTA failed, 00000005.
-------------end of ctrl+c, ctrl+v-----------------

2
Typ zdarzenia: Błąd
Aarghh!! What happened to my PLletters!! I want them back!! ;D ;D ;D
3

Goomish

66%... Please wait, signature is loading
Very cute.... Welcome to the Forums. May I suggest that you try doing a repair. You can do that by going to your add/remove, select avast! and then select repair option. Good luck and, let me know how you make out. :)
4

Thank You for the reply, bob3160 :slight_smile:

Hmm… The strangest (or should I say luckiest:)) thing with those errors is, that Avast! seems to work correctly :slight_smile: (I hope so). I’m using Avast! since a month and those errors happened first time. When I try now to backtrace what I was doing at the time the errors occured I remember that it was probably when I run a manual VRDB creation.
I’ll try to do this again and let You know what happened ;D