Forum Discussion
Azure AD Endpoint Manager User Profile Corruption: Black Screen Flashing Taskbar Explorer Crash Loop
- Jul 24, 2023
Daniel,
We just discovered the same thing and rolled out a fix for it in our environment. For users with an email address in on-prem AD, Azure AD Connect Sync was creating the accounts in Azure online with the pre-Windows 2000 NetBIOS domain name which matches the pre-Windows 2000 NetBIOS user logon name. However, for those without an email, it was creating the account in Azure with the subdomain of the domain FQDN instead of the pre-Windows 2000 name as specified on the account or in Domains and Trusts. Azure AD Cloud Sync was trying to update all accounts to the subdomain and completely ignoring the pre-Windows 2000 names entirely.
As far as experiencing the taskbar issue, once it occurred for one account on the machine, it would then impact all accounts on the machine both pre-existing and new sign-ins. However, accounts that did not have an AD mail attribute would not experience the issue. We found the same SubPkgs key and those that were in the NetBIOS subkeys would have the taskbar, permission, and general SID mismatch errors but those that were in the subdomain subkey would not.
We shut down our Azure AD Connect and are now relying entirely on Cloud Sync. Then, to fix the machines without a reimage, we performed a full Cloud Sync and then ran the following PowerShell script on Azure AD joined machines to clean up the broken accounts. This allowed users to sign in fresh with the subdomain instead of NetBIOS prefix and the issue has not reoccurred, but it's only been about a week.
$CurrentUserSID = (C:\Windows\System32\whoami.exe /User /Fo CSV | ConvertFrom-Csv).SID $CachedAccounts = Get-CimInstance -Classname win32_userprofile | where-object { (!$_.Special) -And ($_.SID -like 'S-1-12-1-*') -And ($_.SID -NotLike $CurrentUserSID) } foreach ($Account in $CachedAccounts) { $SIDtoUser = $null $SID = New-Object System.Security.Principal.SecurityIdentifier($Account.SID) try { $SIDtoUser = $SID.Translate([System.Security.Principal.NTAccount]) Write-Host "Removing $SIDtoUser from list of cached accounts." if ($SIDtoUser -ne $null) { $CachedAccounts = @($CachedAccounts | Where-Object SID -ne $SID) } } catch { Write-Host "Unable to translate SID ($SID) to user." } } if ($CachedAccounts.Count -gt 0) { Write-Host 'Accounts to be removed:' $CachedAccounts | Select LocalPath,SID | ft $Confirmation = Read-Host "Do you want to remove those accounts? (Yes or No)" if ($Confirmation.ToLower() -like "y*") { Write-Host "Removing accounts..." $CachedAccounts | Remove-CimInstance -Verbose } else { Write-Host 'Accounts not removed.' } } else { Write-Host 'No accounts to remove.' }
Hopefully, this script and info helps someone else.
Rexford
MS is still troubleshooting a problematic station we have off to the side. Thankfully after reimaging the ~14 other devices, the issue hasn't returned to those or anywehre else in the enterprise, but we still don't know what/why it occurred.
- Edmundo PenaOct 14, 2022Brass ContributorThe issue is still happening. FML.
- BishopstonITDec 12, 2022Brass Contributor
happening here too. just installed Azure AD Cloud Sync and hybrid users outside of domain all have incorrect password, then flashing screens when they log on......??!! no news??!!
- Edmundo PenaDec 12, 2022Brass Contributor
Microsoft has no idea what’s going on and are completely useless. It’s been a pretty eye opening experience the state of Microsoft Professional and Premier support is a complete joke.
- jmerwinSep 10, 2022Copper ContributorThe other thing we noticed is this.
We have a NPS server to allow users to sign into our WiFi with their windows creds.
Now when a user signs into their onprem device the domain name is dlsd0\username
When a AAD device goes to connect to the SSID and the user says use windows credentials the domain gets autopopulated as dlsd\username- SkyisblueSep 15, 2022Copper Contributor
jmerwin unfortunately in our Organization/tenant the issue appeared two months ago with only administrative accounts when upon expiring password had to renew their credentials.
After this if we use the administrative accounts on any of endpoint devices it creates this taskbar flickering issue.
Until recently other administrative accounts also got affected even without changing the password. We have a hybrid setup.
- Colin KnessSep 15, 2022Copper Contributor
I encourage you to tweet out on this crazy Microsoft experience and message Brad on the Microsoft Linked in App directly how warm and fuzzy we all feel about @Microsoft. Tell all your tech friends. We are level three getting no closer than day 1 , level 1 . For a 24x7 case we should all be worried if there is a BIGGER problem in AZZURE .. the world as we know it will slow down a bit ! Peace out .. love Microsoft hate who they have become !
- Edmundo PenaSep 10, 2022Brass Contributor
sjohn777 it will happen again when you add new endpoints to the azure ad domain/tenant. I believe there is something wrong with azure endpoint provisioning.
- jmerwinSep 09, 2022Copper Contributor
It's seriously the worst I've ever experienced. I don't even know what to try anymore.