Home

Windows 10 profile AzureAD issue after update

%3CLINGO-SUB%20id%3D%22lingo-sub-99807%22%20slang%3D%22en-US%22%3EWindows%2010%20profile%20AzureAD%20issue%20after%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-99807%22%20slang%3D%22en-US%22%3E%3CDIV%3E%3CP%3EOk%2C%20long%20one%20guys.%20%26nbsp%3BThe%20windows%2010%20forum%20sent%20me%20over%20here.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FDIV%3E%3CDIV%3EFault%3A%20on%20a%20very%20few%20occasions%20after%20a%20windows%20update%2C%20an%20AzureAD%20(pc%20is%20AzureAD%20joined)account%2C%20*I%20think%20the%20one%20that%20was%20logged%20in%20at%20the%20start%20of%20the%20update%20process*%2C%20after%20login%20will%20come%20up%20to%20a%20black%20screen%20with%20a%20mouse%20pointer%2C%20however%20the%20GUI%20does%20not%20respond%20to%20clicks.%3C%2FDIV%3E%3CDIV%3ECtrl-Alt-Del%20will%20bring%20up%20the%20security%20screen%20fine%2C%20can%20open%20task%20manager%20and%20log%20out%20OK%20and%20the%20login%20screen%20shows%20up.%20With%20the%20problem%20account%2C%20after%20a%20bit%20of%20button%20pressing%20I%20can%20hit%20the%20Win%20key%20to%20pull%20up%20the%20start%20menu%20(which%20appears%20to%20work%20fine)%2C%20and%20peek%20preview%20will%20allow%20me%20to%20see%20the%20wallpaper%2C%20any%20programs%20i%20start%2C%26nbsp%3B%20and%20desktop%20icons%20fine%2C%20but%20once%20i%20try%20to%20select%20any%20active%20window%2C%20or%20the%20desktop%20the%20screen%20goes%20back%20to%20black%20with%20pointer.%26nbsp%3B%20This%20only%20happens%20on%20the%20one%20specific%20account%20and%20any%20other%20logins%20are%20unaffected%20(both%20previously%20logged%20in%20accounts%2C%20and%20first%20time%20log%20ons).%3C%2FDIV%3E%3CDIV%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20can%20recreate%20the%20situation%20on%20a%20windows%2010%20AzureAD%20joined%20machine%20(at%20least%20the%20several%20i%20tried)%3A%20This%20is%20done%20manually%20via%20reg-edit%20removing%20the%20profile's%20UID%20in%20ProfileList%2C%20and%20the%20deleting%20the%20user%20profile%20directory.%26nbsp%3B%20The%20next%20time%20that%20account%20ties%20to%20log%20on%2C%20you%20get%20the%20black%20screen%20with%20working%20start%20and%20%22hidden%22%20desktop%20as%20described%20above.%3C%2FP%3E%3C%2FDIV%3E%3CDIV%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETroubleshooting%3A%20So%20we've%20ruled%20out%20graphics%20issues%2C%20it%20isn't%20the%20Win%2BP%20issue%20that%20was%20a%20thing%20during%20the%20insider%20previews%20pre-RTM%2C%20it%20appears%20to%20just%20be%20localized%20to%20AzureAD%20profiles%20(non%20administrator)%20that%20have%20been%20on%20the%20PC%20before%20and%20were%20logged%20in%20when%20one%20of%20the%20updates%20were%20applied%20and%20the%20PC%20restarts.%20Again%20this%20has%20only%20happened%20in%20less%20than%201%25%20of%20updates%20across%20your%20networks%20(4%20out%20of%20about%20400).%3C%2FP%3E%3C%2FDIV%3E%3CDIV%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20only%20way%20we%20can%20find%20to%20get%20past%20it%20is%20to%20do%20a%20soft%20or%20hard%20Windows%20reset%20and%20start%20from%20scratch.%20Obviously%20this%20turns%20a%2015-20%20minute%20profile%20reset%20into%20a%203%20hour%20ordeal%20involving%20shipping%20the%20laptop%20back%20to%20this%20office.%3C%2FP%3E%3C%2FDIV%3E%3CDIV%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20to%20sum%20up%20further%20details%20than%20I've%20described%20above%3A%3C%2FP%3E%3C%2FDIV%3E%3CDIV%3E%3CP%3EMultiple%20hardware%20specs%20(Dell%2C%20Lenovo%2C%20HP)%3CBR%20%2F%3EAll%20fully%20up%20to%20date%20Win%2010%3CBR%20%2F%3EAll%20on%20AzureAD%20domains%20with%20PIN%20requirements%3CBR%20%2F%3EOther%20local%20and%20AzureAD%20accounts%20work%20fine%3C%2FP%3E%3CP%3ECan%20replicate%20issue%20easily%3C%2FP%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-99807%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20AD%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-190148%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%20profile%20AzureAD%20issue%20after%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-190148%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20not%20the%20OP%2C%20but%20I've%20managed%20to%20fix%20this%20issue.%20Just%20disable%20Windows%20Hello%20for%20Business%20in%20gpedit.%20It's%20tedious%20though%20since%26nbsp%3Byou'll%20have%20to%20do%20it%20for%20every%20PC%20manually.%20I%20only%20administer%2012%20PC's%20so%20it's%20not%20the%20problem%20for%20me.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-190039%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%20profile%20AzureAD%20issue%20after%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-190039%22%20slang%3D%22en-US%22%3E%3CP%3EDid%20you%20resolve%20this%20as%20we%20have%20the%20exact%20same%20issues%20%3A(%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-116619%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%2010%20profile%20AzureAD%20issue%20after%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-116619%22%20slang%3D%22en-US%22%3EHave%20you%20succeded%20to%20fix%20this%20problem%3F%20I've%20deployed%20Azure%20AD%20in%20our%20office%20at%20the%20beginning%20of%20the%20year%2C%20and%20last%20couple%20of%20months%20this%20issue%20occurs.%20It's%20localised%20on%20one%20PC%20and%20one%20specific%20user.%20Other%20users%20can%20login%20with%20their%20Azure%20AD%20credentials%20on%20that%20PC%20normally%2C%20and%20affected%20user%20can%20login%20on%20other%20PC's%20in%20our%20office%20normally.%20I%20usually%20delete%20the%20local%20profile%20of%20affected%20user%20in%20Advanced%20System%20Settings%20and%20login%20works%20again.%20Unfortunately%20problem%20will%20reoccur%20after%20next%20Windows%20update.%20This%20week%20on%20Wednesday%20I%20had%203%20users%20with%203%20PC's%20affected%20(total%206%20PC's%20and%2012%20users).%20What%20could%20cause%20this%20issue%3F%3C%2FLINGO-BODY%3E
dennis ziegler
New Contributor

Ok, long one guys.  The windows 10 forum sent me over here.

 

Fault: on a very few occasions after a windows update, an AzureAD (pc is AzureAD joined)account, *I think the one that was logged in at the start of the update process*, after login will come up to a black screen with a mouse pointer, however the GUI does not respond to clicks.
Ctrl-Alt-Del will bring up the security screen fine, can open task manager and log out OK and the login screen shows up. With the problem account, after a bit of button pressing I can hit the Win key to pull up the start menu (which appears to work fine), and peek preview will allow me to see the wallpaper, any programs i start,  and desktop icons fine, but once i try to select any active window, or the desktop the screen goes back to black with pointer.  This only happens on the one specific account and any other logins are unaffected (both previously logged in accounts, and first time log ons).

 

I can recreate the situation on a windows 10 AzureAD joined machine (at least the several i tried): This is done manually via reg-edit removing the profile's UID in ProfileList, and the deleting the user profile directory.  The next time that account ties to log on, you get the black screen with working start and "hidden" desktop as described above.

 

Troubleshooting: So we've ruled out graphics issues, it isn't the Win+P issue that was a thing during the insider previews pre-RTM, it appears to just be localized to AzureAD profiles (non administrator) that have been on the PC before and were logged in when one of the updates were applied and the PC restarts. Again this has only happened in less than 1% of updates across your networks (4 out of about 400).

 

The only way we can find to get past it is to do a soft or hard Windows reset and start from scratch. Obviously this turns a 15-20 minute profile reset into a 3 hour ordeal involving shipping the laptop back to this office.

 

And to sum up further details than I've described above:

Multiple hardware specs (Dell, Lenovo, HP)
All fully up to date Win 10
All on AzureAD domains with PIN requirements
Other local and AzureAD accounts work fine

Can replicate issue easily

3 Replies
Have you succeded to fix this problem? I've deployed Azure AD in our office at the beginning of the year, and last couple of months this issue occurs. It's localised on one PC and one specific user. Other users can login with their Azure AD credentials on that PC normally, and affected user can login on other PC's in our office normally. I usually delete the local profile of affected user in Advanced System Settings and login works again. Unfortunately problem will reoccur after next Windows update. This week on Wednesday I had 3 users with 3 PC's affected (total 6 PC's and 12 users). What could cause this issue?

Did you resolve this as we have the exact same issues :(

I'm not the OP, but I've managed to fix this issue. Just disable Windows Hello for Business in gpedit. It's tedious though since you'll have to do it for every PC manually. I only administer 12 PC's so it's not the problem for me.

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
38 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
13 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies