UI Failed to Load is just part of the problem

[REDACTED]

The real problem is Avast shutting down for no apparent reason multiple times in the course of a day. Red "x" on tray icon, "You Are Not Protected" message on hover then opening interface to see the "UI Failed to Load" message. Restart. Rinse and repeat. FYI: repair does not fix the problem and neither does a clean install (using avastclear in safe mode and manually removing any leftover avast/awil folders), reinstalling most current program version, or even an older version which had previously worked flawlessly. I do wish these two "solutions" would stop being offered up as a fix for the "UI Failed to Load" problem when the issue goes deeper.

This is totally unacceptable behavior, widely reported on this and other forums, on a variety of OS from XP to Windows 10, dating back for months. And in my specific case, Avast itself (boot scan and regular scan), Malwarebytes and Trend-Micro Housecall all report a clean machine.

I cannot correlate auto-update definitions as a trigger to the shut down as at least 5 (out of the past 30) shut-downs was NOT incidental to a definitions update. Nor is Behavior Shield the trigger as Avast shut down once while Behavior Shield was disabled and again after I uninstalled the component.

I have read multiple threads and tried multiple solutions and still have no remedy. If anyone has a working solution to this I would dearly love to hear it ... after 15 years of using Avast, I am unwilling to move on unless I absolutely must.

[bob3160]

Please don't start another topic. It only makes support harder. 

[REDACTED]

It was a fuller explanation of the problem, for which I wasn't getting much "support." But no problem ...  there will be no further new topics since I have had no choice but to uninstall Avast and move to a product that doesn't shut down 15 times a day.

[WK_schnarfl]

Same problem, no solution.  I was going to re-install, but if doing all you did was not helping you, then I don't know.

I have used Avast for years, both alone, and concurrently with Malwarebytes Premium.  For years these two products seemed to co-exist peacefully.  I of course do not know whether that's the problem, but I have tried to have the initial loading of Malwarebytes delayed by 15 or 30 seconds.  Still not sure. 
Tried also to have various Avast Shields disabled, to see whether one of these is the culprit.  Did the same with de-activating the hardened mode, first on Avast
then on Malwarebytes, then on both.  Still dancing in the dark.

In response to the Avast Ueberevangelist named Bob, who said  "Please don't start another topic. It only makes support harder." I say this:  This is the most unhelpful response.  When someone responds to a topic that refers to the same or similar problem, then this is not "another topic".  Come down from your high horse and help people, if you can, or else light a fire under someone's butt at the Avast Head office (if you can). I would, if I could.  We are just asking for help with a problem, and if that annoys you, you are in the wrong job, in the wrong place. 

[Asyn]

I have used Avast for years, both alone, and concurrently with Malwarebytes Premium.

Regarding Avast & MBAM, see: https://forums.malwarebytes.com/topic/200324-exclusions-for-avast-users/