Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Tobur on May 06, 2017, 06:56:24 PM
-
Before 17.4.2291 Avast free was working smoothly on my system (Windows XP SP3) but since then each program update has created more and more problems. With 17.4.2291 it was 'UI Failed to load' - but I was at least able to scan individual files and folders from the right-click menu. This is now no longer possible with 17.4.2294 - when I try it Avast attempts (and fails) to open the UI. Is there any way to roll back to before 2291?
-
You can only "roll back" if you have the full installer for a previous version.
The right click scan from the menu is still there in version 2294.
-
The right click menu includes the option to scan OK - but any attempt to use it results in the 'UI Failed to load' screen - and apparently nothing else. This was not happening in 2291 where the scan progress showed.
-
- Other security related software installed..?
- Which AV(s) did you use before Avast..?
-
- Other security related software installed..?
- Which AV(s) did you use before Avast..?
Malwarebytes Free - only recently installed when Avast problems were already there- and Superantispyware Free installed a long time and Avast was OK with it until 2291.
Have used Avast Free for years - before that AVG which I cleared from my system. As I said before 2291 all was well.
-
Repair Avast:
1. Control Panel -> Add/Remove programs -> Avast
2. Click on 'Repair'.
3. Follow instructions.
4. Reboot.
-
Thanks for reply - already tried Repair and many other suggestions - Uninstall - Avastclear tool in Safe Mode - Reinstall - Offline Installer etc. etc. - all to no avail. Still no UI and now no right-click scan. Avast now seems to be a basic "bouncer" at the door of my system ("your system is secured")- but I have little or no control over him! Oh for the 'good old days' of 2016 when Avast worked well.
-
See: https://forum.avast.com/index.php?topic=200573.msg1391147#msg1391147
-
I have checked that post re. Terminal Services. In my case Terminal Services cannot be started but gives an error message. I have read that Windows XP Home does not come with or support Terminal Services feature. In any event Avast was OK before 2291 with my Services as they are now. I think I will give up and leave Avast for now as it is - the "Watcher at the Gate". At least my "system is secured" - OR IS IT ?!!
-
-> https://forum.avast.com/index.php?topic=201308.0
-
See my earlier post above re. Terminal Services.
-
Try: sfc /scannow
-
Have already tried sfc /scannow! I think I have tried all suggested remedies - and a few that no one suggested - but no luck!!
UI fails to load. There seem to be quite a few others with a similar problem.
P.S. Have just seen an Avast FAQ Web Page where this UI issue is shown as 'resolved' - I give up!!!!
-
For most people that may be the case (resolved), it does seem to more of an issue with XP systems (but not exclusively), though it isn't effecting my XP Pro SP3 17.4.2294 system. I haven't got 17.4.2294 0n my other systems (win7 32bit and win10 64bit).
-
When Avast shows a problem as 'Resolved' (dealt with successfully) one might assume that a solution has been found. For those of us (and we are many) who are still seeing 'UI failed to load - This is really embarrassing', the problem is certainly not 'Resolved'. Perhaps someone in Avast might resolve to resolve it!!
-
When Avast shows a problem as 'Resolved' (dealt with successfully) one might assume that a solution has been found. For those of us (and we are many) who are still seeing 'UI failed to load - This is really embarrassing', the problem is certainly not 'Resolved'. Perhaps someone in Avast might resolve to resolve it!!
The problem is any subsequent fixes could well have screwed the resolution, or may not resolve it if there are any other OS/system settings/installations that weren't catered for. As I have said in other topics, I haven't been effected by the UI Failed, so I don't know why it isn't everyone that is effected.
-
When Avast shows a problem as 'Resolved' (dealt with successfully) one might assume that a solution has been found. For those of us (and we are many) who are still seeing 'UI failed to load - This is really embarrassing', the problem is certainly not 'Resolved'. Perhaps someone in Avast might resolve to resolve it!!
The problem is any subsequent fixes could well have screwed the resolution, or may not resolve it if there are any other OS/system settings/installations that weren't catered for. As I have said in other topics, I haven't been effected by the UI Failed, so I don't know why it isn't everyone that is effected.
So the problem is not 'Resolved' - as those of us Affected are well aware. I rest my case!! - and await a 'resolution'.
-
When Avast shows a problem as 'Resolved' (dealt with successfully) one might assume that a solution has been found. For those of us (and we are many) who are still seeing 'UI failed to load - This is really embarrassing', the problem is certainly not 'Resolved'. Perhaps someone in Avast might resolve to resolve it!!
The problem is any subsequent fixes could well have screwed the resolution, or may not resolve it if there are any other OS/system settings/installations that weren't catered for. As I have said in other topics, I haven't been effected by the UI Failed, so I don't know why it isn't everyone that is effected.
So the problem is not 'Resolved' - as those of us Affected are well aware. I rest my case!! - and await a 'resolution'.
Well you can't change history, that is what I'm saying at that point in time avast believed it was resolved.
-
Edit: nevermind question I was gonna ask was apparently already answered.
-
I have been pursuing this problem for some weeks now (I am not very PC literate - I am 81) - but what fascinates me in all this is that the onus seems all the time to be on the user - Uninstall; Reinstall; use Avastclear; Safe mode; Online Installer; Offline Installer ; Try this; try that etc. etc. All very confusing - but where is Avast in all this. It was working on my PC before update 2291. My system has not changed - so presumably something in the update caused the problem.
Perhaps Avast subscribes to Salvador Dali's dictum
“What is important is to spread confusion, not eliminate it.”