I’m constantly having issues browsing in Yahoo’s portal - https://uk.yahoo.com/ - that I browse for news, etc.
I also get this issue in the avast forums.
Several time a day I have to disable https scanning and stop the web shield. I then try to refresh those tabs I can’t view, but I’m still unable to view them.
Only when I enable https scanning and restart the web shield am I able to view the pages.
On occasion I also have to do this same exercise with the Mail Shield.
So there is certainly some work still to be done on HTTPS scanning for XP SP3.
Yes this has certainly been around for some considerable time and there were meant to be fixes, when it was first introduced I didn’t really have an issue when other were reporting issues in the likes of Yahoo and some other sites.
But from the time of the work around for XP is when I started to have issues, weird the fixes for me had the reverse effect. I too wonder about this new web shield HTTPS method, as I thought it was also for XP, but only those with SP3.
For me when they tried the selective/qualified update experiment to stop XP systems getting a beta if they weren’t allowed on XP was another problem area as it still let me install a beta that shouldn’t have been allowed and the only way round that was a clean reinstall.
The last two rounds of beta testing (for XP) and release for 10.4.x and 11.1.x have for me been probably the least stable of all of the betas I have taken part in in over 11 years.
I’m also still getting system lockups whilst browsing (also in MS Excel and also memory errors reported) with no other course of action than hard shutdown. This for me has been the worst as there is no way to gather any data or run the the support tool. Really frustrating.
Not for this beta update, but with the hassle on earlier beta updates I had done a clean install at 2016 beta. And that didn’t resolve any prior issues, in fact I seem to have had more hassle with 2016 than any other given I started out with a clean install.
For beta testing I generally do a program update from the UI as that is what I think most users do in regard of program updates.
What makes this more frustrating is it will work for a while without issue and then loading effectively stops. Then I have to do my dance with the web shield. For now I have the https scanning option disabled, fingers crossed it is working.
I’ve been looking around on the interwebs, other A/V’s that have tried XP SSL scanning have also experienced
similar problems. Perhaps the whole thing in XP is a bit of a kludge and will never work properly…
Well I think it could be deeper than HTTPS scanning as I have had it off for a day or so now, but I again experienced issues when browsing the yahoo Portal https://uk.yahoo.com/.
The same symptoms as before, pages not loading, stopping the web shield and trying to browse/refresh the pages didn’t do anything until I re-enabled the web shield.
Yes I see what you’re saying. I have reverted back to 2218 at least twice now, and this is what I’m running on my XP pc’s.
But the symptoms you describe point to a general lack of stability. Where the problem actually is,
I don’t know.
I would have assumed that turning off SSL scanning in the latest releases would be equivalent to 2218 where it was not implemented -
but it doesn’t seem to be. I’ve seen higher CPU in the task manager even with SSL scanning off, compared to 2218.
For me, avast development cycle lacks any credibility. If SSL scanning in XP is not reliable it should be dropped.
If it’s a problem in avast and the XP infrastructure is sound, avast should explain the situation in full detail.
avast’s behavior is more reminiscent of an unaccountable mad professor than a professional software organization.
Sorry but I completely disagree with your analogy.
Part of the problem is XP is old and doesn’t have the functionality (APIs) that would ordinarily be used in other OSes. So in trying to continue support for XP (unlike many others) they tried another method. But that in itself may have had issues and depending on what SP was installed the additional method wasn’t working 100%.
In the end some restrictions in what SP was required to be able to support https scanning and that was SP3. So those without SP3 probably couldn’t have the HTTPS scanning function, but why I ask myself would they still be on SP2 when SP3 is eons old.
Well my analogy wasn’t great, but when the same problems keep appearing release after release, I get a idea in my head that I couldn’t quite convey…
Is the problem in XP confined to SP2? I’ve never heard it mentioned anywhere. If that’s the case, perhaps avast should qualify the software as needing
XP sp3 at a minimum?
As to why users still running SP2? it’s probably something to do with WGA and other perceived anti-piracy measures, whether real or not.
I haven’t said that it is restricted to XP SP2 (for a start I’m on SP3), just that things have changed in the latest release of avast from 2015 R4 on how the https scanning is achieved in XP and this still needs more work.
Avast hasn’t changed the system requirements for some time, certainly not by any great margin. As for SP2 whilst it is still supported, there are going to be areas that aren’t supported in the that OS because it isn’t possible and the new NG (virtualisation function) is just one thing of the top of my head that isn’t available in XP of any SP variety.