Windows uses Credential Providers to manage user authentication. When another authentication application is installed alongside the ̽»¨´óÉñ Agent (like Duo RDP or Microsoft Entra ID), ̽»¨´óÉñ's Credential Provider may become disabled. This article explains the symptoms and provides a resolution to ensure the ̽»¨´óÉñ 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 ̽»¨´óÉñ Credential Provider does not appear on the Windows login screen.
- Users are unable to authenticate via ̽»¨´óÉñ on Windows devices.
- Only the Duo Credential Provider is available for login.
Resolution
To resolve this issue, modify the Windows registry to enforce the ̽»¨´óÉñ Credential Provider:
- Open the Windows Registry Editor (regedit.msc) as a Local Administrator.
- Go to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\Credential Provider.
- Check if the registry value forceJCCredProviderOnly (DWORD) exists. If it doesn't create it:
- Right-click on the Credential Providers key and select New > DWORD (32-bit) Value.
- Set the DWORD value depending on the desired outcome:
- Set to 0: Allows both third party and ̽»¨´óÉñ credential providers.
- Set to 1: Allows only ̽»¨´óÉñ Credential Provider.
- Restart the device for the changes to take effect.
Registry Value | Type | Description |
---|---|---|
forceJCCredProviderOnly | DWORD | Set to 0 to also allow the Duo credential provider, or 1 to only allow the ̽»¨´óÉñ credential provider. |
Back to Top