Default Windows Credential Provider in silent installation ?

L. Tech

unread,

Apr 10, 2026, 2:05:53 AM (yesterday) Apr 10

to RCDevs Security

Default Windows Credential Provider in silent installation using the ADDLOCAL=InstallAsDefault,SelfReg option

I'm having an issue with the Windows Credential Provider on Windows 11. When I perform the installation via the GUI, everything works fine.

When I perform a silent installation via the command line, I am unable to authenticate. I get a Windows error message: “You could not be authenticated. The username or password is incorrect.”

Yoann Traut (RCDevs)

unread,

Apr 10, 2026, 2:11:35 AM (yesterday) Apr 10

to RCDevs Security

Hello,

Could you provide the exact command you are executing?

Please also share a screenshot of the registry keys located at:
HKLM\Software\RCDevs\OpenOTP-CP after installation.

Additionally, set the registry key debug_mode to 4, then perform a login attempt and send the resulting logs from:
C:\RCDEVS-LOGS\CP.log

https://docs.rcdevs.com/openotp-credential-provider-for-windows/#endpoint-could-not-be-initialized

Regards,

L. Tech

unread,

Apr 10, 2026, 7:01:47 AM (yesterday) Apr 10

to RCDevs Security

Hello,
Thank you for your help. I enabled debug mode and realized that my problem was caused by the WebADM CA certificate on the Windows client side, which was in the wrong format.
I had exported that certificate from the Windows Server certificate store.
So I retrieved the certificate from the WebADM interface, and that solved my problem.
Everything is now working properly.
Thank you very much for your help.

Reply all

Reply to author

Forward