Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: AvastUser015 on May 09, 2014, 03:51:21 AM

Title: .2018 bug?
Post by: AvastUser015 on May 09, 2014, 03:51:21 AM
I may have discovered a bug with the latest update .2018. After installing the update, Windows Update now shows Defender Definitions as available updates. This did not occur with the .2016 version.

Also, with .2016 - when you click Windows Defender in Control Panel, you got a simple box saying that it is turned off. With .2018 - Windows Defender UI opens with Defender off. Obviously, .2018 update changed something.

Has anyone else reported this? You should look into this. Thanks.
Title: Re: .2018 bug?
Post by: CraigB on May 09, 2014, 08:27:55 AM
Has anyone else reported this?
Not that I've seen.

What system - vista, win7, win8? was it an update from the UI, an over the top install or a clean install?
Title: Re: .2018 bug?
Post by: Staticguy on May 09, 2014, 11:42:03 AM
When installing Avast Free, windows defender will be automatically disabled. Is your windows defender disabled?
Title: Re: .2018 bug?
Post by: DavidR on May 09, 2014, 02:39:15 PM
When installing Avast Free, windows defender will be automatically disabled. Is your windows defender disabled?

I thought it was only in windows 8 that windows defender was disabled when installing a resident AV. This because WD in windows 8 is an antivirus (more like MSE), rather than an anti-spyware (windows 7).

That said (I don't have win8 to test), but I think that even with it disabled, it might still receive virus definition updates, via windows update.
Title: Re: .2018 bug?
Post by: AvastUser015 on May 09, 2014, 09:28:42 PM
The OS is Windows 8.1 Pro 64 bit with Update 1. I installed 2018 over-top via avast update. Defender is disabled (always has been). Windows Update never showed Def updates before v2018 and they won't install anyway since it is disabled. In sure that 2018 is the culprit since it is the only changed I have made to my system recently. The difference is that with 2016, a white box popped up to say that Defender is turned off and with 2018, the Defender UI pops up.

I did run services.msc and saw 2 entries for Windows Defender. With 2016 - the start-up type is Manual. With 2018 - I believe the start-up type on one of the entries is Automatic. This may have something to do with it. I can't change it since it is disabled.

I have restored a drive image with v2016. I hope that you can confirm this problem and release a fix. Thanks.
Title: Re: .2018 bug?
Post by: essexboy on May 09, 2014, 09:55:19 PM
Not receiving that on my windows 8.1.1  with Avast .2018
Title: Re: .2018 bug?
Post by: Staticguy on May 09, 2014, 09:58:06 PM
When installing Avast Free, windows defender will be automatically disabled. Is your windows defender disabled?

I thought it was only in windows 8 that windows defender was disabled when installing a resident AV. This because WD in windows 8 is an antivirus (more like MSE), rather than an anti-spyware (windows 7).

That said (I don't have win8 to test), but I think that even with it disabled, it might still receive virus definition updates, via windows update.

My Windows Defender is disabled for good because I installed Avast Free. I don't even see an update for WD for it's definition updates on Microsoft Update.
Title: Re: .2018 bug?
Post by: DavidR on May 09, 2014, 10:34:14 PM
When installing Avast Free, windows defender will be automatically disabled. Is your windows defender disabled?

I thought it was only in windows 8 that windows defender was disabled when installing a resident AV. This because WD in windows 8 is an antivirus (more like MSE), rather than an anti-spyware (windows 7).

That said (I don't have win8 to test), but I think that even with it disabled, it might still receive virus definition updates, via windows update.

My Windows Defender is disabled for good because I installed Avast Free. I don't even see an update for WD for it's definition updates on Microsoft Update.

Thanks for that, I have win7 on my other system and that was receiving windows updates for signatures. I can't recall how I stopped them; I did disable WD, I wasn't impressed that I couldn't completely uninstall it.
Title: Re: .2018 bug?
Post by: bikemanAMD on May 09, 2014, 10:37:08 PM
Not Receiving Windows Defender Defintitions updates on Windows 8.1.1 with Avast 2018...Just other minor issues dealing with (topic on that awaiting replies lol)  otherwise everything seems to be working fine so far

Title: Re: .2018 bug?
Post by: plsrepli on May 09, 2014, 10:38:37 PM
Once Avast is installed (in Windows 8 or 8.1) Windows Update will stop offering Defender updates and that's a good thing for those of us that like to control "when" we download and apply those updates. In fact, I just did a recent clean install of 8.1 Update 1 and (initially) I had Defender updates pending; however, after installing Avast, those pending updates actually disappeared from availability.
Title: Re: .2018 bug?
Post by: Alikhan on May 09, 2014, 10:48:57 PM
I have seen certain cases where installing avast! does not disable WD sometimes. Therefore, it is necessary to check to make sure it's been disabled.

You can easily check that through action center and is not a bug related to this version.