After last huge win 10 update, window's defender reactivated itself, after I had painstakingly disabled it, 2nd time this had happened to me after w10 updates. I managed to completely disable it after w10 update, before the last one with a paid third party uninstaller's tool/ startup mgr. This time could still partially disable it with same installer, but remnants of WD are still running in tasks. WD has now integrated itself with Eset SS, and remnants of WD itself are still running! They are WD's smart screen", "WD notification" ctr. These tasks can be ended by task mgr after EVERY BOOT. As they consume practically no memory not that much of a problem, but it is a AV and could conceivably conflict with my Eset. Anyone aware of this conflict after last massive w10 update, and how can one totally disable WD, now?