FAO Vlk - Avast Log Errors after Installation of Beta 1178

Vlk,

Can you help with these error message I have reported, they have occured on both instances of installing Avast 4.1.1178

These are when you go into Avast log viewer and the program run section with the 7 boxes of which 2 are called ERROR and WARNING.

They both occured at the same time and one shows in Warning and is aswServ::AavmStart ERROR…

And the one in the ERROR section of the log is
AAVM - Initialization error: AavmStart: avworkInitialize failed, 0000007B.

It’s strange that it happened a second time like it did with my first install, remember this is a second install of the Beta.

I am just curious as to why these were received in the Avast Log Viewer program run section of the log viewer.

I would just like to also say that these errors do not re-appear even if they are removed from the log, however I have kept them in the log this time.

This is on 98 S.E

This forum is one of the best for the participation of the development team but, as I have learned in several years here, those folks are very busy doing their full-time development jobs. They may not have the time to respond to every demand on them in the forum.

If problems occur just once in the log and do not appear again with the continued use of the product, however repeatable on an installation, then … I will say here as I would say to those that I support full time with avast … do not fret yourself.

No problems.

It was just that I think it was Igor that suggested that although it occured and the program worked then ok, but he didn’t like the errors, so I thought to post.

I am only trying to help, but will refrain from posting anymore about this.

;D

Let’s not get too dramatic … errors that do not recur are not the end of the world.

Maybe verbose of the logs… it always frighten us but, like Alanrf said, don’t worry that much.

I don’t look at the log viewer unless there are errors displayed to the screen or there is a noticeable problem with avast and even then a lot of the information is not user friendly but more to help the developers.

If the error was so serious then I would expect a pop-up to be displayed and as Alan said I wouldn’t go chasing a single error return. When it becomes a regular occurrence then you should devote some time to it, otherwise you will never be done chasing shadows.