*&^%$#@! MSpy did it again!
-
RE: Windows Defender. I have always disabled it. However there's a scheduled task that will run even if you disable the windows defender service and registry entries:
Attachment 371889
Checked registry for MS Spynet and all entries seem to be disabled. I don't use MSE.
Attachment 371891
I checked task scheduler and I couldn't find an entry for Windows Defender.
-
-
I checked task scheduler and I couldn't find an entry for Windows Defender.
Okay no problem. It must have been deleted sometime in the past.
-
I checked task scheduler and I couldn't find an entry for Windows Defender.
Okay no problem. It must have been deleted sometime in the past.
I seem to recall that Lady Fitzgerald once used MSE.
MSE not updating beyond definition version 1.143.376.0
Installing MSE deletes the scheduled task shown below.
Uninstalling MSE does not restore it.
(At least not to the same location.)
-
-
That's interesting. I wonder if Windows Defender Service startup is disabled via msconfig> services?
As far as I can work out these two files are responsible for running update checks for windows defender:
C:\Program Files\Windows Defender\MpCmdRun.exe
C:\Program Files\Windows Defender\MSASCui.exe
I'd suggest a scan using AutoRuns then search for "Defender" just in case there's an entry somewhere that is still enabled.
-
I turned off defender just to play with it a bit,
Checked and there wasn't a task listed as UNI showed.
Kind of odd I have noticed after uninstalling MSE which updates came as Optional possibly recommended but defenders comes as important :/
-
What were the KB's that Microsoft sneaked in.
KB915597
It gets even more insidious. I went into Windows Defender to see what was going on (the update was definitions for Windows Defender) and found it had turned itself back on (I had it turned off since I have an AV), was checking for definitions before running scans, apparently downloading and installing them, and also has something I hadn't seen before: Microsoft SpyNet. Supposedly, it only sends information about detected spyware threats but one line in what SpyNet does was especially chilling: "In some instances, personal information might be unintentionally sent to Microsoft." Unintentionally my Aunt Fanny! MSpy went too far a long time ago and has been steadily getting worse. I may not wait until 2020 to tell MSpy to go to hell!
What were the KB's that Microsoft sneaked in.
KB915597
It gets even more insidious. I went into Windows Defender to see what was going on (the update was definitions for Windows Defender) and found it had turned itself back on (I had it turned off since I have an AV), was checking for definitions before running scans, apparently downloading and installing them, and also has something I hadn't seen before: Microsoft SpyNet. Supposedly, it only sends information about detected spyware threats but one line in what SpyNet does was especially chilling: "In some instances, personal information might be unintentionally sent to Microsoft." Unintentionally my Aunt Fanny! MSpy went too far a long time ago and has been steadily getting worse. I may not wait until 2020 to tell MSpy to go to hell!
RE: KB915597
I've been messing aroud with Portable Windows Updates Notifier (application) and interestingly the default settings automatically install KB915597. Personally, I set the app not to install that update. So the question is why does this app offer to install this update by default? It also offers to install KB2310138.
Last edited by Callender; 20 Sep 2015 at 08:15.
Reason: another correction
-
-
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 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.
-
..so why not report the problems yourself?
-
..so why not report the problems yourself?
Because I prefer to avoid them.