We can’t sign you with this credential because your domain isn’t available

Imagine a situation when you are usually able to login to your system with cached credentials and get the following error:

We can’t sign you with this credential because your domain isn’t available. Make sure your device is connected to your organization’s network and try again. If you previously signed in on this device with another credential, you can sign in with that credential.

We can’t sign you with this credential because your domain isn’t available
Ideally, as soon as it points to an issue with the domain joining, users would delete the computer/s from the domain and rejoin them. However, it doesn’t usually help. A few other preliminary steps that could be tried are trying to boot the system with no network connectivity, removing the local profile directory for the user, changing GPO for event log retention, etc.

We can’t sign you with this credential because your domain isn’t available

If it nothing work, we could proceed to the following troubleshooting:

1] Remove the user from the protected user’s group

Many users reporting this issue reported the cause as the user being added to a specifically protected user group in the active directory. For company managed systems, please contact the system administrator for the same. Learn more about protected user groups on docs.microsoft.com.

2] Verify the DNS settings

Conflict with the DNS settings could possibly cause this error. Check this reference to learn more about correct DNS settings.

3] Using Security Policy snap-in

Please backup your data before attempting this fix.

  1. Press Win + R to open the Run window and type the command secpol.msc. Press Enter and it open the Security Policy snap-in.
  2. In the security policy snap-in window, navigate to Security Settings > Local Policies > Security Options.
  3. In the right-pane, search for the policy Interactive logon: Number of previous logons to cache (in case domain controller is not available). Double-click on the policy to modify the value of the policy.
  4. Set the value of “Do not cache logons” to 0.

This troubleshooting was referred from the Microsoft Answers website here.

Posted by on , in Category Windows with Tags
Karan Khanna is a passionate Windows 10 user who loves troubleshooting Windows problems in specific and writing about Microsoft technologies in general.