Vista SP2 RC Security Updates crash NOd32

[bradtech]

After applying the last two SP2 Vista updates via Windows Update I now get a message from NOD32 telling me the real time scanner has encountered an error, and NOD32 need to be reinstalled..

I have attached the three updates Installed, and the affect it had on NOD32 after a restart, and installation/applying of the updates.

[bradtech]

hmm. Did a reboot, and was still there.. Tried doing a repair install and it gave me some privilege error like nod couldn't reinstall itself due to rights possibly.. I disabled UAC thinking something may have changed with the security updates and SP2.. Did a reboot, and NOD32 is now working again without actually doing a reinstall..

[funkydude]

You're not the first person to report problems with SP2. I'm curious if it's just a problem with installation or a general SP2 problem ESET might need to push a PCU to fix.

[bradtech]

{QUOTE-> You're not the first person to report problems with SP2. I'm curious if it's just a problem with installation or a general SP2 problem ESET might need to push a PCU to fix. <-QUOTE}

What was odd is that i had zero issues with just a SP2 install. It seems that the security upates after SP2 installed were what caused my problem. I did not have to uninstall NOD32 or even the Security updates to fix NOD32.. I just disabled UAC from msconfig, and did a reboot..That solved the issue. I tried a reboot prior to disabling UAC and that did not fix it. So then I began to make changes.. What lead me to believe there was some kind of permission issue or security feature was when i tried to do a simple "repair" option from NOD32 in Programs and Features.. It would not allow NOD32 to even do this.. I thought to myself "this seems like UAC"..

I wonder if those particular Security Updates applied on top of SP2 have hosed something up regarding UAC, and NOD32 causing the real time protection to get hosed up... This would maybe be something a ESET developer would lke to play with in a VM setup.. I'd hate to see the official non RC SP2 for Vista or Server 2008 to cause any issues down the road because of something Microsoft changes up

[funkydude]

Well I know a lot of UAC work went into v4, if MS changed it somehow in SP2 it could explain the breakage.

[bodean]

Same issues here. Been going on for a week now. If Eset can admit to and fix this error, might not be renewing at the end of the month.

[bodean]

Just reinstalled NOD 32 Vista 64 version, same error comes up. Nice.............:thumbd: :thumbd:

[Skoorb]

Just to confirm (although this is my first post), it's happening to me as well.

Also, try uninstalling it while in this state - it seems impossible.

If anyone (especially from Eset) wants any logs, or other info, do let me know.

Does anyone have any other temporary solutions apart from disabling the whole of UAC permanently? It's a bit of an ugly work around.

Thanks.

[bodean]

I've disabled UAC from the day I installed Vista 64. This hasn't been the rut of the problem.

Sent an email 5 hours ago to tech support. No response yet............

[bodean]

Typical canned response from tech support:

Thank you for contacting ESET Customer Care. Based on the symptoms you described, reinstalling your ESET security product will be necessary. For step-by-step instructions on this process, please click or copy/paste one of the following Knowledgebase articles into your web browser:

Version 4.0:

http://kb.eset.com/esetkb/index?page=content&id=SOLN2116



Funny, I've reinstalled 4 times today to no avail.

If everyone who has the problem can do this:
1. Download SysInspector here:

http://www.eset.com/download/sysinspector.php

and email it to Eset I am sure it will hurry them along with fixing this product.

[bodean]

NOD 3.0.684.0 works without any issues. Just version 4 doing this.
Still no response from anyone on the issue.

:thumbd:

[funkydude]

I'm betting it's a WFP issue. Did they change something in it? I don't have a changelog.

[Marcos]

We'll check it out, I have already notified our developers and testers.

[bodean]

{QUOTE-> We'll check it out, I have already notified our developers and testers. <-QUOTE}

Thanks. Keep us updated. Guess I'm stuck with V3 until V4 is fixed.

[branio]

Can you guys who got the problems confirm that you were using the Beta build 16497 of SP2?
Because with the newest Release Candidate build (16670) the problems aren't observed at all... I mean, those KB958624 and KB956802 aren't even offered for downloading through the WU anymore.
The SP2 RC (released on March 4th) I downloaded was from http://technet.microsoft.com/en-us/windows/dd262148.aspx. No problems with the V4. I tried it on both fully updated (those two KBs were already installed) Vista x64/x86 SP1 and also on clean Vista x64, without any updates installed, so SP2 RC was the first one (those KBs aren't offered anymore).

[bodean]

Under System in the control panel, my version of SP2 for Vista 64 is v.286

[branio]

{QUOTE-> Under System in the control panel, my version of SP2 for Vista 64 is v.286 <-QUOTE}

Same here. Ok, one last thought: would you compare the filesize of your SP2 installer file?
These, listed below, are the ones from the MS site I mentioned before, Release Candidate build (16670):

597˙229˙424 Windows6.0-KB948465-X64.exe
354˙613˙640 Windows6.0-KB948465-X86.exe

From what I've seen, the Beta build was presented as the same KB948465, but I'm confident, that filesizes would be different :lurking:

[bodean]

Running this:

http://www.windowsvistaweblog.com/2009/02/24/windows-vista-sp2-rc-build-600216670090130-1715-v286-in-beta-testers/

[bodean]

Any update from the company on a fix, patch, updated version?

[Skoorb]

I'm running the official release candidate of SP2 detailed at http://technet.microsoft.com/en-gb/windows/dd262148.aspx (v.286, build 16670). I installed it through the Windows Update route linked on that page. I manually installed the optional pre-req at http://www.microsoft.com/downloads/details.aspx?FamilyId=910baf28-f32a-43ee-a63a-1fe85ab651ac&displaylang=en before hand. I have no updates listed in Windows Update that I have yet to install, apart from the Office Live Add-In.

I upgraded to Nod32V4 from V3 while Vista SP2 RC was installed.
I uninstalled Nod32 through the Control Panel, rebooted my machine, then installed V4.

When I started getting the errors (from the first reboot after installation), I did a manual uninstall and reinstall. The steps I followed were:
Uninstall from Programs and Features - this lead to an error message on a few files.
Reboot, and in safe mode deleted everything listed in http://kb.eset.com/esetkb/index?page=content&id=SOLN2116&actp=search&viewlocale=en_US&searchid=1237062339129.
Manually removed the service with sc.exe
Followed http://support.microsoft.com/kb/315539 to open device manager and manually deleted the eset devices.
Deleted the Eset registry entries:
-HKEY_CURRENT_USER\Software\ESET
-HKEY_LOCAL_MACHINE\Software\ESET
Rebooted
Reinstalled.
Disabled self-defence mode

Now, the error message saying I need to reinstall only occurs occasionally, on certain boots. When it does, NOD32 still automatically quarantines the EICAR test files when I download them from the EICAR site, so it may not actually be as dead as it says it is. When I reboot the system again, the error message usually goes away for a few boots.

I hope this is some use for you, let me know if you need any more.

Alex

[bodean]

Any update from THE COMPANY on when a new version/fix will be released?
Or has it gone on deaf ears over at ESET?

[bodean]

UPDATE from ESET on issue:

Following is the email I got from them

~Private communications removed as noted in the Terms Of Service (http://www.wilderssecurity.com/tos.php) for using these forums.~{QUOTE-> This restricts the public posting of any private communications without the express permission of all parties involved in that communication, whether those be emails, instant message logs or any form of private messages. <-QUOTE}



If you look at the email, it's another one of those canned "Uninstall/reinstall" but this time, for v3. Funny, the whole conversation / issue has been with V4.

Good help hard to find these days I guess.

[branio]

I believe they are working on this issue. So far, I have been able to reproduce the problem with the v4 not starting correctly when there is SP2 RC installed. Still, this isn't happening always, only in about 5-10% of system starts.

[Badgerman]

I had the issue with Vista x64 Ultimate SP2 v.286. My NOD32 try icon came up orange and told me to re-install. I had uninstalled NOD32 V3, run CCleaner, CleanMyPc, Disk Cleanup, rebooted and installed NOD32 V4.

As I read this thread last week I reverted back to V3. I thought my system was a little snapper/quicker with V4 so I checked everyday anxiously awaiting the fixed V4.

My patience ran out and I re-installed V4 right over top V3 and it's worked for days with several reboots and no errors. Go figure ; /

[bodean]

Has anyone tried NOD 32 v4 with the latest Vista SP2 RTM-Escrow build that is now out?

"" Sources say that the RTM Escrow build of Windows Vista and Windows Server 2008 Service Pack 2 has been released to a group of internal testers. The build number of this pre RTM build is 6002.17506.090313-1730, compiled on March 13, 2009. The RTM build numbers are also finalised and would be 6002.17507.090319-1515 and 6002.17508.090320-1600 ""

[bodean]

So far so good with the RTM-Escrow build of SP2 vista 64

[bodean]

I take that back, errors are back. The typical "Maximum Protection is not ensured" error, and asking to reinstall. Back to v3 til NOD32 can fix this problem.

[bodean]

Does anyone know if this has been fixed, and is safe again to install SP2 RC?

[bodean]

What do we have to do to get someone from NOD 32 to first A)admit the issue and B) give an ETA on when it will be fixed? This issue has been going on for a few months now, and not one rep has replied to this thread. What a shame.
:thumbd: :thumbd: :thumbd:

[jeremyf]

in my experience, no one actually from Eset reads this forum, besides Marcos, and I am not sure if he is Eset employed? he tries, but there is ALOT of threads here....

this forum really is mostly for other users to try to figure things out together, in other words, it is not used properly by Eset, (it would be a valuable resource if they chose to monitor it and and if they actually responded here, they would earn permanent loyalty in users).

bah...

[agoretsky]

Hello,

I just did some testing with the release candidate for the service pack and was not able to reproduce this. Could you send me an ESET SysInspector log from your computer via PM to look through?

Regards,

Aryeh Goretsky

{QUOTE-> After applying the last two SP2 Vista updates via Windows Update I now get a message from NOD32 telling me the real time scanner has encountered an error, and NOD32 need to be reinstalled..

I have attached the three updates Installed, and the affect it had on NOD32 after a restart, and installation/applying of the updates. <-QUOTE}

[tanstaafl]

Hey bodean...

Chill out man... you are complaining about ESET not working correctly with BETA/RELEASE CANDIDATE VISTA/CRAP.

I'm sure they appreciate your feedback, but your attitude is misplaced...

Expecting them to just drop everything and fix an issue with a BETA SERVICE PACK for VISTA/CRAP is not only a watse of resources, its just plain silly.

Sheesh...

[JuliusB]

{QUOTE-> Hey bodean...

Chill out man... you are complaining about ESET not working correctly with BETA/RELEASE CANDIDATE VISTA/CRAP.

I'm sure they appreciate your feedback, but your attitude is misplaced...

Expecting them to just drop everything and fix an issue with a BETA SERVICE PACK for VISTA/CRAP is not only a watse of resources, its just plain silly.

Sheesh... <-QUOTE}

First, Vista is not crap and is already used in 25percent of computers(look wikipedia os market share), second this SP2 most of us have is NOT beta. It's not even RC. It's RTM Escrow, means almost RTM.
I also get this problem. Randomly, it seems. The last few times I booted my computer everything worked fine, so I cannot try one thing myself.
And that one thing is trying to disable v4 Self-protection and see if the problem persists.
I suggested this in several topics, but no one seemed to answer. An answer would provide valuable information both for people looking for a fix/at least temporary one and maybe ESET too. Everybody just keeps creating topics with problems..

[MikeMcr]

{QUOTE-> Expecting them to just drop everything and fix an issue with a BETA SERVICE PACK for VISTA/CRAP is not only a watse of resources, its just plain silly <-QUOTE}
You might want to check your facts. The RTM release of SP2 is now available. It is NOT a beta any more. See the front page of Neowin.net.

[bradtech]

I'm sure ESET is aware of this, and is trying to make a solid solution. Takes time to work bugs out, and figure out why it happened, and implement a solution that is not half-cocked and will end up breaking more.. That is the main reason I report findings is to get a better product.

[trjam]

{QUOTE-> I'm sure ESET is aware of this, and is trying to make a solid solution. Takes time to work bugs out, and figure out why it happened, and implement a solution that is not half-cocked and will end up breaking more.. That is the main reason I report findings is to get a better product. <-QUOTE}
And that is what in the end, will give you a better product. Kudos my man.:thumb:

[jeremyf]

+2 points for bradtech

[UglyChild]

::)

I can get a better answer out of our useless politicians these days.


After 4 updates and new builds, the main issue has not been fixed yet, and SP2 is about to hit main MS Update website in very short time.

If you think you have a problem now, wait till half your customers start calling and flooding your mail boxes all at once. That will wake your asses up.

[bradtech]

{QUOTE-> And that is what in the end, will give you a better product. Kudos my man.:thumb: <-QUOTE}

It's part of doing business. I am just happy Marcos, and whoever helped him fix my Novell Netware Client crashing issues after providing a Kernel Dump for them to look at. I got a build that was not officially releases a day after he looked at it, and it totally saved my ass, and will help come renewal time. Of course I have criticisms, and recommendations on what I want to see.

[agoretsky]

Hello,

Private Message sent.

Regards,

Aryeh Goretsky

[Kanna]

I actually have a bigger issue than just the 0x101a error...

- Installing the program at first goes through with no errors
- Upon first update the program will report error 0x101a
- After a manul restart, the error still persists and NOD32 cannot update itself
- The ESET directory is not writeable by any process or user, including Administrator and SYSTEM
- The ESET registry key entries are not writeable by any user, including Administrator and SYSTEM
- Taking ownership of these resources did not resolve the permissions issue
- Upon uninstall:
- MSI will report unable to delete files even if you have ownership and full access to the ESET folder
- manually deleting registry keys after taking ownership will result in "error while deleting key"

The only way to remove all traces of NOD32 is to boot with WinPE, load the local registry hive and remove the offending entries, then proceed to delete files manually.

All this is on a clean install of Windows Vista SP2 6002.18005RTM

[sleeper]

Unfortunately I have to confim the problem that Kanna reports, in addition I'm getting reproducibly a BSOD upon login. The error occurs in emon.sys. Booting into safe mode I can disable the ESET service and login again normally. However, disinstallation (automatic or manual) of NOD32 is not possible because of insufficient privileges exactly as described by Kanna.

The issue occured first after installing SP2 RTM on a system that ran w/o problems for several months. Now I'm getting the BSOD using Nod32 4.0.424 BE on a clean install of Windows 2008 server x64 SP2 6002.18005 RTM.

[jimwillsher]

Same here. During stage 3/3 of the SP install, e.g. the login screen, eamon.sys causes a BSOD. Fantastic.

Oh well, I wanted an excuse to wipe and install Win 7 RC, and guess I just found that excuse...

[Recall]

Right, I am getting the same issue here. It will be ok for a few days, then I get the problem with it not starting. I also got a bsod on reboot when I installed SP2 RTM FINAL, but a forced reboot and it installed ok the second time.

The only way to fix it when the issue occurs is to uninstall it and remove all registry keys which is a bloody pain the arse. ESET please give us an indication you are working on this issue. My subscription is up soon, I even convinced my Dad to get a triple licence.

It is very frustrating and seems to be a permission issue, as it causes errors when I uninstall as well.

[YeOldeStonecat]

{QUOTE-> Hey bodean...

Chill out man... you are complaining about ESET not working correctly with BETA/RELEASE CANDIDATE VISTA/CRAP.

I'm sure they appreciate your feedback, but your attitude is misplaced...

Expecting them to just drop everything and fix an issue with a BETA SERVICE PACK for VISTA/CRAP is not only a watse of resources, its just plain silly.

Sheesh... <-QUOTE}

SP2 for Vista has been RTM for a while now.

More importantly....going back to last year, it's been known SP2 for Vista was going to be coming out soon. All those RCs. And Microsoft gives software developers access to it, so that they have time (for those software developers that think ahead and use this time) to get their product compatible with it. This is logical, the better software companies utilize this time to prepare their product so that it's ready and fully compatible with the service pack once it's publically released. Instead of scrambling around after the fact when a bunch of their users call support with crashes.

[bathisland]

Okay in all fairness here is a good experience. I have Nod AV 4.0.424 running. I installed the RTM of the Vista SP2. Granted it took a long time to install (between 45 and 60 mins....and it might have to do with the fact that i did not disable Nod or it might not have taken as long....will never find out now). After reboot, all is well and no errors whatsoever with Nod or with Vista.

The only weird thing happening to my computer is that it is showing that I have Bitdefender installed as AV (which i had 2 months ago and only for 2 hours). Pretty weird but Nod is running well so am not too bothered about it.

[Kanna]

I think if you already have nod32 installed before doing the update then you're fine. I just tested it on vista sp1, installed nod32, then installed sp2 afterwards. Going that route worked for me.

[bodean]

{QUOTE-> Hey bodean...

Chill out man... you are complaining about ESET not working correctly with BETA/RELEASE CANDIDATE VISTA/CRAP.

I'm sure they appreciate your feedback, but your attitude is misplaced...

Expecting them to just drop everything and fix an issue with a BETA SERVICE PACK for VISTA/CRAP is not only a watse of resources, its just plain silly.

Sheesh... <-QUOTE}

I find it odd that NOD32 v4 breaks with Vista sp2, yet runs fine in Windows 7 RC (7100)

[MOM2009]

{QUOTE-> I think if you already have nod32 installed before doing the update then you're fine. I just tested it on vista sp1, installed nod32, then installed sp2 afterwards. Going that route worked for me. <-QUOTE}

This worked for me 1 day. on the second day i always get the messages posted on the first post in this thread. i have to disable UAC then NOD32 works again.


Nod Antivirus 4.0.417 german on vista ultimate x64

[Brama]

Vista32 SP2 RTM (official, not Escrow) gives issues with nod32 4.0.424.0.

After the SP installation it seems to work but on next reboot you have: red eset icon on taskbar, unknown error 0x004 sent by eset and real time protection disabled.

If I scan the C: drive to fix possible errors, on next reboot eset is working properly until following reboots.

It seems something related to permissions with cached drivers that are reset after a disk scan.

I hope to see a solution soon.

[agoretsky]

Hello,

Can you send me an ESET SysInspector log from your system? That may be helpful in determining why this occurred on the computer. I have sent you my email address via the forum's private messaging subsystem.

Regards,

Aryeh Goretsky

{QUOTE-> Vista32 SP2 RTM (official, not Escrow) gives issues with nod32 4.0.424.0.

After the SP installation it seems to work but on next reboot you have: red eset icon on taskbar, unknown error 0x004 sent by eset and real time protection disabled.

If I scan the C: drive to fix possible errors, on next reboot eset is working properly until following reboots.

It seems something related to permissions with cached drivers that are reset after a disk scan.

I hope to see a solution soon. <-QUOTE}

[Brama]

{QUOTE-> Hello,

Can you send me an ESET SysInspector log from your system? That may be helpful in determining why this occurred on the computer. I have sent you my email address via the forum's private messaging subsystem.

Regards,

Aryeh Goretsky <-QUOTE}

I will send this afternoon.
Thanks.

[Skoorb]

Hey everybody.

Just a quick note to say that a solution has now been released, and is documented at http://kb.eset.com/esetkb/index?page=content&id=SOLN2254.

[agoretsky]

Hello,

Please see http://www.wilderssecurity.com/showthread.php?t=244205 for updated information.

Regards,

Aryeh Goretsky