Two Issues with New version 4.2...

Got a pop-up during install over the
top of version 4.0
** see image

number two **see image[taskbar image]
which includes second issue about not being protected after install
and reboot why NOD32 commands me to update microsoft monthly updates
or I am not fully protected? seems like a little intrusive to me

 

windows xp pro op system

 

That's funny as I didn't get that pop-up when I installed on XP Pro SP3 32bit and it works fine here. Also I'm fully patched as to your second issue.

TH

 

How do I I disable my ESET security product from notifying me about Windows updates? See screenshot for driver signing problem, adjust to suit accordingly.

 

Hello,

In some circumstances, you may receive a Hardware Installation dialog prompting you about whether or not to continue installing the software. Go ahead and click on the Continue Anyway button to finish installing ESET NOD32 Antivirus v4.2.35.0. This may change in a future release of the software.

Just like the 4.0 releases of ESET's software, the 4.2 releases can check for missing Microsoft updates. The most likely reason for the prompting of the new updates is that Patch Tuesday occurred a couple of days ago on March 9th. For more information on this feature, including instructions on how to disable it, see ESET Knowledgebase Article #2196, " How do I disable my ESET security product from notifying me about Windows updates?."

Regards,

Aryeh Goretsky

 

thank you all!!

 

Did you get it up and running OK G

TH

 

Of note from your feedback elsewhere, run the Avast uninstaller run the manually removal for ESET AV, reboot and install a new build from the download center.

 

siljaline, thank you! prior to moving towards NOD32
I ran the above software and then installed 4.0 and that
version seemed to run ok...when installed[or up-graded]
to 4.2..system slowed to a crawl....
once removed NOD32 v4.2...back to smokin fast pc
really does not make sence to me either?.........

 

I am frankly baffled since you run XP Pro SP3, there should be no problems.
Best guess is that you have a software or hardware conflict somewhere.
Can you upload the uninstaller log file from the ESET uninstaller ?
That may help diagnose what went wrong.

 

No, everything to do with NOD32 is gone...its all good

 

Are you actually serious? Do you hear what you are saying? If that is the case, I would like an EXACT list of circumstances of when this would occur. I was just about to push out the upgrade to my 1000+ clients, and you better believe that if that started happening all over the place, it would have been the LAST time ESET would be seen in my district. You spend all the time in the world instructing your client NOT to ever just accept a popup like that for security reasons, and then the actual security software goes and pulls a move like that? I hate to sound rash, but something like that happening WITHOUT even telling a customer it might happen seems a bit immature for a software company. Can you imagine if I even had even just 200-300 of my clients all of the sudden be faced with that. My tech line would be ringing off the hook all day long. It was bad enough that it blue screened 4 of the 20 test systems I tried pushing the upgrade to. I guess I need to know more information, please.

Thanks
Scott

 

Meaning, you are back with Avast as your AV ?

* If you want to go forward and do additional troubleshooting, please advise.

Regards,

 

From what software (nod ? windows ?) this pics comes.... i never seen it

Windows XP Home 32 bits

thanks

 

Pirhana,
The answer to your question is here

 

I do know how to set warning for MS update. May be my question is not clear.....

My question is about Drivers signing options, i had never seen this Drivers signing options windows with my XP home. This windows is from XP or NOD32 ?

T'es de Montreal, y'a pas un forum francais qq part ? J'aimerais bien m'expliquer en francais pour mieux me faire comprendre mais c'est anglais ici.

 

Please note below as previously posted regarding Driver Signing:

 

ok......... now i think i understand, i had the first windows but dont remember the second one

thanks

 

This is good, merci ! Are we to understand that the installation on your machine is completed ? Why this Driver Signing Issue has cropped up, I do not know for sure. Just force the installation regardless of the driver signing warning.

 

yes, v4.2.35 is installed and run well, ekrn.exe issue look like to be fix.

I will check more carefully these two windows when i will install the french canadian version

 

The new build, should fix the ekrn issues, someone from ESET would have to confirm this but I believe this to be true.
There are many new improvements to the new build that some outside of this Forum that are very pleased with.

Please advise if there is anything else we can help you with.

 

Aryeh,

Will this affect silent pushes to remote workstations (prompt)? We have 200+ users that freak out when anything "changes". I'd like to warn them if necessary....

 

I will tell you this, I am getting ALOT of blue screen issues when pushing this install out to upgrade my clients. It only seems to happen if they do not reboot for a few hours after the install, when the icon is orange recommending a reboot. I don't want to do more than a few at a time for now until SOMEONE answers my above question...I have never had that happen before (blue screening), even when upgrading from version to version for the last couple of years. In my environment, I cannot do a push and reboot during school hours. If they keep blue screening during the updates, I will have to figure out another deploy method for after school.

Update: the blue screen is coming from eamon.sys

Just an FYI...

 

Hello,

I have seen the message displayed twice that I can recall in 4.5 years at ESET, so it is something that occurs with very low frequency and is related to the driver signing options for the operating system. As Siljaline noted, it can be mitigated by adjusting the settings for that option.

It is always a good idea to do a test deployment to a few workstations before begining a mass upgrade to verify compatibility.

Regards,

Aryeh Goretsky