"We can't sign into your account" - Redstone

[HappySCCM]

We logged this as a bug to Microsoft and were waiting on a fix. Win10 incorrectly detects the profile as a temp profile.

It looks like it has been fixed in the latest cumulative updates so you can turn the GP on if you don't want labs filling up the User dir!

[Ephelyon]

May I ask how you went about logging it? I couldn't find a proper way to do so as a business customer...

 

Also, I'm assuming you mean build 447?

[HappySCCM]

We log cases via http://premier.microsoft.com

We have a certain amount of support hours provided for our contract and if it is a bug no hours are lost. I'm not sure how this is purchased apart from knowing it's part of our license agreement

 

Edit: I'm not at my desk but at least the last 2 updates contain the fix

Edited November 17, 2016 by HappySCCM
Versions info

[agelus]

I am still getting this error with latest windows 10 1607 updates. (14393.693)Setting up offline build through sccm task sequence. Everything works well apart from this "We can't sign into your account" notification.Mandatory profile setup which removes profile on logoff. Any assistance is appreciated.

[Arthur]

Mandatory profile setup which removes profile on logoff.

Did you create your mandatory profile in Audit Mode? Do you still get the error after deleting the profile from the list of profiles?

[ReBoot]

Might be a bit obvious but do you have a .V6 mandatory profile setup on your server. I was getting this error until I realised that the Anniversary Edition of Windows 10 uses a .V6 extension for the profile folder which in my case didn't exist.