Jump to content

x7007

Members
  • Posts

    95
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by x7007

  1. 3 hours ago, Marcos said:

    When it comes to games and interactive mode, I'd start off by disabling gamer mode which prevents interactive dialogs from popping out. It is not a good idea to use both together.

    image.png

    it's disabled long time ago since the beginning. still happens that it doesn't open for programs or games. only after windows restart it remembers to open the interactive window.

  2. I tried playing forza horizon 5 and it kept saying new connection for every server/ip it wanted to connect, if it didn't show in interactive mode then it wouldn't even connect to the game server. SHAME, sometimes randomly it doesn't even pop-up the interactive connection menu and it doesn't connect to the server/game/program until I restart computer, then suddenly it shows up

  3. 7 hours ago, Marcos said:

    ESET supports DirectStorage as of v15.0. The above error is not caused by ESET, otherwise our driver would be listed instead of volsnap.sys.

    According to

    , temporarily disabling System restore should do the trick.

     

    Today I did some update to eset it did some update bar and %, and after the update I checked it again, system restore still on.

    It could be also update 2022-09 Cumulative Update for Windows 11 Version 22H2 for x64-based Systems (KB5017321) fixed it.

    C:\> fsutil bypassIo state c:\
    BypassIo on "c:\" is currently supported
        Storage Type:   NVMe
        Storage Driver: BypassIo compatible
     

     

    Detection Engine;25963;21/09/2022
    Rapid Response module;20975;21/09/2022
    Update module;1027;07/07/2022
    Antivirus and antispyware scanner module;1592.1;24/08/2022
    Advanced heuristics module;1216.2;06/06/2022
    Archive support module;1333.1;06/09/2022
    Cleaner module;1228;06/06/2022
    Anti-Stealth support module;1181;14/07/2022
    Firewall module;1428.1;22/06/2022
    Translation support module;1941;02/09/2022
    HIPS support module;1444.1;12/09/2022
    Internet protection module;1446;04/07/2022
    Advanced antispam module;7936;08/09/2022
    Database module;1117;24/05/2022
    Configuration module;2021.1;11/07/2022
    Direct Cloud communication module;1130;24/08/2022
    Rootkit detection and cleaning module;1032;18/01/2022
    Network protection module;1692;15/07/2022
    Script scanner module;1131;05/09/2022
    Network Inspector module;1048;20/01/2022
    Cryptographic protocol support module;1070;08/06/2022
    Databases for advanced antispam module;8500;21/09/2022
    Deep behavioral inspection support module;1118;02/02/2022
    Advanced Machine Learning module;1124;17/08/2022
    Telemetry module;1066.1;24/05/2022
    Security Center integration module;1037;02/06/2022

     

     

  4. When running the command it says error means it can't work. please update ESET to support Directstorage, as Bitdefender and Kaspersky still don't support it also, we can't risk security for performance. but we need this for anyone who has NVME.

     

    using version 15.2.17.0 

     

    C:\> fsutil bypassIo state c:\
    BypassIo on "c:\" is not currently supported
        HResult: 0x80820003 (BypassIO cannot be enabled while a volume snapshot exists)
        Driver:  volsnap.sys
        Reason:  One or more snapshots are active on the volume
        Storage Type:   NVMe
        Storage Driver: BypassIo compatible

  5. That was not the fixed.

    I've found the issue was with the Windows Software Protection service .  It's something with the windows activation .  If you are using non legit windows and some "activation" softwares then if it doesn't activate the windows properly it is causing this . that why many other people doesn't have this issue cause they have legit or using other kinds of activation .    When I activated the windows properly I didn't have this error anymore .  This error also effect computer speed cause it's a bunch of other things with the windows activation.

  6. 10 minutes ago, itman said:

    This issue is a mystery to me since I am running Win 10 x(64) and EIS 12.0.31 w/o such problem.

    I suspect this might be related to how the Win 10 1809 upgrade was performed? I performed the upgrade by doing an in-place upgrade from 1803 using a prior 1809 .iso file downloaded using the MediaCreator tool.

    I would suggest opening an admin level command prompt window and run this command:

    DISM.exe /Online /Cleanup-image /Restorehealth

    This will run for a while and will fix any system issues it finds with your 1809 build.

    I did all the dism commands. it didnt fix the issue.  maybe you don't leave ur computer 24/7?  my computer is staying on all the times. 

  7. 8 hours ago, horion70 said:

    Same issue here. It seems there is a compatibility bug with latest windows 1809. Tested on 3 windows 10 pro ver. 1809 computers with the latest eset version 12.0.31.0. The crash in ShellExperienceHost mostly happens when temporary disable and then enable eset or randomly when action center shows any message. Also when eset is disabled when clicking on windows message in notification center to enable, eset does not auto enable. The crash also showing in reliability monitor. I have temporarily unistall eset antivirus until the bug is fixed.

    Eset can u fix this please? it happened also with ver 11 eset common... 

  8. Hi,

    Since using Eset with Windows 1809 it started showing on the Event Viewer always the same error.  I just uninstalled Eset to test something and as soon as I installed it back again the error came back . exactly when eset finished installing the error showed up.   There is not really anything that crashing or showing anything that closed unresponsively but this error always show up only with eset installed.  it happened also with version 11 I think but with all 12 versions.  using latest version at the moment

     

    Can you check and fix it ?

     

    Faulting application name: ShellExperienceHost.exe, version: 10.0.17763.1, time stamp: 0x5b9c8bd8
    Faulting module name: Windows.UI.ActionCenter.dll, version: 10.0.17763.1, time stamp: 0x5b9c576b
    Exception code: 0xc0000409
    Fault offset: 0x000000000008fbaf
    Faulting process id: 0x1e6c
    Faulting application start time: 0x01d478ac9ddfad7f
    Faulting application path: C:\Windows\SystemApps\ShellExperienceHost_cw5n1h2txyewy\ShellExperienceHost.exe
    Faulting module path: C:\Windows\ShellExperiences\Windows.UI.ActionCenter.dll
    Report Id: 192f2d33-268e-4da6-b7a3-1e3a8f3666bd
    Faulting package full name: Microsoft.Windows.ShellExperienceHost_10.0.17763.1_neutral_neutral_cw5n1h2txyewy
    Faulting package-relative application ID: App

  9. I was having the same issue like galaxy ,  exactly the same. and there is a trace to start menu from event viewer.   It is ALWAYS the same error with the same numbers and it can repeat it self like 3-7 times in a row .    it seems somehow it has to do with the windows notification .   I couldn't open the Start Menu at all. it just didn't open , but the search did , if I went to the Windows 10 notification thing (pop up) or menu  and clicked on it, then somehow the Start Menu started working.    I think it was something with the Windows UI that couldn't detect Eset properly and stuck in the middle without completing some of it tasks and causing some time fail error , because also  SlashRose said windows didn't detect the ESET on the Windows UI center , so I think it's the same issues.   after reinstalling Eset Antivirus only it works fine without error for the time being .     Usually it happens when the system is idling a long time .    but before I reinstalled it happened like 5 times in a row, just before I uninstalled it.

     

     

    Fault bucket , type 0
    Event Name: MoBEX
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: Microsoft.Windows.ShellExperienceHost_10.0.17763.1_neutral_neutral_cw5n1h2txyewy
    P2: praid:App
    P3: 10.0.17763.1
    P4: 5b9c8bd8
    P5: Windows.UI.ActionCenter.dll
    P6: 10.0.17763.1
    P7: 5b9c576b
    P8: 000000000008fbaf
    P9: c0000409
    P10: 0000000000000007

  10. On 11/20/2017 at 5:49 PM, Marcos said:

    The reason for the change is that Windows will sometimes delay sending TCP ACK to the point that the active connection would stall. Despite numerous appeals and released fixes the problem was never solved completely. This is only happening with ESET's network drivers installed. We're changing this value to force Windows to send ACKs more often as a workaround.

    It doesn't affect protection.

     

     

    Can I change it back to N/A instead 1 when using Eset Antivirus only ?  Without the internet Security Firewall ,  just the ESET Antivirus Edition.

  11. 6 minutes ago, Marcos said:

    I don't think this will change since with TcpAckFrequency set to 1 the performance is much worse. Honestly, you are the only user that I've heard of where the behavior is opposite.

    Because when  ESET set it from Default n/a which is nore 0 or 1 .   then it uses less UPLOAD speed.   my connection is 500mbit/10mbit  so I am very limited with upload .     ESET changing the TcpAckFrequency to 1 uses more UPLOAD speed because it send more upload because how it works .     

    The question is if I install ESET and it changes the registry to 1  , can I set it to Default n/a like it was without ESET without causing issues with the ESET Firewall or protection ?

  12. 1 hour ago, Marcos said:

    We added the option to maintain inactive TCP connections to solve certain issues in the past. If you don't experience any issues with this option disabled, you can keep it disabled.

    ok,

     

    So this is the fix for the WFP Compability , need to keep it disabled and RSC works fine.. finally I've found the issue.

     

    Also another question . Can ESET work without TcpAckFrequency  set to 1/Disabled ?     because it effect the performance of my connection.     When installing ESET it changes automatically the setting.

     

    What happens if ESET is installed and set automatically TcpAckFrequency to 1  and I change it to  TcpAckFrequency default n/a  ? which means it doesn't exist.  would ESET won't work properly or causing issues ?

×
×
  • Create New...