Domain Account Username or password invalid after upgrading from Home to Pro

Alex Riggs 6 Reputation points

I started at a company with about 100 users, all of which are remote. Only about 10 of those users was on the domain. I am slowly getting users on the domain, but everything being remote is a challenge. I have worked out a device tunnel using RRAS, and using Offline Domain Join to create a cert for authentication, joining to the domain, etc.

I've got several users on the domain and now I am running into issues with one of them. They were using Windows 11 Home. We purchased an upgrade key and changed the user to Windows 11 Pro. The unfortunate part of this is I have learned that a lot of the remote laptops here are using Windows 11/10 Home.

On Friday I got a user upgraded, on the domain, able to login, using the device tunnel, etc. Monday morning comes and they can no longer log in with their domain account. Using a screen sharing agent I have installed, I attempted to login with my domain account as well with no luck. I reset the user's password and clicked "user must reset password at login". When he logged in, it asked him to reset his password, he did, then went to login with it. Again, invalid password.

I did some research and I found this was a known bug with Windows 10. He said his computer was Windows 10 then he upgraded to Windows 11 at one point. His computer is fully up to date now with Windows 11. My question is, does this bug still effect Windows 11 if the update wasn't taken before upgrading to Windows 11? And what can I do about it without having the computer physically in front of me? Replacing this one isn't that bad, but it's the other 85 computers I worry about!

Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
3,619 questions
Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
5,964 questions
Windows 11
Windows 11
A Microsoft operating system designed for productivity, creativity, and ease of use.
3,509 questions
No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Dave Patrick 329.6K Reputation points Microsoft MVP

    Might try patching both problem member and domain controllers to latest available. Also check that the problem member and domain controller both have the ip address of DC listed for DNS and no others such as router or public DNS.

    --please don't forget to upvote and Accept as answer if the reply is helpful--

  2. Dave Patrick 329.6K Reputation points Microsoft MVP

    You could look for something here.

    --please don't forget to upvote and Accept as answer if the reply is helpful--