According to the report of Jekku, it is not about how many reboots you made, or how many updates, but about rebooting after a definition updates was in fact performed.
So rebooting 5 times during 8 hours, for example, may not catch the event until an update was actually applied. Statistically (well, just as a mean value), you get 1 update every 12 hours. No matter if you reboot 20 times, but if you reboot after receiving that next update.
During 2 days, if rebooting several times, you would see that the event is almost not reported except for one reboot after an update (or after 3 updates with no reboot in between, doesn’t matter).
Of course, I am assuming that your systems are behaving the same as in Jekku’s case.
I very well know about this specific problem, Since I had the same thing with version .1352 I downgraded to .1289 to see if it is still present. Answer is -no-.
To make my previous statement more precise for you:
It’s running now for two and a half days, 6 def. updates with either shutdowns or reboots behind.
My system is not online for 24 hours, but only periodically may be a total of 3 hours per day. That implies shutdowns startups and reboots. So I have at least one shutdown or reboot after a def update.
it is obviously clear that ady4um has no clue about Window 7 systems!
He should leave this problem to those that know and run Windows 7 and he does not want to disclose what country he resides in nor indicate what operating system he uses. ???
Yes, evidently you have rebooted after some definitions update, but craigb mentioned 5 reboots in 8 hours “only”. That period of time (which in some cases would not be enough to trigger this event) and the rebooting frequency was the main reason for the comment.
@YoKenny,
I tend to avoid publicly posting personal impressions or opinions on other forum members. If I were to do such a thing, I would probably be wrong, since some simple forum posts coming from people from all over the world with different cultures are not even close to the vicinity of being enough to have some kind of valid impression of anyone / someone.
Evidently and obviously, it wouldn’t add anything, just like your opinions with no fact at all. I would consider asking you, politely, to concentrate on the real issues and technical matters, but since anyway you already carefully read the signatures more than the main posts, my request to you would be a waste of time (to say the least).
I was about to repeat myself with previously posted explanations. This is the last time I fall into this worthless OT with you. If you want to share with me technical issues, I am very open to that. Otherwise, don’t even bother; I don’t care.
Let’s move on into the next technical issue and the next Beta version.
Since I had this “unexpected shut down error (6008)” with version .1352 everytimes a new def update came in I reverted to version .1289 again and it was OK.
Now I tried .1356 as an over thetop update. The error is immediately back after the first def update! :o :o :o
Came back to .1289 and observing the system now. After the next update this evening I will report back!
Edit: First big def update of .1289 to current status folowed by a reboot did not show the 6008 error in the event viewer.
@jrace: Could you try to uninstall the .1289 build and make a clean install of .1356? I did that and didn’t get an error after first def update/reboot. However, I did get a strange error window during uninstall (.1354): DllRegisterServer returned 0x8002801c. I don’t know if this has anything to do with our problem, but I remember seeing that error once before. That was when I first discover this 6008 error problem and unistalled my avast.
I bet I won’t get that system shutdown error until the next program update when the next build is updated over the old one.
Like you I made a clean install of .1356, it made directly after install the first def update, I rebooted the whole load and what did I see: -nothing, no 6008-
That seems to have solved it. With crossed fingers I’m waiting now for the evening update and will check what comes. Hope you are right with your bet! ;D
But anyway even when it works out somebody should alert “Vlk” on this to have an eye on it!
Well, I don’t think this issue is solved yet. What I meant to say was, that even if we didn’t get any errors (I don’t know this yet) with this current build .1356 (clean install), I bet we will start to get them again as soon as the next build installs itself over the current one.
Seems that a clean install will work without problems(?), but an update over the old version won’t and we’ll start to get those 6008 errors when def update/reboot is made(?). That’s what has happened so far, isn’t it? Well, this is just my speculation and we’ll see how it goes when the next build is released…
And I was unfortunately wrong… I just got an 6008 error after def update/reboot with my clean installed avast .1356. So, we are back in square one again! >:(
A few minutes ago I had the same experience with the evening def update of .1356. As you say, we are back to the start and I have absolutely no clue. ???
I will now finally go back to .1289 and try again when the new stable version is rolling out.
Still watching this post.
Right. We’re investigating the issue (and would really love to have it resolved before releasing the next program update), but we will likely not hold the release of the update until we find a solution - because the issue was present even in the last stable version, so the new update won’t make things any worse.
I confirm. 6.0.1203 build was the last one which worked ok and the problem has been there since.
Thank you for investigating this issue, I hope you can find the cause.
I definitely confirm that my system is running well and without 6008 errors on Version .1289.
Just had another def update on .1289 and the following reboot did not have any 6008 errors.
A weird happening. :
A member of another forum directed me here as I’m getting related trouble. Avast Free latest version is on both of my pc’s. The error I’m getting only occurs on my Laptop.
I just got an 6008 error after def update/reboot with my clean installed avast .1356. So, we are back in square one again! >:(