Windows 10: Black screen with cursor after install and first login

Just upgraded my bro-in-law's HP Pavilion desktop from 8.1 to 10. It's got an AMD processor, but I don't know which one exactly...probably one of the lower level ones. It was a refurb from Fry's, purchased a couple of months ago. It was running 8.1 just fine.

The upgrade process to win 10 went smoothly, got the pretty picture and the standard login screen, entered login info and got a series of messages welcoming me to win 10 and that the system was being configured. Then a message that said the install was "taking a bit longer than usual" and to wait a while longer. Stayed on this for about 10 minutes, and then screen went black with a cursor. And it's been that way for the past two hours. Just leaving it for now hoping it will magically come up with the win 10 desktop, but so far no love.

Any ideas?

:)

 

[ASUS A550C] Installed Nvidia drivers and got either black screen or screen glitchy

Still the same. But with black screen with no cursor after login

 

Black screen with only mouse cursor at startup after windows 10 installation.

Hi Larsen,

Did your PC ever reach the Windows login screen? Did it go black before or after login?

Regards,

Jack

 

OK, turns out this was a non-issue for me. I left the computer on overnight, and in the morning it still had the black screen with cursor. I reasoned that since I'd already signed in before the screen went black, windows was probably running but for some reason I couldn't see it. Did a control-alt-delete and the task manager appeared on the screen! Used the power button in the lower right to shut down completely. Then started it up again, got the sign-in screen, signed in and viola, got the win 10 desktop. Have no idea why this happened, but a simple restart fixed it.

 

The first two-three times you run Windows 10, Windows Update is probably downloading and installing updates. If an update stucks for some reason, Windows is waiting at the black screen. Maybe that was your case. When you restarted, Windows attempted to reinstall that update which then succeeded. I don't have another explanation.