One solution for blocked internet connection after the 1451 update

Avast Free Antivirus / Premium Security
1

This was my solution to get the new 1451 version update working. After the update on top of the previous version, the new version somehow blocked the connection to the internet. I then did a uninstall with the Avast tool from the safe zone and tried a full install. Internet still would not connect. This was with Windows 7 64 bit. I then tried it on a Windows XP 32 bit system after a safe zone uninstall with the same results of not connecting to the internet. I normally have in the Avast Firewall Policies, the “Use Fast Checksums” not selected for it’s increased security. This setup I had to change. Once the “Use Fast Checksums” was selected (checked) the internet connection worked for both Windows 7 and for Windows XP when tested. I hope this can help others who have had their internet connection blocked after the new update. I would consider this to be a bug with the new version.

2

Hi, this is a mystery for me, why should that help. Would please be so kind and try turning it off again to verify that it will again start causing problems? I would also really like to see your config.xml and rules.xml files from fw config folder. Would you mind sending me zipped the xml files from "C:\ProgramData\AVAST Software\Avast\fw".

Thanks a lot,
Lukas.

3

I can (only) confirm that others reported the same in the update thread.

4

This post by the OP resolved some issues: http://forum.avast.com/index.php?topic=100316.msg802073#msg802073

thanks to the OP ;D

5

I confirmed the issue on this Win 7 machine. The “use fast checksums” was selected so I deselected it and closed IE9 and then tried to go to my home page. I got the good old “Windows cannot display this web page” message and I had no connectivity. I then re-selected the fast checksums and everything went back to normal.

6

Hi guys, thanks again. Now I can confirm that as well, there was a bug found and will be corrected as soon as possible by a program update.

7

Thanks for the info, at least we had an easy workaround for this bug. :wink:

8

This bug should have been fixed with the new release of v.7.0.1456. You can upgrade via the GUI, the reboot your machine.