explorer crash
2 TopicsWindows Boots to Black screen, NO Desktop, taskbar, start ,menu
Starting yesterday after a cumulative update installed in windows update, I started having an issue where I couldn't access zip files because the instant I would click or right click on one it would crash explorer and cause it to restart. I could open them by starting 7zip or winrar manually but oddly enough if I tried opening them as admin to extract to a protected directory it would again crash explorer and cause it to restart Yesterday I attempted fixing it with sfc /scannow which did find and fix some errors but did nothing to fix the problem I was chasing, so I gave up and put it off to the next day. The update is the only notable change I could think of to attribute the problem to so today I tried to use system restore to roll back the changes and that failed, twice, and on the second time when windows rebooted, it went to a black screen, with the dialog box open saying that the restore had failed, but nothing else ever started. Thinking it had perhaps started in safe mode, I used ctrl/alt/delete to log out and restarted from there, only to return to the same black screen. So now using ctrl/alt/delete to gain access to the taskmanager is the only way I'm able to get an instance of explorer to open so I can open a browser etc. and is the only way I'm able to use the computer at all now. I tried once more to run the sfc /scannow command but it found nothing. I don't know how to start the settings app manually, if it's even able to start at all, to be able to know what build I'm on or what the update number was that started this, so I'm afraid I'm not really able to provide much to go on in that regard. All I know for sure is i must get this rig back into some kind of usable form in order to comb through it and pull out all the things that must be backed up if a OS reinstall is my only way forward, so any help to get my desktop environment back would be a HUGE help and greatly appreciated.174Views0likes2CommentsAzure AD Endpoint Manager User Profile Corruption: Black Screen Flashing Taskbar Explorer Crash Loop
We are in the midst of a Azure/Endpoint Manager (Intune) Migration. 300+ Endpoints and are running into deployment nightmare: We are experiencing a very odd, completely random issue when a previously Synced Hybrid Azure AD User logs into their endpoint (which was previously working without issue for weeks/months) and then suddenly fails to load. This issue only seems to occur when NEW endpoints are added to the Azure AD tenant/domain. We know the issue is about to happen when you receive a call from an end-user stating their previously working credentials are "no longer working". When the the user attempts to login via "other user"; The login will proceed, and the user will login to a black desktop/screen and flashing taskbar. Windows Task Manager is not responsive; Safe-mode options will not produce a better end result. Upon reviewing the logs you will see "explorer.exe" crash loop prompting urtcbase.dll. Azure AD homed user accounts and local user accounts are able to login without issue into the endpoint. The issue is only specific to Hybrid Azure AD User Profiles (on-premise cached/home' d accounts). I'm thinking it has to do with a conflict of the on-premise SAM Account name. I'm not sure why adding new endpoints to the tenant causes the issue. This particular issue is happening across all different makes, models, and Window Image variations. The issue is specific to only Azure AD Profiles that attempt to login to the endpoint. Precursors: Incorrect password prompt. Requires uses to select "other user" After selecting other user, user profile experiences delayed "Welcome" Black screen appears with flashing taskbar, rending the profile useless If we attempt a Wipe/Restore the issue will randomly reoccur on another workstation. I believe the issue is specific in the way Windows try to load/create the profile for Azure AD users. I'm not sure if AutoPilot is attempting to configure these endpoints in Hybrid mode. However we've noticed discrepancies in the naming convention of some profiles and domains. For example: AzureAD\FirstLastName shortdomain\FLast I believe the User Profile Service is somehow bugged and causing a mismatch between the registry's SID for the user profile. Has anyone else experienced this issue? We are desperate for answers; this is worse than any virus as its random intermittent nature will return after a fresh system restore. I've received a call from another organization stating they are seeing the same issue occur throughout their deployment. I believe this is now a wide-spread issue. We have a ticket opened with the Microsoft on this. Windows Performance Team is reaching out to Azure Team.Solved27KViews0likes52Comments