Anybody noticed an error message on shutdown since installing NOD32 4?

Had this once after installing V4 but never again.

 

It's been happening to me too with ESS 4.0. Never happened before with ESS 3.0.

It appears to be related to the ESS 4.0 updater. If you shutdown without any updating (manually or automatically) then there is no popup.

It also appears to be only with XP. My friend's computer has XP and the trial version of ESS 4.0 and he gets that popup too in the same manner.

On the other hand, I've got another friend with a Dell Laptop with Vista Home Premium and ESS 4.0 and no popup yet (only installed ESS yesterday...maybe to soon to tell).

 

Unfortunately this issue is still present in version 4.0.417

 

Same error here. XP Pro SP3.

 

I'm only getting the error message on shutdown!

 

We are seeing this error generated at each user logoff.

 

How is disabling error reporting supposed to resolve the shutdown issue ?
This a just a workaround.

 

Yes it is a workaround as the cause of the error triggering dwwin.exe is still present.
If I were to guess, it is most likely an access violation error that triggers it.

I don't use V4 myself (I still use v3), but I've encountered the same issue with other software.

 

just had an email from eset support - basically this should be fixed by downloading and installing the latest build (4.0.417)

 

I am currently running the above build, the issue persists.
As Marcos mentioned in another thread a while back, it was OK, to install new builds over top providing you got the prompt to save your current settings. Which the last over-top install did. Still having the shutdown issue, though - not persistant but it still does occur.

 

Same build and not persistant either,................. but it still does occur.

 

Same here, the problem still occurs when my Windows XP shutting down.

 

I noticed the problem in event viewer only, intermittently. The Zone Alarm tweak didn't help.

Both of my pc's are XP-SP2, but only one of them has that symptom. I was wondering if that might have something to do with the intermittent failure of scheduled scans to run per my rules. I was experiencing some duplicate (simultaneous) scheduled scans on both pc's, but following procedures in a KB support sent me on 4.0 scan scheduling seems to have eliminated duplication.

However, the pc with the intermittent shutdown error -- and ONLY that pc -- is still missing some scheduled scans completely. Anyone else?