Jump to content

PhilS

Members
  • Posts

    2
  • Joined

  • Last visited

About PhilS

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    USA
  1. Sorry I should clarify... I'm not familiar with ESET. The product was on its way out of our company when I started, so I can't say one way or another. But it should be stated that I don't know the first thing about it other than being asked to remove it. I believe it was just a business decision there were no functionality complaints I am aware of. That being said I wanted to clarify my question, when I search machines that have it installed via our LabTech installation, I'm seeing both ESET Endpoint AV and ESET NOD32 installed. Meaning those are still there. The question I'm asking is if I manually change the registry key to allow the 2018-01 MS updates, will ESET apps running on those machines cause the bluescreens/no boot situation described in some of the MS articles? Basically the only reason for the reg key is to prevent the update from running on a machine that has AV that could cause bluescreen/no boot situations because it is addressing the CPU/memory in such a way that will cause these errors after the MS update is applied. Worded in another way, Webroot told us day 1: "We don't have a patch to change the registry key, but our product is already compatible with the updates, so please manually change the registry key and get updated". The crux of my question is whether or not the same is true with ESET.
  2. Are old versions of ESET/NOD32 compatible? Reason I ask is we have some clients that are no longer using it but the agent was left installed due to uninstallation issues we have yet to be able to resolve. I'd like to release their ability to get the updates by changing the registry key but I wasn't sure if previous versions are compatible with the 2018-01 MS updates. I'm presuming they are since it seems the change identified for your new version is simply the registry modification.
×
×
  • Create New...