Windows 10: Azure OOBE / Welcome Screen Users Logging in

Good morning,We have our computers at work connected to Azure & the team have been logging in out of Windows 10 perfectly for 12 months. One of my users logged in on the reception team today & we got "Desktop is preparing/ Setting Up Windows/ Won't be long/ almost there" essentially the first login setup you get when people first ever sign inmessage, this ultimately reset everything from the Users Desktop, Shared Network Folders, Start Menu etc. I have reset the machine [this one is seldom switched off] & logged in with a different user that logs in everyday & received the same

:)

 

Retrieve Windows 10 Azure AD connected user

I have a Azure AD joined machine (via Win10 OOBE).
Is there a way to reference the email address that is used in a script or to show this via cmd?

I have a piece of software which I need to install (on mass silently) and need to pass in the email address to the installer.

Any suggestions are welcome!

 

Black Screen after Log on


Computer boots to windows log on,have no password here.After a minute on log on it go to a black screen,stays there forever. I can get to Task Manager from black Screen,lost on what to do next. Just want my Windows 10 back, not sure what caused this problem. Any Suggestion on what my next step should be?*Sad

 

User OOBE Broker process running in background

I'm having the same issue with have user oobe broker running in the background and I can see it in the task manager. Can we end this process in the task manager or does it need to continue to run in the background? I have done all the stuff
KingFirebeard has done. Also another thing I noticed is that when this oobe is running my onedrive folder shows under common logs filecoauth files what are those.? It creates one every 10 mins. But my onedrive is disable because I don't use it. So
why is it creating those files then? When I turn on my computer or restart it does not create those files until oobe broker is running. I tested this to makesure it was the oobee doing this I have ended the user oobe broker in task manager and that stopped
filecoauth files to not be created. So could you please tell me if it is alright to end the oobe in the task manager? Also what does filecoauth.exe do and why are they creating logs if my onedrive is disabled?