All of a sudden I cannot get any of my internet browsers to load. The only thing I have changed today is update Avast. I double click on Chrome, IE and firefox nothing happens. The programs appear in the task manager for a second then disappear. I assume this has to be because of the Avast update. I even tried going back to a backup and it still does not work. Tried to update avast and it says everything is updated.
Perform a repair of avast and check if the problem is solved (reboot after doing so).
If not, perform a clean installation and check again.
Tried to repair, didn’t help. Completely uninstalled and everything works. Probably go with another antivirus. This was a mess.
Glitches can happen.
As you are the only one reporting this it was more likely a problem on your specific system.
Wait for the patch>>
https://forum.avast.com/index.php?topic=208020.msg1417691#msg1417691
The fix was released many hours ago in a VPS update (streaming update), so it should be fixed by now. If you still have the issue, do a manual VPS update and I would also suggest a reboot.
The fix did not come. I uninstalled the antivirus.
I’ll try a new installation in 12 or 24 hours.
I updated Avast just 10 minutes ago, and Firefox 55.0.3 won’t load. Noticed there is a fix but I either I cannot get it (updating avast again said everything is up to date) or it’s already installed, but still no go for Firefox. And it is only Firefox. I have Vivaldi & K-Meleon installed & both runs fine. I already do fresh Firefox install and it’s no go.
Tried booting to safe mode where Avast didn’t load and firefox runs fine.
Plz help
Apparently I am not the only one.
me neither
not yet fixed it
As of VPS v170901-0 Firefox still not working for me.
Versions
Firefox: v55.0.3 32 & 64bit (fresh install), v53.0.2 32bit
Avast
Engine & Definitions: v170901-0
Program: v17.6.2310
Curiously, Waterfox & K-Meleon, which are forks from Firefox, runs smoothly. Vivaldi, which is Chromium based, also run without problem.
There is an issue with the webshield. This is how I was able to fix it, so I could use all my internet browsers -
Open up Avast
Go to Settings
Go to Components
WebShield
Click on Customize
Unclick ‘Enable HTTPS scanning’
That issue has been solved in the yesterdays update/fix.
Can confirm this issue is still present (for me at least).
I’ve tried disabling Avast, rebooting (several times), manually checking for updates (which claims it’s already up to date), all to no avail. My only solution as to this minute is to uninstall Avast and reboot, doing so allows Chrome and Thunderbird to run just fine afterwards (at least until I re-install Avast).
It appears that the hooks “snxhk64.dll” and “aswhooka.dll” are to blame (both located in “…\Avast” and “…\Avast\x64” respectfully).
Each crash has “The thread tried to read from or write to a virtual address for which it does not have the appropriate access” as the Exception (collected via “AppData\Local\CrashDumps”).
I also noticed that Visual Studio was taking a little longer to load while the newest Avast client was installed, though I have no concrete evidence to this (could just be my imagination).
Interestingly enough, Internet Explorer didn’t seem to be affected. It loaded without issue during my woes.
Follow instructions: https://www.avast.com/faq.php?article=AVKB33#artTitle
I have exactly the same problem after installed the latest update. All my browser installed not work (IE, Firefox, Chrome). All of them crash.
Can you confirm (those who are affected with browsers not loading) that you are running the latest version of Avast 17.6.2310 as well as the latest VPS via Settings > Update?
Just re-installed to check for you;
Virus Database release date: 01/09/2017 1:06:12 PM
Virus Database version: 170901-2
Program release date: 31/08/2017 9:53:42 AM
Program version: 17.6.2310 (build 17.6.3625.0)
Attempting to manually run a update for either results in a “already up to date” message.
Yes, I can confirm the version is 17.6.2310
Hello guys, thanks for the report. Based on the symptoms this does not seem to be related to the yesterday’s issue - which was entirely inside the virus database and could hardly cause browsers to shutdown. We need to look into this. Thanks Lukas