- Windows login issues can be serious since they can actually prevent you from accessing your PC.
- For example, we will be showing you what to do when you encounter Windows login error 0x80090016.
- For more articles on this topic, head over to our Windows Login Errors Hub.
- If you need further help, check out our dedicated Windows 10 Errors page.
Error 0x80090016 can arise for users when they try to set up Windows 10 PINs or log in with them. The error message states:
We weren’t able to set up your PIN. Sometimes it helps to try again or you can skip for now and do this later.
If you need to fix that to set up a PIN in Windows 10, check out these potential resolutions for error 0x80090016.
How do I fix Windows error 0x80090016?
1. Run a System File Checker scan
- First, try scanning with the System File Checker. Press the Windows key + R to launch Run.
- Enter cmd in Run’s Open box.
- Press the Ctrl + Shift + Enter key combination to open an elevated Command Prompt.
- Although not always essential, it’s a good idea to run a Deployment Image scan first.
- To do that, input DISM.exe /Online /Cleanup-image /Restorehealth and press Enter.
- Then input sfc /scannow in the Prompt, and press the Enter key.
- Wait for the SFC scan to do its stuff, and then restart Windows if it repairs files.
2. Clear the NGC folder
Clearing the NGC folder, which you’ll need to take ownership of, is one of the most confirmed fixes error 0x80090016.
- First, press the Windows key + E key combination, which opens File Explorer.
- Select the Hidden Items checkbox option on the View tab.
- Then open this folder path in Explorer: C: > Windows > ServiceProfiles > LocalService > AppData > Local > Microsoft.
- Next, right-click the NGC folder to select Properties.
- Select the Security tab on the window that opens.
- Click Advanced to open the window shown in the snapshot directly below.
- Then click Change to open the Select User or Group window.
- Enter the user account name for the one you’re currently logged in to.
- Click the Check Names button.
- Press the OK button.
- Select the Replace owner on subcontainers and objects option.
- Select the Apply option.
- Click OK to close window.
- Open the NGC subfolder.
- Press Ctrl + A to select all its content.
- Press the Delete button on the Home tab.
3. Enable Turn on convenience PIN Sign-in
Users can fix error 0x80090016 with Group Policy Editor in Windows 10 Pro and Enterprise.
- To do that, enter gpedit.msc in Run; and press the OK button.
- Expand Computer Configuration on Group Policy Editor’s navigation pane.
- Then click Administrative Templates, System, and Logon on the left of the window.
- Double-click Turn on convenience PIN sign-in on the right panel within Group Policy Editor.
- Select the Enabled radio button.
- Click the Apply button to save the setting.
- Press the OK button to exit the window.
4. Roll back Windows
Error 0x80090016 might also be due to recently installed third-party software, which you remove by restoring Windows to a restore point. To do that, check out the System Restore post that provides guidelines for rolling back Windows.
Selecting a restore point that goes further back will more likely resolve the error as it will remove more software.
Those are some of the confirmed resolutions users have fixed PIN error 0x80090016 with. So, the above resolutions will usually fix the issue.
Note that the above resolutions are not for the Microsoft Store error that shares the same 0x80090016 code.
Let us know which ones worked best for you by leaving us a message in the comments section below.
FAQ: Learn more about Windows Login errors
- Can I skip the WIndows login screen altogether?
Yes, you can skip the login screen in Windows by using these two tricks.
- Why does my Windows login freeze?
There are plenty of reasons as to why your Windows login screen is slow, or if it freezes.
- Why doesn’t my Windows auto-login work?
Many software issues can cause your Windows auto-login feature to stop working. If you want to fix that, simply follow this detailed guide.
Editor's Note: This article was originally published in March 2020 and was revamped and updated in July 2020 for freshness, accuracy, and comprehensiveness.