[fixed] Avast causes Blue Screen after Windows 10 Anniversary Update

[petr.chytil]

Thanks everyone for all the reports. It really helped us to find the root cause.
If everything goes well, we are going to release an emergency update today. The update will be applied even during the clean installation. Beside that, we are going to include the fix in the offline installer of a Beta version which is also going to be released today.

Right now, the fix is being tested.

Once it is ready, I will let you all know!

[REDACTED]

*clap-hands*

I really appreciate this. Thanks for the power!!

I do not understand why some people are really angry and shouting on Avast - this is my first issue for years now as a paying customer and I still would recommend Avast to every friend ...

[REDACTED]

Great news, thank you!

[REDACTED]

*clap-hands*

I really appreciate this. Thanks for the power!!

I do not understand why some people are really angry and shouting on Avast - this is my first issue for years now as a paying customer and I still would recommend Avast to every friend ...

As a non paying customer i second this. Mistakes are made everywhere, it is the reaction to made mistakes that make the difference... I wonder how these people react irl when a coworker or a friend makes a mistake.

anyway, thanks for the support Avast

[CaptainLeonidas]

Thanks everyone for all the reports. It really helped us to find the root cause.
If everything goes well, we are going to release an emergency update today. The update will be applied even during the clean installation. Beside that, we are going to include the fix in the offline installer of a Beta version which is also going to be released today.

Right now, the fix is being tested.

Once it is ready, I will let you all know!

I will check this thread closely so I can install the AIS once again on my Surface once the update/fix becomes available.

Thanks for the update.

[petr.chytil]

One more note,
this issue occurs only on Intel Skylake CPUs when VT-x instructions are enabled in the BIOS. As a workaround, you can temporarily disable the VT-x in BIOS.

[CaptainLeonidas]

One more note,
this issue occurs only on Intel Skylake CPUs when VT-x instructions are enabled in the BIOS. As a workaround, you can temporarily disable the VT-x in BIOS.

No idea if this applies on a standard Surface Pro 4. If so I will have to look up where this is hidden in it's UEFI.
Also does this mean VMWare/VirtualBox or Hyper-V users still have an issue when running Avast on their workstations?
I would assume so.

Can it also be solved by avoiding the use a loose component/not installing a component or is it part of the basic drivers needed to even run the Avast anti-virus software?
(Again I assume this being the case as some folks have issue's with the free version as well..)

[REDACTED]

Thanks to Avast for an incredibly quick response on this. Pretty impressive.

[REDACTED]

Just for giving you more info.
I just update my second desktop with i5-760 + windows 10 + avast free.
Anniversary update installed at the first try.

[REDACTED]

ok on august the 2nd I tried install win10 anniversary update and it failed twice due to avast and BSOD.  ok so I uninstalled avast through add/remove programs.   then I got the win10 update installed.  so after its all working good stupid me installed avast fresh install and yeah you guessed it bsod.  so I had to go onto another computer and find that this forum shows all kinds of issues with this new update and avast.  Great.   so I found your avast cleaner and booted into safe mode and ran it.   got my computer working good.   Yes I have a skylake cpu i7  and now I see you MIGHT have it fixed.  but to be honest I don't know if I trust your software anymore over 15 years of using it and installing it on clients computers I work on.  its like you guys gave up and don't care anymore at all, this is a horrible issue that should of never happened PERIOD. 

[Eddy]

Sure, and you are perfect and never do something wrong/make a mistake.
Besides, you should blame Microsoft for not testing all possible combinations of hardware/software before releasing the update.

[REDACTED]

Petr -

Thanks for the quick turnaround on a fix.  Please let those of us who restored to Windows 10 Build 1511 what we should do.  That is, will we need to uninstall Avast, perform the Anniversary Update, then do a clean install?  Or will we be able to apply the update, disable shields and not uninstall Avast, then perform the Anniversary Update?  I'd like to avoid any more BSODs or boot loops.

Thanks again.

[Eddy]

Apply the avast update before updating Windows and everything should be fine.

[REDACTED]

One more note,
this issue occurs only on Intel Skylake CPUs when VT-x instructions are enabled in the BIOS. As a workaround, you can temporarily disable the VT-x in BIOS.

Have 2 new pc.  "Intel Skylake CPUs when VT-x instructions are enabled in the BIOS" is disable in bios.
Fresh instalation Windows 10 Anniversary Update. same BSOD after install Avast.

[REDACTED]

One more note,
this issue occurs only on Intel Skylake CPUs when VT-x instructions are enabled in the BIOS. As a workaround, you can temporarily disable the VT-x in BIOS.

Not sure of this. In my Asus Z170-A with i7-6700, VT-d is DISABLED by default.