Is there any chance you guys can show us the Exploit and Rootkit popups as it’s unlikely we’ll be able to see them anytime soon ourselves and since we can’t induce them like for file detections using EICAR…
Thanks for the update, but so far it seems not to have solved the “UI Failed to load” issue on Avast Premier after windows 10 update (1803).
After installing version 2338, after restarting the PC got the “UI Failed to load” error again.
Are you fixing problems or creating additional ones?
Using the Full Offline Installer and upgraded fine on XP PRO SP3 and on Windows 10 Home 64 computers. But please, put the Settings Button back on the Left Side where it was before and should stay. Also when you bring up the Licenses Page, the Close button (X) is on the Upper Left … Normal convention for programs is the Close Button should be in the Upper Right Corner
Avast failed at the first two restarts after the program update. It started fine at the third and two subsequent restarts, I wonder if it just needed the update to take before the problem was resolved. Anyway … that’s enough restarts for one evening.
I managed to get it going for now (Avast Premier. Did a clean install, worked fine. Switched off the machine, when after a while I switched it on again, there it was again the UI failed to load. Rebooted and so far it is working, but this is getting ridiculous and rather upsetting.
Now on top of that a minor question: How to deactivate the bothering promotional messages for other avast products in Avast Premier?
+1 for my W10 64b ,but just 1 reboot for my W7 and my WinXP
On the other hand , just (few minutes ago) updated W10 to 1803 Spring Update , no “UI failed to load” issue for now…but I had previously disabled avast
That isn’t the title of the video.
For me, the first reboot after the update took forever and all shields were disabled. Enabling these shields did not work.
A second restart, which again took a long time, allowed Avast to work with all shields active.
Hopefully Avast isn’t causing the long delay in the restart.
There would appear to be an incorrect build number for the new program version 18.4.2338 (Build 18.3.3860.316). Not following the program version of 18.4.xxxx.