itman

If you reside in one of the countries listed in the above KB article, you should be able to disable auto renewal as described here: https://help.eset.com/home_eset/en-US/license_autorenewal.html

It means that the Eset previous feature which auto detected Eset predefined financial web sites and opened a new browser window in Banking & Payment Protection mode has been eliminated. This processing was the case in previous Eset versions when the Secured all browsers option is disabled. Current Eset release options are either enable Secure all browsers option, or manually open a Banking & Payment Protection mode browser session via Win desktop Eset B&PP icon.

I also have suspicious this issue is related to Eset's ELAM driver, eelam.sys, since this is what Windows uses in WCS processing in regards to verifying third party AV/firewall use. This driver appears not to have been updated recently and might not be compatible with new Azure code signing requirements?

I will also note that the issue appears to be different for Win 10 versus Win 11. On Win 10, all I observe is two Win event log entries; one for AV database and one for firewall database, being created at system restart time. The same event log entries are not created via Win fast startup mode. Everything else system-wise appears to be fully functional. Eset AV and firewall registration in WSC is OK and all Win related services are active.

The first thing you need to do is contact your ISP and verify what equipment they issued to you. It appears that you are using a modem versus a combo modem and router/gateway unit which is the norm these days in network communication devices issued by ISP's. All a modem does is allow your PC to connect to the ISP's network. It has no capability to set up a local subnet network and monitor its internal communication. Standard network security practice is to connect a standalone modem to a router which in turn is connected to your PC. Router's also include a hardware based firewall and optionally, IDS protection. As far as how Eset Network Inspector reacts when interfacing with a modem, it appears it is identifying all external devices currently sharing the ISP network. In other words, Network Inspector use with a modem only connection is non-applicable.

@Marcos would have to load ver. 17.0.13 into Early Access section of the forum for you to download it. The question is how did you access ver. 17.0.13 in the first place to perform on-top upgrade of ver. 16.2.15?

The first thing that needs to be done is to verify that these smartphone connections actually exist on your gateway/router. Open your gateway/router GUI interface via browser; e.g. http://192.168.1.254 or what whatever your IPv4 gateway IP address is. Now search for these smartphone device connections. One reason for such smartphone connections existing on your gateway/router is visitors ask to use your Wi-Fi connection and set up their smartphone on your gateway/router.

👍

After years of frequenting this forum, I can state with confidence the following. Eset "silence" to a posted problem means; 1. Yes. its a problem. 2. Eset doesn't want to discuss/admit the problem publicly.

Ahh ............. No B&PP protection. No new Browser Privacy & Security protection. I guess the labeling "essential protection" sums up its features.

Great! Also, past postings on this issue stated a system restart did resolve the issue for most users.

In ver. 17.0.15, the Browser Protection module also controls Banking & Payment Protection functionality. If you are running Eset with "Secure all browsers" option enabled, when you open Chrome, Firefox, or Edge you should see the green border with "X" symbol on the right hand side of the web page. If this is the case, you can assume Browser Protection is operational.

In Eset GUI Advanced setup setting, open Advanced options and perform the following. Verify that AMSI setting is enabled per below screen shot. If not, enable it. If AMSI setting is enabled, toggle the setting off and then on. Is the problem now resolved?

The OP is stating the HIPS option is missing in Computer Protection section on his Eset installation. However, the HIPS option appears in Advanced setup settings under Detection Engine settings and appears to be fully functional.

Eset HIPS settings are accessed via Setup -> Computer Protection.

I can connect to the web site w/o issue using Firefox;

I don't have an Eset Server product installed but I assume the below client firewall rules are still applicable. Eset firewall has two default rules in regards Win shared file and printers; one for outbound activity and one for inbound activity. Below is the default outbound rule; This outbound rule is applicable to all Eset firewall profiles. However, the corresponding inbound default firewall rule only allows inbound network traffic for the Eset Private firewall profile.

The only way I know of to exclude drivers from Windows Defender is to add their respective .sys files to WD's real-time scanning exclusion list. First, verify this is how it is being done. If it is not being done this way, post how it is being done.

Problem resolved. I had previously did testing in regards to ver. 17 prior to official release which resulted in my doing multiple ESSP re-installations. I forgot to perform an Eset GUI HIPS "Allow all drivers to load" setting reset to clear all drivers listed. Appears Eset was loading all those drivers into memory for only God knows why. BTW - this Allow all drivers to load setting never worked right. Per Eset on-line documentation; The driver list is supposed to be empty after Eset installation. In reality, the reverse is the case with the list populated with all existing drivers.

Appears that's the case ....................🙄 Sorry, meant ver. 17.0.15.

This is a ver. 17.0.5 first. Browser protection module missing from this NOD32 installation.

Did this yesterday and so far haven't seen a problem. However, ekrn.exe after sytem startup and Eset scan processing completes is using around 100 MB of memory on Win 10 x(64) 22H2 . This is 2.5 times larger than used in Eset versions prior to 17.0.15.

Prior vers. of ESSP always used approx. 40 MB of memory. Earlier today I check ekrn.exe and it was using 87 MB of memory. Just checked it again and its using 129 MB of memory. Now I am running Secured Browser in always on mode which I didn't do in the past.

Sucuri scan is clean: https://sitecheck.sucuri.net/results/https/samples.rebackoffice.com/client/eleven-seventeen-interactive-stacking-plan/ .

The problem here has nothing to do with VPN usage. In fact, the only person who posted in the forum using a VPN resolved the issue: https://forum.eset.com/topic/38859-limited-direct-cloud-connectivity-issue/#comment-176295