Jump to content

Zardoc

Members
  • Posts

    117
  • Joined

  • Last visited

About Zardoc

  • Rank
    Newbie
    Newbie

Profile Information

  • Gender
    Male
  • Location
    Canada
  • Interests
    Mad Scientist

Recent Profile Visitors

1,646 profile views
  1. @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.
  2. 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 ?
  3. @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
  4. Thanks Marcos. So to make this simple, we can remain on V16 without issues and eventually a v17 fix will pop up ? Thanks
  5. 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.
  6. 22631.2715 has the smart screen updates (windows11.0-kb5032190-) and the error is not showing up. I will upgrade to RP build now.
  7. No issues on Win build NO issues on Win build 22631.2506. Security Center starts promptly.
  8. @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.
  9. 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. 🙂
×
×
  • Create New...