Windows 11 25H2 login sometimes shows a black screen or missing taskbar
Asked by
MellowPine47
Is anyone else seeing Windows 11 systems fail to load the desktop correctly after the latest 25H2 updates? The symptoms are either a black screen after login or a desktop that appears without the taskbar. After reviewing event logs, crash data, and other diagnostics, this looks similar to a documented Explorer and XAML-related issue, even though our systems have a newer patch installed than the version that supposedly included the fix. Could the problem have returned in a later update? The suggested PowerShell workaround isn't practical in our college environment because most users are students and PowerShell is blocked for them through AppLocker.
Answers
I've run into something similar, although in my case it happens occasionally when the computer wakes from sleep. The desktop comes back without loading correctly, so it may be related to the same Explorer or taskbar problem.
Reply to this answer
A reboot usually clears it temporarily, and running SFC and DISM has helped on some machines. Unfortunately, that doesn't seem like a lasting fix when the issue keeps returning.
Reply to this answer
The likely cause may be a timing issue between AppX applications registering and Explorer starting. If Explorer loads before the component responsible for the taskbar is ready, Explorer can fail and leave the user with a black screen or no taskbar. That would also explain why the workaround targets the application-registration process.
Reply to this answer
Disabling Fast Startup has reportedly helped some people, but it may not apply here if the computers reach the normal lock and login screens first and the failure only occurs after authentication.
MellowPine47: Right, our systems reach the login screen normally. The failure happens during or immediately after the user signs in, so Fast Startup doesn't seem like the main trigger for us.
Reply to this answer
Add your answer
Answers are reviewed before publication.
MellowPine47: That matches what we're seeing. Rebooting gets users working again, but our student profiles aren't permanent, so the problem eventually returns.