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:
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.
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.
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.
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.
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.
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.
“Script: <PATH of the VBS Script> Line: x Char: x Error: The description of the error. Code: xxxxxxxx Source: (Source of the error)”At the time of writing, it isn’t clear yet what the root cause of the error really is but there are several potential fixes you can check out to fix it. You can try to run the System File Checker or set the default value for the .vbs key, or troubleshoot the problem in a Clean Boot State. You could also try to repair Install Windows 10 or scan your computer for malware. For more detailed instructions refer to the following options.
DIR /AL /S
“This setting determines how the system responds when a user tries to install device driver files that are not digitally signed. It establishes the least secure response permitted on the systems of users in the group. Users can use the System in Control Panel to select a more secure setting, but when this setting is enabled, the system does not implement any setting less secure than the one the setting established. When you enable this setting, use the drop-down box to specify the desired response. “Ignore” directs the system to proceed with the installation even if it includes unsigned files. “Warn” notifies the user that files are not digitally signed and lets the user decide whether to stop or to proceed with the installation and whether to permit unsigned files to be installed. “Warn” is the default. “Block” directs the system to refuse to install unsigned files. As a result, the installation stops, and none of the files in the driver package are installed. To change driver file security without specifying a setting, use System in Control Panel. Right-click My Computer, click Properties, click the Hardware tab, and then click the Driver Signing button.”
“The program can not start because corefoundation.dll is missing from your computer. Try reinstalling the program to fix this problem”. "This application has failed to start because CoreFoundation.dll was not found. Re-installing the application may fix this problem." “The procedure entry point_CFBundleCopyFileTypeForFileData could not be located in the dynamic link library corefoundation.dll.” "MobileMe Control Panel cannot continue as Apple Application Support is missing or outdated. Please uninstall and reinstall the latest version of iTunes and MobileMe Control Panel to fix this issue.”Though this error code is not fatal but if it is not fixed immediately it will hamper your ability to load and run Apple programs on your system.