Kimiya Kitani

I have been able to confirm here is that for macOS Ventura 13.5.2 and 13.6 devices with ESET 7.3.3600.0 installed, on September 27, 2023, a yellow warning message prompted a reboot, and the reboot After the reboot, ESET Web&E-mail, which is present in the VPN settings, stopped working, and this caused the inability to connect to the Internet, which was also reproduced on several terminals. The network was restored by removing ESET Web&E-mail in the VPN settings and disabling ESET. Subsequent installation of ESET 7.4.1100 solved the problem. Perhaps something in them was broken because the problem occurred when the ESET module or per-definition file was automatically updated (ESET itself was not updated). Since the problem is fairly easy to reproduce, one wonders why it was not noticed in the testing phase before the release of the latest modules, etc., in the previous version (but there is no release information for 7.4 on this forum). The following screenshot, taken only from the Japanese version, is a warning that appeared today in ESET 7.3.3600. If you reboot with this warning, it means that ESET is the cause of your Internet connection failure. The main messages in the figure below are as follows Attention. All modules are up-to-date We recommend that you restart your computer

Hi Kurt Dodill! Awesome! Yes, I downloaded 7.4.1100.0 and installed it manually, and the reboot warning disappeared and it appears to be working fine. So it must be an ESET problem. I need to do some more testing, but I think I can get by with this.

Hi, Mr. Marcos Recently, I have not updated my operating system (macOS 13.5.2) and I got a warning to restart ESET, so I restarted it and now I have a problem. Is this a macOS problem? If it affects all Mac users, all Mac users need to disable or remove ESET. The impact is too great. Is there any way to temporarily disable ESET so that when the problem is fixed it can be re-enabled again without having to install ESET?

I am attaching an English screenshot of the ESET error message dialog again with the English UI and a screen shot of the settings where you can disable ESET. ESET Web&Email protection under System Settings > Network > VPN (turning this off will disable ESET and allow you to connect to the Internet. (However, you will need to reinstall ESET to be able to use it again). My Mac OS: macOS 13.5.2 and 13.6

After applying today's update and rebooting, my colleague and I received an ESET startup error and could no longer connect to the internet. The following Japanese message is as follows: "All modules are up-to-date" "We recommend restarting your computer" As a matter of urgency, we removed the ESET proxy system (disabling ESET) and were able to connect to the net. System Settings > VPN > Delete ESET VPN setting. Then I reinstalled ESET 7.3.3600.0 and activated it and no problem there. After updating and rebooting, I get the ESET error(attached file: "Error: A communication error has occurred. again and can't connect to the internet.") This is a serious problem.

I think I solved this problem by re-creating the policy presented by Marcos (I have only checked it on the device I have yet). I will apply the new policy to the whole system and see how it goes. [Operation] 1. I prepared ESET 10.1.2050 which had blank Firewall rules and an IP set 2. create a new policy from the ESET administrator server and apply the re-created policy 3. Wait a while (a few minutes) 4. My defined FIREWALL rules and IP set were displayed on the ESET client. From the above, I still think the policy was too old. Thank you for Marcos!

Here is the report as of now. I have not yet had time to try creating a new policy as presented by Marcos. At this stage, we have upgraded our ESET management server from 9.1 to 10. ESET PROTECT (Server), version 10.0 (10.0.1129.0) ESET PROTECT (Web Console), version 10.0 (10.0.133.0) Then create and prepare the installer. 1. delete ESET and reboot 2. install ESET ( 10.1.2046 ) 3. wait for the module to be updated 4. upgrade to 10.1.2050 was indicated. Reboot the terminal After doing this, Firewall related policies remained blank. When I revert to 10.0.2045, the Firewall related policies come up as configured on the management server. Now I am wondering if I need to re-create the policy once on the management server. However, I will be out of the country for a while, so I will try this after mid-September.

I have not updated the management system because it is still taking some time due to the circumstances of the outsourced management company yet. At this time, we have applied for the beta release and set the version of the firewall module to 1439. However, there is no change in the situation. Both the firewall rule and IP set in the ESET management server's policy settings are blank, and there is only the default rule on the ESET side in the case of version 10.1.2046.0. Uninstalling and reverting to one previous version will apply the policy and return to normal.

I have not found a drastic solution at this time, but I have found a tentative workaround. After updating to 10.1.2046 version, I checked the Firewall log and noticed that DHCP (69/udp -> 69/udp) is blocked. Then, looking at the default rules of firewall, I noticed the following permissions for inbound, but not for outbound. So I added a rule that grants permission to outbound, and the problem was solved. Allow DHCP for svchost.exe Local ports: 67, 68 /udp SYSTEMROOT\system32\svchost.exe Allow DHCP for service.exe Local ports: 67, 68 /udp Remote ports: 67, 68 /udp SYSTEMROOT\system32\service.exe Allow IPv6 DHCP for svchost.exe IPv6 DHCP Local ports: 546, 547 SYSTEMROOT\system32\svchost.exe Remote pots: 546, 547 However, for the my device, after updating the firewall settings from the ESET server, the FIREWALL rules for the client devices disappeared, as shown in the forum below. Only the defaults are in place. This does not change after removing and reinserting ESET. I also tried it on another terminal and it did not destroy the FIREWALL rules on that one, especially on the client. This is the part I am wondering why. Firewall rules may no longer apply due to a change in settings in another policy that is not related to firewall settings The ESET management system is using ESET PROTECT (Server), version 9.1 (9.1.1296.0), which is a bit old, so I am planning to change it to 10.0.15.2.

Also, when waking up from sleep, the following dialog message “the network has been changed.” is displayed. The network is blocked and cannot be connected unless the firewall is temporarily disabled.

Yes. As shown in the screenshot below, the Firewall module uses 1438.2.

The problem is not reproduced on the previous Windows version 10.0.2045.0. Problem: A network connection is blocked when ESET Windows version 10.1.2046 is running on a terminal that is not connected to the network. Workaround: Temporarily disabling ESET FIREWALL will allow network connections. Thereafter, the network connection will remain open even if ESET FIREWALL is enabled. However, if the network connection is turned off, the computer is started, and ESET is running, the network connection is blocked. The problem occurs with both new installations and updates of Windows version 10.1.2046. Reproduced on multiple devices. Downgrading to the previous Windows version 10.0.2045.0 does not reproduce the problem.

Excellent. Thank you very much. I was able to install ESET 7.1 using that repository link!

Thank you for presenting the site. I was able to download until version 6, but since version 7 I can only download via the repository. Reference: https://forum.eset.com/topic/32717-eset-endpoint-antivirus-for-macos-version-7117000-has-been-released/ == ESET Endpoint Antivirus for macOS 7.1.1700.0 has been released. The current version is available only for managed environments from the ESET repository. ESET Endpoint Security will be released later. == Do you know where to find this managed environments from the ESET repository? I am using the Japanese version of ESET's management server, but I am restricted from using the English repository (the distributor says this cannot be removed).

I currently have a contract with ESET Endpoint at the university and our department uses it. However, all language resources except Japanese has been removed by the company that the university contracts. ESET supposed to be multilingual, but only Japanese can be installed. This means that the repositories that can be managed by the ESET Management Server are also only available in Japanese. There are many English speakers at Japanese universities, so I want to support the resource in English at least. Currently the Windows version can download products from eset.com, but the Mac version is now repository-only. Therefore, the Mac version of the English product is not available in Japan.