Unable to access internet in Google Chrome

[Haresh2015 3]

Dear Sir,

    Our customer using ESET Internet Security v12.0.31.0 and he facing issue in 4 systems, 
  Unable to access internet in Google Chrome and webpage can’t display or page unresponsive.

Observation:
1.    Issue not occurring in other browser (Edge or Internet Explorer)
2.    Already ESET Firewall filtering mode set to Learning state.
3.    Pause Web Access Protection and SSL/TLS, but issue not resolved
4.    Issue resolved after pause Firewall Protection.

Solution: remove all firewall rules in ESET Advance Setup.

Collect ESET Log Collector log with Advance diagnostic logging and Procmon log and upload it here.
Procmon log: ftp://ftp.nod.sk/support/Logfile_Yashvi.PML

ESET Log Collector Log: ftp://ftp.nod.sk/support/eis_logs_Yashvi1.zip

So please check issue and do needful as soon.

[Gio 0]

ESET Endpoint Security, versions 6.5 through 7.0.2100.4

ESET Security Management Center (Server), Version 7.0 (7.0.451.0)
ESET Security Management Center (Web Console), Version 7.0 (7.0.413.0)

 

 

We have had dozens of these events also. Our clients from different sites keep calling in. I've tried disabling UAC User Account Control via policy and we still need to get on each PC to make the change. Is the issue possibly related to the Alerts and Notifications section, and not the Access Setup section?

Edited February 18, 2019 by Gio
Added

[Gio 0]

Wiping all of our firewall rules isn't something we can do. We would need the specific rule to delete/modify.

Is this the section to which you're referring?

[itman 1,739]

2 hours ago, Haresh2015 said:

Solution: remove all firewall rules in ESET Advance Setup.

I would have first set the Eset firewall to its default setting of  Automatic which allows all outbound connections and see if that resolved the Chrome issue. I would also delete all existing rules that apply to Chrome. -EDIT- Prior to deleting the Chrome rules, take a screen shot of all its existing rules. Those can then be reapplied one by one testing the impact of each rule to determine the rule/s preventing Chrome's start up or impacting its execution.

Edited February 18, 2019 by itman