Windows 10: "We Can't Sign You In" Problem / creates the temp profile....

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.

 

That was the first thing I found and tried. It doesnt solve the intermittent issue.

 

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.

 

What I posted in #10, 5 days ago, has worked as the problem has not occurred again.
All I can add is that the UWP Apps are being updated in preparation for the 1803 SCU version update feature of Timeline.

Whilst the guides on here are useful they won't be taking in to account the new feature updates of the UWPs.

 

Same problem here also !
Random , sometimes all goes well and suddenly , WHAM, again this nasty login-problem .
Brinks fix seems not so easy to me , so Im searching for the cullprit or/and waiting for next Windows 10-upgrade . There must be a reason , but its hard to discover , I see lots of people with the same problem , so MS has to fix it someday.............!!
Maybe next upgrade will solve this annoying bug , though I will install with accounts and software in place ( no clean install , costs me too much time for installing all my software again !) Will see...............*Rolleyes

 

Thanks,
The UWP Apps and Store do seem to be the cause of the problem, atleast for the most part.
Instead of updating them, I went ahead and removed all apps and the store entirely(we never use). Tried 150 reboots and the issue did present itself once, but this is atleast much better than before.

For anyone curious on how, there are a lot of guides/scripts out there on selectively removing the apps but I just used in powershell:
Get-AppxPackage -AllUsers | Remove-AppxPackage
**Beware** This removes everything and the store as well.

 

I only use a local account (Win 10 Pro 1709 Build 16299.248) and have never used the store (knowingly) but am still experiencing the problem. It happened again earlier this evening after I decided to carry out a restart.

It took me a second restart and and then a sign out/sign in before I got back to 'my' local account rather than a temporary profile. *Sad

 

We never used it either. But apparently it does its own thing.
Try updating and removing unused apps, or removing everything alltogether.

 

FWIW we are having the same problem on about 12 different Windows 10 and 7 pro computers, it first appeared April 5th so i'm wondering if it was a recent MS update. We are using local user accounts, no domain. The problem seems exacerbated by 3rd party software LogMeIn where the issue happens during a remote session within about 5 minutes of the connection, usually prior to logging off. However it also happens during a regular reboot without any remote sessions. We have seen the issue on a few PCs even without LogMeIn at boot time.

It seems the USERPROFILE environment variable is set to the System Profile user instead of the usual login user, the solution was to change it back to recover, but it keeps reoccurring.

Was wondering if this is due to an issue with fast user switching.


The logs look like this:

76298,Application,Microsoft-Windows-User Profiles Service,ERROR,PC-208829,4/17/2018 2:59:18 AM,1508,SYSTEM\NT AUTHORITY,"Windows was unable to load the registry. This problem is often caused by insufficient memory or insufficient security rights. DETAIL - The process cannot access the file because it is being used by another process. for C:\Users\Admin\ntuser.dat "
76299,Application,Microsoft-Windows-User Profiles Service,ERROR,PC-208829,4/17/2018 2:59:18 AM,1502,Admin\PC-208829,"Windows cannot load the locally stored profile. Possible causes of this error include insufficient security rights or a corrupt local profile. DETAIL - The process cannot access the file because it is being used by another process. "
76300,Application,Microsoft-Windows-User Profiles Service,ERROR,PC-208829,4/17/2018 2:59:18 AM,1515,Admin\PC-208829,"Windows has backed up this user profile. Windows will automatically try to use the backup profile the next time this user logs on. "
76301,Application,Microsoft-Windows-User Profiles Service,ERROR,PC-208829,4/17/2018 2:59:18 AM,1511,Admin\PC-208829,"Windows cannot find the local profile and is logging you on with a temporary profile. Changes you make to this profile will be lost when you log off. "
76302,Application,Microsoft-Windows-User Profiles Service,ERROR,PC-208829,4/17/2018 2:59:19 AM,1508,SYSTEM\NT AUTHORITY,"Windows was unable to load the registry. This problem is often caused by insufficient memory or insufficient security rights. DETAIL - The system cannot find the file specified. for C:\Users\TEMP\ntuser.dat "
76303,Application,Microsoft-Windows-User Profiles Service,ERROR,PC-208829,4/17/2018 2:59:19 AM,1505,Admin\PC-208829,"Windows cannot load the user's profile but has logged you on with the default profile for the system. DETAIL - The system cannot find the file specified. "

 

Yes, I have seen exactly the same errors in the eventviewer .
It happens random , you never know before , when it happens again , very,very nasty bug !!
Im almost sure its a Win10-update ...........

Question remains ; WHAT can we do about it , will next Win10-upgrade solve this problem................???? *really