Custom Credential Providers Fails to Load on Windows 10 [Tutorial]
34Custom Credential Providers Fails to Load on Windows 10 [Tutorial]
f your custom credentials providers don’t load when you log in to Windows 10 for the first time, this tutorial can guide you. Credentials providers are the primary mechanism for authenticating users – they are currently the only method for users to prove their identity, which is required for login and other system authentication scenarios.
The Windows credential provider framework allows developers to create custom credential providers. When Winlogon wants to collect credentials, the logon user interface queries each credential provider for the number of credentials it wants to enumerate. After all, providers have listed their tiles, the logon user interface displays them to the user. The user then interacts with a tile to provide the necessary credentials. The login user interface submits these credentials for authentication.
If your custom credential providers don’t load when you first log on Windows 10, then this tutorial will be able to guide you. Credential providers are the primary mechanism for user authentication—they currently are the only method for users to prove their identity which is required for logon and other system authentication scenarios.
The Windows Credential Provider Framework enables developers to create custom credential providers. When Winlogon wants to collect credentials, the Logon UI queries each credential provider for the number of credentials that it wishes to enumerate. After all, providers have enumerated their tiles, the Logon UI displays them to the user. The user then interacts with a tile to supply the necessary credentials. The Logon UI submits these credentials for authentication.
Custom credential providers fail to load on Windows 10
Let us say that you have a Windows 10-based computer that is not joined to a domain and custom credential providers are installed on the computer. You log on to the computer for the first time after it starts. In this scenario, the custom credential providers are not called.
According to Microsoft, this issue is by design. A Windows 10 update improves the Use my sign in info to automatically finish setting up my device after an update sign-in option. This feature is used for the first logon. Therefore, custom credential providers do not take effect.
To work around this issue, you’ll need to disable the automatic system logon of the last user by setting the DisableAutomaticRestartSignOn Registry key.
Here’s how to do it. Before you proceed with the registry tweak, backup the registry or create a system restore point in case the registry operation goes south.
This tutorial will apply for computers, laptops, desktops, and tablets running the Windows 10 operating system (Home, Professional, Enterprise, Education) from all supported hardware manufactures, like Dell, HP, Acer, Asus, Toshiba, Lenovo, and Samsung.