This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(57.599999999999994, 45%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJS%3C/text%3E%3C/svg%3E)
I receive this error when trying to create a pin: 0x80090010 after OOBE is finished. MS references it as 0x80090010 NTE_PERM under Errors with unknown mitigation, which isn't really helpful.This is occurring from their crappy free Windows 11/356 lab.
I reset the OS but still the same error. Is this a bad config in Azure? There are pin options in my account sign-in options.
Any ideas?
Hello,
Over RDP. virtual environments like VMware etc.. Windows Hello is going to give you some errors.
They way Windows Hello (Pin, Biometrics etc.) works is using hardware machine.
If this answer solves your issue, please vote for it so other community members know that this is a quality answer.
This lab has been terrible. So I'm accessing it per MS instructions via Hyper-V manager. It would still be problematic u think? These are the log errors. Windows Hello for Business provisioning will not be launched.
Device is Microsoft Entra joined (or hybrid joined): Yes
User has logged on with Microsoft Entra credentials: Yes
Windows Hello for Business policy is enabled: Yes
Windows Hello for Business post-logon provisioning is enabled: Yes
Local computer meets Windows hello for business hardware requirements: No
User is not connected to the machine via Remote Desktop: No
User certificate for on premise auth policy is enabled: No
Machine is governed by none policy.
Cloud trust for on premise auth policy is enabled: No
User account has Cloud to OnPrem TGT: Not Tested
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(188.79999999999998, 35%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EZM%3C/text%3E%3C/svg%3E)
@JJ STOKES, Thanks for posting in Q&A.
From the information you provided, it seems that the target device's hardware does not meet the requirements. Basically, Windows Hello for Business need TMP, so please turn TPM on Hyper-V manager and try again.
If there is any update, feel free to let me know.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 82%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESG%3C/text%3E%3C/svg%3E)
We have the same error, my VM run on Hyper-V 2025, the Secure Boot and TPM was activated. When I try to initialize Windows Hello for Business at the installation when my VM was Entra Join, I receive the pin creation failure error 0x80090010.
It's not the first time I provision Windows Hello for Business in VM, but I don't understand this error and why I have it.
Hi, Steve Gauvin
Currently, there is not much useful information I can find and based on the official document, it is recommended that you contact Microsoft support to get more help.
I'm ending this post. Nothing is working. This is just an unsupported lab that becomes outdated so fast. After restarting the lab 3x I've just given up on so many of the presenting issues and just trying to get past them regardless.
Thanks everyone!
Hi, @JJ STOKES
If you want to get more information about this issue, it is recommended that you contact Microsoft support to get more help.
I'm ending this post. Nothing is working. This is just an unsupported lab that becomes outdated so fast. After restarting the lab 3x I've just given up on so many of the presenting issues and just trying to get past them regardless.
Thanks everyone!