New
#11
And here happened three times on Saturday, no repeat performance today though.
And here happened three times on Saturday, no repeat performance today though.
I see some people had problems with their local accounts but mine was an microsoft account. Weird thing is I tried out helmut's solution as well as deleting temp and weird profiles on users folder. Atempted to restart my PC multiple times and no "we cannot sign you into your account" problem. Not sure which is which but I feel this is too early to tell as you're all having the same problem. Its just feels so weird. Because of that I decided to create another user account. If I ever encountered that error again, I'll try out Brink's solution. :)
Okay, im rebooting it one more time and I get we cant sign in to your account error. So Helmut's suggestion doesn't work. Now I'm off to do Brink's suggestion.
I know this may show my ignorance or total lack of knowledge
i had this happen to me yesterday and i ignored it and restart my pc then i ran antivirus/malware software i.e malaware bytes and it came up with loads of entries from news.ru which had placed entries all over the registry etc etc ....dont know what they where for or what they did but it may be worth looking to see if you also have these entries.....news. ru ar famous for backdoor and covertly gaining access to pc's and this seems like one off theirs....
Hmmm...interesting. However, I just ran both malwarebytes and windows defender and they're looking pretty clean. So...it couldn't be that.
Although I tried out Brink's suggestion and it didn't seem to work. I look at the .bak sid key, the profileimage was located at my user profile while the current one, where I had the "we cant sign you in" error, the profile image was located at "c:\\users\temp" or whatever that location is. The tutorial steps seems quite the opposite although I followed the steps besides that and I modified the dword of "state" ro 0.
I don't have a local account, only a Microsoft account. It happens very randomly and so far I just log out as it suggests and log back in with no issue. No clue why this just started last week. After the new Windows update comes out and if it continues then I will research this more.
Anyone found a solution to this?
We have about 100 machines running multiple versions or Windows 10(1511,1607,1703,1709) and this started happening to us also just a week ago. We found that this problem would occur about 10% of the time at startup, all with local accounts that autologin, no password. Signing out then back in goes back to the regular account.
I've tried almost everything I could find on the net. I even setup a brand new machine, made sure it was disconnected from the internet and rebooted it 100 times. No issue.
I then connected it to our WiFi, rebooted 5 times and the profile issue came up again. Disconnecting it from WiFi would not fix it. Now it exhibits the same 10% failure rate seen on all the other machines online or offline.
This is driving me crazy. The fact that this started happening at the same time for everyone makes me think its Microsoft pushing some stupid broken update through a hidden proccess or something.
Did you try Brinks solution on page 1? I haven't tried it as I was going to see what happens after the Spring update. I don't have or use a local account. Only a Microsoft account. I am also using the auto sign in and it still happens randomly. I can't reproduce it on purpose. Just started happening randomly for no reason.
I am guessing then it must have been one of the security updates that messes with the auto log in. Doesn't seem to matter if it is a local account or Microsoft account. It randomly fails to auto login.