Have you tried restarting your PC?
Do you have any other Anti-Virus software installed?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
hi guys,
i use only Windows Defender as an antivirus Program, but i got "the threat service has stopped. restart it now." i restart it but nothing changed! and i've seen some topics tell that if you change "DisableAntiSpyware" value to 0, it will fix the problem, but when i follow the path i didn't find this "DisableAntiSpyware" !
please help!
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Have you tried restarting your PC?
Do you have any other Anti-Virus software installed?
Some users might be experiencing a glitch with starting the Threat Service (Windows Defender Antimalware Service) that was delivered on Patch Tuesday. So the first thing to try would be manually restarting the PC lots of times, with a break between the restarts (Start button > Power > Restart), as suggested by Le Boule in this thread:
This issue might also be related to the known glitch where the Security Center Service needs to be restarted in order to get Windows Defender up and running – so try this:
1. Press Win Key + R
2. Type “services.msc” and click OK.
4. Right-click on Windows Defender Antivirus Service and click Start.
Other suggestions for starting Windows Defender are presented in this Forum Article:
I hadn’t noticed that PrashantKumar96 actually advised setting DisableAntiSpyware = 0 **** in his forum article. Before you do that, you should always try just deleting any possible entry for DisableAntiSpyware = 1, since that setting might have been added by another program or by malware – and that setting will always prevent Windows Defender from starting. For the sake of both ease and safety, this should be done with a REG command.
Type “cmd” in the search box; and then right-click on Command Prompt and select Run as administrator.
And then copy, paste, and enter this command:
REG DELETE "HKLM\SOFTWARE\Policies\Microsoft\Windows Defender" /v DisableAntiSpyware
This is the proper way to enable Windows Defender when it's been turned off via Group Policy.
We can see that there’s a general confusion with respect to this Group Policy setting by the way that Brink equates deleting the DisableAntiSpyware entry with setting its value to 0.
DisableAntiSpyware DWORD
(delete) or 0 = On
1 = Off
https://www.tenforums.com/tutorials/5918-turn-off-windows-defender-windows-10-a.html
But this setting actually uses a three-state logic, where the absence of the setting specifies the normal Automatic Disabled compatibility mode for Windows Defender. Setting DisableAntiSpyware = 0 sets Windows Defender's operational state to “always on” [DisableAntiSpyware = 0 (logical “no/never”)], whereas [DisableAntiSpyware = 1 (logical “yes/always”)] sets Defender’s operational state to “always off”; and where removing the DisableAntispyware registry entry simply returns Defender to its default operational state – where Defender will be automatically disabled by the installation of any third-party AV app, and automatically enabled when a third-party AV app is uninstalled.
Windows Defender operational states
Truth Value of DisableAntiSpyware Operational State
Undefined (unspecified) Automatic Disabled (default)
True (1, logical yes/always) Always Off
False (0, logical no/never) Always On
Therefore, setting DisableAntiSpyware = 0 should only be done as a last resort, after first deleting any DisableAntiSpyware entry, and after all of the following troubleshooting steps have been fully applied, since having to resort to this “always on” setting means that there’s something seriously wrong with the system; and because this setting will have adverse and unforeseen consequences. For example, I set Defender to “always on” after installing Avast Free in order to see what effect this would have – and although I didn’t see any prompt to restart the Defender Service in the WDSC app itself, the prompt did immediately appear in the Windows Defender Antivirus UI, and this turned on Windows Defender (complete with real-time protection) after just a moment's hesitation.
So we need to be clear that setting DisableAntiSpyware = 0****will allow Windows Defender to run alongside any third-party AV app with its real-time protection enabled, which would result in all kinds of different performance and operational issues in the event that a third-party AV app was installed at some future point in time. So this setting is something to be avoided if at all possible, and you should always try the REG DELETE command provided above first, and then follow these troubleshooting steps before setting Windows Defender to "always on":
If none of these steps allow you to restart the Windows Defender Antivirus Service, then you can try setting the Group Policy for Widows Defender to “always on”.
Type “cmd” in the search box; and then right-click on Command Prompt and select Run as administrator.
And then copy, paste, and enter this command:
REG ADD "HKLM\SOFTWARE\Policies\Microsoft\Windows Defender" /v DisableAntiSpyware /t REG_DWORD /d 0 /f
Then click the Restart button (it might be necessary to restart the PC first).
If this REG ADD command fails to resolve the issue, then run the REG DELETE command above to delete the Disable Antispyware entry, and then temporarily install a free third-party AV solution to tide you over until we can get a handle on things. Replacing Defender with a third-party AV app should at least provide you with a viable alternative for Defender’s real-time protection, and allow you to connect to the internet safely:
https://www.pcmag.com/article2/0,2817,2388652,00.asp
GreginMich
Alright, an update:
So for the poor soul who has the same issue, finds this thread, and is looking for an easy solution, I hope you managed to solve this with less hassle than I did.
yes i did but nothing changed, i had malwarebytes but i uninstall it completely and the problem still exist !