Microsoft Defender keeps restarting: what to check first

If Microsoft Defender keeps restarting, the cause is usually a Windows update finishing, another antivirus or security tool taking over, or a problem with the Windows Security app or Defender service. Start with the safe checks: restart Windows, finish any pending updates, and see whether another security product is installed. If the loop continues, repair Windows Security and check for corruption or a policy conflict.

What “keeps restarting” usually means

“Keeps restarting” can mean different things, and the fix depends on which one you’re seeing.

If the Windows Security window closes and opens again, that points more toward the app itself or a Windows update finishing in the background. If Defender protection turns off and then comes back on by itself, another antivirus or security tool may be taking control. If the whole PC is restarting, that’s a broader Windows problem, not just Defender.

A restart once after an update can be normal. Windows may briefly reset Defender components while it finishes installing changes. Repeated restarts, repeated “needs attention” prompts, or Defender turning off again after you re-enable it usually point to corruption, a policy conflict, or another security product interfering.

Before you start

Use this quick check to narrow down what’s actually restarting.

• If only the Windows Security window is closing and reopening, focus on the app and its services.
• If Defender says protection is off and then turns back on, look for another antivirus or security suite.
• If Windows itself is rebooting, deal with the PC restart first, because Defender won’t stay stable until that is fixed.
• If this is a work or school device, local changes may be overwritten by organization policy.

The quick checks that solve this most often

Start with the safest checks first. They fix a lot of cases without changing settings.

1. Restart Windows. A clean reboot clears temporary glitches and finishes some background changes. After the restart, open Windows Security and see whether Defender stays open and enabled.

Finish pending Windows updates.Open Settings > Windows Update and install anything waiting there. If Windows asks you to restart, do that before checking Defender again.

Settings > Windows Update

If Defender was only restarting because an update was in progress, this often stops the loop.

3. Check for another antivirus or security suite. Look in Apps > Installed apps or Apps & features for a second antivirus, endpoint protection tool, or cleanup/security suite. If one is installed and actively managing protection, Defender may disable parts of itself and relaunch while Windows hands off security control. If you find one, use that product’s own uninstaller or management tool to remove or disable it. Don’t delete files by hand. After that, reboot and check Defender again.
4. Run a quick health check. Open Windows Security and run a quick scan. Also check whether Windows shows any alert about protection status or a service needing attention. If the app opens normally and the status stays on after the scan, that’s a good sign the issue was temporary. If these checks fix the problem, stop here. If Defender still restarts, move on to repair steps.

The fixes to try when it still comes back

If the easy checks didn’t hold, repair the pieces Defender depends on, starting with the least disruptive option.

1. Repair or reset the Windows Security app. In Windows, open the app settings for Windows Security and use Repair first if it’s available. That keeps your settings and only fixes the app files. If Repair doesn’t help, use Reset only if you’re comfortable reapplying any custom security settings afterward. The expected result is that Windows Security opens normally and stays open after you close and reopen it. If it still relaunches or closes itself, the problem is probably not just the app shell.

Check the Defender services.Open the Services console and look for Microsoft Defender-related services. They should not be stuck disabled or repeatedly stopping and starting.

services.msc

If a Defender-related service is set to disabled or keeps failing, that can point to a policy, a third-party security tool, or system corruption. Don’t force random startup changes if the service is being managed by organization policy on a work PC; that can be overwritten again.

3. Look for policy settings that disable Defender. If this is a personal PC, check whether a local policy, management tool, or leftover antivirus policy is turning Defender off. On managed devices, group policy or device management may intentionally control Defender, which can look like restarting or disabling. If you know the machine is managed by work or school software, stop here and check the organization’s security policy instead of trying to override it locally.

Check system files.Corrupted Windows files can make Defender components reload or fail repeatedly. Run the built-in system file check and let it finish before testing again.

sfc /scannow

If SFC reports repairs, reboot and test Defender again. If it reports that it found problems it could not fix, that usually means a deeper Windows repair is needed before Defender will stay stable.

5. Recheck after each change. After one repair, reboot and test before making another change. That makes it easier to tell which fix actually stopped the restarting, and it avoids stacking changes on top of each other.

How to tell if it’s actually fixed

Defender is probably fixed if Windows Security opens normally, the protection status stays on, and the window no longer closes and relaunches on its own.

After a reboot, check that:

• Windows Security stays open instead of immediately refreshing or restarting.
• Real-time protection remains enabled, if that setting is available on your device.
• No repeated restart prompt appears.
• The Defender service does not drop out and come back on its own.

If the problem comes back only after you open a specific antivirus or management app, that app is likely the source of the conflict. If Defender stays stable for a full reboot cycle and no warning returns, you’ve probably cleared the cause.

Conclusion

If Defender still keeps restarting after these checks, the remaining cause is likely a managed policy, a damaged Windows installation, or another security product still holding control. Revisit the last step that changed anything, then decide whether the device needs admin support or a deeper Windows repair.