Zardoc

Thanks Marcos

Hi, Just got an update for the Everything-1.4.1.1026.x64 I get messages Failed to execute Admin command and failed to execute User command. How to circumvent this please ? Link to site Thanks Added note: MSI installed fine.

Thanks Marcos. 🙂

Thanks Marcos. don't have a link by any chance ?

There is a new version 17.1.9.0 Is there a download link plz ?

Hi, When is the next update with a permanent fix?

@Marcos, Why is this taking so long? Even if this is not a serious issue it just makes Eset loose credibility on a lagging issue. I have around 40 licences circulating and my customers don't like problems especially with their anti virus.

Hi,Is there an update on this issue ? Seems to be really long to fix. 🙄

I understand your answer and thank you for responding.

I must say that first I am very upset that Marcos did not follow up on my question. I am a long time customer and I re-sell the AV to many users. Now, I need a straight answer from someone. Does this anti Virus version work properly event though it is popping up error messages ?

@Marcos, I am installing a lot of NOD32 on my customer's machines. Despite the error message, is there something that is preventing the antivirus from doing it's job properly ? In other words, can a user run it without any issues ? If not, how do I keep the software from upgrading to v17 ? Thanks

Thanks Marcos. So to make this simple, we can remain on V16 without issues and eventually a v17 fix will pop up ? Thanks

OK, This is what I noticed; When I upgraded to V17 on build 22631.2506 of Windows, after reboot security center starts right away. Same thing for all updates added after the fact up to 22631.2787. If you are running 22631.2787 and then upgrade to v17 then error 16 and then 19 pop up in the viewer and after that a 2 minute delay is noticed (on my machine) before Security Center kicks in on every boot. What I did notice when I upgraded to V17 on build 22631.2506 was that Event error 19 showed up right away but did not cause delays with Security Center. It started right after boot. So there's something funky in V17.

Updating:

22631.2715 has the smart screen updates (windows11.0-kb5032190-) and the error is not showing up. I will upgrade to RP build now.