Yubico Forum

I have setup my key in our Windows CA, I can do initial login on windows 7 machines without an but not windows 10, all I get in the error log is the message below.
I am able to unlock a machine with my key though on W10.



Is there a problem or should the certificate have been setup differently from the guide.

Hi,

I have the Same Problem, but only tested with Windows 10.

Could anybody help ??

Regards,

Frank

Hello Frank,

Can you please provide details as to your setup? What version of Windows are you using for your CA? Windows 2008 or Windows 2012?

Best Regards,
Matthew
Yubico Support

My Team is experiencing this exact problem as well. Windows 10, and 8.1 logon doesn't work, however "run as", RDP sessions, and Windows 7 logons work. Also unlocking computers works as well.
We have a 2008r2 CA. I followed the documentation at https://www.yubico.com/wp-content/uploa ... _FINAL.pdf as best I could, but due to the interface being a bit different, there are a few changes.
Any luck solving this?

We have same problem, Windows 10 machines with 2012 r2 CA and 2012 r2 AD environment I'm only able to open locked sessions with smart card but not log in to windows 10 machines.

I also have the exact same problem. Please advise!

I have my environment setup with AD 2012 R2/CA 2012 R2 and working fine with Win7/10 using YK4's via PIV. Let me know if I can be of assistance.

Hi

I got this from support, so I'm really interested in how you did get it to work for Windows 10?

//

We have confirmation from Microsoft this is indeed a bug in the Smart-Card authentication on Windows, the bug only affects the YubiKey as it contains multiple applets and the Smart-Card authentication process in Windows 10 does not properly send the applet select command to select the CCID applet for authentication, unfortunately the fix for this will not be available until the next Anniversary update for Windows due out in Spring 2017. we are continuing to work with Microsoft in hoping we can persuade them to release the fix sooner. The bug was introduced when Microsoft began to make changes to the authentication providers as they have begun to deprecate some legacy cryptographic algorithms such as SHA-1.

I sent you a PM so that we can figure this out and we can come back here to post what we found. I never have run into this error. We have been running PIV for about a year with 450 users.

I can't answer to your PM, I'm not trusted Can someone help me?