Jump to content

Samoréen

Members
  • Posts

    257
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by Samoréen

  1. I also have this error at the beginning of a Windows session :

    The Windows Security Center Service was unable to establish event queries with WMI to monitor third party AntiVirus, AntiSpyware and Firewall.

    Strangely enough, Windows is notifying me from time to time that both WIndows Defender and ESET NOD32 are disabled. But if I look in the Security Center, ESET NOD32 is listed as active (Windows Defender is disabled on my system).

     

  2. Hi,

    [running ESET NOD32 10.1.219.0]

    I'm getting this error multiple times (a lot) in the Event Viewer during a Windows 10 Creators session. The Windows Security Center usually says that ESET NOD32 is recognized but sometimes, I see that ESET is trying to re-reregister (the Eset icon has the "I" overlay and the home screen says that Eset is again trying to register). I have run the ecmd /registerav command (command accepted) but this doesn't change anything. Also, sometimes Outlook 2010 says that there's no antivirus installed (status : invalid) and if I check the WMI database at that time (using wbemtest), there's actually no antivirus registered.

    Any clue ? What could be the cause of the temporary "unregistration" of ESET NOD 32 ?

    Thanks.

  3. Hi,

    After the Creators update, I now have the same problem. I'm getting a bunch of error messages in the Event Viewer :

    Error while updating ESET NOD32 Antivirus status to SECURITY_PRODUCT_STATE_ON.

    I do have run ecmd /registerav command and the result was "command accepted". But this had no effect.

    I'm running version 10.1.219.0 of ESET NOD32.

    HKEY_LOCAL_MACHINE\SOFTWARE\ESET\ESET Security\CurrentVersion\Info | WscState doesn't exist in my system.

    Thanks in advance.

  4. Just now, Marcos said:

    These are not warnings, only notifications about submitted files that are not logged by default.

    You can disable logging under Tools -> ESET LiveGrid and turn off "Enable logging" .

    I understand but that's not the problem. I'm just bothered by all these suspected files that ESET is finding on my system. If I understand you well, these are Windows system files unknown from the current ESET version (because the last ESET update is older than the recent Creators update ?) and for which I should see these notifications only once ?

  5. Hi,

    Now that I have installed the Windows 10 Creators update, I am receiving a lot of warnings about "files" being sent to ESET :

    11/07/2017 17:45:33;ESET Kernel;File  'uefi:\\Volume 2\CpuDxe' was sent to ESET for analysis.;
    11/07/2017 17:45:35;ESET Kernel;File  'uefi:\\Volume 2\FileSystem' was sent to ESET for analysis.;
    11/07/2017 17:45:51;ESET Kernel;File  'uefi:\\Volume 2\CORE_DXE' was sent to ESET for analysis.;
    11/07/2017 17:45:53;ESET Kernel;File  'uefi:\\Volume 2\Runtime' was sent to ESET for analysis.;
    11/07/2017 17:45:54;ESET Kernel;File  'uefi:\\Volume 2\FtBbUpdate' was sent to ESET for analysis.;
    11/07/2017 22:40:04;ESET Kernel;File  'uefi:\\Volume 2\ASUSXBBUpdate' was sent to ESET for analysis.;
    11/07/2017 22:40:05;ESET Kernel;File  'uefi:\\Volume 2\ReFlash' was sent to ESET for analysis.;
    11/07/2017 22:40:06;ESET Kernel;File  'uefi:\\Volume 2\PciBus' was sent to ESET for analysis.;
    11/07/2017 22:50:09;ESET Kernel;File  'uefi:\\Volume 2\AmiBoardInfo' was sent to ESET for analysis.;
    11/07/2017 22:50:10;ESET Kernel;File  'uefi:\\Volume 2\ECDXE' was sent to ESET for analysis.;
    12/07/2017 11:47:38;ESET Kernel;File  'uefi:\\Volume 2\ECFWUpdate' was sent to ESET for analysis.;
    12/07/2017 11:47:39;ESET Kernel;File  'uefi:\\Volume 2\SIOBasicIODxe' was sent to ESET for analysis.;
    12/07/2017 11:47:41;ESET Kernel;File  'uefi:\\Volume 2\CpuInitDxe' was sent to ESET for analysis.;
    12/07/2017 11:47:44;ESET Kernel;File  'uefi:\\Volume 2\SmmBaseRuntime' was sent to ESET for analysis.;
    12/07/2017 13:02:00;ESET Kernel;File  'uefi:\\Volume 2\SmmDisp' was sent to ESET for analysis.;
    12/07/2017 13:02:01;ESET Kernel;File  'uefi:\\Volume 2\SmmThunk' was sent to ESET for analysis.;
    12/07/2017 13:02:02;ESET Kernel;File  'uefi:\\Volume 2\CpuPolicyDxe' was sent to ESET for analysis.;
    12/07/2017 13:02:03;ESET Kernel;File  'uefi:\\Volume 2\MicrocodeUpdate' was sent to ESET for analysis.;
    12/07/2017 13:02:04;ESET Kernel;File  'uefi:\\Volume 2\CpuSmmSaveRes' was sent to ESET for analysis.;
    12/07/2017 13:02:06;ESET Kernel;File  'uefi:\\Volume 2\CpuSpSMI' was sent to ESET for analysis.;
    12/07/2017 13:40:54;ESET Kernel;File  'uefi:\\Volume 2\SBDXE' was sent to ESET for analysis.;
    12/07/2017 13:40:55;ESET Kernel;File  'uefi:\\Volume 2\SBRun' was sent to ESET for analysis.;
    12/07/2017 13:40:57;ESET Kernel;File  'uefi:\\Volume 2\SmmChildDispatcher' was sent to ESET for analysis.;
    12/07/2017 13:40:58;ESET Kernel;File  'uefi:\\Volume 2\SmmChildDispatcher2' was sent to ESET for analysis.;
    12/07/2017 13:40:59;ESET Kernel;File  'uefi:\\Volume 2\AcpiModeEnable' was sent to ESET for analysis.;
    12/07/2017 13:41:00;ESET Kernel;File  'uefi:\\Volume 2\SleepSmi' was sent to ESET for analysis.;
    12/07/2017 15:14:47;ESET Kernel;File  'uefi:\\Volume 2\SBSMI' was sent to ESET for analysis.;
    12/07/2017 15:14:48;ESET Kernel;File  'uefi:\\Volume 2\PchSpiWrap' was sent to ESET for analysis.;
    12/07/2017 15:14:49;ESET Kernel;File  'uefi:\\Volume 2\WdtAppDxe' was sent to ESET for analysis.;
    12/07/2017 15:14:50;ESET Kernel;File  'uefi:\\Volume 2\ActiveBios' was sent to ESET for analysis.;
    12/07/2017 15:14:58;ESET Kernel;File  'uefi:\\Volume 2\IoTrap' was sent to ESET for analysis.;
    12/07/2017 15:15:06;ESET Kernel;File  'uefi:\\Volume 2\IntelLegacyInterrupt' was sent to ESET for analysis.;
    12/07/2017 15:54:09;ESET Kernel;File  'uefi:\\Volume 2\PchInitDxe' was sent to ESET for analysis.;
    12/07/2017 15:54:10;ESET Kernel;File  'uefi:\\Volume 2\PchSmiDispatcher' was sent to ESET for analysis.;
    12/07/2017 15:54:11;ESET Kernel;File  'uefi:\\Volume 2\PchPcieSmm' was sent to ESET for analysis.;
    12/07/2017 15:54:12;ESET Kernel;File  'uefi:\\Volume 2\PchReset' was sent to ESET for analysis.;
    12/07/2017 15:54:13;ESET Kernel;File  'uefi:\\Volume 2\PchS3Peim' was sent to ESET for analysis.;
    12/07/2017 16:57:55;ESET Kernel;File  'uefi:\\Volume 2\PchS3Support' was sent to ESET for analysis.;
    12/07/2017 16:57:56;ESET Kernel;File  'uefi:\\Volume 2\PchSerialGpio' was sent to ESET for analysis.;
    12/07/2017 16:57:57;ESET Kernel;File  'uefi:\\Volume 2\SmartTimer' was sent to ESET for analysis.;
    12/07/2017 16:57:58;ESET Kernel;File  'uefi:\\Volume 2\PchSmbusDxe' was sent to ESET for analysis.;
    12/07/2017 16:57:59;ESET Kernel;File  'uefi:\\Volume 2\SmmControl' was sent to ESET for analysis.;
    12/07/2017 16:58:00;ESET Kernel;File  'uefi:\\Volume 2\PchSpiSmm' was sent to ESET for analysis.;

    Anyone seeing the same warnings ? Any idea about what is going on ?

    Thanks.

  6. Hi Peter,

    59 minutes ago, Peter Randziak said:

    does the issue persist, if you switch to Pre-release updates?

    Yes, because switching to pre-release update had no effect on the program itself. Only the virus database was updated.

    Can you try close and browsers a e-mail clients, disable SSL/TLS protocol filtering wait a minute and enable it again?

    This didn't help.

    If the issue persists please enable the IMAP scan again, enable "Protocol filtering advanced logging" start the outlook and wait for a while, disable the logging and send me a private message with packed contents of the Diagnostics directory to check.

    Do you get any error or the outlook just stays in connecting state?

    Outlook says after a while that it cannot connect to the server.

    Which Diagnostics directory ? I only see one on my system : C:\Users\<me>\AppData\Local\Diagnostics. It doesn't seem to be related to ESET. Or do you want a Sysinspector log ?

     

  7. 3 hours ago, Peter Randziak said:

    I'm not 100% sure but I think it checks the resolution of an active window VS the display resolutions

    Thanks. You mean, it checks the size in pixels of the active window compared to the display resolution, I guess ? I have no such window active when the problem occurs.

    However, I do have some hidden windows that have dimensions corresponding to the screen display (or bigger : e.g. 1921x1201). They all belong to the system with exception of a couple of them belonging to Microsoft Office (Outlook).

    Since I didn't have the problem before version 10.1.204.0, maybe the detection algorithm has changed and is now mistakenly taking the hidden windows into account ?

  8. Further testing...

    No application running with exception of the ESET NOD32 UI, which is the only opened window on the desktop. I use the Alt-Tab combo a couple of times and voilà, the Gamer Mode switch is briefly enabled (becomes orange and then back to paused state) and after that I get the infamous "ESET requires your attention" message. I can reproduce at will.

     

  9. 10 minutes ago, Marcos said:

    Does turning off "Do not display notifications when running applications in full-screen mode" make a difference?

    No. It's even worse. Moreover, if I open the ESET NOD32 UI, switch to another app using Alt-Tab and switch back to the ESET UI (still using alt-Tab), I can see that the Gamer Mode switch is sometimes briefly enabled (becomes orange) and then switches back to Paused after a few seconds.

  10. 37 minutes ago, Marcos said:

    1, Try turning off the option to activate gamer mode if an application running in a full-screen mode is detected. Haven't come across other reports about this behavior manifesting when switching between applications.

    Gamer mode is set to Paused and the option named "Do not display notifications when running applications in full-screen mode" is checked. Anyway, the problem occurs even when no application is running in full-screen mode.

  11. Hi,

    Since installation of version 10.1.204.0 I keep seeing this message popping up from the system tray. Clicking on the notification has no effect (because actually there's nothing to pay attention to). This mainly happens when switching from an application to another using Alt-Tab (Windows 10 Pro 1511 64-bit).

    This is really exasperating since I found no way to stop this misbehavior. This, added to other bugs and to the fact that I'm now unable to temporarily disable protection when I need to (a bug that should already be fixed) questions the way the people in the quality insurance dpt. at ESET are doing their job. I have used ESET NOD32 professionally for many years and I never had such problems. Now each version is bringing its share of regressions and corrections take too much time to be released.

×
×
  • Create New...