Windows 10 2004 blank black screen with mouse after login.

Question

Hello,

I have some computers that updated to 2004 and now one that updated 20H2 that are experiencing a black screen with mouse after login. I can't bring up task manager with CTRL-ALT-DEL. if there computer is onsite and connected to the domain network it logs in fine. I disconnect it from the network it will not login. We are currently doing a network login to connect to the company VPN then login to the computer so the domain is available. I do not see this behavior on update 1909 or below.

Any help trouble shooting this would be helpful.

Thanks

Answer 1

I've seen this question all over the place, and a multitude of answers which so far don't fix this issue for me. Although the scenario I'm having is slightly different.

I've set up a new laptop for a domain user, installed applicable drivers, patches, windows updates, etc. and when the user connected to the network either via their docking station or corporate wi-fi everything works as advertised.

However, if the user signs in to their account when not connected to the docking station, to the corporate wi-fi, he gets the black screen with the white cursor after logging in.

To further complicate this, if the user leaves the laptop running for 30 minutes to an hour it will eventually come up with the desktop. However, even then when the user moves the cursor over the task bar, the cursor changes to the blue spinning "busy" cursor and the user has wait up to an other 30 minutes to actually be able to use the laptop.

Now, two ways I get around this:

1. I can sign in with a different domain user or a local user and it starts just fine.
2. Unmap all map drives "net use * /del" before the user disconnects from the network and shuts down / restarts the laptop off the network.

Things I've tried:

1. System Restore remove last updates installed.
2. Delete the User Profile and recreate it.
3. Reset the Windows Installation and Add the user first prior to any updates, patches, etc.

And I am beginning to encounter this issue with other users and devices that remote to the network.

This problem only seemed to start after the 2004 update.

Any other suggestions?

Answer 2

Hi,
Thanks for sharing here!
If users need to logon disconnected from the domain, please confirm the following local and domain policy :
Interactive logon: Number of previous logons to cache
under Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options
Make sure that the value is not set to O.

Best Regards,

Answer 3

@Fan Fan

the Number of previous logons to cache setting is set to 3

Answer 4

Hi,

Was wondering if this issue has been resolved? We are currently experiencing the same exact issue with both 2004 and 20h2 updates.

We found that recreating the user profile fixes the issue. This issue has come up for all 5 of the computers that we tested the upgrades to 2004 and 20h2 so it seems like something with the update is corrupting the domain user profiles. Not an ideal solution when you have hundreds of PCs that could potentially install the upgrade. Doesn't seem to affect local user profiles.

Interested to see if anyone else has found better solution.

Thanks
Dave

Answer 5

We are having the exact same issue. @Matt Wolfe I sure hope you found the issue. I went through and disabled every GPO and the issue persists.

One of the interesting idiosyncrasies is that the built-in domain Administrator has not has this behavior happen. I don't know if that is because of our GPO configurations though - but it was an interesting exception. Created users with Domain Admin rights do still have this problem.