Upgraded from 8.1 to 10. Went smooth. Put computer to sleep for a day, now it refuses to take the absolutely correct password for my Microsoft account. I type it and reveal it and its 100% correct. It still says "that password is incorrect. Make sure you are using the password for your Microsoft account". I then jump on another pc, log in to that very same MS account using that exact password.
I emailed MS and they replied back that I emailed the password team or some crap and gave me a link to a generic FAQ about windows 10. Which did no good for me. Any idea why windows 10 refuses to log me in with very much the correct password they are asking for? Obviously it seems it's an F up that has occurred with my copy of windows 10 , or something.
Thanks for any help!
UPDATE- Thanks for the suggestions guys, but unfortunately, none worked. I can verify it is asking for my "Microsoft Account" password. I can then go on another computer, use the same email it shows on the windows 10 logon screen, with the same password, and can log in to the account fine. Yet it lies and tells me im entering the wrong password on the Win 10 logon. I check the password by clicking the "password reveal" button, and everything it typed correct. I am at a loss. IT does the same whether I have the computer online, or offline.
UPDATE UPDATE= Ok, this is weird. I logged in to the windows account for the locked PC on my good rig. I logged in fine and checked the "recent activity". IT SAYS I SUCCESSFULLY LOGGED IN EVERY TIME I TYPED THE PASSWORD IN ON THE LOCKED COMPUTER. So, the system on their end thinks im logging in fine with the password on this locked computer, but the computer itself says its the wrong password. What the hell does on do about that!?
"Successful sign-in (3 events) 8/26/2015 10:49 PM - 11:13 PM United States
Successful sign-in 8/26/2015 11:13 PM United States
Successful sign-in 8/26/2015 10:51 PM United States
Successful sign-in 8/26/2015 10:49 PM United States"
LAST UPDATE-6/18/16- I resolved it by reinstalling Windows 10 again on the computer not long after the last update above this one. That's the only way I got around it. I am guessing there is another way around it, but I did not have the patience. Since then, I haven't had an issue. Not sure what it was doing.
I emailed MS and they replied back that I emailed the password team or some crap and gave me a link to a generic FAQ about windows 10. Which did no good for me. Any idea why windows 10 refuses to log me in with very much the correct password they are asking for? Obviously it seems it's an F up that has occurred with my copy of windows 10 , or something.
Thanks for any help!
UPDATE- Thanks for the suggestions guys, but unfortunately, none worked. I can verify it is asking for my "Microsoft Account" password. I can then go on another computer, use the same email it shows on the windows 10 logon screen, with the same password, and can log in to the account fine. Yet it lies and tells me im entering the wrong password on the Win 10 logon. I check the password by clicking the "password reveal" button, and everything it typed correct. I am at a loss. IT does the same whether I have the computer online, or offline.
UPDATE UPDATE= Ok, this is weird. I logged in to the windows account for the locked PC on my good rig. I logged in fine and checked the "recent activity". IT SAYS I SUCCESSFULLY LOGGED IN EVERY TIME I TYPED THE PASSWORD IN ON THE LOCKED COMPUTER. So, the system on their end thinks im logging in fine with the password on this locked computer, but the computer itself says its the wrong password. What the hell does on do about that!?
"Successful sign-in (3 events) 8/26/2015 10:49 PM - 11:13 PM United States
Successful sign-in 8/26/2015 11:13 PM United States
Successful sign-in 8/26/2015 10:51 PM United States
Successful sign-in 8/26/2015 10:49 PM United States"
LAST UPDATE-6/18/16- I resolved it by reinstalling Windows 10 again on the computer not long after the last update above this one. That's the only way I got around it. I am guessing there is another way around it, but I did not have the patience. Since then, I haven't had an issue. Not sure what it was doing.