Having read issues similar to my own in a few threads, I’m hoping somebody at Avast can at least confirm that the problem is recognised?
Shortly after upgrading to .2016, Dropbox is stuck endlessly trying to sync files, including some that were successfully synced before the program update, but without any progress. Other users with the same issue have reported the same Avast update as a common factor.
I’ve tried to go back to .2013 via System Restore and while it suggest that Avast has indeed reverted to the previous version, it is continually suggesting that I reboot. And the Dropbox problem persists.
Can someone please suggest a potential fix please? Avast has worked really well for me until now, but I will have to use something if this problem is not going to be resolved immediately.
Avast Free Antivirus 2014.9.0.2016
Windows 7 64 Ultimate
I just wonder if this really is the web shield, then another option is to check the avastUI > Settings > Active Protection > Web Shield > sprocket icon (settings) - and check the ‘Scan traffic from well-known browser processes only’ option.
Thanks for replying so promptly, Asyn. I was just about write that it hadn’t improved matters when the familiar little green Dropbox tick reappeared ;D Took a while, hopefully it won’t be as slow in future and things are back to normal.
Not sure why it wouldn’t help/work - If the dropbox process isn’t a browser, as per the ‘Scan traffic from well-known browser processes only’ option, then it shouldn’t be going through the web-shield (stream filter).
Obviously I don’t have any issues on this system (XP Pro) as it doesn’t use the new stream filter. However, on my win7 netbook I don’t have any issues with the new stream filter and dropbox as I have the ‘Scan traffic from well-known browser processes only’ option checked. So it appears to be working for me.
Another option could also be adding the dropbox executable to the web shields Process to exclude.
Well Dave, I tried the other options you mentioned in other threads and it didn’t help. It seems only some W7 (mostly 64Bit) machines are affected by this problem. Also it was initially fixed in 9.0.2013 but came back in 9.0.2016. (http://forum.avast.com/index.php?topic=144367.0)