Domain credentials not working on Windows 8.1 after reboot
Fixed it by removing my Windows Indentity credentials from the Credential Manager in the Control Panel, and adding it again.
The "Persistence" attribute for the credentials then changed from "Logon Session" to "Enterprise", and I'm now able to reboot/logoff and log in again while away from the network
Related videos on Youtube
Mathias R. Jessen
Working professionally as a Microsoft Systems Administrator at Booking.com with a focus on Active Directory and Security. Interested in topics like: Information Security, Web Server technologies, Server Hardening, Application Development, Network Infrastructure, Process Management Interested in products/technologies like: Windows, Active Directory, PowerShell, IIS, Exchange Server, Apache, DNS, .NET and much more...
Updated on September 18, 2022Comments
-
Mathias R. Jessen over 1 year
On my new Windows 8.1 laptop installation, I can log in with my domain credentials when on the office/domain network. After hibernating the laptop and taking it offline I can still use my domain credentials to unlock the existing desktop session, indicating that Windows has successfully cached my credentials.
While still offline, if I reboot the machine however, I get a "The password is incorrect" error when authenticating with my domain account.
How do I make sure the cached credentials persists after a reboot?
-
Ramhound over 10 yearsWas this installation upgraded from Windows 8 or was it a fresh installation. If you didn't remove the computer from the domain before you upgraded that could cause a problem.
-
Mathias R. Jessen over 10 yearsFresh install, no upgrade
-
Ramhound over 10 yearsIt seems like you solved this. The next question I was going to ask you if the name of the computer was unique.
-
Mathias R. Jessen over 10 yearsYou think it fails Kerberos auth on the office because of dup SPNs, and fall back to NTLM?
-
Ramhound over 10 yearsMy line of thought was that if the computer name wasn't unique or was the name of a previous Windows 8 machine that it would be trying to use credentials or other attributes that wasn't valid for Windows 8.1 because of a change. It was simply going to be something I was going to suggest.
-