We have identified a potential issue that can arise when the registry settings supporting the use of our Windows Login Provider are not correct or are incomplete. The issue presents as a lockup of the Internet browsers when FIDO functions are called.
If the Windows Login Provider DLL is present, the CredProv section of HKLM\Software\SurePassID is populated, and the credential provider filter is set to show only the SurePassID Windows Login Provider, but the registry settings making our provider a valid credential provider are missing, then you may see this condition occurring.
The fix is to either temporarily disable our provider entirely by removing the .DLL from c:\windows\system32, renaming it, or you can put back into the registry the settings that enable our provider as shown here:
From our RegisterSurePass .reg file:
Windows Registry Editor Version 5.00
Please have the correct registry settings when using our credential provider.