Windows Event Log Error 6008 - request

[Roderunner]

Using Avast Free newest version. Win7 H Prem. 32bit. All updates inc. SP1

Well, both systems have 2 GB of RAM and both are Windows Seven 32 bits, but only one have this problem.

I'm starting to think this is not related to a system specification, but rather to the "dirty bit" when Windows is not shut down correctly. I mean, it seems like if Avast definitions update would trigger the dirty bit, somehow (I'd rather not continue with the concept, because I don't really have any basis to it, and it would unnecessarily "scare" users about nothing really important). I know it sounds strange but...

Of course I am not an Avast Team member, so we still need to wait for them to find out the reason(s) for this strange behavior.

In the meantime, keep reporting so they can find some common denominator.

When closing down, I close all open program then use shut down button in start menu.

[YoKenny]

When closing down, I close all open program then use shut down button in start menu.

Interesting post by JoeP517:
http://windowssecrets.com/forums/showthread.php/142560-Event-Viewer-ID-6008?s=bd78c6dd74976ae84810fc835b1a8e88&p=829816&viewfull=1#post829816

I see OpenDNSupdater. I'd also disable the WinPatrol system monitor.

  I have both on my system.

[Roderunner]

When closing down, I close all open program then use shut down button in start menu.

Interesting post by JoeP517:
http://windowssecrets.com/forums/showthread.php/142560-Event-Viewer-ID-6008?s=bd78c6dd74976ae84810fc835b1a8e88&p=829816&viewfull=1#post829816

I see OpenDNSupdater. I'd also disable the WinPatrol system monitor.

  I have both on my system.

I'm a member of Windows Secrets Lounge, He was replying to me.

[jrace]

Are there any experiences so far with the new .1367 release and the "6008 error"?

[YoKenny]

Are there any experiences so far with the new .1367 release and the "6008 error"?

Not so far on my Windows 7 system.

[tenseur]

Same problem with the last version 1367 !. I have the problem since the 1289 version.
Not serious by avast   ... 2 months to wait for another update ... abused!

All is OK, if I kill the service avast before I restart or close my PC. The problem is avast
 

[Jekku]

Same problem with the last version 1367 !. I have the problem since the 1289 version.
Not serious by avast   ... 2 months to wait for another update ... abused!

All is OK, if I kill the service avast before I restart or close my PC. The problem is avast

Well, I can't confirm this, because it seems that my two computers work as they should now (.1367). No 6008 errors after three def updates / reboots. I'll monitor my computers for a couple of days. Hope this lasts!
On the other hand, this isn't completely fixed since tenseur still have problems.

What about the others? craigb, YoKenny, jrace, RodeRunner etc...?

@tenseur:
Have you tried a clean install .1367?

@Vlk:
Did you do something about that issue for this build or is this just a coincidence?

[tenseur]

Yes and nothing change !

[YoKenny]

What about the others? craigb, YoKenny, jrace, RodeRunner etc...?

No 6008 errors for three updates as well and installing v6.0.1367

[jrace]

I updated from .1289 to .1367 via the program interface hoping the "6008 error" (unexpected shutdown) would not show up again like in all the "betas" in-between.

Since update to .1367 I had 4 def. updates with shutdowns and/or reboots afterwards and guess what:

No "6008 error" anymore!

Vlk, is it now just a mystery, because everyone complaining had that behaviour also in version .1289 except for me, or did you find that little devil and killed it?

[tenseur]

I have this problem, unless I kill the process avast. What to do?

Also when I try to update avast, well the windows slidebar to crash!

It is from lee 1289, and I think it has something to do

[ady4um]

I have this problem, unless I kill the process avast. What to do?

If you use Avast Pro or AIS, backup your license file first.

What about the removal utility for Avast, cleaning ALL previous versions you ever had by running it for each one? Use Windows Safe Mode directly for better results.

After that, manually search for any hidden folders containing the words "avast" and/or "alwil" and delete them too.

Then install the latest stable version 6.0.1367 (please download anew), reboot and test for a couple of days (at least) before getting to any new conclusion about the 6008 event ID issue.

You would need to configure Avast again, and if you have files in the chest they will be gone too.

Of course, I can't guarantee you if this would solve the problem, but at least it gives you a clean base line.

Please report back.

[tenseur]

I will retry the install 

[ady4um]

I will retry the install 

You meant the removal of ALL versions. The utility is located at http://www.avast.com/uninstall-utility, but the instructions there are a little bit different from what I suggested here.

[tenseur]

Here is reinstalled. I have over the problem of crash slidebar when I look if I have an update of avast, so I think that's it. I hope it's ok, I would tell you