Windows defender started with avast

[blindfreddy]

Avast Internet Security version 19.5.2378  Build 19.5.4444.503

Windows 10 Pro 64 Bit version 1903  build 18362.145

Booted up computer today and windows defender started up with avast. Took a long time to boot up.
When booted up the avast icon in task bar was red saying "you are unprotected".
Clicked to open GUI which did not load.

I ended up uninstalling avast and reinstalled all is well at the moment. Have restarted and booted up several times.

Just curious if anyone else have had this problem and what was done to rectify this problem.

Cheers

[bob3160]

Avast Internet Security version 19.5.2378  Build 19.5.4444.503

Windows 10 Pro 64 Bit version 1903  build 18362.145

Booted up computer today and windows defender started up with avast. Took a long time to boot up.
When booted up the avast icon in task bar was red saying "you are unprotected".
Clicked to open GUI which did not load.

I ended up uninstalling avast and reinstalled all is well at the moment. Have restarted and booted up several times.

Just curious if anyone else have had this problem and what was done to rectify this problem.

Cheers

Sounds like there was a problem with something in Avast and it never loaded properly hence, Defender became the default AV.
If that ever happens again, I'm sure Avast would love to see a support package to see what went wrong.
https://support.avast.com/en-us/article/33/
I'm sure that a simple repair of Avast would have fixed the problem which is less time consuming than an uninstall and re-install.

Repair Avast:
Open the Avast User Interface > Menu > Settings > Troubleshooting > Repair App. > Restart the Computer
I've seen it happen after a Windows update.

[blindfreddy]

Thank you bob3160 for your reply

If it happens again I will attempt to send a support package.

I will also try a repair also if it happens again, I do over react at times

Cheers

[Vapor]

Windows 10 had that issue in the past were would disregard your personal AV and load Defender regardless I had that happen month or so ago in my son's Windows10.

You can avoid future issues and disable defender all together in registry, you shouldn't really resort of doing that,  but at least you know you can if you need to 

[blindfreddy]

Windows 10 had that issue in the past were would disregard your personal AV and load Defender regardless I had that happen month or so ago in my son's Windows10.

You can avoid future issues and disable defender all together in registry, you shouldn't really resort of doing that,  but at least you know you can if you need to 

Thanks for your reply Vapor 

I googled how to disable windows defender by using the registry. Doesn't look to difficult if I follow the instructions.  "( But I would find a way to  stuff it up) .

I will give that ago if the problem became consistently, and was not able to remedy the problem with avast.

Of course I will back up if I do try it.

Cheers

[schmidthouse]

Windows 10 had that issue in the past were would disregard your personal AV and load Defender regardless I had that happen month or so ago in my son's Windows10.

You can avoid future issues and disable defender all together in registry, you shouldn't really resort of doing that,  but at least you know you can if you need to 

Thanks for your reply Vapor 

I googled how to disable windows defender by using the registry. Doesn't look to difficult if I follow the instructions.  "( But I would find a way to  stuff it up) .

I will give that ago if the problem became consistently, and was not able to remedy the problem with avast.

Of course I will back up if I do try it.

Cheers

I personally would NOT recommend any Registry Edits (Disabling Defender).
If that is done and Avast for whatever reason stops protecting then you have no backup and therefore No Protection.
Ideally, WD kicks into protection if the 3rd party (Avast) Firewall fails (stops protecting)
I run Avast Premier on Win 10 1903 64Bit and have had NO issue with Defender not disabling.
I would recommend providing info(logs) as Bob3160 has mentioned as the most effective way of resolving the issue you are having.....

[blindfreddy]

Hi schmidthouse thanks for your response 

If the problem returns I will definitely provide the support package  bob3160 was referring to.

I probably be to much of a chicken to change anything in the registry, as I would only do this as a last resort.

Cheers

[schmidthouse]

You're welcome.

Providing logs for the developers not only is the best way to see 'exactly' what's going on with your system configuration, not to mention any bug resolution/fix will also benefit everyone.

[bob3160]

Hi schmidthouse thanks for your response 

If the problem returns I will definitely provide the support package  bob3160 was referring to.

I probably be to much of a chicken to change anything in the registry, as I would only do this as a last resort.

Cheers

One other thing to consider. If you defeat Defender via a reg. fix and you again have a problem with whatever third party Av you happen to be using,
Defender will not automatically start and protect you as it did in your last episode.
I'm kind of happy that Defender is always there as backup, just in case.

[schmidthouse]

Hi schmidthouse thanks for your response 

If the problem returns I will definitely provide the support package  bob3160 was referring to.

I probably be to much of a chicken to change anything in the registry, as I would only do this as a last resort.

Cheers

One other thing to consider. If you defeat Defender via a reg. fix and you again have a problem with whatever third party Av you happen to be using,
Defender will not automatically start and protect you as it did in your last episode.
I'm kind of happy that Defender is always there as backup, just in case.

You're welcome.
As Bob3160 has confirmed the concern I stated in post #5 (not editing the Registry) I think your decision to provide a support pkg can work to resolve the issue