@Georgetech It's probably a certain component in Eset that you could disable to work around the problem. Something like a "web shield" feature.