Latest Avast 17.x breaks Windows 10 insider builds.

boris1m · 2017-03-03T21:56:31.000Z

I have tried updating to the latest Avast 17 on the latest as well Windows insider build (15046) that has caused the computer to stop booting. It goes into automatic repair mode, fails, and refuses to find either any restore points or anything else.

Booting into Safe mode does not work either.

I have restored from Monday backup which had brought me back to the previous build (1503x or something) with previous version of Avast. Everything worked fine, but updating to Avast 17 on that did not work either.

Are there any known incompatibilities between latest Avast and Windows builds?

Thanks!

Eddy · 2017-03-04T03:25:04.000Z

Please (re)search before posting.
Things like this have been explained already.

It is not avast that breaks Windows, but the other way around.
You can’t expect software to work on a Windows version that is not (yet) released.
Next to that, Microsoft seem to have gotten the habit of breaking the functionality of av’s in their insider builds.
There are tons of posts about all over the Internet.

boris1m · 2017-03-04T05:43:19.000Z

Well, I did not see any reports for this particular builds in either insider forums or even here.

That Microsoft breaks pretty much anything they can in W10 is old news now. But 12.3.2280 works fine on either build, so it is something that changed in Avast itself, anyway, even if technically is Microsoft’s fault.

jim2 · 2018-03-27T16:41:25.000Z

When one software manufacturer is HUGE and the other MUCH SMALLER, it is always the job of the smaller to make itself compatible with the larger.

I realize Insider builds come flying out without notice, but this attitude of which company is to blame is ridiculous. The big dog in the room sets the rules. Every time.

So I am not advocating beating up Avast when a compatibility issue arises, but it’s Avast’s job to scramble to resolve the problem - with humility.

DavidR · 2018-03-27T17:33:43.000Z

I guess you didn’t see the date this topic started 03 March 2017 over a year ago, not March 2018.

Announcements