Version: 18.4.2338

[REDACTED]

Probably I was not clear enough. The 3 reboots were only a check up (a triple check, just to say so), I had no problem at all even after the first reboot.

Personally, I disabled the Behavior Shield because it was the source of a lot of problems for me. Actually I only keep the basic shields active: Web, Mail, and (of course) filesystem Shield.

That's not really a 'fix' though and that shouldn't have to be done to 'fix' it.

The fact remains that the devs need to make a fix that actually fixes the issue permanently. Especially now that it looks as though their 'troubleshooting' fix isn't working anymore.

[Patrick2]

Well before This Avast version I had NO issues,  now I had a lot,  and sick of it,  Permenant solution to UI Failing needed, Fix to Behavior Shield not turning on for folks that wanna use that,  and Stopping of Corruption of files in winsxs folder, how that happened I have no idea,  removal and reinstall didn't help either.    I'm almost ready to do a clean install of WIndows 10 1803  and not even bother reinstalling Avast Free at this point

[REDACTED]

Well before This Avast version I had NO issues,  now I had a lot,  and sick of it,  Permenant solution to UI Failing needed,

QFT

[Patrick2]

QFT?

[bob3160]

Well before This Avast version I had NO issues,  now I had a lot,  and sick of it,  Permenant solution to UI Failing needed, Fix to Behavior Shield not turning on for folks that wanna use that,  and Stopping of Corruption of files in winsxs folder, how that happened I have no idea,  removal and reinstall didn't help either.    I'm almost ready to do a clean install of WIndows 10 1803  and not even bother reinstalling Avast Free at this point

Time to find out what other security programs you're using.
No problem here with Avast Free an 4 different systems.

[Patrick2]

Avast Free main program
and Malwarebytes 3.5.1

Nothing else
Defender should be off,  Shutdown nightly, corrupted Avast files in winsxs folder and manifests,  doing clean install tomorrow, is it safe to reinstall Avast, or should I stick with Defender til Avast is working well

[bob3160]

Avast Free main program
and Malwarebytes 3.5.1

Nothing else
Defender should be off,  Shutdown nightly, corrupted Avast files in winsxs folder and manifests,  doing clean install tomorrow, is it safe to reinstall Avast, or should I stick with Defender til Avast is working well

If your OS is corrupt, you're going to have problems with other programs. Surprised it's only a problem with Avast.

[Patrick2]

System File checker only gets to 2 percent, how it corrupted I have no idea, as I just was attempting to get Avast past the UI Failed screen/and behavior shield working

CBS Log lists Avast.crt a lot

(1)  StageFile: flags: 8 app: [Avast.VC140.CRT, version 14.0.25325.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]'win32']) comp: Avast.VC140.CRT, version 14.0.25325.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]'win32' file: [l:30 ml:31]'api-ms-win-crt-heap-l1-1-0.dll' srcfile: @0x1ff0cbd6cc0

 (2)  StageFile: flags: 8 app: [Avast.VC140.CRT, version 14.0.25325.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]'win32']) comp: Avast.VC140.CRT, version 14.0.25325.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]'win32' file: [l:12 ml:13]'msvcp140.dll' srcfile: @0x1ff0cbd7580
  (3)  StageFile: flags: 8 app: [Avast.VC140.CRT, version 14.0.25325.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]'win32']) comp: Avast.VC140.CRT, version 14.0.25325.0, arch x86, versionScope neutral, pkt {l:8 b:fcc99ee6193ebbca}, type [l:5]'win32' file: [l:33 ml:34]'api-ms-win-crt-runtime-l1-1-0.dll' srcfile: @0x1ff0cbd75f0

you get the idea, i got a ton of those in system file checker log, why doing clean install again in morning, then will think if i should even reinstall Avast or not

[bob3160]

Personally can't understand how or why you're complaining about Avast when you have those types of OS problems.
Fix the OS first then do a clean install of Avast. If at that point you still have a problem, then I can understand your concern.

[Patrick2]

Yeah well other machines were clean installed not long ago, and those are having the problems I mentioned

Laptop
and Desktop 2 still having issues

but i'll clean install this one in morning and give Avast another shot, hopefully works properly then and stays working

[Patrick2]

Yeah think I may just fix OS, and not even bother reinstalling Avast...I reported this even when it wasn't offical 1803, UI failing to load, a nd Behavior shield issues, but don't know if that topic got much replies or anything,

 Originally installed 17133 RTM build or was suppose to be, had issues then on Desktop 2 Machine,  same with 17134 when was on Release preview, may have reported then also somewhere buried in 18.2.x version area

OS has System File Checker corruption, seems to be pointing to an Avast file, so just on safe side think will do one more clean install of Windows 10 Pro 17134 (1803) just to be on safe side lol,  as for Avast iffy I'll reinstall again

[bob3160]

Your computer, your choice.

[predatorz]

Updated to 18.4.2338 sucessfully on my laptop and desktop.
Laptop have the problem of UI not loading at 2nd reboot, 3rd reboot no more problem with Avast.
 

[REDACTED]

QFT?

Quoted For Truth

Updated to 18.4.2338 sucessfully on my laptop and desktop.
Laptop have the problem of UI not loading at 2nd reboot, 3rd reboot no more problem with Avast.
 

That's too many restarts. I shouldn't have to restart my Windows 10 laptop 3 times just to get it to work properly. Which is why the devs need to release a permanent fix so that something like this doesn't have to be done.

Time to find out what other security programs you're using.
No problem here with Avast Free an 4 different systems.

Yeah but you restarted 3 times with Avast Free right?

As I just stated above, that's too many times to restart a computer just to get it to work properly. That shouldn't have to be done to get it to work properly.

Which is why I'm hoping an actual permanent fix is made by the devs so this doesn't have to be done.

[Patrick2]

Actually 2 Users reported this problem with UI Failing and Behavior Shield failing as early as April 12th, as we decided to upgrade early to the possible final 17133 at that time.   What was Avast doing after we reported the issue?   Did they even test Avast products on 17133, and 17134 prior to release?   at this point it seems like they didn't

This program should've been smooth from the get go soon as Windows 10 April Update was officially released,  Us Windows Insiders reported issue way early, yet nothing was done to fix the issues it so appears, I even used Avast submit feedback option, but appears that did nothing either

I know was reported in both 18.3 part of Avast forum, and 18.4 beta section that Avast had problems with Spring Update as early as April 12th