Version: 18.4.2338

Good news everyone,
new stable version 18.4.2338 has just been released.

What’s new:

  • Detection dialogues for Anti-exploit and Anti-rootkit Shields
  • My Licenses section
  • Dropdown menu in top bar
  • Earn Rewards program
  • Wi-Fi Inspector redesign

Fixed:

  • GDPR compliance
  • Fixed a few crashes related to Firewall drivers
  • “Scanning in progress” is no longer reported in tray after install
  • Toaster from Game Mode is not shown when Silent Mode is enabled
  • UI not responding when shields are disabled
  • Behavior Shield crashes

How to install:

  1. Update from your existing Avast version via Settings → Update → Update program

  2. Or you can download and install from here

Online installers (recommended):

http://files.avast.com/iavs9x/avast_free_antivirus_setup.exe

http://files.avast.com/iavs9x/avast_internet_security_setup.exe

http://files.avast.com/iavs9x/avast_premier_antivirus_setup.exe

Offline installers:

http://files.avast.com/iavs9x/avast_free_antivirus_setup_offline.exe

http://files.avast.com/iavs9x/avast_internet_security_setup_offline.exe

http://files.avast.com/iavs9x/avast_premier_antivirus_setup_offline.exe

We hope you enjoy the new version!
AVAST Team

Thanks for the new release :slight_smile:

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?

omg WTF are you fix nothing!!

still same after restart again avast ui error :frowning:

The ‘UI failed to load’ is still occurring.

It happened to me AGAIN after I tried to update to this version on my Windows 10 laptop.

There needs to be a permanent fix.

I’d appreciate any help with this.

Thank you.

For some reason i had to restart my PC twice to get all the updated functionalities. Maybe others should try this too.

Never ever had an UI failed till you “fixed” the thing and now i’m getting this eror on my netbook. Not cool.

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.

Too many restarts for me.

A permanent fix needs to be issued. :-\

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?

Unfortunately that doesn’t help me because I’m using Avast Free. :cry:

+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


https://screencast-o-matic.com/screenshots/u/Lh/1525983057527-2724.png

[b]https://youtu.be/6_OC2o7nAoA[/b]

Why exactly did you post this?

This doesn’t help most of us who are having the ‘UI Failed to load’ issue. :-\

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.

That’s still too many restarts though.

I’ll wait for the devs to respond to this situation that they clearly have not fixed.

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.

I think you will need to restart for the build number to change. It is still Build 18.3.3860.316 until the reboot is done.