All the constructive feedback and information was helpful and appreciated. Although in a comment I said that it was not working, I was incorrect in that what I expected being the passwordHash, securityStamp and cuncurrencyStamp matching to a user (myself) made it invalid. When inspecting those fields I noticed that somehow or maybe because it had not been completed, the email confirmation field was set to 0. Therefore not allowing the user to log in regardless of whether the password was correct or not. When I updated the email confirmed flag to true, the user was able to log in with the updated password.

Thus the answer was to double check as to the real reason the user was getting rejected during login and make sure it was not the password update performed by the admin.

Mostly, I apologize to any and all KIAs. I can't seem to find my SLA handbook from school 40 years ago. So there may and probably be some grammar, punctuation and other errors.