Avast and Microsoft August Patchday

[brightside22]

Hi,

on the last MS Patchday a kernel update was offered that caused conflict with some systems. Avast seems to be one possible cause of trouble.

I have read that Avast is aware of the problem and has issued fixes. http://www.infoworld.com/t/microsoft-windows/microsoft-needs-your-help-fix-botched-patch-kb-2859537-225314

Unfortunately, I cannot find any information from Avast directly which Avast version is the problem and what the fix exactly is.

Is there any news?

Thank you!

[essexboy]

Avast has solved the problem with an update,

This was probably via a signature update or an emergency update

[Sahri]

Avast has solved the problem with an update,

This was probably via a signature update or an emergency update

Program or definition update?

[brightside22]

Hi,

I cannot find any information directly from Avast whether it is a program emergency update or not. Since this is obviously a kernel problem as MS states, I personally doubt it to be a definition update.

The changelog for Avast 8 doesnt say anything nor for Avast 7.

Since MS13-063 is a Windows Kernel update -- always problematic, reaching into the inner sanctum -- a lot of people have reported problems. The most frequently reported problems, with Avast and the games Rift, Final Fantasy, and Defiance, seem to be related to developers hooking into the kernel in unexpected ways. Those are more-manageable problems. If you're still having trouble running the Rift game after authentication, install the latest patch from Rift (available since Aug. 15). Avast has solved the problem with an update, but no word yet on small game developers.

[GTX66]

http://www.infoworld.com/t/microsoft-windows/microsoft-needs-your-help-fix-botched-patch-kb-2859537-225314

This update should be removed from your system until MS fixes it. It had caused me many problems.

[brightside22]

Susan Bradley from the Microsoft forum wrote:

They are 'throttling" the update as they typically do when they see issues with an update.  For those that have installed it and see no issues (as I have here personally) there is no need to uninstall the update.  For those that see it unchecked, leave it be and it will be 'unthrottled' at a later time.

I personally installed the update before issues became public. I had not had any bluescreens or problems yet. I am just worried. I also thought about uninstalling but the advice from MS seems to be to keep it unless one does have problems.

If Avast were not mentioned as one possible component of possible issues I wouldnt worry. But Avast is mentioned as a cause of conflict.

[GTX66]

Just Google that update and you will see how many people are having issues. There must be a problem with it as MS is working on a fix. If there was nothing wrong with it then they would not.

[MikeBCda]

I think the point has already been well made that while the problem is serious, it doesn't affect all users (e.g., no problem on my system).  I'm curious whether anyone's seen any stats on the percentage of users who are affected, and what progress (if any) has been made towards identifying specific hardware-OS-software combination(s) which I believe are the "trigger" for the problems.

[midnight]

I haven't had any problems.

[GTX66]

I think the point has already been well made that while the problem is serious, it doesn't affect all users (e.g., no problem on my system).  I'm curious whether anyone's seen any stats on the percentage of users who are affected, and what progress (if any) has been made towards identifying specific hardware-OS-software combination(s) which I believe are the "trigger" for the problems.

http://www.infoworld.com/t/microsoft-windows/microsoft-needs-your-help-fix-botched-patch-kb-2859537-225314

You can check out the link above.