Avast UI Fails after Windows 10 Update (Spring Update) 1803

[REDACTED]

Using Avast Free AV v18.3
Windows 10 Pro 1803

I decided to upgrade to latest windows update knowing things would break. Other than several breaking issues with windows, avast's UI didnt like the update and UI crashes and never recovers no matter what I do, including completely uninstalling and deleting all of Avasts' folders and reinstalling.

I believe this may be a bug in Avast. Thinking about testing latest Avast beta to test if it fixes this issue.

Update:
Avast Free AV v18.4 beta has same UI issue.

[Patrick2]

Best to Wait til the next version of Windows 10 is Final/officially released, as of right now only officially on Insider Fast/Slow and Release Preview ring, I'll admit I did try it on my insider release preview PC, 18.4 beta and have same issue with Ui, ended up removing and just relying on Windows Defender right now til 1803 is officially final

[REDACTED]

Way ahead of you, removed Avast and I am currently waiting. Wanted to report the bug to Avast.

[bob3160]

Thanks for the report. I've made Avast aware of the problem.
Next move is up to them.

[Patrick2]

Wonders How long it will be til Final Spring Creators out, due to this issue that I also experienced, relying on Windows Defender til it's final lol,  I know option to restore system drive image or clean install to go back to 1709, but trying to avoid another clean install,  moral lesson here don't run Insider Release preview or install a Windows OS update early in an attempt to save time lol


I figured was "sorta final lmao" so I was like yeah install early while I got time,  did on 3 systems lol, then stopped before did 4th one

[Asyn]

...moral lesson here don't run Insider Release preview or install a Windows OS update early in an attempt to save time lol

+1

[REDACTED]

I'm wondering if this is similar to what I am seeing on Server 2008 R2.  I try to launch the console, this fails, at which point everything except the mouse disappears from the screen.  I can Ctrl-Alt_Del but the only way I can recover is to log off and start again.  So far this has happened on all console access attempts on the server.  My 2012 server seems fine.

[bob3160]

There isn't any guarantee of compatibility if you're using a build.
When the final release comes out and you still have a problem, then there's a problem.

[matthew343]

FYI, the official release of v1803 came out on 4/30 and if you install from the Media Creation Tool, it does not let you proceed unless you uninstall Avast.

[bob3160]

FYI, the official release of v1803 came out on 4/30 and if you install from the Media Creation Tool, it does not let you proceed unless you uninstall Avast.

https://forum.avast.com/index.php?topic=156141.msg1459636#msg1459636

[calliefgrace]

I am also experiencing this issue after the update to 1803. I have tried uninstalling and reinstalling but to no avail.

[matthew343]

I wound up here via Google, FWIT I did disable Avast til next boot, the major difference my Avast icon looks different, possibly because I am using Endpoint Protection.

[REDACTED]

I wound up here via Google, FWIT I did disable Avast til next boot, the major difference my Avast icon looks different, possibly because I am using Endpoint Protection.

When you first install the Windows update 1803 and reboot on first install it deactivates Avast, all you have to do is do another reboot after going to desktop and Avast is working fine, mine is so far .

[bob3160]

You can also deactivate the Avast Shields until the system is restarted
before you start the upgrade process as recommended in the video.

[Happychappy]

After the April windows update I have had to do  system restore,avast going down and  blue screen of death 4 times tonight.

Thanks MS.

How do i stop this crappy update and only get critical updates ?

tia