Zardoc

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.

No issues with build 22631.2715. Security Center starts promptly.

No issues on Win build NO issues on Win build 22631.2506. Security Center starts promptly.

Trickling in.

@pete12, sometimes we don’t understand the implications of coding, especially with security software. You can’t always say, let’s add a comma to the line and it’s fixed. MS has stringent settings for security and also updates their code on the OS. So, what Joseph explained is that he sees the problem and is trying to see where the code doesn’t align with the Security Center and they will try to fix the problem on their end (if it is their problem). Pushing people to fix something fast is never good. It frustrates everyone and is a waste of time. It’s like making a soufflé. “The hardest part of making a soufflé is when you incorporate the beaten egg white with yolks, and the rest of the batter. You have to be very careful to fold the egg whites slowly, so that they don’t melt.” 😜 When people take their time to fix something, the chances of success are better. Getting an explanation acknowledging the issue and trying to find a fix tells us at least someone knows about it and they will try to fix it as soon as it is possible.

Hi JosefG, Thanks for the the explanations. I hope you can sort it out. I'll just tell my customers to be patient. AV works fine. It's just cranking the engine takes more time and the carburetor needs an adjustment. That's an explanation they'll understand. 🙂

So, I tried to keep calm and did my own testing. Security Center does work, but with version 17 it takes 2 minutes for it to start hence the messages in security Center NOD Security Center 2 minutes 2023-11-22_22-44-05.mp4

I've been on this forum way before it was just an Eset Forum and I even recommended Eset on my own website for many years. Aryeh knows me and I usually don't post because there's nothing good on TV. I install Eset on all my customers machines and my customers are important. I hope Eset sees it the same way. So, I am not asking if I should ignore error messages. They aren't publicity messages. When they show up it means something is wrong. Is it major? I don't think so. Am I going to ignore it ? I'm trying not to. But with the kind of comments I'm getting and with the experience I have I'm close to dropping this and running back to version 16. I gave a full log and it showed clearly Security Center was not turned on. So my question is simple @Marcos why is version 17 not turning on the security Center on boot and is Eset looking for a fix? So if you want to keep giving replies that have no foundation to getting a fix, i'll get back to my customers and install something else until I see someone cares because it doesn't seem like it. 🙄

On every reboot, it's shows security center not started. So this is update v17 related. None of this with v16.

When update to V17 security Center doesn't start on BOOT.

Just updated without touching anything except update package.

If you look hard right on your image, it's stopped. So same issue.

Hi Marcos, I did not change that setting. It changed to that after update. So, there is that is turning off the security center with this update. I installed Version 16 and the security center works fine. Why is it not starting after this update. That's something that either the update or a command in the coding is not right with Windows perimeters and doesn't turn on the security center. I and I'm sure neither of those who posted have messed with the Security Center settings, before or after install.