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(3.2, 63%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
Hello,
I have sent PIN in Windows Hello.
Lock the screen and Entered the PIN and received the below message
AllowDomainPINLogon under "\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System" is set to 1
But above message "this option is temporarily unavailable windows hello" appears.
Please help
![](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(89.60000000000001, 81%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERA%3C/text%3E%3C/svg%3E)
Since when this problem started?
Did you download or install any program before this problem started?
Try run Windows Update and download and install all updates and restart your PC.
![](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(92.8, 23%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESS%3C/text%3E%3C/svg%3E)
There may be several reasons for this pop up message. You need to go through the trial error method to fix it. Kindly go through the following article:
How to fix – Windows Hello “This option is currently unavailable”
Synchronization between Azure AD and On-premises AD require 2 hours. Now it is solved.
What was the deployment type of WHFB? I'm experiencing the same with Cloud kerberos trust deployment type. As per MSFT, PIN should start work right after creation and it shouldn't wait for Entra ID (Azure AD) to AD sync.
Any advice please?