<div>I wonder if this is related to this issue I reported against the MSYS2 version of gpg?<br></div><div><br></div><div><a href="https://github.com/msys2/MSYS2-packages/issues/2329">https://github.com/msys2/MSYS2-packages/issues/2329</a><br></div><div><br></div><div class="protonmail_signature_block"><div class="protonmail_signature_block-user">Doug</div><div class="protonmail_signature_block-proton protonmail_signature_block-empty"></div></div><div><br></div><div class="protonmail_quote">
â€â€â€â€â€â€â€ Original Message â€â€â€â€â€â€â€<br>
On Wednesday, June 16th, 2021 at 1:43 PM, Jan Mosig <jan.mosig@posteo.de> wrote:<br>
<blockquote class="protonmail_quote" type="cite">
<p>Hello everyone,</p>
<p>it seems like there is something wrong with the latest gpg4win
(or gpg) release wrt. Yubikey support. I just installed it on a
new Windows 10 machine and could not get gpg --card-status to work
(No such device). I then downgraded to gpg4win 3.1.15 and
everything worked like a charm. You may also want to have a look
at reddit:
<a href="https://www.reddit.com/r/yubikey/comments/n4n96r/fix_gpg_to_recognize_your_yubikey_again_after" target="_blank" rel="noreferrer nofollow noopener">https://www.reddit.com/r/yubikey/comments/n4n96r/fix_gpg_to_recognize_your_yubikey_again_after</a></p>
<p>Setting "disable-ccid" in scdaemon.conf did not help at all on my
machine. I have attached the scdaemon log file which is generated,
when running gpg --card-status. Sry for some german parts in
there. "Kartenfehler" means card error :)</p>
<p>Any thoughts?</p>
<p>Best regards<br>
</p>
<div>-- <br>
Dipl.-Inf. Jan Mosig (<a href="mailto:jan.mosig@posteo.de" rel="noreferrer nofollow noopener">jan.mosig@posteo.de</a>)<br>
<strong>OpenPGP-Fingerprint:</strong> <a href="https://keys.openpgp.org/vks/v1/by-fingerprint/76EE007AA8477D08537A55EFEAFA5E6709F31765" target="_blank" rel="noreferrer nofollow noopener">76EE
007A A847 7D08 537A 55EF EAFA 5E67 09F3 1765</a>
</div>
</blockquote><br>
</div>