Troubleshoot: Windows Credential Provider is Disabled

Windows uses Credential Providers to manage user authentication. When another authentication application is installed alongside the JumpCloud Agent (like Duo RDP or Microsoft Entra ID), JumpCloud's Credential Provider may become disabled. This article explains the symptoms and provides a resolution to ensure the JumpCloud Credential Provider functions correctly.

Important:
  • Proceed with caution when using the Windows Registry Editor.
  • A device restart is required to apply any changes to the registry.

Symptoms

  • The JumpCloud Credential Provider does not appear on the Windows login screen.
  • Users are unable to authenticate via JumpCloud on Windows devices.
  • Only the Duo Credential Provider is available for login.

Resolution

To resolve this issue, modify the Windows registry to enforce the JumpCloud Credential Provider:

  1. Open the Windows Registry Editor (regedit.msc) as a Local Administrator.
  2. Go to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\Credential Provider.
  3. Check if the registry value forceJCCredProviderOnly (DWORD) exists. If it doesn't create it:
    1. Right-click on the Credential Providers key and select New > DWORD (32-bit) Value.
    2. Set the DWORD value depending on the desired outcome:
      • Set to 0: Allows both third party and JumpCloud credential providers.
      • Set to 1: Allows only JumpCloud Credential Provider.
  4. Restart the device for the changes to take effect.
Registry ValueTypeDescription
forceJCCredProviderOnlyDWORDSet to 0 to also allow the Duo credential provider, or 1 to only allow the JumpCloud credential provider.
Back to Top

Still Have Questions?

If you cannot find an answer to your question in our FAQ, you can always contact us.

Submit a Case