Avast Premier and Windows 10 May 2019 Update

[zero365]

I've recently installed the May 2019 Update for Windows 10 x64. Update went fine and all but somethings off with Avast displaying as a another security provider. It's not registering as a security provider though it effectively (or it should) disabled Windows Defender. I'm just wondering if Avast products are fully compatible with the May 2019 update?

Also the firewall of avast premier keeps on popping up every restart saying that I've connected to a new network. It's like it's not remembering that I've already set it to identify as a private connection. I've already tried clean installing avast premier but situation remains the same.

[zero365]

I've attached on how it looks like Windows Security. Also... Windows Firewall is reporting that it's still on but Speccy says the firewall I'm using is Avast.

[zero365]

Another thing...

I can still run Windows Defender quick scans and its other features like real-time protection are still on even though Avast is installed. Won't these have any conflicts if not fixed? Sorry for the multiple replies, I can't seem to find any edit button on this post of mine.

[novakja]

Hello, thank you for the report.

We have not encountered this issue in our internal testing but we will investigate.

Could you possibly provide us with support package according to instructions at FAQ Submitting a support file using the Avast Support Tool ?
Do not forget to post the file ID here so we can find it on the target ftp.
This would greatly help the investigation.

Thank you!

[zero365]

Sure, let me get into that shortly. I'll update this post once I'm done, Thanks again.

[zero365]

Here's the File ID you requested: HW8JZ

[mchain]

Another thing...

I can still run Windows Defender quick scans and its other features like real-time protection are still on even though Avast is installed. Won't these have any conflicts if not fixed? Sorry for the multiple replies, I can't seem to find any edit button on this post of mine.

Snip will be attached for the edit feature: 

(In this example I've clicked Modify>Attachments and other options>Attach>Modify Post.png)

[zero365]

Any updates on this?

[bob3160]

Probably not till Mon.

[zero365]

I've reverted back to 1809 since my issue is annoying me. Probably won't update to the latest feature update until this beta test of Microsoft is over.

EDIT:

Now the same issue showed on the 1809 build of Windows 10.

[novakja]

Hello,
sadly we were unable to reproduce your issue so far.

The log file for the component responsible for registering Avast as an AV provider in windows security center is also missing. Please, could you go to "Menu -> Settings ->Troubleshooting -> Logs", enable Debug logging, and then perform "Repair app" just above the logs section? After the repair is complete (will prompt for reboot), please generate and send us new support package, hopefully the required logs should be present this time.

Also, if the repair does not fix the issue, I would suggest to use Avast Clear to completely remove Avast from your system, and then reinstall it to standard path ("C:\Program Files"). Using non-standard installation paths is discouraged by Microsoft as can be read i.e. here.


Thank you very much for your cooperation!

[zero365]

Sure, will do that. Will update this topic again as soon as I get into it.

[traceyw]

Just this minute realised I have the same problem. Initially I thought it was down to Windows 1903 but just now I reset my network to Private using the facility provided in the Avast dialogue that appears and it immediately reverted back to Private whereas I've had to have two goes at it using the Network settings dialogue. Even sent a Feedback Report to MS! As Zero365 says, there's something not right somewhere -- and its annoying.

Tracey

[Asyn]

Hi Tracey, if you're willing to help, see Reply #10.

[bob3160]

There appears to be another post on this same topic:
https://forum.avast.com/index.php?topic=227414.msg1506926#msg1506926