<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-gb">
<link rel="self" type="application/atom+xml" href="https://forum.yubico.com/feed.php?f=35&amp;t=2757" />

<title>Yubico Forum</title>
<subtitle>...visit our web-store at</subtitle>
<link href="https://forum.yubico.com/index.php" />
<updated>2018-01-04T15:38:52+01:00</updated>

<author><name><![CDATA[Yubico Forum]]></name></author>
<id>https://forum.yubico.com/feed.php?f=35&amp;t=2757</id>
<entry>
<author><name><![CDATA[ChrisHammond]]></name></author>
<updated>2018-01-04T15:38:52+01:00</updated>
<published>2018-01-04T15:38:52+01:00</published>
<id>https://forum.yubico.com/viewtopic.php?t=2757&amp;p=10087#p10087</id>
<link href="https://forum.yubico.com/viewtopic.php?t=2757&amp;p=10087#p10087"/>
<title type="html"><![CDATA[Re: GPG4Win on a Surface Book Cannot Detect YubiKey]]></title>

<content type="html" xml:base="https://forum.yubico.com/viewtopic.php?t=2757&amp;p=10087#p10087"><![CDATA[
<div class="quotetitle">wiktor wrote:</div><div class="quotecontent"><br /><div class="quotetitle">Sas wrote:</div><div class="quotecontent">It is not just a driver. Most importantly is to uninstall Yubikey Smart Card Minidriver software from &quot;Programs and Features&quot;<br /></div><br />I've identified this Minidriver as a cause that makes Windows not see X.509 certificates on the card. Unfortunately this Minidriver software is installed automatically with Yubico Smartcard Driver. The driver itself is harmless it can be left as is but the &quot;Yubikey Smart Card Minidriver&quot; in &quot;Programs and Features&quot; needs to be uninstalled before Windows can interact with certs there.<br /><br />After importing new certs remember to use <div class="codetitle"><b>Code:</b></div><div class="codecontent">yubico-piv-tool -k -a set-chuid</div> and re-insert the key (it makes Windows think it's a new card and bypass cache).<br /><br />I wonder if someone from Yubico can comment on what the &quot;Minidriver&quot; does actually? I thought it's responsive for adding support for EC-based certs (that are not visible by default in Windows) but on my machine it just completely doesn't work.</div><br />Hey, thanks for your reply. I've done this (in fact, I totally reset PIV first so let's hope I still have my GPG keys!). The key is now coming up in Device Manager as an &quot;Identity Device (NIST SP-800-73 [PIV])&quot; but GPG still can't talk to it from my Surface Book <img src="https://forum.yubico.com/images/smilies/icon_e_sad.gif" alt=":(" title="Sad" /><br /><br />I don't have the time at the moment to reinstall Windows as recommended by Yubico support.<p>Statistics: Posted by <a href="https://forum.yubico.com/memberlist.php?mode=viewprofile&amp;u=4942">ChrisHammond</a> — Thu Jan 04, 2018 3:38 pm</p><hr />
]]></content>
</entry>
<entry>
<author><name><![CDATA[wiktor]]></name></author>
<updated>2018-01-04T15:18:49+01:00</updated>
<published>2018-01-04T15:18:49+01:00</published>
<id>https://forum.yubico.com/viewtopic.php?t=2757&amp;p=10086#p10086</id>
<link href="https://forum.yubico.com/viewtopic.php?t=2757&amp;p=10086#p10086"/>
<title type="html"><![CDATA[Re: GPG4Win on a Surface Book Cannot Detect YubiKey]]></title>

<content type="html" xml:base="https://forum.yubico.com/viewtopic.php?t=2757&amp;p=10086#p10086"><![CDATA[
<div class="quotetitle">Sas wrote:</div><div class="quotecontent"><br />It is not just a driver. Most importantly is to uninstall Yubikey Smart Card Minidriver software from &quot;Programs and Features&quot;<br /></div><br />I've identified this Minidriver as a cause that makes Windows not see X.509 certificates on the card. Unfortunately this Minidriver software is installed automatically with Yubico Smartcard Driver. The driver itself is harmless it can be left as is but the &quot;Yubikey Smart Card Minidriver&quot; in &quot;Programs and Features&quot; needs to be uninstalled before Windows can interact with certs there.<br /><br />After importing new certs remember to use <div class="codetitle"><b>Code:</b></div><div class="codecontent">yubico-piv-tool -k -a set-chuid</div> and re-insert the key (it makes Windows think it's a new card and bypass cache).<br /><br />I wonder if someone from Yubico can comment on what the &quot;Minidriver&quot; does actually? I thought it's responsive for adding support for EC-based certs (that are not visible by default in Windows) but on my machine it just completely doesn't work.<p>Statistics: Posted by <a href="https://forum.yubico.com/memberlist.php?mode=viewprofile&amp;u=5035">wiktor</a> — Thu Jan 04, 2018 3:18 pm</p><hr />
]]></content>
</entry>
<entry>
<author><name><![CDATA[ChrisHammond]]></name></author>
<updated>2017-11-09T00:58:26+01:00</updated>
<published>2017-11-09T00:58:26+01:00</published>
<id>https://forum.yubico.com/viewtopic.php?t=2757&amp;p=9974#p9974</id>
<link href="https://forum.yubico.com/viewtopic.php?t=2757&amp;p=9974#p9974"/>
<title type="html"><![CDATA[Re: GPG4Win on a Surface Book Cannot Detect YubiKey]]></title>

<content type="html" xml:base="https://forum.yubico.com/viewtopic.php?t=2757&amp;p=9974#p9974"><![CDATA[
<div class="quotetitle">jrotello wrote:</div><div class="quotecontent"><br />Do you happen to have the Symantec PKI Client installed? I just narrowed mine down to that. Once I uninstalled it (luckily we are moving to a different solution for vpn certificates) and rebooted the Yubikey started working with GnuPG.<br /><br />Current Setup:<br /><br />Windows 10 - 1709 (Build 16299.19)<br />Cisco AnyConnect Client - 4.5.02033<br />Yubikey 4 - Firmware 4.2.8<br /><br />I hope this info helps you further diagnose your machine.<br /><br />-j<br /></div><br />Thanks for your response! I don't have this installed. I tried uninstalling the Cisco AnyConnect client too just in case (even though it doesn't conflict on my desktop) to no avail.<br /><br />Interestingly, the machine has started installing the YubiKey Smart Card Minidriver automatically:<br /><div class="codetitle"><b>Code:</b></div><div class="codecontent">Driver Management has concluded the process to add Service UmPass for Device Instance ID SCFILTER\CID_597562696B657934\9&amp;32612CC5&amp;3&amp;YUBICO_YUBIKEY_4_OTP+U2F+CCID_0_SCFILTER_CID_597562696B657934 with the following status: 0.<br /></div><br /><br />Even uninstalling this in appwiz.cpl causes it to be reinstalled on replug of the YubiKey.<br /><br />I tried manually switching to the PIV driver but still no luck with that <img src="https://forum.yubico.com/images/smilies/icon_e_sad.gif" alt=":(" title="Sad" /><br /><br />Yubico support recommended just reinstalling Windows because apparently that fixed an issue on the Surface Pro, but surely there's another way?<p>Statistics: Posted by <a href="https://forum.yubico.com/memberlist.php?mode=viewprofile&amp;u=4942">ChrisHammond</a> — Thu Nov 09, 2017 12:58 am</p><hr />
]]></content>
</entry>
<entry>
<author><name><![CDATA[jrotello]]></name></author>
<updated>2017-11-08T20:41:51+01:00</updated>
<published>2017-11-08T20:41:51+01:00</published>
<id>https://forum.yubico.com/viewtopic.php?t=2757&amp;p=9973#p9973</id>
<link href="https://forum.yubico.com/viewtopic.php?t=2757&amp;p=9973#p9973"/>
<title type="html"><![CDATA[Re: GPG4Win on a Surface Book Cannot Detect YubiKey]]></title>

<content type="html" xml:base="https://forum.yubico.com/viewtopic.php?t=2757&amp;p=9973#p9973"><![CDATA[
Do you happen to have the Symantec PKI Client installed? I just narrowed mine down to that. Once I uninstalled it (luckily we are moving to a different solution for vpn certificates) and rebooted the Yubikey started working with GnuPG.<br /><br />Current Setup:<br /><br />Windows 10 - 1709 (Build 16299.19)<br />Cisco AnyConnect Client - 4.5.02033<br />Yubikey 4 - Firmware 4.2.8<br /><br />I hope this info helps you further diagnose your machine.<br /><br />-j<p>Statistics: Posted by <a href="https://forum.yubico.com/memberlist.php?mode=viewprofile&amp;u=4428">jrotello</a> — Wed Nov 08, 2017 8:41 pm</p><hr />
]]></content>
</entry>
<entry>
<author><name><![CDATA[ChrisHammond]]></name></author>
<updated>2017-10-20T12:51:03+01:00</updated>
<published>2017-10-20T12:51:03+01:00</published>
<id>https://forum.yubico.com/viewtopic.php?t=2757&amp;p=9906#p9906</id>
<link href="https://forum.yubico.com/viewtopic.php?t=2757&amp;p=9906#p9906"/>
<title type="html"><![CDATA[Re: GPG4Win on a Surface Book Cannot Detect YubiKey]]></title>

<content type="html" xml:base="https://forum.yubico.com/viewtopic.php?t=2757&amp;p=9906#p9906"><![CDATA[
<div class="quotetitle">Sas wrote:</div><div class="quotecontent"><br />It is not just a driver. Most importantly is to uninstall Yubikey Smart Card Minidriver software from &quot;Programs and Features&quot;<br /></div><br />Thanks for your reply!<br /><br />I removed the driver too. The only Yubico software I have installed is shown here:<br />add remove programs.PNG<br />I also deleted the C:\ProgramData\Yubico\ykey folder entirely.<br /><br />All OEM Drivers installed have been exported by Driver Store Explorer below. The only one that could be questionable is the Cisco VPN driver (some posts indicated that sometimes VPN applications cause issues by hijacking the smart card), but I have this exact VPN program on my desktop which works flawlessly.<br /><br /><div class="codetitle"><b>Code:</b></div><div class="codecontent">OEM INF   INF   Package Provider   Driver Class   Driver Date   Driver Version   Driver Signer   Driver Size<br />oem91.inf   commonsystem.inf   INTEL   System devices   07/14/2015   10.1.1.9   Microsoft Windows Hardware Compatibility Publisher   52152<br />oem50.inf   csi2hostcontrollerdriver.inf   Intel Corporation   System devices   06/24/2016   30.10586.7109.2672   Microsoft Windows Hardware Compatibility Publisher   144106<br />oem79.inf   csi2hostcontrollerdriver.inf   Intel Corporation   System devices   05/24/2017   30.15063.10999.4731   Microsoft Windows Hardware Compatibility Publisher   142354<br />oem21.inf   heci.inf   Intel   System devices   12/24/2015   11.0.0.1176   Microsoft Windows Hardware Compatibility Publisher   2312029<br />oem8.inf   heci.inf   Intel   System devices   11/16/2016   11.6.0.1042   Microsoft Windows Hardware Compatibility Publisher   259724<br />oem29.inf   iactrllogic64.inf   Intel Corporation   System devices   05/24/2017   30.15063.10999.4731   Microsoft Windows Hardware Compatibility Publisher   206712<br />oem82.inf   iaisp64.inf   Intel   System devices   05/24/2017   30.15063.10999.4731   Microsoft Windows Hardware Compatibility Publisher   71509<br />oem47.inf   iaprecisetouch.inf   Intel Corporation   Human Interface Devices   01/26/2017   1.2.0.83   Microsoft Windows Hardware Compatibility Publisher   805067<br />oem80.inf   iaprecisetouch.inf   Intel Corporation   Human Interface Devices   09/09/2016   1.2.0.70   Microsoft Windows Hardware Compatibility Publisher   804727<br />oem7.inf   intcaudiobus.inf   Intel(R) Corporation   System devices   01/20/2017   9.21.0.2102   Microsoft Windows Hardware Compatibility Publisher   343864<br />oem18.inf   intcoed.inf   Intel(R) Corporation   System devices   05/17/2016   8.20.0.931   Microsoft Windows Hardware Compatibility Publisher   30618224<br />oem24.inf   intcoed.inf   Intel(R) Corporation   System devices   01/20/2017   9.21.0.2102   Microsoft Windows Hardware Compatibility Publisher   39565712<br />oem75.inf   ov5693.inf   Intel Corporation   System devices   05/24/2017   30.15063.10999.4731   Microsoft Windows Hardware Compatibility Publisher   5837231<br />oem3.inf   ov7251.inf   Intel Corporation   System devices   05/24/2017   30.15063.10999.4731   Microsoft Windows Hardware Compatibility Publisher   764579<br />oem6.inf   ov8865.inf   Intel Corporation   System devices   05/24/2017   30.15063.10999.4731   Microsoft Windows Hardware Compatibility Publisher   4561752<br />oem38.inf   samsung_usb_driver.inf   libusb.org   Universal Serial Bus devices   07/14/2009   6.1.7600.16385   Unknown   2742126<br />oem87.inf   skylakesystem.inf   INTEL   System devices   07/14/2015   10.1.1.9   Microsoft Windows Hardware Compatibility Publisher   57548<br />oem31.inf   skylakesystem.inf   INTEL   System devices   07/14/2015   10.1.1.9   Microsoft Windows Hardware Compatibility Publisher   58790<br />oem103.inf   ssudbus.inf   SAMSUNG Electronics Co., Ltd.   Universal Serial Bus controllers   01/02/2014   2.11.7.0   Microsoft Windows Hardware Compatibility Publisher   155738<br />oem109.inf   ssudcdf.inf   SAMSUNG Electronics Co., Ltd.   Universal Serial Bus controllers   01/02/2014   2.11.7.0   Microsoft Windows Hardware Compatibility Publisher   73087<br />oem112.inf   ssuddmgr.inf   SAMSUNG Electronics Co., Ltd.   Ports (COM &amp; LPT)   01/02/2014   2.11.7.0   Microsoft Windows Hardware Compatibility Publisher   247358<br />oem105.inf   ssudmarv.inf   SAMSUNG Electronics Co., Ltd.   Universal Serial Bus controllers   01/02/2014   2.11.7.0   Microsoft Windows Hardware Compatibility Publisher   2238929<br />oem106.inf   ssudobex.inf   SAMSUNG Electronics Co., Ltd.   Ports (COM &amp; LPT)   01/02/2014   2.11.7.0   Microsoft Windows Hardware Compatibility Publisher   247356<br />oem104.inf   ssudrmnet.inf   SAMSUNG Electronics Co., Ltd.   Universal Serial Bus controllers   01/02/2014   2.11.7.0   Microsoft Windows Hardware Compatibility Publisher   1603432<br />oem108.inf   ssudsdb.inf   SAMSUNG Electronics Co., Ltd.   Universal Serial Bus controllers   01/02/2014   2.11.7.0   Microsoft Windows Hardware Compatibility Publisher   2238473<br />oem97.inf   ssudserd.inf   SAMSUNG Electronics Co., Ltd.   Ports (COM &amp; LPT)   01/02/2014   2.11.7.0   Microsoft Windows Hardware Compatibility Publisher   247751<br />oem98.inf   ss_conn_usb_driver.inf   SAMSUNG Electronics Co., Ltd.   Universal Serial Bus controllers   01/02/2014   2.11.7.0   Microsoft Windows Hardware Compatibility Publisher   65726<br />oem49.inf   sunrisepoint-lpsdhost.inf   INTEL   SD host adapters   07/14/2015   10.1.1.9   Microsoft Windows Hardware Compatibility Publisher   50796<br />oem76.inf   sunrisepoint-lpsystem.inf   INTEL   System devices   07/14/2015   10.1.1.9   Microsoft Windows Hardware Compatibility Publisher   134456<br />oem62.inf   sunrisepoint-lpsystem.inf   INTEL   System devices   07/14/2015   10.1.1.9   Microsoft Windows Hardware Compatibility Publisher   133734<br />oem20.inf   surfaceaccessoryfwupdate.inf   Surface   System devices   03/04/2017   1.2.108.0   Microsoft Windows Hardware Compatibility Publisher   18620<br />oem14.inf   surfaceacpibattery.inf   Microsoft   Batteries   11/13/2015   1.2.0.2   Microsoft Windows Hardware Compatibility Publisher   19051<br />oem35.inf   surfacebasefwupdate.inf   Microsoft   System devices   10/03/2016   2.0.97.0   Microsoft Windows Hardware Compatibility Publisher   492809<br />oem66.inf   surfacebaseintegration.inf   Microsoft   Human Interface Devices   08/18/2015   1.1.359.0   Microsoft Windows Hardware Compatibility Publisher   80398<br />oem96.inf   surfacebutton.inf   Microsoft   System devices   06/09/2016   1.1.662.0   Microsoft Windows Hardware Compatibility Publisher   139564<br />oem45.inf   surfacecamerawindowshello.inf   Surface   System devices   08/01/2017   1.0.85.1   Microsoft Windows Hardware Compatibility Publisher   17694<br />oem15.inf   surfacedigitizerintegration.inf   Microsoft   Human Interface Devices   08/18/2015   1.1.359.0   Microsoft Windows Hardware Compatibility Publisher   81108<br />oem37.inf   surfacedisplaycalibration.inf   Microsoft   System devices   11/18/2015   1.1.381.0   Microsoft Windows Hardware Compatibility Publisher   71016<br />oem39.inf   surfacedockfwupdate.inf   Microsoft   System devices   03/22/2016   1.2.6.0   Microsoft Windows Hardware Compatibility Publisher   700629<br />oem63.inf   surfacedockintegration.inf   Microsoft   Human Interface Devices   03/14/2016   1.0.6.0   Microsoft Windows Hardware Compatibility Publisher   62018<br />oem43.inf   surfacedtxdriver.inf   Surface   System devices   04/27/2017   1.3.792.1   Microsoft Windows Hardware Compatibility Publisher   3185978<br />oem13.inf   surfaceec.inf   Microsoft   Firmware   07/29/2016   90.1277.256.0   Microsoft Windows Hardware Compatibility Publisher   180569<br />oem86.inf   surfaceintegrationdriver.inf   Surface   System devices   05/15/2017   1.1.333.0   Microsoft Windows Hardware Compatibility Publisher   132737<br />oem56.inf   surfacekeyboardbacklight.inf   Microsoft   System devices   09/14/2015   1.1.373.0   Microsoft Windows Hardware Compatibility Publisher   188405<br />oem32.inf   surfaceme.inf   Microsoft   Firmware   05/01/2015   1.0.0.0   Microsoft Windows Hardware Compatibility Publisher   16622<br />oem61.inf   surfaceme.inf   Surface   Firmware   04/05/2017   11.6.25.1229   Microsoft Windows Hardware Compatibility Publisher   2052173<br />oem26.inf   surfaceme.inf   Microsoft   Firmware   07/26/2016   11.0.15.1003   Microsoft Windows Hardware Compatibility Publisher   2052382<br />oem71.inf   surfacenvmexpresscontroller.inf   Microsoft   Storage controllers   12/05/2016   11.0.0.1   Microsoft Windows Hardware Compatibility Publisher   18754<br />oem88.inf   surfacepen.inf   Microsoft   Human Interface Devices   07/27/2015   1.1.352.0   Microsoft Windows Hardware Compatibility Publisher   18721<br />oem84.inf   surfacepenclickfilter.inf   Microsoft   Keyboards   08/18/2015   1.1.350.1   Microsoft Windows Hardware Compatibility Publisher   83195<br />oem2.inf   surfacependriver.inf   Microsoft   Human Interface Devices   05/23/2016   12.0.303.1   Microsoft Windows Hardware Compatibility Publisher   1933496<br />oem90.inf   surfacepenintegration.inf   Microsoft   Human Interface Devices   08/18/2015   1.1.359.0   Microsoft Windows Hardware Compatibility Publisher   82262<br />oem68.inf   surfacepenpairing.inf   Surface   System devices   03/10/2017   3.0.0.1   Microsoft Windows Hardware Compatibility Publisher   234141<br />oem19.inf   surfacepowermeter.inf   Microsoft   System devices   02/19/2015   1.1.65.1   Microsoft Windows Hardware Compatibility Publisher   17593<br />oem0.inf   surfacesam.inf   Surface   Firmware   02/16/2017   90.1610.256.0   Microsoft Windows Hardware Compatibility Publisher   195635<br />oem27.inf   surfaceservicenulldriver.inf   Microsoft   System devices   10/11/2016   1.0.241.0   Microsoft Windows Hardware Compatibility Publisher   789939<br />oem11.inf   surfacesoftwareservicingdriver.inf   Microsoft   Human Interface Devices   07/12/2015   3.0.10.0   Microsoft Windows Hardware Compatibility Publisher   55907<br />oem36.inf   surfacestoragefwupdate.inf   Microsoft   System devices   10/16/2015   1.1.447.0   Microsoft Windows Hardware Compatibility Publisher   2834034<br />oem74.inf   surfacesystemtelemetrydriver.inf   Microsoft   System devices   08/20/2015   3.0.100.0   Microsoft Windows Hardware Compatibility Publisher   83488<br />oem52.inf   surfacetouch.inf   Microsoft   Firmware   06/20/2016   51.250.94.229   Microsoft Windows Hardware Compatibility Publisher   328390<br />oem12.inf   surfacetouchservicingml.inf   Microsoft   System devices   05/11/2016   1.0.207.0   Microsoft Windows Hardware Compatibility Publisher   2935163<br />oem10.inf   surfaceuefi.inf   Surface   Firmware   06/13/2017   91.1741.768.0   Microsoft Windows Hardware Compatibility Publisher   3951435<br />oem64.inf   surfaceusbhubfwupdate.inf   Microsoft   System devices   12/02/2016   1.0.519.0   Microsoft Windows Hardware Compatibility Publisher   1057237<br />oem92.inf   adobepdf.inf   Adobe   Printers   01/20/2017   12.1.0.0   Microsoft Windows Hardware Compatibility Publisher   1722843<br />oem100.inf   android_winusb.inf   ASUSTeK COMPUTER INC.   Kedacom USB Device   03/25/2014   8.0.0.2   Microsoft Windows Hardware Compatibility Publisher   2815834<br />oem42.inf   android_winusb.inf   Google, Inc.   Kedacom USB Device   08/28/2016   11.0.0.0   Microsoft Windows Hardware Compatibility Publisher   2897575<br />oem58.inf   android_winusb.inf   Google, Inc.   Kedacom USB Device   08/28/2014   11.0.0.0   Google Inc   2754724<br />oem83.inf   atgh4627.inf   Intel Corporation   Display adapters   03/09/2017   21.20.16.4627   Microsoft Windows Hardware Compatibility Publisher   684549744<br />oem9.inf   dlcdcncm.inf   DisplayLink Corp.   Network adapters   04/05/2017   8.2.1629.0   Microsoft Windows Hardware Compatibility Publisher   618852<br />oem85.inf   dlidusb.inf   DisplayLink   Display adapters   05/22/2017   8.2.1952.0   Microsoft Windows Hardware Compatibility Publisher   11227322<br />oem72.inf   dlusbaudio.inf   DisplayLink Corp.   Sound, video and game controllers   04/07/2017   8.2.1638.0   Microsoft Windows Hardware Compatibility Publisher   761523<br />oem25.inf   hdxsstm.inf   Realtek Semiconductor Corp.   Sound, video and game controllers   08/05/2016   6.0.1.7895   Microsoft Windows Hardware Compatibility Publisher   21504430<br />oem81.inf   iacamera64.inf   Intel   Sound, video and game controllers   05/24/2017   30.15063.10999.4731   Microsoft Windows Hardware Compatibility Publisher   38818956<br />oem89.inf   intcdaud.inf   Intel(R) Corporation   Sound, video and game controllers   05/10/2016   6.16.0.3197   Microsoft Windows Hardware Compatibility Publisher   2601197<br />oem53.inf   intcdaud.inf   Intel(R) Corporation   Sound, video and game controllers   12/01/2016   10.22.1.97   Microsoft Windows Hardware Compatibility Publisher   7965766<br />oem95.inf   mbtr8897w81x64.inf   Marvell Semiconductor, Inc.   Bluetooth   02/09/2017   15.68.9114.29   Microsoft Windows Hardware Compatibility Publisher   22107<br />oem4.inf   mrvlpcie8897.inf   Marvell Semiconductor, Inc.   Network adapters   02/09/2017   15.68.9114.29   Microsoft Windows Hardware Compatibility Publisher   1126655<br />oem78.inf   msux64w10.inf   Microsoft   Network adapters   01/24/2017   10.4.124.2017   Microsoft Windows Hardware Compatibility Publisher   485395<br />oem28.inf   nvmso.inf   NVIDIA   Display adapters   04/23/2017   22.21.13.8194   Microsoft Windows Hardware Compatibility Publisher   519875881<br />oem116.inf   prnms001.inf   Microsoft   Printers   06/21/2006   10.0.16299.15   Microsoft Windows   88504<br />oem30.inf   prnms006.inf   Microsoft   Printers   04/29/2013   16.0.1626.4000   Microsoft Windows Hardware Compatibility Publisher   128775<br />oem115.inf   prnms009.inf   Microsoft   Printers   06/21/2006   10.0.16299.15   Microsoft Windows   41460<br />oem101.inf   ssudadb.inf   SAMSUNG Electronics Co., Ltd.   Kedacom USB Device   01/02/2014   2.11.7.0   Microsoft Windows Hardware Compatibility Publisher   2240289<br />oem107.inf   ssudeadb.inf   SAMSUNG Electronics Co., Ltd.   ADB Interface   01/02/2014   2.11.7.0   Microsoft Windows Hardware Compatibility Publisher   1574845<br />oem102.inf   ssudmdm.inf   SAMSUNG Electronics Co., Ltd.   Modems   01/02/2014   2.11.7.0   Microsoft Windows Hardware Compatibility Publisher   384911<br />oem114.inf   ssudmtp.inf   SAMSUNG Electronics Co., Ltd.   Portable Devices   01/02/2014   2.11.7.0   Microsoft Windows Hardware Compatibility Publisher   32664<br />oem110.inf   ssudnd5.inf   SAMSUNG Electronics Co., Ltd.   Network adapters   01/02/2014   2.11.7.0   Microsoft Windows Hardware Compatibility Publisher   1594043<br />oem111.inf   ssudrmnetmp.inf   SAMSUNG Electronics Co., Ltd.   Network adapters   01/02/2014   2.11.7.0   Microsoft Windows Hardware Compatibility Publisher   1635764<br />oem99.inf   ssudrnds.inf   SAMSUNG Electronics Co., Ltd.   Network adapters   01/02/2014   2.11.7.0   Microsoft Windows Hardware Compatibility Publisher   39193<br />oem46.inf   surfacedisplay.inf   Microsoft   Monitors   08/31/2015   1.1.207.0   Microsoft Windows Hardware Compatibility Publisher   20064<br />oem113.inf   u2312hm.inf   Dell Inc.   Monitors   06/11/2012   2.0.0.0   Microsoft Windows Hardware Compatibility Publisher   26799<br />oem94.inf   vpnva-6.inf   Cisco Systems   Network adapters   02/26/2014   3.1.6019.0   Microsoft Windows Hardware Compatibility Publisher   73991<br />oem54.inf   wdcsam.inf   Western Digital Technologies   WD Drive Management devices   10/09/2015   1.1.0.0   Microsoft Windows Hardware Compatibility Publisher   81464<br /><br /></div><br /><br />As an update, I have been able to use my YubiKey with my other Windows 10 laptop out of the box just fine, too. All I needed was GPG4Win.<br /><br />The only thing I can think of at the moment is a conflict with the Windows Hello for Business smart card driver for the face ID built into the machine. Has anybody with a Surface Book / Pro 4 been able to use GPG with YubiKey?<p>Statistics: Posted by <a href="https://forum.yubico.com/memberlist.php?mode=viewprofile&amp;u=4942">ChrisHammond</a> — Fri Oct 20, 2017 12:51 pm</p><hr />
]]></content>
</entry>
<entry>
<author><name><![CDATA[Sas]]></name></author>
<updated>2017-10-20T12:41:04+01:00</updated>
<published>2017-10-20T12:41:04+01:00</published>
<id>https://forum.yubico.com/viewtopic.php?t=2757&amp;p=9905#p9905</id>
<link href="https://forum.yubico.com/viewtopic.php?t=2757&amp;p=9905#p9905"/>
<title type="html"><![CDATA[Re: GPG4Win on a Surface Book Cannot Detect YubiKey]]></title>

<content type="html" xml:base="https://forum.yubico.com/viewtopic.php?t=2757&amp;p=9905#p9905"><![CDATA[
It is not just a driver. Most importantly is to uninstall Yubikey Smart Card Minidriver software from &quot;Programs and Features&quot;<p>Statistics: Posted by <a href="https://forum.yubico.com/memberlist.php?mode=viewprofile&amp;u=4939">Sas</a> — Fri Oct 20, 2017 12:41 pm</p><hr />
]]></content>
</entry>
<entry>
<author><name><![CDATA[ChrisHammond]]></name></author>
<updated>2017-10-19T21:16:01+01:00</updated>
<published>2017-10-19T21:16:01+01:00</published>
<id>https://forum.yubico.com/viewtopic.php?t=2757&amp;p=9903#p9903</id>
<link href="https://forum.yubico.com/viewtopic.php?t=2757&amp;p=9903#p9903"/>
<title type="html"><![CDATA[Re: GPG4Win on a Surface Book Cannot Detect YubiKey]]></title>

<content type="html" xml:base="https://forum.yubico.com/viewtopic.php?t=2757&amp;p=9903#p9903"><![CDATA[
Thanks so much for your response @DanielJewell. Unfortunately removing the Yubico drivers still has not solved this issue, however :/<br /><br />I'm getting different results, however. When I run certutil -scinfo the YubiKey is detected properly but when it tries to gather info I get an error that looks like this:<br />smartcarderror.PNG<br /><br />Any further ideas? I am also on Windows 10 build 16299.19. This is how my Device Manager looks:<br />devicemgr.PNG<p>Statistics: Posted by <a href="https://forum.yubico.com/memberlist.php?mode=viewprofile&amp;u=4942">ChrisHammond</a> — Thu Oct 19, 2017 9:16 pm</p><hr />
]]></content>
</entry>
<entry>
<author><name><![CDATA[DanielJewell]]></name></author>
<updated>2017-10-19T18:46:56+01:00</updated>
<published>2017-10-19T18:46:56+01:00</published>
<id>https://forum.yubico.com/viewtopic.php?t=2757&amp;p=9901#p9901</id>
<link href="https://forum.yubico.com/viewtopic.php?t=2757&amp;p=9901#p9901"/>
<title type="html"><![CDATA[Re: GPG4Win on a Surface Book Cannot Detect YubiKey]]></title>

<content type="html" xml:base="https://forum.yubico.com/viewtopic.php?t=2757&amp;p=9901#p9901"><![CDATA[
Update: <br /><br />Found this post: <!-- l --><a class="postlink-local" href="https://forum.yubico.com/viewtopic.php?f=26&amp;t=2739&amp;start=10">viewtopic.php?f=26&amp;t=2739&amp;start=10</a><!-- l --><br /><br />Uninstalling the &quot;YubiKey Minidriver&quot; from Programs and Features (Start &gt; Run &gt; appwiz.cpl) and changing the driver to the Identity Device NIST restored functionality.<p>Statistics: Posted by <a href="https://forum.yubico.com/memberlist.php?mode=viewprofile&amp;u=4944">DanielJewell</a> — Thu Oct 19, 2017 6:46 pm</p><hr />
]]></content>
</entry>
<entry>
<author><name><![CDATA[DanielJewell]]></name></author>
<updated>2017-10-19T18:40:58+01:00</updated>
<published>2017-10-19T18:40:58+01:00</published>
<id>https://forum.yubico.com/viewtopic.php?t=2757&amp;p=9900#p9900</id>
<link href="https://forum.yubico.com/viewtopic.php?t=2757&amp;p=9900#p9900"/>
<title type="html"><![CDATA[Re: GPG4Win on a Surface Book Cannot Detect YubiKey]]></title>

<content type="html" xml:base="https://forum.yubico.com/viewtopic.php?t=2757&amp;p=9900#p9900"><![CDATA[
I am having the same issue - Windows 10 / 1709 - Build 16299.19<br /><br />According to Device Manager, the system sees the Smart Card device as a &quot;YubiKey Smart Card&quot; with a driver version of 9/22/2017 (v3.3.1.5) provider Yubico. Even rolling back the driver to be an &quot;Identity Device (NIST SP 800-73 [PIV])&quot; doesn't work. <br /><br />certutil -scinfo fails and the device does not detect the authentication certificate stored on the PIV module. <br /><br /><div class="codetitle"><b>Code:</b></div><div class="codecontent">Microsoft Base Smart Card Crypto Provider: Missing stored keyset<br />Microsoft Smart Card Key Storage Provider: Missing stored keyset<br /><br />--------------===========================--------------<br />CertUtil: -SCInfo command FAILED: 0x80090016 (-2146893802 NTE_BAD_KEYSET)<br />CertUtil: Keyset does not exist</div><br /><br />The PIV Manager tool *does* see the device (PIV Applet Version 4.3.5) and sees the loaded certificate in the authentication slot (9a). <br /><br />Likewise, the PIV command line tool can read the certificate just fine. <br /><br />I have also tested my built-in traditional smart card reader with a PIV smart card and it works just fine on this build of Windows.<p>Statistics: Posted by <a href="https://forum.yubico.com/memberlist.php?mode=viewprofile&amp;u=4944">DanielJewell</a> — Thu Oct 19, 2017 6:40 pm</p><hr />
]]></content>
</entry>
<entry>
<author><name><![CDATA[ChrisHammond]]></name></author>
<updated>2017-10-17T16:52:41+01:00</updated>
<published>2017-10-17T16:52:41+01:00</published>
<id>https://forum.yubico.com/viewtopic.php?t=2757&amp;p=9883#p9883</id>
<link href="https://forum.yubico.com/viewtopic.php?t=2757&amp;p=9883#p9883"/>
<title type="html"><![CDATA[GPG4Win on a Surface Book Cannot Detect YubiKey]]></title>

<content type="html" xml:base="https://forum.yubico.com/viewtopic.php?t=2757&amp;p=9883#p9883"><![CDATA[
Hi there,<br /><br />I have a YubiKey 4 that works perfectly on my desktop (running the latest Windows 10 insider build) out of the box with GPG4Win. I managed to generate gpg keys on the device and sign Git commits all in PowerShell.<br /><br />However, on my Surface Book I cannot get gpg to pick up the device. I have tried installing the YubiKey PIV driver, uninstalling it, removing drivers, etc., and I always get this:<br /><div class="codetitle"><b>Code:</b></div><div class="codecontent">PS C:\Users\Christopher&gt; gpg --card-status --verbose<br />gpg: selecting openpgp failed: No such device<br />gpg: OpenPGP card not available: No such device<br /></div><br /><br /><div class="codetitle"><b>Code:</b></div><div class="codecontent">PS C:\Users\Christopher&gt; gpg --card-edit --verbose<br /><br />gpg: selecting openpgp failed: No such device<br />gpg: OpenPGP card not available: No such device<br /><br />gpg/card&gt;<br /></div><br /><br /><div class="codetitle"><b>Code:</b></div><div class="codecontent">PS C:\Users\Christopher&gt; gpg-connect-agent.exe --hex &quot;scd apdu 00 f1 00 00&quot; /bye<br />ERR 100663406 Card removed &lt;SCD&gt;<br /></div><br /><br /><div class="codetitle"><b>Code:</b></div><div class="codecontent">PS C:\Users\Christopher&gt; certutil -scinfo<br />The Microsoft Smart Card Resource Manager is running.<br />Current reader/card status:<br />Readers: 2<br />  0: Windows Hello for Business 13<br />  1: Yubico Yubikey 4 OTP+U2F+CCID 0<br />--- Reader: Windows Hello for Business 13<br />--- Status: SCARD_STATE_PRESENT | SCARD_STATE_UNPOWERED<br />--- Status: The card is available for use.<br />---   Card: Identity Device (Microsoft Generic Profile)<br />---    ATR:<br />        3b 8d 01 80 fb a0 00 00  03 97 42 54 46 59 04 01   ;.........BTFY..<br />        cf                                                 .<br /><br />--- Reader: Yubico Yubikey 4 OTP+U2F+CCID 0<br />--- Status: SCARD_STATE_PRESENT | SCARD_STATE_UNPOWERED<br />--- Status: The card is available for use.<br />---   Card: Yubikey 4 Smart Card<br />---    ATR:<br />        3b f8 13 00 00 81 31 fe  15 59 75 62 69 6b 65 79   ;.....1..Yubikey<br />        34 d4<br /></div><br />After this, I am asked for my login PIN a couple of times and the Windows Hello (device #0) certificates are shown. Once it processes device #1 (the YubiKey) the following data is outputted.<br /><div class="codetitle"><b>Code:</b></div><div class="codecontent">Displayed  cert for reader: Windows Hello for Business 13<br /><br />--------------===========================--------------<br /><br />=======================================================<br />Analyzing card in reader: Yubico Yubikey 4 OTP+U2F+CCID 0<br />Microsoft Base Smart Card Crypto Provider: Missing stored keyset<br />Microsoft Smart Card Key Storage Provider: Missing stored keyset<br /><br />--------------===========================--------------<br />CertUtil: -SCInfo command FAILED: 0x80090016 (-2146893802 NTE_BAD_KEYSET)<br />CertUtil: Keyset does not exist<br /></div><br /><br />Any idea what is causing this? I've been battling with it for hours. The only idea I can think of is that gpg is defaulting to the Windows Hello quasi-smart card and therefore ignoring the YubiKey but I'm not sure of a way of testing this as I am new to smart cards. To reiterate, the same version of gpg4win worked fine on a desktop out of the box with the same version of Win10.<br /><br />Many thanks!<p>Statistics: Posted by <a href="https://forum.yubico.com/memberlist.php?mode=viewprofile&amp;u=4942">ChrisHammond</a> — Tue Oct 17, 2017 4:52 pm</p><hr />
]]></content>
</entry>
</feed>