This error code is not listed.
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
Same here, just got that.
@officedocsbot assign @e0i
Hello, @GenericUser321 , @jdenicola67 Thank you for submitting feedback.
In our understanding the error code that you have noted might actually have surfaced from other services rather than _Windows Hello_ itself.
Find below a quoted reply from our Content Developer:
DaniHalfin wrote:
For error codes unlisted here, in most cases those are transient error codes
being surfaced by other services in the Windows Hello dependency chain.
We are working on something to improve the user experience in that regard,
but that will not solve the issues you are experiencing.
If we find a reoccurring error codes that isn't covered here and should be
(meaning, in most cases, it is coming from Windows Hello and not other
components) we'll make sure to add it to this page.
Also note that the feedback section that you have used to submit this issue is intended for product documentation issues only.
Please consider consulting to _Feedback Hub_ for any of your suggestions, questions or feature requests to help Microsoft improve your experience. Find the link to _Feedback Hub_ below:
Microsoft Windows 10 Feedback Hub
We are closing this issue but feel free to re-open it if you feel that we might have missed something.
Have a nice day.
@officedocsbot close
Idem with the new Win 10 1903, a standalone workstation.
I still have a hello face reco on my Surface pro 5, i tried to add a PIN code
Searching for this error code, 0x801c004d in Bing and other popular search engines seems to mostly return articles referencing issues with Windows Hello. While this might be an issue from a Dependency as previously suggested, the error code should probably be mentioned in the "errors with unknown mitigation" section
Also came here looking for a solution to this, and not finding the code in the MS article Windows Hello errors during PIN creation.
For us, this feature was working until we updated to 1909. We are now unable to set PIN. This needs to be covered off by Microsoft in this article, as there's a clear link between setting up PIN, and this error.
It's common enough for this article to exist and a number of other forum posts. I've yet to see a post with a solution. So I think it's down to MS to update the article with at least a clue where the problem lies (and you know, if it's not too much to ask, a solution)
@e0i - there are too many other articles and search results pointing here. This needs to be open, and considered the parent issue. It shouldn't be closed until resolved.
@officedocsbot close
@GriffReborn Thank you for following up with this issue. The case for this specific error code is under re-investigation.
@mapalko _Dani_ has informed that you can help us with this issue. The community is also eager to hear about 0x80070490. Thank you.
That error code maps to error not found. With just the error code it is difficult to map it to a specific component or issue.
What is the solution for 0x801c004d
I am still getting this error. pls post solution
Getting same error
Getting the same error.
I have tried clearing the TPM workspace, cleared the NGC store, and reset the winbiodatabase to no avail. I now find the following issues:
a. When I reset the NGC store (by renaming the file), the windows Hello environment looks OK, but when I attempt to set up a new PIN I get the error 0x801c004d and windows reports that the Windows Hello environment is not available
b) On the "Require Sign In", I have a red error message stating that "Windows Hello is preventing some options from being displayed".
c) As I am running Windows Home, I do not have access to gpedit.msc which is suggested in a number of places.
Environment
I am running a local account on Windows 10 Home edition. All available windows updates have been applied.
Same problem here. Problems after restoring a backup to my PC. Now Hello isn't working.
Same problem here. Problems after restoring a backup to my laptop. Now Hello isn't working.
@mapalko Can you provide clarifications? Thank you.
@Camalo1337 @datphuquoc81 @DaveWP have you opened a feedback hub item for this behavior? Have you tried running "certutil -deletehellocontainer" from cmd or powershell to try cleaning up state?
@Camalo1337 @datphuquoc81 @DaveWP have you opened a feedback hub item for this behavior? Have you tried running "certutil -deletehellocontainer" from cmd or powershell to try cleaning up state?
This solved the problem for me. Thank you!
Most helpful comment
This solved the problem for me. Thank you!