Os Windows 10 32Bit Version 1607 build (14393.693)
Product : It does not matter which version i try, Avast! free/Internet Security.
After a clean installation i Installed the free version first then after the UI issue there is nothing much which i can do since i can’t even get the options to change any thing even if i want to. It is practically useless with the bug.
This is extremely frustrating since i am using avast since 2006 and never ever had a problem like this which rendered it useless to this extend.
When you ran the avastclear tool, did you run it for all version of Avast that you had installed on your system.
In your reply you mentioned both the free version and Internet Security. To actually do a clean install, you would have had to run the cleanup tool twice. Once for each version installed. Once that was done, then install the Avast version of your choice.
I have done clean installations for both and even i tried running it in a VM machine i set up to test if it is going to work or nope and it failed the load the UI there as well. This is some weird but a very bad issue. The product cannot be used now. It does not matter how many times i tried clean installation of the product(Free & IS). Even the latest beta is no exception as it also fails in getting the display up and running. Since it failed in a clean OS installed VM machine set up for just this purpose, i can only say that some thing is really wrong with the product. Also there have been multiple reports about the same issue on the thread so it is some sort of a serious issue.
Why doesn’t Avast fix the problem instead of making us go through hoops to fix a problem on their end? So many posts of the same problem, you fix it Avast or i’ll take my business elsewhere.
There are going to be may tens of thousands of system permutations and installed software running. Not all are going to be experiencing this problem, so identifying the cause isn’t as simple as it may seem.
just started having this issue after the latest windows 10 update , system was fine before this , as a paid for service i expect it to work within certain exceptions like the borked virus defs from earlier in the yr . things happen . ever since they merged with the other product ive encountered two issues now . this needs more direct attention IMO
want to add i have run the Repair to no effect either .
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
After the repair, a reboot is required for the changes to take effect.
You should also reboot after a clean install to make sure all of the changes take place.
Good day/night. I’m having this same problem, but with the 17.3.2291 update, that I installed yesterday.
I’m having the issue in my netbook (Windows XP Professional 32 bit service pack 3)
So far I tried:
Using the -repair- option from the program list under control panel
A clean re-installation (actually 2) for which I:
1.- unninstaled from control panel- reboot
2.- use the avast clean tool- reboot in safe mode to let it do its thing- reboot
3.- removed manually the avast folder that was still on program files
4.- Used CCleaner to fix the registry- reboot
5.- Installed avast from the offline package (previously downloaded)- reboot
And I still have this problem. Since avast seems to being working normally on the background, I guess I can wait until a patch fix this (because its working normally on the background, RIGHT?) But I’m really concerned. This small netbook is very dear to me (Its the first computer I bought with my own money) and I take pride on how its still working nicely… and depends on avast for its security, since it doesn’t have OS support…
I have read every post I could find on this subject (Windows XP SP3 Avast Free update to 17.3.2291 - UI failed to load etc.). I have tried ALL the suggested solutions to no avail. The previous poster says they can wait for a patch to fix this - but my simple question at this point is - is there or will there be a patch to solve the problem or should we just abandon Avast? I have posted elsewhere under Problems with XP SP3 but despite hundreds of views there is no solution offered that works.
Views doesn’t mean those viewing have the same problem, they are views, nothing can be read into it than that.
You will see by my signature that my main system is XP Pro SP3 and I have always been on the latest version (currently running the latest beta version) and I have never come across this problem. I dare say I’m not alone in this issue (nor are you), with this kind of inconsistency does make it harder to pin down.