As you know, Windows Hello offers you quick access to computers since you can log in to your Windows devices three times faster compared to passwords with the help of the camera via Face recognition and fingerprint reader. This way, Windows Hello will recognize you right away. However, there are also times when you might encounter some problems when using Windows Hello. For one, if you are trying to add the PIN method to Windows Hello on your Windows 10 computer but you suddenly encountered an error code of 0x801c004d or if you are trying to use your existing pin and you encounter an error code of 0x80070490 along with an error message that says, “Not recognized”, then read on as this post will guide you on how you can fix both of these errors. Here is the complete content for both errors:
- “0x801c004d – Unable to enroll a device to use a PIN for login”
- “0x80070490 - Not recognized, Pin and fingerprint are no longer options for signing in”
If you got any of these two errors, there are several potential fixes you can check out to resolve them. You can try to check for any Windows Updates or create the PIN again or check the CNG Key Isolation Service. You could also try to reset the TPM or create a new User Account. For more information, follow the instructions provided below.
Option 1 – Try checking for any available Windows Updates
The first thing you can do is to check for any available Windows Updates. It is possible that your computer may be outdated and is the reason why you’re having troubles with Windows Hello. To check for Windows Updates, just go to Settings and from there, head over to the Update and Security section and click on Windows Updates located on the left pane, and then click on the Check for Updates option. Wait until the process of checking updates is completed and if it finds new updates, install it. After you install the new Windows Updates, check if you can now add the PIN on Windows Hello or not.
Option 2 – Try creating the PIN again
The next thing you can do is to create the PIN again by signing out and signing in again and then try creating the PIN once more. If this does not work, you can try restarting your computer and creating the PIN again. You could also try removing the PIN and then change it.
- Remove the PIN by going to Settings > Accounts > Sign-in options.
- From there, go to the PIN section and click on the Remove button.
- You will be asked to verify your account to proceed in removing the PIN, enter your credentials.
- Restart your computer and then set up a new PIN.
- Once you’re done, restart your computer and check if the error is gone now.
Option 3 – Try checking the CNG Key Isolation Service
The CNG Key Isolation Service is the one that stores and uses long-lived keys in a secure process complying with the common criteria requirements and it is possible that the error could be related to this service. This service is hosted in the LSA processes and provides key process isolation to private keys and associated cryptographic operations as required by the common criteria. Thus, you need to check this service to see if it’s the one that’s causing the error.
- Tap the Win + R keys to open the Run dialog box and type “services.msc” in the field and hit Enter to open the Windows Services Manager.
- Next, locate the “CNG Key Isolation Service” and once you find it, double click on it to open its Properties box.
- After opening its Properties, check its Startup type and select Manual. This is the default setting and if it is Disabled, then it’s no wonder why you’re getting errors with Windows Hello, thus, you need to enable it.
- Once done, restart your computer and check if you can now add the PIN to Windows Hello. If you still get the error, then you might want to try setting the CNG Key Isolation Service from Manual to Automatic and then click on the Start button and see if it fixes the error or not.
Option 4 – Try to reset the Trusted Platform Module or TPM
You might also want to try resetting the Trusted Platform Module or TPM to fix the error. You can do this by opening Windows PowerShell and then executing the “Clear-Tpm” command. After that, check if the error is now resolved.
Option 5 – Try to create a new User Account
You could also try to create a new User Account on your Windows 10 computer to fix the Windows Hello error. Once you have created a new local user or administrator account in Windows 10, check if you are now able to add the PIN from this newly created user account.
العربية
বাংলা
简体中文
Nederlands
English
Français
Deutsch
עִבְרִית
हिन्दी
Italiano
日本語
한국어
Português
ਪੰਜਾਬੀ
Русский
Español
So far I believe each person on this planet has at least heard of Marvel superhero movies, perhaps even watched a few of them, and no wonder. Movies are spawning now over 20 titles and they are not really released as events described in them.
Throw into mix TV series and you can get confused pretty fast. Now it was officially stated that all TV series that were released before Wanda vision is no canon in Marvel cinematic universe which simplify thing a little but there are still series that are.
Lately, Microsoft has trying to fix Print Nightmare with various methods and patches. The last patch has seemingly fixed Print Nightmare but it has broken the Alt-tab key combination.
It has been reported that the latest patch has broken famous key combinations for quickly switching from window to window. It seems that combination is not working or it is switching to desktop, even going to blank screen if switching from the full-screen game.
Valve has officially announced that Steam Deck will be compatible with Windows 11 despite TPM 2.0 Microsoft requirements.
From the beginning, Deck was announced like a mini handheld PC device. Powered with new Steam OS 3.0 based on Linux. However, besides out-of-the-box OS it was also stated that Deck will be a personal device meaning that other PC-based operating systems could be installed on it and even run your typical applications in it.
Since Microsoft announced Windows 11 hardware requirements, specifically the TPM 2.0 requirement many users voiced concern that Steam Deck will not be able to connect to Windows 11
TPM 2.0 is something that Microsoft requires for every internal and hardware component that is to connect on a Windows 11 device. This is to ensure that only trusted devices would be included in the array of a PC setup and avoid any problems like malicious hardware injecting software into a system.
This would also minimize the compromise Windows would have, as unverified or untrusted devices connect to a Windows PC.
However, Valve and AMD are ensuring us that Deck will not have any issue connecting to a PC running Windows 11 or even if you wish to transform Deck itself into a Device running Windows 11. 