It’s not exactly what I’ve done .
I did not install the free version, but simply uninstalled the firewall shield on AIS.
It’s true that now for AIS, there’s not much difference between it and free version anymore, but you could have kept Avast premier with what you don’t have with free :
@ chris,
you used a hammer to solve the problem, MrDJ used a sledgehammer.
You’re correct, the problem appears to be with the Firewall so that’s the only thing that needed to be removed.
quick update.
i did not know i could just delete the firewall.
i have now worked that out and loaded my license back to premium but deleted the firewall in troubleshooting.
Hi All, thank you very much for your responses. Problem is one of our core kernel libraries, so unfortunately BSOD can be thrown on all Windows Versions (we know about its occurrence on Windows 10) and in all Avast editions because problematic library is used by both network drivers - Firewall and WiFi inspector.
Currently, we are testing fixed drivers. They will be released via emergency update tomorrow.
I started to have BSoD everytime I turned on my PIA with the new Jan 2019 avast update. I use premier Avast and PIA. To solve this issue, I uninstalled avast and installed the older avast 2018. It worked fined. But Avast kept automatically updating itself, then the BSoD was back again. So i had to reinstall 2018 avast all over again and set to no update and manual update. But avast still kept automatically updating after few day. So far avast manual update has not been working.
email received from support that a micro update patch was being pushed out around 6.30pm uk time.
nothing received yet but a fatal blue screen instead :-
removed firewall again and will just wait now.
yes Bob and thats when i got the fatal blue screen.
that was over 2 hours ago and no update come through yet on premier. still showing 6th Feb and upto date.
would the fix be in the virus definitions as i would of thought it would be in the applications update.
if it is actually in the definitions then its not worked as that had already loaded before i got the blue screen when my vpn loaded.
I apologize for the inconvenience but please be patient. We must build new driver and it must be signed by Microsoft. It is time consuming but I hope that fix will be released today.
Exactly the same as above, I am trying to find the problem since last week Thursday, in addition, multiple attempts to uninstall and re-install ExpressVPN failed even though AVAST was disabled,
what a waste of my time.
Interestingly I am running two computers with almost the exact setup, Win7 Professional, AVAST Premier, ExpressVPN, the only difference is that my 64-bit keeps crashing while the 32-bit works just fine.
Hi, the fix was just released. As soon as you will see 19.2.4186.429 or higher version in your UI the uupdate was successfully delivered on your system.