Jump to content

SCI

Members
  • Posts

    6
  • Joined

  • Last visited

Posts posted by SCI

  1. 5 minutes ago, FRiC said:

    I tried exluding *.mui which didn't work, and it seems to be for a different product any way. For me it's random which servers (not just dc) it affects, and also rebooting many many times sometimes bring the server back. Servers that didn't get affected the first time may also not boot the next time.

    Since a new ESET installs don't require reboots, what I ended up with was removing ESET in safe mode using the uninstaller tool, then clean install. Will see what happens next Patch Tuesday.

    Thanks for the info. We have a lot of servers, so manually doing an uninstall and clean install on each will take too long. Making the issue more complex is that these are Azure VMs, so all we really have are boot diagnostic screenshots to see what's going on. Going the safe mode approach really isn't an option. I guess we'll have to wait until the next build is released.

  2. 2 hours ago, Marcos said:

    Does the problem persist with the engine released after May 23?

    The server won't boot with v9 installed, so there's no way for me to test anything released after May 23. I have to restore a snapshot of the entire server with the old ESET version in order to get it back online.

  3. 4 hours ago, Marcos said:

    The only issue that I'm aware of was the one related to processing MUI files and it was already fixed on May 23.

    This is for ESET Server Security v9.0.12012.0, the latest version (according to your website) which was released on May 4, 2022. When this update is pushed to a Windows Server 2022 domain controller, the server will get stuck at "Waiting for Computer Settings" forever after the installer restarts the machine.

    Since this version predates the May 23 date you referenced, do we need to manually add an exclusion for *.mui files?

×
×
  • Create New...