Problem Loading Web Images When Shields are On

system · 2017-07-04T08:06:12.000Z

I have difficulty displaying webpages when the Web shields are turned on. For instance the photo below shows my Twitter profile attempting to load. When the shields are turned off, everything works fine. I tried repairing the installation, but that didn’t work.
On Yahoo and Twitter I get messages on the notification bar, “waiting for pbs.twimg.com” and “waiting for S.yimg.com”. Facebook shows blank images. Sites with purely text content display ok.

http://i1256.photobucket.com/albums/ii490/Eugbug/Fullscreen%20capture%2004072017%2084421%20AM_zpsfnfzhcp4.jpg

Asyn · 2017-07-04T08:16:48.000Z

Which Avast…? (Free/Pro/IS/Premier)
Which version…?
OS…? (32/64 Bit…? - which SP/Build…?)
Other security related software installed…?

system · 2017-07-04T08:37:52.000Z

Can’t copy and paste the details, so here’s an image:

http://i1256.photobucket.com/albums/ii490/Eugbug/Fullscreen%20capture%2004072017%2092706%20AM_zpsdegze9ca.jpg

OS is Vista 32 bit. SP 2.

No other security software installed.

Browser is Firefox version 52.2.1.

I’ve tried disabling HTTPS scanning as suggested on other posts and this remedied the problem.

Asyn · 2017-07-04T08:40:20.000Z

Known issue on Vista. It should help to disable HTTPS scanning in the web shield.

hannon31 · 2017-07-04T15:26:03.000Z

Same exact issue I have on XP, which I posted about in a previous post.

Everything works fine, only when you disable the HTTPS scanning button.

According to others on here, this seems to be a bug only affecting XP and Vista.

Hopefully, there will be a bug fix for this in the next update.

system · 2017-07-04T18:49:19.000Z

Yeah. My Avast upgraded today, and I came on here because I had the same issue as you. Same setup, Vista 32 bit sp2, Firefox. It was actually stopping some sites from loading completely, preventing my main email address from letting me logging in, and blocking a lot of content, which was pretty problematic (until I tried turning off the shield and realized it was an Avast issue). Turning off HTTPS scanning seems to have fixed the problem, though. Hopefully there will be a fix soon.

Announcements