17.1.2286 UI Failed to load. AV Service is not responding

[Asyn]

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

[REDACTED]

bob3160 Avast repair approach worked for me, thanks

[bob3160]

bob3160 Avast repair approach worked for me, thanks

You're welcome.

[iggy67]

Same issue, I ran the repair and did perform a clean installation of the latest version and it didn't do squat. I'm on a windows 10 64bit pc.

[bob3160]

Same issue, I ran the repair and did perform a clean installation of the latest version and it didn't do squat. I'm on a windows 10 64bit pc.

The next step would be to submit a support file:
https://forum.avast.com/index.php?topic=196459.msg1415127#msg1415127

[Eddy]

Much easier is perhaps installing/updating to the latest version.

[REDACTED]

I created an account here just to tell everyone what I did to fix mine.
I am using XP SP3 and had the "UI Failed to Load" after a recent program update.
I tried everything suggested in this thread - but nothing worked except this:
I went into SERVICES and set every single service that I had set to DISABLED and changed them all to MANUAL. I then rebooted my PC and lo and behold - I got back my UI and the AV service.
I'm not sure which one did the trick, but I'm leaving everything as is.
Most of the services that were originally DISABLED were Network related since my PC used to be on a network but is no longer.
I hope this helps someone else
good luck

[REDACTED]

έχω XP SP3 μετά από ενημέρωση του avast μου λέει UI Failed to load δοκίμασα να κάνω επιδιόρθωση αλά τίποτα

[Eddy]

Παύλος Ζιώγας,

1) This is a English forum

2) This is a bout a (real) old version of avast.

Doesn't make much sense to still post in this thread.

[chris..]

Hello,

I went into SERVICES and set every single service that I had set to DISABLED and changed them all to MANUAL. I then rebooted my PC and lo and behold - I got back my UI and the AV service.

yes, already mentioned , for xp users only (it's different for others OS) , it's mainly "Terminal Service" to enable (manu or auto)

@Eddy:yes 17.1.2286 is an old version , but the problem "UI failed to load" has not stopped with this version, it still exists with the latest version 17.7.2314 
Maybe it's not worth creating a new topic for each new version ?

@Παύλος Ζιώγας
with win xp sp3 , try (as said before) to enable windows "terminal service"

[REDACTED]

AVG Posted a REAL FIX for this problem for Wndows XP, 7, Vista, 8 and 10..... It finally fixed this problem for me and it was very EASY... I do not know if AVAST has a post similar to this one for AVG, but they should have one IMHO... here is the link or url for it....

https://support.avg.com/SupportArticleView?l=en&urlName=How-to-resolve-an-issue-when-AVG-shows-the-UI-Failed-to-load-error&supportType=home

That is an AVG Address and is 100% SAFE.

[DavidR]

AVG Posted a REAL FIX for this problem for Wndows XP, 7, Vista, 8 and 10..... It finally fixed this problem for me and it was very EASY... I do not know if AVAST has a post similar to this one for AVG, but they should have one IMHO... here is the link or url for it....

https://support.avg.com/SupportArticleView?l=en&urlName=How-to-resolve-an-issue-when-AVG-shows-the-UI-Failed-to-load-error&supportType=home

That is an AVG Address and is 100% SAFE.

There is a support entry for avast also, https://support.avast.com/en-us/article/Troubleshoot-Antivirus-UI-Failed-load.

[REDACTED]

TY DavidR..... after hours of reading i never saw the one for Avast until now... That one WORKS!!!

[DavidR]

You're welcome.

I think that is the first time that avast support link has been actually posted (certainly by me), whilst most of the information relating to stopped services has been but not all in one post/location.

I just went straight to support.avast.com and typed in the 'UI Failed to load error' into the search function and up it came.

[chris..]

Strange because it's not the same service (for win xp) to enable between avg support(terminal service) and avast support(Remote Desktop Services) 
For my winxp , the issue was only on terminal service .