Totally incompatible with my Home and Pro installations. I’m not going to give any more details at this time because I’m still trying to get both systems back on W10 16188 where Avast works without issue. Avast developers start your engines because here come the reports.
As the insider builds are just as you could say are beta version there is not guarantee that all software will work on it.
If there is a problem, report it to MS and have them fix things.
The problem is not avast but the insider build from MS.
@Eddy: Thanks for your opinion and advice; however, I can’t agree your assumption that the problem lies totally with MS at this time because there are other 3rd party AVs working just fine with 16193. Of course I will report it to MS as such; however, since Avast has never really gotten a chance to test their AV with the newest Insider build, who knows where the problem lies? Now, I do understand these things can happen and I wasn’t trying to knock Avast at all. They have been really good to me over the years and I intend to stick with them once the next “public” build is released.
I just did a clean install of W10 Insider build 16193. I then attempted to install Avast. It hung at 99% completion and never finished.
Avast does work nicely on the previous W10 Insider build 16188.
This issue has been reported via the MS insider program but I thought it would also be nice to give the Avast community an FYI as well.