On my Windows 10 Enterprise technical preview machine (build 10049), it locked out after inactivity and now only offers the option to login with "Other user". On this screen, it only seems to want a Microsoft account, although if I enter a valid Microsoft account it says the password is wrong. It won't accept a domain account, and it does not seem to offer any way to switch to the normal domain login screen.

I am locked out of the PC and unable to use it. When I reboot, it goes back to the same login screen.

Help!

Hi,

Is the system joined to a domain? If a machine is joined to a domain, then after restart, the domain name should be displayed under "Other User" even though it doesn't display other user accounts. See snapshot below:

And for domain account, please make sure to type the format as domain\username

While if you have other local user account, then I recommend you login to that user acocunt (format as .\localusername) check the system info and check the policy below:

Local Security Policy\Local Policies\Security policies\Interactive logon: Do not display the last user name, it should be "Not configured" or "Disabled".

Rrgards

Hi Yolanda

Yes, the machine is joined to a domain. However, as you can see from the screenshot, it is not offering me the option to login with a domain account. It is prompting for an "email address" not "user name". I can only assume the login process has somehow become corrupted.

If we try to enter any form of domain credential, it comes back with an error asking you to enter a valid e-mail address. If we enter a valid Microsoft account, it comes back with the message that the password is incorrect even though it is correct.

The only way forward I can see is to wipe and rebuild the machine.

Thanks
Knox

Hi,

Are you using Cisco AnyConnect?
I got this problem also after installing version older than 3.1.07021.

Gerald

Interesting.

Yes, I am using AnyConnect. With the machine unusable, I can't verify what version is installed. It was the latest version available in around mid February.

Were you able to recover the machine, or did you end up rebuilding it?

Hi,

I was able to recover with System Restore and you need a working local admin on your computer to use it.

Your problem belongs to Cisco NAM which seems to break the Win10 Logon system.
I reported this on the Cisco forums and a few days later, 3.1.07021 was released.

NAM is now working correctly but seems a bit slow to detect and validate the network, unlike in Windows 7 or 8.x

Gerald

• Proposed as answer by Gerald Mathieu 24 minutes ago