thank you for this thread.
we declared a major incident on Wednesday and experienced the exact same issue of macs with ventura and 7.3.3600 asking for a restart and then no browsing.
We use jamf and had a pppc config profile targeting ventura macs to allow the web filtering. This config profile in effect means we accept (allow) the web filtering on users behalf. I found that by un scoping this config profile, users could then browse. Similar to what others have said about removing or turning off web proxy filter.
its just very coincidental that Mac OS Sonoma was released the same day.
I feel that Mac OS sonoma has changed some behaviour and eset has made a change to 7.3.3600 to preempt this , but it’s causing this unexpected blocking of the web filter proxy.
to be clear none of our macs were on sonoma.
I was really confused and unsure if it was a task I set to update to 7.3.3600 that caused this or a scan task that updated modules
but I think now eset have changed something preempting a change to Sonoma but lacked regression testing with ventura.
I have a call open with eset support and will be notifying them of this thread.
Rory Edwards received kudos from j-gray in ESET EEA 7.3.3600.0 update broke my network