Event banner
Event details
Mike-Danoski
Microsoft
MicrosoftI can't think of a setting that might impact this behavior. If I were you, I would potentially try to set a new pin and open a support case if the behavior continues.
After running through some scenarios and deep Googling, I determined that the credential provider our VPN client added to Windows was interfering with the ability for the OS to prompt for PIN and was causing the persistent password prompt. I actually added a comment to the linked Spiceworks post below. Once I deployed a configuration profile to hide the credential provider, PIN sign-in was restored and working exactly as designed. Obviously, I do not expect Microsoft to test WHfB on operating systems with non-Microsoft credential providers registered, but what are the chances that we can get some sort of note/warning in the documentation that the presence of a third party credential provider may interfere with the ability for WHfB to work properly?