Jump to content

Uxorious

Members
  • Posts

    8
  • Joined

  • Last visited

Everything posted by Uxorious

  1. So the base problem is indeed not ESET (even though clearly MS would like something to be different according to the event viewer). Apparently something in the update 4 days ago made this happen for a lot of people. The solution is to add a new/different registry key to enable LSA. No idea why this is now needed. https://www.elevenforum.com/t/enable-or-disable-local-security-authority-lsa-protection-in-windows-11.11104/#post-274436
  2. The one it complains about is eamsi.dll, but it actually has multiple signatures. That top one looks good, but the bottom one can not be verified.
  3. After updating Windows 11 the other day, Windows 11 now complains that Local Security Authority Protection is off. Looking into the errors in Event Viewer, it looks like the cause is that ESET binaries are not properly signed. Anybody else seeing this?
  4. How can we ask to have this be considered? WSL will soon be out of beta, and power users will increasingly rely on that environment for their work.
  5. I will leave pre-release on then - I can spend the 30 minutes to find a workaround/disable ESET if something bad happens. However, I don't understand the 2nd part of your quote. 2 posts earlier you said we can currently NOT go back to the release version until something else is fixed. Do you mean that we *normally* can go back, but right now you have another bug that prevents that from working?
  6. For keeping pre-release updates on, what is your definition of a non-production machine? I'm using my PC daily ... is that a production machine? What is the risk of keeping pre-releases on?
  7. I installed a clean Windows 10 Pro (1703) and ESET Smart Security 10.1.204.0 today, and I'm seeing the same problem :-(
×
×
  • Create New...