Window's Defender impossible to completely disable in Win10

[Nietzsche 0]

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? 

[itman 1,659]

1 hour ago, Nietzsche said:

They are WD's smart screen", "WD notification" ctr.

These are enabled in Win 10 CE for security reasons.

First, it is not WD's SmartScreen but Win 10's native SmartScreen which is independent of any security solution. It will perform reputational scanning on anything with the "Mark of the Web" i.e. downloaded from the Internet. I have found it useful in alerting for "unknown" program startup that Eset's LiveGrid allows to run w/o issue.

WD Notification Center is enabled by default since WD is the backup security solution if your third party AV solution malfunctions or is disabled by malware. WDNC allows for immediate switch over to WD in these instances. If it is removed or disabled, there will be a noticeable lag until WD actual enables itself which could allow malware to run unabated.

[Nietzsche 0]

While WD not cntr was consuming practically no memory, poss conflict still remained in my mind w/ eset. noticed on another pc running eset and paid uninstaller w/ start mgr, that WD was starting by name. On this laptop, with Win 10, it was entered as "SecurityHealth", with full name Windef obscured. After disabling WD no longer running at all. Assume other's have resolved this issue in their own manner. If Window's Defender was harder to disable or more efficient there would be no need fore eset etal. knew there had to be a way to completely disable.