Kimiya Kitani

I'm not sure what happened when the problem occurred, but I'll check again the next time it happens.

I have attached a screenshot. When the problem occurred, I checked it on several devices, including those of other staff members. When I checked today, it had been fixed.

The site for downloading Eset is displayed strangely. Isn't the display strange at https://eset.com, too? It may be a CSS problem, but I think the information is generally not visible.

Since then, we have received no more inquiries about the trouble, so we have determined that this policy setting has brought it under control. Thank you for the information.

Thank you for the replay. Yes. There are no particular problems such as being unable to print, but some users have contacted us saying that warnings have started to appear. I added a policy in the admin console to exclude spoolsv.exe from application modification detection. I'd like to see how it goes.

Thank you for the reply. Is there a policy setting (Admin Console) that does not display this warning?

ESET Endpoint Security 11.1.2052.0 Windows11 I heard from some users that their PCs suddenly started getting the warning in the attached file (English translation below). It is not always present and cannot be reproduced. Then, it doesn't affect communication in particular. Do you know why this warning came out of nowhere? == English translation in the warning dialog message == ESET suddenly warns, "The application has been modified." One of the rule applications (spooler subsystem application) has changed. If you are unsure whether this change is legal, disable any previously created permission firewall rules. Application path: C:\Windows\System32\spoolsv.exe (PID 5536) Signatory: Microsoft Windows Publisher: Microsoft Corporation Evaluation: Detected 2 weeks ago Disable Allow Firewall Rules? ===

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.