Microsoft Defender cannot sign in: what to check first

If Microsoft Defender won’t sign in, the usual causes are the wrong Microsoft account, a network or service issue, or stale cached sign-in data on the device. Start with the safest checks first, because you can often fix it without changing any permanent settings. If those checks fail, the next reversible step is to clear the stuck sign-in state and try the account again.

What the sign-in problem usually looks like

The problem often shows up as a sign-in loop, an account verification failure, or Defender opening but never getting past the sign-in screen. You may enter your details and end up right back where you started, or the window may close and reopen without completing the sign-in.

To tell where the problem is, use the behavior of the same account elsewhere:

• If the same Microsoft account signs in on the web or in another Microsoft app, the account is less likely to be the problem.
• If the account fails in other Microsoft services too, the account itself is more likely the cause.
• If the account only fails on this one device, the device’s cached sign-in data or network state is more likely to be involved.

If you see a message, the exact message varies. The message alone is less useful than whether the same account works elsewhere and whether the failure happens on one device or everywhere.

Before you start

This guide applies when Defender launches but won’t complete sign-in, especially after a password change, a restart, a network switch, or a Windows update.

Check these first:

• Make sure you’re trying the Microsoft account tied to Defender on this device, not a different personal account or a work or school account.
• Make sure the device has a working internet connection.
• If this is a managed work or school device, stop before removing accounts or security connections unless you know which account Defender is using.

If you are unsure whether the account is personal or managed, don’t clear anything yet. Check that first, because removing the wrong account can affect other apps and access.

The safest first check before changing anything

1. Confirm the account you’re using. Compare the email address you’re entering with the account you expect Defender to use. If you have more than one Microsoft account, make sure you’re not mixing up a personal account with a work or school account.
2. Check the connection. Open a website or another online service and confirm it loads normally. If the connection is weak or unstable, switch to a known-good network and try Defender again.
3. Restart the device. A restart clears temporary sign-in state without changing your account or uninstalling anything. After the device comes back up, open Defender and try signing in again before making any other changes.

If sign-in works after one of these checks, the issue was likely temporary. If it still fails, the problem is probably not just a typo or a brief connection glitch.

A reversible fix if sign-in still fails

The next step is to clear the stuck sign-in state and then sign back in with the same account. This is reversible because you can stop after the first part, and you can add the account back the same way if needed.

If this device is tied to a managed work or school account, don’t remove accounts or security connections unless you know which one Defender is using. Removing the wrong one can affect other apps and access.

1. Open the Windows settings area that manages accounts and connected sign-in details. Find the Microsoft account that Defender is using and note which account is currently linked.
2. Remove only the stuck sign-in entry for that account. Use the option that disconnects, signs out, or removes that one account only. Do not wipe the whole device setup or remove unrelated accounts.
3. Restart the device again. This gives Windows a clean chance to rebuild the sign-in state.
4. Sign back in with the same correct Microsoft account. Use the account you confirmed earlier, then try Defender again.

If this does not help, stop before making broader changes such as resetting the whole app or removing unrelated accounts. At that point, the issue may be with the Microsoft account itself or with the device’s identity settings, and those need a more careful check.

How to confirm it worked

The fix worked if Defender accepts the sign-in and stays signed in after you close and reopen it. You should also be able to return to Defender without being sent back to the login screen.

A stronger sign is that the account shown inside Defender matches the one you intended to use and the app still opens normally after a restart. If the same error comes back right away, the issue is not resolved yet.

If Defender still fails but the same account works in another Microsoft service, the device is still the likely problem. If the account fails everywhere, the account side needs attention before you try more app changes.

Frequently Asked Questions

How do I know if the problem is Defender or my Microsoft account?

If the same account signs in elsewhere but not in Defender, the app or device is the likely problem. If the account fails in other Microsoft services too, the account itself is more likely the issue.

Is it safe to remove the account and add it again?

Usually, yes, if you remove only the stuck sign-in entry and you’re sure it’s the right account. If the device is managed by work or school, be careful because the wrong removal can affect other sign-in data.