Reply to thread

Message

<blockquote data-quote="SeriousHoax" data-source="post: 1005367" data-attributes="member: 78686">Yeah, this is normal. I was in 22H2 Insider builds for a while, and it&#039;s been like this for a long timr. So this is normal behavior. It&#039;s always running now, even though it doesn&#039;t use any system resources excluding ram. But I think by default it updates the signature once a day. Correct me if I&#039;m wrong about this info.If you&#039;re bothered by it, then uninstall your third-party AV, turn off Defender&#039;s Tamper Protection and use Defender Control to disable the service. You&#039;ll also lose the Windows Security Icon. You can use Defende Control after installing third-party AV also but it works when Tamper Protection is off and Tamper Protection can not be turned off when a third-party AV is installed. So one way or another you have turn it off to use Defender Control.There could be other extreme methods also but doing it like this seems safe enough to me. Otherwise, ignore the running process. MS has probably done it to make it harder to disable Defender&#039;s service.</blockquote>

[QUOTE="SeriousHoax, post: 1005367, member: 78686"] Yeah, this is normal. I was in 22H2 Insider builds for a while, and it's been like this for a long timr. So this is normal behavior. It's always running now, even though it doesn't use any system resources excluding ram. But I think by default it updates the signature once a day. Correct me if I'm wrong about this info. If you're bothered by it, then uninstall your third-party AV, turn off Defender's Tamper Protection and use Defender Control to disable the service. You'll also lose the Windows Security Icon. You can use Defende Control after installing third-party AV also but it works when Tamper Protection is off and Tamper Protection can not be turned off when a third-party AV is installed. So one way or another you have turn it off to use Defender Control. There could be other extreme methods also but doing it like this seems safe enough to me. Otherwise, ignore the running process. MS has probably done it to make it harder to disable Defender's service. [/QUOTE]

Verification