Windows was very excited about the introduction of Windows Hello. I don't blame them for that because the new concept was revolutionary, but fewer people understood it. However, the irritating part was that they set the updates in such a way that every time a user started the system he would ask to set the PIN. This was especially true with company-controlled systems, as they knew company users would be interested in the PIN system.
For those who liked it, it must have been an occasional problem, but those who chose not to set their PIN couldn't find any options to bypass the PIN setup screen. They clicked Next and then skipped the installation which was annoying. Also, they had to do exactly the same thing every time they booted the system.
To eliminate this message we should clearly indicate to the system that we are not interested in configuring the PIN. These are the methods to do it:
Solution 1] Make changes to Windows Defender settings
Although Windows Defender was meant to be used in conjunction with antivirus and other system security software, it always manages the PIN request page.
We may make the changes when we try to boot the system in the following way:
1] Log into to the system without going through the Windows Hello prompt screen as usual.
2] When on the desktop screen, click the up arrow in the menu in the lower right corner of the screen.
3] Click on the Windows Defender icon (a shield icon) to open the Windows Defender settings.
4] Click and open the account security settings.
5] Select Configure and Discard.
Solution 2] Change Group Policy
Since the problem is often with company-managed systems, making changes directly to Group Policy could be very helpful.
1] Press Win + R to open the Run window and type the command gpedit.msc.
2] In the Group Policy Editor, go to the following path:
Computer Configuration >> Administrative Templates >> System
3] Open the Logon folder.
4] Find and double-click the Enable convenience policy Log in with PIN.
5] Move the radio button to Disabled, then click Apply and then OK.
Interestingly, most users today are not seeing this error, and the precise reason is that companies have already changed this policy on managed systems. For those who don't have this guide it would be helpful.