Dun

It is not very unusual to have issues with latest version of web browsers running in sandbox. That is one of the reasons why I mentioned Firefox ESR and sandboxie 1.4.2 (currently next to last SBIE version)

I created new discussion on Sandboxie Github https://github.com/sandboxie-plus/Sandboxie/discussions/2383 as well

Sandboxie-Plus 1.2.0 introduced new feature: "Use a Sandboxie login instead of an anonymous token". However, enabling it prevents HTTPS websites loading. Further explanations how "Use a Sandboxie login instead of an anonymous token" works: https://github.com/sandboxie-plus/Sandboxie/discussions/2064 Sandboxie developer DavidXanatos asked to create a thread there asking ESET developers to look at the issue. He suggested that there might be an old workaround applied on your security software for the old Sandboxie versions: https://github.com/sandboxie-plus/Sandboxie/issues/2025#issuecomment-1196343325 Original issue posted on the open-source Sandboxie repository: https://github.com/sandboxie-plus/Sandboxie/issues/2025 Requirements to reproduce the issue: - Operating system: Windows 11 22H2 // Windows 10 Enterprise LTSC 2021 x64 (21H2) (10.0.19044.1806) - Sandboxie Plus 1.4.2 // 1.2.0 x64 - ESET Endpoint Security 9.1.2060.0 // Eset Internet Security 15.2.11.0 x64 - Firefox 102.4.0esr x64 // Microsoft Edge 106.0.1370.52 x64 Firefox shows PR_END_OF_FILE_ERROR, Microsoft Edge ERR_CONNECTION_CLOSED error Steps to reproduce: 1) Install Firefox, Edge, Sandboxie 1.2.0 or newer, ESET and make sure SSL scanning is enabled. Firefox download: https://www.mozilla.org/en-US/firefox/enterprise/#download Microsoft Edge download: https://www.microsoft.com/en-us/edge/business/download?form=MA13FJ Sandboxie download: https://github.com/sandboxie-plus/Sandboxie/releases/ 2) Run Edge/Firefox in any sandbox and visit any HTTPS webpage to confirm it will load correctly 3) Close all sandboxed apps 4) Run Sandman -> Options -> Global settings -> Advanced config -> Enable 'Use a Sandboxie login instead of an anonymous token' 5) Run Edge/Firefox in any sandbox and visit any HTTPS webpage to confirm it will NOT load correctly Due to this incompatibility issue, since Sandboxie versions 1.2.7 the "Use a Sandboxie login instead of an anonymous token" is disabled by default.

This has not been fixed:

I would like to find simple way of stopping all files in a specific folder accessing/communicating with the web. I have worked how to do it for specific .exe files but it is laborious doing it for several. Any ideas appreciated.

https://forum.eset.com/topic/23723-after-enabling-virtual-machine-feature-the-pc-bsod-every-start/?do=findComment&comment=114743

Rename C:\Windows\System32\drivers\eamonm.sys in safe mode (I also renamed C:\Program Files\ESET\ESET Security\Drivers\eamonm\eamonm.sys) in safe mode, start in normal mode, revert changes, upgrade as per guide. Works fine

Thank you for your support. However the issue is very easy to reproduce with smart security or internet security and I have already provided way to much unnecessary information about my computer

I was able to narrow down the issue. Take huge executable file and create firewall rule about it. Make sure to enable it. When you click ok to apply settings you will see it will take much much longer than usually. But this is not yet the cause of the 100% core usage by ekrn.exe. After that create any other firewall rule and enable it. When applied - there you go, CPU core is fully utilized and network is unusable. To revert it, just disable (do not delete) the rule about huge size of the executable file. If you will not disable the problematic rule then after 15-30 minutes the CPU usage will go down but raise again hours later for some reason. Also it will raise at computer startup and waking up from sleep mode. Please let me know when you can fix it

Please check PM. Should I provide the esetperf.etl as well?

I forgot to mention that if I restart my machine network protection does not work. It takes over 10 minutes to calm down the cpu usage by ekrn.exe, then the protection lights green. Please find logs in PM.

Hello Whenever I change Eset Endpoint or Eset Internet Security from default to custom, I notice ekrn.exe uses 100% of one of cpu cores for 20 minutes. It happens when I start any application which connects to the internet like Chrome or VPN. It does not happen with default settings. All settings I change is do not clean malware if found in files and ask the user, network settings to public network and block couple apps in firewall. It does not matter if I do it with Endpoint or Internet Security or if I change settings manually or import configuration file. Event log does not show any errors. It started happening after windows updates 3 weeks ago. What should I do about it?

I also had issue with firewall which started with delay of 20 minutes. After repairing .net framework and restarting the computer, everything went fine this time

Google Chrome is up to date Version 80.0.3987.149 (Official Build) (64-bit) I can not provide logs. Eset causes so high cpu usage I can not move mouse properly. Every app hangs completely. It also breaks my internet connection. Not sure if I should see eset component/driver in network card properties How can downgrade to EIS 13.x previous build?

Same problem. Latest Eset internet security build cause the issue

I have the same problem since I restarted the computer. Reinstalling did not fix it

I resolved this by blocking access to all LAN IPs except mine and router/AP IPs. For some unknown (to me) reason I had to use 2 firewall rules: one Local hosts rule and one Remote hosts rule. Weird

Hello, I use Win10 x64 Pro && ESET SS 9.0.349.14 x64 && Firefox x64 44.0.2. I've tried everything to get SSL filtering working with FF, but ESET simply doesn't filter it. SSL certificate in FF is missing, as well as Firefox executable from %ProgramFiles% on ESET SSL filtered programs list. On EICAR tests using HTTP file access is blocked in browser (access denied) while using HTTPS files are blocked in %temp%. How to resolve this? BTW: using ESET website I send a question to support:

Yes, LAN_Atheros_Win7_64_VER21021 [16.07.2013] 7-8.1 x86/x64. It's Qualcomm Atheros AR8152/8158 PCI-E Fast Ethernet Controller. I always set custom DNS (different than ISP defaults, but the same custom DNS are set up on the router). Static LAN IP set up on the router as well, auto-detect on windows. IPv6 and file and print sharing for Microsoft Networks network card components are disabled. I always use the same configuration (for at least couple years). No, www.eset.com starts working with delay too. No. edit@: I just did. Uninstalling network adapter drivers and installing them again fixed the issue. Now if I disable the adapter, wait a bit and reenable it, it takes 2, maybe 3 seconds to get the Internet connection back. Startup apps do not show up Internet access errors anymore. Thank you for help. I can't believe it was so easy to fix...

Hello, I had this issue 3 times: once on Windows 7 and ESET 8, later on Windows 10 preview builds and ESET SS 8 pre-release updates, and finally now on Windows 7 again. I had ESET SS9 beta, then used uninstall tool and installed ESET 9 stable. Without ESET on clean Windows installation as well as with ESET installed for a first time, it takes up to 10 seconds to connect to the internet. The easiest way to check that time is to disable and re-enable currently used network adapter in device manager. After using the uninstall tool and installing ESET 9 stable it takes 90 seconds to connect to the Internet. Also the startup programs can't connect to the Internet at OS startup and gives me annoying popups. I've tried to use the following Microsoft FixIt tool: https://support.microsoft.com/en-ie/kb/299357 but it did not help.

Hello, I use ESET Smart Security 9.0.141.0 beta. DHCP range on my router is set up to 192.168.1.2-192.168.1.252. The router address is *254, AP address is *253. I have firewall in 'Interactive mode' to control apps internet access. I want to block ANY incoming and outcoming traffic from and to other hosts in the same network. I marked home network as public (same for any new networks without asking). Firewall rules I've tried to add manually: 1) 192.168.1.2-192.168.1.252 range in 'local' tab in IP field, direction 'both', action 'deny', protocol 'any', notify user 'yes', 2) Adding 192.168.1.2-192.168.1.252 range to new 'zone' first and then select the zone instead of IP range in rule editor. None of them worked, I still could send ping requests and got replies. I will appreciate any given help