How to fix the Black Screen of Death

A domain-joined machine that logs in to a completely black screen (no desktop, no Start menu, no error message) — commonly called the “Black Screen of Death” — is usually a sign of a corrupted machine trust relationship or a broken user profile shell, rather than a hardware or graphics driver fault.

Fix

You’ll need the credentials for a local administrator account on the machine before starting.

1. Boot the machine into Safe Mode.
2. Log in with the local administrator account.
3. Open Computer Management and re-enable the built-in Administrator account if it’s currently disabled.
4. Reset the local Administrator account’s password.
5. Reboot out of Safe Mode back into normal Windows, to the login screen.
6. Log in as the local Administrator account you just reset.
7. Remove the machine from the corporate domain (make it a workgroup machine temporarily).
8. Reboot again and log back in as the local Administrator account.
9. Open an elevated Command Prompt and run:

   gpupdate /force /boot

10. Reboot again, log in as local Administrator once more, then rejoin the machine to the domain.
11. Reboot a final time and log in using a normal Active Directory account.

The machine should now log in to the domain normally without the black screen recurring. This works because removing and rejoining the domain forces a fresh machine trust relationship and profile setup, clearing out whatever corruption was causing the shell to fail to load.

A Less Disruptive Alternative, If This Is a Trust Relationship Issue

The full domain leave-and-rejoin above works, but if the underlying cause is specifically a broken machine trust relationship (rather than a corrupted profile or shell), the PowerShell cmdlet Reset-ComputerMachinePassword (or the older netdom resetpwd) can fix it with far less disruption — it simply resyncs the computer account password with Active Directory from an elevated local admin session, without ever leaving the domain. Run it from Safe Mode with Networking if the machine can’t get far enough to reach a normal desktop. One important caveat: this only addresses trust-relationship/secure-channel errors specifically — if the real cause is a corrupted user profile or a broken shell (explorer.exe) rather than a trust issue, it won’t help, and the full steps above (or a profile-repair approach) are still what’s needed.

Resources

• guide