Samoréen

Members
  • Content count

    139
  • Joined

  • Last visited

About Samoréen

  • Rank
    N/A

Contact Methods

  • Website URL
    http://www.ppphoto.fr

Profile Information

  • Gender
    Male
  • Interests
    Photography

Recent Profile Visitors

561 profile views
  1. HIPS and Anti-Stealth not working

    Sorry. You don't know which ones. Just try to re-install those mentioned in the thread I quoted. This always solved the problem for me (I have the same problem with each program update since version 9).
  2. HIPS and Anti-Stealth not working

    Leynaa, Try to re-install those that are marked as "unable to communicate with..." and those mentioned in the thread I mentioned. Re-installing a driver will do no harm anyway. Good luck.
  3. HIPS and Anti-Stealth not working

    leynaa, Did this issue appear after an update of ESET NOD32 ? In which case, have a look there : or here
  4. Problem solved by setting the Security Center service logon to System. Don't know why this had been changed.
  5. Re-installing Windows from scratch as well as all other applications and tools just to fix this issue is certainly not an option. WMI works normally on my system. Just, it seems there's a problem with the SecurityCenter(2) namespace. This issue is typically the kind of problem where all involved vendors are dumping the issue on each other. Since this problem appears with other antivirus software as well, I'm not saying that ESET is necessarily the culprit. But it's obvious that both companies (MS and ESET) should cooperate in order to diagnose the problem.
  6. More details about this : If I go to the Security Center in Windows, it says ESET NOD32 antivirus is turned on. Now if I use WMIC to enumerate the installed antivirus software, it says "No instance available". How is this possible ?
  7. 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).
  8. 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.
  9. 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.
  10. Andrey, You should look at these threads : I also have TMP / TEMP variables that point to a non default folder. This is my solution in order to fix that problem while waiting for a fix. Note that this must be done after each update. Since this is lasting since version 9, I'd really like a fix now.
  11. No change observed here. You should see with your provider.
  12. 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 ?
  13. 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.
  14. Where is this option located ? .... Never mind. Got it !