*&^%$#@! MSpy did it again!

[Jacee]

Did you disable Windows Defender in Services?

 

[Lady Fitzgerald]

Did you disable Windows Defender in Services?

No, I had disabled it from within Defender. However, thanks for asking. I went into services and disabled there as well.

 

[Callender]

That will probably fix it!

 

[groze]

I don't want to pollute Lady Fitzgerald's thread by continuing to document the interactions of MSE and WD. I just offered a possible explanation as to why the scheduled task for WD was not found.

Lady Fitzgerald is using Avast and it had an update recently (see here).

Maybe:
1) During that update, it uninstalls part of the core components before installing new core files.

2) During the uninstall process, WD was enabled.

3) The update installation of the new version failed to disable WD.

I did download the latest free version. That install did disable WD; however, a full install might differ from an update install. Maybe other Avast users could check to see if WD is currently disabled.


None of the above info explains why/how the WD definitions updated.

I haven't updated Avast yet. They have had too many problem updates lately so I'm waiting to see if any get reported, same as I do with MSpy updates.

That might be the problem Lady Fitzgerald. I read somewhere Microsoft was to add a feature to windows defender in windows 10. That if you don't update any virus software within a certain amount of time it will automatically turn windows defender back on. Maybe Microsoft also added this feature to both windows defender and windows MSE in the older windows operating systems. I hope you understood what I said.

 

[Jacee]

Let us know if the problem is solved

 

[Lady Fitzgerald]

It will take quite a while to know if the problem is solved or not since it occurred sporadically.