"We can't sign in to your account" after installing 1607

[juliee]

I thought the changes in 1607 to the "Education" version (turning off the store by default, etc.) sounded hopeful, so downloaded an .iso and applied it to a couple of computers. Sure enough, our old friend Candy Crush is gone...but on signing in, domain users get "We can't sign in to your account. The problem can often be fixed by signing out of your account and signing back in. If you don't sign out now, any files you create or changes you make will be lost." Needless to say, signing out and back in just gives the same opaque message. Users cannot access their Documents, etc. This is on a domain joined computer with roaming profiles and folder redirection.

 

 

What might cause this? I tried asking on TechNet and got crickets...

 

I'm really regretting having gone down the Windows 10 path. Too many hours trying (and mostly failing) to make the so-called "Education" edition suitable for an education environment. Everything I was reading about 1607 for Education sounded encouraging, after the 1511 debacle.

 

: (

[ZeroHour]

Microsoft released a update on the 31st of August that may fix that in case you have not rolled it out.

[juliee]

What number? I have KB3189031, KB3176938, and KB3176936 as of this morning. The behavior hasn't changed.

I note that the folders for Documents and Pictures, which should be redirected by group policy, do show up in File Explorer--but they're local, not redirected as they should be. Test files placed there persist between logins, but locally, not in the redirected location on the server.

These folders are being correctly redirected on 1511.

[Ephelyon]

Perhaps this thread should be merged with this one from earlier?

[juliee]

Aha! Yes. I searched, but failed to find that one....

[ArthurDent]

I had this issue with Windows 10 Education using roaming profiles. It didn't happen in v 1511 (build 10586), it started when we upgraded to v 1607 (build 14393). I lived with it and then when I installed v1703 (build 15063) it went away.

[dry]

It's worth checking the size of the roaming profile that's getting the error. We had one profile quite a while ago that was 8GB+ in size, and Windows was failing to download the profile in it's entirety before logging on resulting in the error you describe.

[ArthurDent]

It happened with all users so profile size was not a factor e.g. my test user has a 2Mb profile.

[KK20]

we had this issue early on, I fixed it by providing .pdf file association to acrobat DC. Windows was forcing it to edge and was causing an issue with the profile on login, the file association GPO made it go away.