- #Pin not working windows 10 install#
- #Pin not working windows 10 manual#
- #Pin not working windows 10 windows 10#
- #Pin not working windows 10 trial#
Hopefully, Windows will now be able to contact Microsoft's servers and validate your password so you can logon.Īdded a note to help find the right registry files.When you turn on iCloud Drive, iCloud for Windows creates an iCloud Drive folder in File Explorer. Wlidsvc (Microsoft Account Sign-in Assistant)Īnd these services need to be set to Automatic startup (Start = 2):
#Pin not working windows 10 manual#
These services need to be set to Manual startup (Start = 3): Some of these may seem unnecessary, but they are dependencies for other services. The short name is where you'll find it in the registry, in parenthesis is the long name for it. For reference, the valid values for startup type here are: Under HKEY_LOCAL_MACHINE\ssystem\ControlSet001\Services, we're going to go to each service and edit the Start key value. This time, we'll load the SYSTEM hive as ssystem. Reboot back to the WinRE command prompt and open regedit again. To make this work, we need to enable some logon services for Microsoft Accounts and make sure network access is enabled by enabling services. If it tells you that your password is incorrect (even though it's the right password), that means the password has never actually been used before and we have to do some extra steps. In my case, it was just going back to Normal Startup in msconfig. Now reboot. If you're lucky, you can now logon with your password, and then hopefully fix whatever is causing the issue. This will turn off that "Require Windows Hello" setting. There there is a key for DevicePasswordLessBuildVersion. Go to HKEY_LOCAL_MACHINE\ssoftware\Microsoft\Windows NT\CurrentVersion\PasswordLess\Device. It's the registry from the stripped down version of Windows that you're currently using to fix this. (Note: Don't use the version on the X:\ drive. My instructions will assume you name them ssoftware and ssystem like I do. This will give us a new listing under HKLM. I normally just use an extra s in front of the name, but it really doesn't matter as long as it's not something that's already there. The hive files will be in C:\Windows\System32\config (or in the case of one of my computers, it was E:\).
To do that, first select HKEY_LOCAL_MACHINE, then select File -> Load Hive. So you have to manually load the registry hive to be able to edit them.
#Pin not working windows 10 install#
This will bring up the registry for the recovery environment (WinRE), not your install of Windows. The much newer preview build never asked for one. It did use the password and didn't seem to have any trouble on the one machine that required me to do it. You may be asked to log in at this point, which I think depends on your which build of Windows it is. This will bring up the Recovery options on reboot.Ĭlick Troubleshoot -> Advanced Options -> Command Prompt. This disabled all the required services and then I couldn't logon because the only account on the computer was made using a Microsoft Account instead of a local account.Īfter pressing ok and rebooting, I was presented with this:įirst, hold down Shift while pressing restart on the logon screen. This setting is enabled by default.įor me, this happened because I enabled Diagnostic Startup in msconfig.
#Pin not working windows 10 windows 10#
The problem is caused by a sign-in setting for Microsoft accounts in later builds of Windows 10 that prevents you from using a regular password to logon, but doesn't work at all if the services that make Windows Hello work aren't running. This may not solve the problem completely if it was originally caused by something different than my problem, but hopefully it'll be a good head start for those people. Then later, I recreated the problem on a virtual machine of a fresh Windows 10 install to see which thing I did actually fixed it and discovered another potential problem that people may encounter.
#Pin not working windows 10 trial#
This happened to me last night and I want to document it here so that hopefully someone else won't have to spend 3 hours trying to fix it through trial and error, or worse, have to "Reset my PC" or reinstall, which I was very close to doing before I solved it.