There is a problem when adding Passkeys.

[willow-god]

Select Topic Area

Question

Body

Hello respected GitHub technicians, I am a Chinese user who encountered a problem when adding a passkey. Recently, I reinstalled my computer, and tried to verify it with the computer's PIN key in GitHub, but it failed. So I deleted the original key and tried to re-add the PIN key. During the addition process, it displayed: "This device cannot be registered." The request in the console received a 422 response code: "Failed to load resource: the server responded with a status of 422 ()". I don't know how to solve this problem.
I couldn't find any relevant results even after searching the Internet, so I had no choice but to seek your help. I hope I'm not bothering you, thank you!

Then I tried to enter the computer's PIN code.

And then an error occurred.

My previous computer was running Windows 11, and the computer after reinstalling is running Windows 10. I had already deleted the original passkey before adding it (because the old passkey also couldn't be verified).

Thank you again.

[subhash-kr0]

1. Understand the 422 Error Code
   The HTTP status code 422 indicates "Unprocessable Entity," which means the server understood the request but couldn't process it due to semantic errors. This could relate to the way the passkey is being created or associated with your GitHub account.

2. Verify Your Setup
   Operating System: Ensure your current OS (Windows 10) supports the passkey registration process. Passkeys rely on platform support for WebAuthn, which should work on both Windows 10 and 11.
   Browser Compatibility: Use an up-to-date browser like Chrome, Edge, or Firefox. Older versions might not support passkey registration.
   GitHub Passkey Requirements: Confirm that GitHub passkeys are enabled and supported in your account and region.

3. Check Windows Hello Settings
   Since you're using a PIN, ensure Windows Hello is set up properly:

Go to Settings > Accounts > Sign-in options.
Confirm that Windows Hello PIN is enabled and functioning.
Test the PIN in other applications to confirm it works as expected.

4. Clear Old Credentials
   Remove any leftover credentials that might conflict with the new setup:

Press Windows + R, type certmgr.msc, and hit Enter.
Look for certificates or credentials related to GitHub under Personal > Certificates or Trusted Root Certification Authorities.
Delete any entries associated with GitHub (if safe to do so).

5. Attempt Re-registration
   Log in to GitHub and go to Settings > Security > Passkeys.
   Start the passkey registration process again.
   Follow the instructions to register the passkey, ensuring you select the correct device.

You can also check this topic here -> https://github.com/orgs/community/discussions/67791 , as it looks like you aren't the only one that encounters similar issues to the ones described in the topic over the past year.

[willow-god]

Thank you for your guidance. After I tried switching browsers, everything went back to normal. Maybe it was because I was using the BETA version of Chrome, even though it was the latest one.
Thank you for your reply. I wish you smooth work and a happy life！

[subhash-kr0]

I'm glad to hear that switching browsers helped resolve the issue. It makes sense that the beta version of Chrome could have caused the problem. Thank you for your kind wishes! Wishing you smooth and successful work as well, and a joyful life ahead!"

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐