Win 10 pro joined to Domain - cant log in

It might be a too obvious solution but are you logging in as:

DOMAIN\Username

As the syntax?

Matty,
Yes tried that and other variants.
Thanks

One note to make is that i just migrated my exchange on premise account to O365 but that should have no impact. My user account is still in ADUC as i checked from another PC. I cannot log in using ay other account either.

John,
Allow me to try your approach and I will post back results.

Make sure you're trying to login to the domain.  Use domain\username as the username, not just username.

Otherwise, login in locally as computer\username.

Is the PC a laptop or a desktop?  Is it wireless or wired?  Sometimes Wireless does not connect to the network until after login - but if that happens, it can't authenticate with the server.  So everyone is a bad username and password.  Use wired connection to at login at least once and establish a cached credential.  And look over the various options for wireless to ensure it's properly setup to start BEFORE login so that group policies can properly apply.

the connection is wired as i always do wired for first domain log in attempt. I have already tried all variant of log in combinations. I will be trying John's suggestion first.

I figured I'd start with the most obvious first. Unless you've already started the Windows reinstall/upgrade process, I'd login to the DC and see if event viewer shows the failed login attempts in the DC's security log from the account and domain-joined PC in question. If not, then the upgraded PC is not communicating with the DC. Make sure that the PC in question has the DC's IP address defined as the primary DNS. If you have permissions/credentials to do so, attempt to login as domain admin on the PC. Also, when logging on try using both the NETBIOS name of the AD domain as well as the Fully Qualified Domain Name (domain.local or whatever)

I'd also create a local admin account on PC (just to be sure), remove it from the domain. Verify that DNS is right, and that you can ping the DC by name, and then add it back. Maybe something went wrong during the AD join...

Let us know!

Matt

John,
it appears your solution worked. Thank you for the response. quite curious why this happens. never had the issue occur on any other upgrades we had at the office.
Thanks again

Thank you. Some upgrades work and some do not. I have had both happen to me, so I was posting out of experience. Thanks for the update.

I was having the same issue on a clients network and after searching high and low for a solution I came upon this thread.

John's solution was the ace in the hole!

Thanks a lot John!

Finally after all my searching, I come across a solution that worked. Thanks for sharing you're experience with this issue John ! I has also solved my problem!

Can you keep all programs with John solution or just data ?

Thank you,

You have a choice to Keep All, Keep just Data or Keep Nothing.

Thanks John, this fixed the issue without fail.

Thank you for the update and I was happy to help

John,

I tried this after doing a Windows 10 Home to Windows 10 Pro update (I was unable to login to the domain after the upgrade). When I ran the upgrade from the Media Creation Tool, the system reverted back to Windows 10 Home. I may have lost my upgrade in the process and still cannot login to the domain. Any thoughts on this one?

Does anyone know if there is a Microsoft Knowledge Base (KB) on this?

I am not sure why it would revert to Home, but you need to re-apply the Pro Upgrade

I will look for a Microsoft KB on this, but I do not know right off the bat.

I just had this happen for me for the first time on v.1903 and I stumbled over a better solution.  

My system in question was not trusting the local domain and any administrative functions kept showing various error saying elevation was required, local domain not trusted, and other unexpected error messages.  I was going to simply re-image it from scratch when I logged in as the Local Admin user account with a v.1903 USB Setup drive attached.  The PC simply was able to repair it's local domain issues on the fly and it has had no problems since.

I keep .ISO's of the most recent and supported version of Windows 10 (as well as past versions) so that I can create a USB key when needed and I would recommend using a matching version of the Windows source files if I ever need to try this again.