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

[Victor Hugo]

i'm getting this logged in the event log:

Application popup: dwwin.exe - DLL Initialization Failed : The application failed to initialize because the window station is shutting down.

i've attached the generated file i've recovered from my temp folder which coincides with the shutdown - as you can see the error is coming from egui.exe.

is there any way to solve, or should i go back to v3?

[ronjor]

I'm seeing the same error on XP Home, SP3. This does not occur using V3.

[Victor Hugo]

glad to see it's not just me, i am too running xp sp3 (media centre edition)

[Victor Hugo]

i've fired off an email to support, so i'll let you know how i get on.

[ronjor]

{QUOTE-> i'll let you know how i get on <-QUOTE}Thanks. :thumb:

[jedi_m]

Same error here, but not all the time, it's random.
Please post if any fix is comming.
Thanks,

[Victor Hugo]

i've noticed it comes up not *every* single time - it seems to happen when you've had egui open to view stats or change settings, then it seems to do it. i'll add that to the report.

[arqarq]

Got the same problem here on XP x64. It is rather random. Have no idea what's causing this and how to solve it.

[Victor Hugo]

i haven't heard back from tech support yet - they contacted me the day after i did the report to send them a sysinspector report but i've heard nothing since.

[ronjor]

Thanks Victor Hugo. We will see what they come up with.

[acooldozen]

Yup.same problem here XP SP3 WMCE!

[Joan Archer]

I haven't noticed any problems since upgrading to version 4, this is on a Vista Home Premium 32bit system.

[c2d]

{QUOTE-> Same error here, but not all the time, it's random.
Please post if any fix is comming.
Thanks, <-QUOTE}

Same here...it started 15 days ago

[prius04]

Another "same here". The popup went by so quickly I wasn't able to read it at first but it started occurring, on a random basis, after I installed v4.

[Philippe_FR22]

Another "same here". I noticed it yesterday night when shutting down my PC... But already happened once, according to events records

Regards

[NyteWysh]

Same here ... happens randomly.

[acooldozen]

Solved my issue. It was ZoneAlarm firewall. Just increased the trust level on Eset service. Problem went away. Will keep you posted.

[prius04]

{QUOTE-> ...it seems to happen when you've had egui open to view stats or change settings... <-QUOTE}
Confirmed here; numerous reboots yet the error message **only appears** when I've had egui open.

[funkydude]

I never get the error message but I get something really weird when I look at the "watch activity", it keeps playing the XP ding wav file over and over again. Only noticed this in XP using EAV, not seen it in Vista with ESS.

[prius04]

Are you sure you're not getting the error message? Most of the time, after I've had egui open and restart, the thing **really** flies by and requires no user input.

Just for laughs, check Event Viewer >> System and see if you have an "Application Popup" entry (under Source) that indicates "dwwin.exe - DLL Initialization Failed".

[funkydude]

Nope, event viewer reveals no errors, just still the same XP sound over and over, really odd...

[prius04]

Sheesh! That sound is definitely odd. "Watch activity" is completely silent on both machines on which I have EAV v4 installed (both XP SP3). Have you taken a look at the stuff listed in the Sounds tab in Sounds and Audio Devices in CP? Just a thought.

BTW, there is no error message in event viewer, at least it's not listed as an "error". Rather, the "Type" of event is simply "Information"....."Application Popup" is listed as "Source" (not saying you haven't already looked for that, though).

[The Hammer]

No problems with version 4 yet.

[Novicex]

I had the same problem with XP sp3 Pro, Ess 4, solved by killing DWWIN in anywhere;D

[prius04]

I found an old trick that killed the error message:

1) Control Panel >> System >> Advanced tab,
2) Click "Error Reporting"
3) Check "Disable error reporting" and *uncheck* "But notify me when critical errors occur"

Fooled around with egui quite a bit yet no error message on shutdown thereafter. YMMV, of course.

[Banger696]

Had this once after installing V4 but never again. :isay:

[DarrenDavisLeeSome]

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).

[arqarq]

Unfortunately this issue is still present in version 4.0.417 :(

[Argonite]

Same error here. XP Pro SP3.

[acooldozen]

I'm only getting the error message on shutdown!

[Argonite]

We are seeing this error generated at each user logoff.

[siljaline]

{QUOTE-> I found an old trick that killed the error message:

1) Control Panel >> System >> Advanced tab,
2) Click "Error Reporting"
3) Check "Disable error reporting" and *uncheck* "But notify me when critical errors occur"

Fooled around with egui quite a bit yet no error message on shutdown thereafter. YMMV, of course. <-QUOTE}
How is disabling error reporting supposed to resolve the shutdown issue ?
This a just a workaround.

[haerdalis]

{QUOTE-> How is disabling error reporting supposed to resolve the shutdown issue ?
This a just a workaround. <-QUOTE}

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.

[Victor Hugo]

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

[siljaline]

{QUOTE-> just had an email from eset support - basically this should be fixed by downloading and installing the latest build (4.0.417) <-QUOTE}
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.

[acooldozen]

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

[Roland3]

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

[Ardmore]

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?