Hello,
My desktop personal computer is running Avast Free AntiVirus version 17.4.2294 under Microsoft Windows XP Professional SP3 (32-bits). However the Avast software failed to launch and failed to run successfully after Windows startup (normal mode).
This problem happened yesterday Friday June 23rd 2017 afternoon after solving out some technical issues related to memory usage, apparently not connected with any security software programs in general and with Avast software program in particular.
When Admin user trying to execute the software user interface from the Windows Taskbar, it says the following message :
"Avast UI failed to load. This is really embarrassing. AV service is not responding"
I tried to make a repair operation on Avast software program through the appropriate option in the Control Panel but it did not work out as a solution. The Avast icon in the right-hand side of the Taskbar still shows a red-colored cross.
Can anybody from the avast forum community help me out with this technical issue ?
Thanks in advance,
Romain44.
What, where, how? Please could you give a bit more information or guidance? Search for ‘Terminal services’ on my computer just comes up with remote access stuff and I doubt I’d have to start that…
I guess it means calling up the Task Manager first, then switching to the tab ‘services’ there… ?
And then manually starting the Avast services? (Avast Antivirus and Avast Firewall Service)
Well, I did that - but it doesn’t solve the problem, I still get ‘UI failed to load’.
Any other ideas?
Best, Kerstin
‘the Terminal service’ => like… name?
If this doesn’t mean the Avast services that are in that list, how can I identify the service in question? In that seemingly a mile long list there is none that’s called ‘terminal service’ so I really don’t know which is the one.
Scroll down to Terminal Service and start (run) that service. Set it so it automatically starts in the Properties window when Windows starts. Close the Services window when done and reboot.
Ah, sorry, I’m on Windows 8.1 - I overlooked that detail in romain’s message -.-.
In the task manager, services tab, I’m in the extended mode, but I don’t find anything like box services either.
After some more research I even activated the remote support services in the system options but it didn’t help. (And I don’t have the slightest idea what caused the problem in the first place or I’d try to backtrack my steps - *sigh)
Remote support services allows someone to access your system remotely.
I suggest you start your own topic since it’s not related to this one and give a much detail as possible.
Except that I had the same error with AVAST and ended up feeling puzzled when I was asked to see if the TERMINAL SERVICE was running and the trail stops here.
Since ALL services are listed I expect TERMINAL SERVICE to be listed as a service, possibly with a status of DISABLED or STOPPED or BROKEN or MISSING, but there is no entry for a TERMINAL SERVICE at all. I think it may be renamed or included in some other service in WIndows 10 based on the lack of hits when I searched for it.
BUT regardless! I had the same symptoms as kersten13 and was able to get AVAST working again by doing the following:
Press WINDOWS key
“ADD OR REMOVE PROGRAMS”
Choose AVAST program and pick “MODIFY” (the other option is “UNINSTALL”)
Another window comes up with various options (update, repair, modify) choose “REPAIR”
When it finishes the repair process, try to run AVAST again.
NOTE: You get the exact same error! But this time when it prompts to ask if you want to restart the AVAST SERVICE it works.
I’ve tried both clean uninstalling (several times) and repairing through the windows control panel uninstall.
Still keep getting the little red cross in the system icon tray and have to click restart to get it working. Happened a few time over the past week or so but today its constantly failing.
I also looked for terminal service and see no such service listed?
There is no Terminal Service in windows 10 as such, but there is another Service (the name of which escapes me) that actually makes the same call as the Terminal Service does in winXP.
I am having the same problem with Avast free shutting down multiple times over the past 30+ hours. I made my own thread with no intent to hijack this one. Simply adding my voice to the growing chorus.
Thanks, though I’m still not sure on this one as services.msc shows this service as Manual and it isn’t started, yet my Avast is up and running including the UI.
If Terminal Services wasn’t running in XP the UI error would be being displayed. In XP my Terminal Services, is on Manual, but it has Started (presumably because Avast made the call).
Yes , I think so.
Those with “UI failed to load” issue (xp) , terminal service were totally disabled (so , even if avast wants , he can’t made the call)
But , as I said before , I don’t know If we can make an assimilation (same resolution) with W10 “Remote Desktop Service” and Wxp “terminal service” ?
As we can see from W10 users , issue seems to be solved just by a clean install of avast without worrying about a windows service
Well given what Microsoft said in the link you gave “Terminal Services Is Now Remote Desktop Services” I would expect to see the Remote Desktop Services (TermService in my previous image) actually running or the error Avast UI Failed and being unable to load. Which isn’t the case on my win10 Home 64bit laptop.
It certainly doesn’t make a clear comparison possible.
EDIT: Also what this article doesn’t appear to be for Win10, but for Windows Server 2008 R2.
[i]In Windows Server 2008 R2[/i], all Remote Desktop Services role services have been renamed. The following table lists both the former name and the new name of each Remote Desktop Services role service.
