What I do not understand is why, when I have AIS and windows 10 build 10576, have never experienced this problem in any shape or form, and I have been running 10 since the first preview... If it was Avast related then I would experience it which would suggest that you need to be running the right (wrong ) combination of programmes to trigger the error. But, the question is what is the programme combination ? I run no other security or privacy software. My start up just has Avast, a theme changer and Flux
Going off of your post, I just upgraded to the same build yesterday, and the issue has been persistent since a few versions back. If I can give any insight into this problem, I'm thinking it may be relative to how your system has upgraded to newer builds over time.
With this particular computer, a bad build upgrade forced me to start over fresh with Windows 10 on a post-main release insider build. Since around that time, I've had this issue with Avast. Prior to reinstalling, Avast worked just fine.
Going further into this, I've noticed similar situations presented by Windows 10 itself in relation to upgrades and clean installs. Using older builds way back when, I continued to upgrade to newer insider builds as they were released. In doing so, I noticed small bugs arising that should not have existed, such as the Settings and Power buttons being missing from the Start Menu, like in older builds, when they should have reappeared. Reinstalling the
same build fresh resolved it. I also remember Microsoft recommending Insiders to use released ISO's to reinstall their insider build systems clean every so often to avoid any upgrade bugs.
Knowing what I know now, it is leading me to believe that somewhere in Windows 10, in some sort of specific scenario like this, Avast is triggering an existing Windows 10 bug, (whether it be Avast's fault or Microsoft's is yet to be seen). That being said, I think a better
permanent solution should be sought out rather than everyone arguing over who is at fault. Either Microsoft or Avast is going to need a fix or workaround for this, and with them both pointing blame elsewhere, it isn't going to happen. I say we, as a community, attempt to research the issue in our own scenarios, and try to find a common ground that leads to a solution, as we have done in the past. Clearly something is wrong on someone's end. It doesn't really matter who made the mistake or created the issue so long as it gets resolved quickly and efficiently.
I would like to also point out that, for the sake of research, that I have also read CCleaner as being at fault for this. I also have this application, and I had it before and after every upgrade mentioned in the previous half of this post, (which was installed alongside Avast, but was only run manually). Given the number of people reporting this issue with Avast, I'm doubting
all of them have CCleaner, but to say that Microsoft is entirely at fault may not be fair. Obviously the OS has a bug in it, but the trigger is still unknown. It could be multiple different kinds of software out there, Avast and CCleaner included, that cause it to arise. If Avast finds a solution, it could eventually be shared with the other applications causing the issue. (Now that seems like even more reason for us to figure this out, if you ask me).
For what it is worth, this issue also only affects me personally after running the computer for an extended period of time. I often also hibernate it now, and sometimes come back to it being turned on by itself for unknown reasons. I'm doubting that this relates to the issue, but maybe it can provide some common information to diagnosing the problem.