Avast UI Failed to Load (AV service is not responding)

RDS also with W10
https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-whats-new
http://www.techadvisor.co.uk/how-to/windows/how-use-remote-desktop-connection-in-windows-10-3632113/

Not clear enought for me but I think the new avast UI (web link ?) is more or less used remotely by avast in real time.

In the same query , why some users can no longer install avast when they are disconnected from the web ?

Everything seems related to remote monitoring and much less as before to local monitoring by the user

Also, a grain of sand in windows services (RDS, terminal server) and problems occur with avast

Well I would have thought that the ‘grain of sand’ would be it is set to Manual by default and it isn’t running, so why is my win10 Home and avast free 17.5.2232 still running and not experiencing and issue.

What I also can’t see is avast running (calling) and then closing Remote Desktop Services for every time it needed to run any remote activity is performed. If it is so crucial as to cause the" Avast UI Failed to Load (AV service is not responding)" error of the title, I would have thought it would be running all of the time.

Maybe just once at logon.
Can you try to inform the service in “disabled” rather than “manual” … and try to reboot the computer ?
I am curious to know if the interface opens normally

tried with my win xp (terminal service set in “manual”) , it’s OK
set to “disabled” → UI failed to load.

Edit:Sorry, I think that’s what you were explaining in #17 :wink:
with xp , It remains started even in manual
with 10 , (your screen) RDS status → Stopped … started once than stopped ?

Yes, that’s it, my XP Pro SP3 system has no problem what so ever, it is just so weird - Terminal Services is set to Manual by default, yet it is running (as I would expect if avast needs the service running).

So if the Remote Desktop Services is the new Terminal Services in win10, why its not running (or run once and stopped) is beyond me. And more so, why aren’t we seeing many more win10 with this issue.

Whatever the reason/issue, this certainly needs avast team input, added to the bug list and fixed A.S.A.P. After all this is no cosmetic issue but a serious issue that demands urgent action.

Reported to Avast. Hope that gets a reply and an answer.

My Remote Desktop Service (Windows 7.1 Pro) is set to manual and always has been yet the UI Failed To Load … This Is Embarrassing message continues to plague me. I have my own thread on this situation https://forum.avast.com/index.php?topic=205616.0 but am trying to contribute toward a resolution.

Your problem may well be related to the fact that it’s a Remote Desktop. Let’s hope they come up with a solution to your problem. :slight_smile:

I just looked on my w7 , RDS is completely disabled , yet Avast UI is OK
So you are right “It certainly doesn’t make a clear comparison possible”

Waiting for avast reply about , we will see whether it concerns a remote desktop service or something else

I was referring to RDS (services.msc) which reportedly is the “same” as Terminal Service on XP, subject of this thread. My pc is not “a Remote Desktop.” I am simply trying every conceivable suggestion to get Avast to stop shutting down. :frowning:

The only shut downs I ever see are with the Behavior Shield which quite often
needs to be started after a system boot.
Avast is already aware of that problem and will hopefully fix it soon.

As I said, I’m trying every conceivable suggestion from a compilation of threads on this subject: including first disabling Behavior Shield, then completely uninstalling the component. Neither stopped the behavior red “x” … “You Are Not Protected” … “UI Failed to Load.” Not that I would want to live without Behavior Shield as I consider it rather important.

Since I have now pretty much spent three full days trying to resolve this without any success whatsoever I suspect it’s time to move on to a different AV program, which makes me incredibly unhappy after 12+ years of reliability.

THANK U 8) my AVAST works now - good help !

Greetings from Berlin (Germany)

C:\WINDOWS\System32\svchost -k DComLaunch

Yes, it works, thanks

The problem in W10 seems to be a bit different. I have this problem too. The service crashes every 10 to 20 minutes. After several reinstalls (with and without the cleanup tool) and one experimental install into a fresh W10 VM that was busted as well, I just gave up and uninstalled my AIS and am running only with Malwarebytes (and before someone asks, yes, I also tried with Malwarebytes uninstalled, several times).
After going through the service logs, the only suspicious entry is one saying idsagent stopped responding, which roughly corresponds with the time the avast service crashes.

That points to Symantec ??? Was that ever installed and if so, how was it removed ???

No, that’s only a similar name, it actually points to avast Behavior Shield.

The Behavior shield is a know problem that’s supposed to be fixed by release 17.6.
I need to start it virtually after every reboot but once started remains running.

Windows 10 with Avast Premier. I noticed the UI was perfectly clean, white, no text or graphics. I rebooted and it won’t load at all. It will show up in the “show hidden icons” section, but on mouseover, it disappears. Checked services.msc and it is running there, but no GUI. When I look at active processes, only the Behavior Shield shows as active.

Based on what I’m reading here, I should try a fresh install. I think.

Repair Avast:
Control Panel> Program and Features (Add/remove program)>Select Avast> Select Repair. Reboot when completed
https://www.avast.com/faq.php?article=AVKB204

If Repair doesn’t fix the problem, try the following:
Clean Install of Avast:
https://goo.gl/4Ptzkf
If you need additional help with the Clean Install, watch this:
https://youtu.be/p-h3myRD51A

Worked like a charm. I followed your instructions and downloaded the Premier offline installer and the Avast clean tool, just in case.

Thank you for your help. I promise not to be an idiot next time. Repair…so easy.