OLEAUT32.DLL entry in Event viewer?

Why all of a sudden is there this entry in the Event viewer…it’s related to Avast,which I’ve had for years and never seen this dll entry before?

It isn’t related to avast as such but avast would be one of many applications that would use this I guess.

http://www.auditmypc.com/process/oleaut32.asp

So why would it suddenly appear as an entry?

I haven’t got the slightest idea as you haven’t said why it is in the Windows event viewer ???

All you have done is post the reference to it in explorer, not why it was in the event viewer, an error, info, text of the log entry, etc.

Thought I was clear…it’s not an error,warning or info,it’s just a sub entry with nothing it in and it just appeared this morning.

The only info I got [attachment] was through the registry key under current control set/services/event log!

So if its not an error what is this you are talking about ?

So if there is no event viewer error there is no issue.

The registry can seriously spoil your whole day, I don’t go wandering round it looking for things unless I get information (in the form of an error) that there is a problem.

Wow…! :eek:

It’s a log entry that just appeared today and it has to be connected with Avast…this is ridiculous!

Is it related or not?!

But the picture says its source is from avast!..

Strange…

Wait im going to google this dll^^

-AnimeLover^^

It is just an information entry and I honestly wouldn’t worry about it, as I said I don’t visit the event viewer unless I’m getting errors displayed to the screen or experiencing problems (for the very reasons seen in this topic), especially if it is a single entry. If this were a regular occurrence then perhaps it would be worth hunting, even so for an Info entry I really wouldn’t bother.

It is ‘indirectly’ linked to avast, but it is about avast using the oleaut32.dll to record that the VPS has been Updated and for some reason that failed. It may be related to a user without administrative permissions, I just don’t know.

So if you wish you can monitor it after VPS Updates as that would seem to be the time it occurs and if it is a regular occurrence then it could be that what is being looked for, the ‘source’ information is missing or damaged (more speculation) or as mentioned above.