How to prevent and fix
All Avast installations should be patched now but in case you need a step by step help - https://www.avast.com/en-us/faq.php?article=AVKB272#artTitleWhat happened (simple version)?
Avast Antivirus without Thursday’s patch + Windows 10 Anniversary Update + Intel Skylake with Intel VT on = BSOD.What happened (in detail)?
On Tuesday, August 2, Microsoft released their latest version of Windows 10 - the Anniversary Update - via the Windows Update channel. While the majority of our users didn’t have a problem, certain HW configurations didn't mix well with the update. To be specific, when the Windows 10 Anniversary Update was combined with our aswvmm.sys driver on an Intel CPU from the Skylake family with Intel® Virtualization Technology (Intel VT) enabled in the BIOS, the update resulted in a BSOD. This occured during upgrades to the Windows 10 Anniversary edition from previous versions of Windows, and during clean installations of Avast Antivirus on systems already running the Anniversary Update.When was it fixed?
For a better insight into what was patched and when, please see the following timeline.
Aug 2 8PM - Window 10 Anniversary Update starts rolling out
Aug 3 1AM - First mention on forum about the BSOD
Aug 4 8PM - Emergency update released for Avast 12.2.2276 - clean online installations are fixed
Aug 5 9AM - Emergency update released for Avast 12.1.2272, 2016.11.2.2262, 2016.11.1.2253, Avast for Business 12.1.2512, 11.2.2511
Aug 5 9PM - Avast Emergency update is scheduled to run every 12 hours or about 10 minutes after system startup.
All above mentioned versions should now be patched.Is Avast Antivirus compatible with the Windows 10 Anniversary Update?
Yes. For the time being, however, please don't perform installations using offline installers without an internet connection. We will update offline installers later.Update:
Offline installers of Avast Antivirus 12.3.2279 already contain the fix - https://forum.avast.com/index.php?topic=189836.0Why was the incompatibility not discovered sooner?
We're still investigating the answer to that. Neither the Windows Insider program nor the Avast Antivirus Beta channel indicated any forewarning of such behavior.Thank you!
We're very thankful to our Avast users especially those who posted here on the forum! You helped us discover the root cause much faster which drastically sped up our delivery of the fix.
Have a good day,