Windows 10: Windows 10 commonly boots to a black screen with no cursor?

Yeah, just registered with Ten Forums and all that good stuff, and so here's my first of possibly many issues I shall bring to you. xD I upgraded my preview build of Windows 10 (10130) to the pro final version because the preview wasn't able to find additional builds and kept crapping out on standard updates. All went smoothly, but the first thing I noticed is that the next time I booted cold, Windows 10 would get past the "starting windows" screen and play the startup sound. However, the logon interface never appeared, or the cursor. All that was displayed was a solid black screen. I hard reset by holding down the power button and tried it again, which gave me the same thing. Again, hard reset. This still commonly happens, along with my CMOS date/time settings apparently being wiped after such reset. Sometimes the cursor appears, but mostly it doesn't. Usually after trying enough times it'll pull through or by starting it after selecting a recovery option from F8. "Enable low resolution video" I know worked before, but it didn't give me low res display. (Not that I'm complaining) It could likely be because I installed over the preview, and in-place installations typically have issues. I'm also running a program to provide titlebars with aero styled glass transparency, and my graphics driver is up to date. Any thoughts...? *Confused

:)

 

Windows 10 boots to a black screen with no cursor

Hello,

Thank you for posting your query in Microsoft Community.

I understand the inconvenience you are facing currently. Let me help you in resolving the issue.

This issue could occur due to incompatible, outdated or corrupted device drivers. You can also check if detaching all other peripheral devices except for keyboard and mouse works out the issue. The issue (black screen) you’re
facing could be most likely related to display drivers and could be resolved by updating the drivers. Without the correct driver, the hardware or device that you want to use won't work properly. Refer to the below link and check if it helps.

Troubleshoot black screen problems

http://windows.microsoft.com/en-us/windows-10/troubleshoot-black-screen-problems

Do get back to us with the update of the issue.

 

Windows 10 boots to a black screen with no cursor

Just to say, I received a brand new HP Spectre x360 laptop today, with Windows 10.

One hour later, I'm having this issue.

Screen is dead, no cursor, no "Press ESC for BIOS options"... nothing.

But once in a while, if I press some keys, Windows 10 will play a jingle at me.

Problem is, I don't know if this is a hardware problem or Windows 10 problem.

Users are reporting problems in both cases.

Mike & his dead 1-hour-old expensive new laptop

 

Probably a dumb question, but did you upgrade from 7 or 8.1 through the insider program to build 10130?

 

I had installed the Technical Preview on a partition that was separate from Windows 7. I had started with build 9926. In that case I could boot either 7 or 10 TP in a dual boot.

 

Build 10130 expired recently, that might be the cause of your problems. Were you activated or did the insider program button say "fix me"?

 

My build was activated. Unless that's not what's you're talking about.

 

No, that is one thing I was curious about. Even if you clean installed build 9926 as long as you kept upgrading builds in a timely manner you should have been ok. But it did seen like your build had expired. at least that would have been a possibility. BTW welcome to 10 forums. When did you install the RTM build? I'm kinda stuck on the idea that your build expired, but have you tried booting in safe mode or tried any of the repair options from the "choose other options" on the dual boot screen?

 

Pretty much as soon as a new build released, (I set myself to fast ring) I waited a few days and then updated to it. But when was 10130 supposed to expire? I don't think it was then, because I wasn't getting shut down every so many hours or features reduced. I upgraded to RTM this August, 8/8 to be exact. (Thank you systeminfo CMD command) I tried the reset PC option (in order to function with my new motherboard) and it still occurred. The only others are to use an image or system restore, which if it's been going on since I went to RTM, that wouldn't help either. The preview didn't have this issue. If I went into safe mode, what would you want me to try? Or just see if it boots without a black screen?

 

Ok so everything was working until you replaced the motherboard? Your win 7 was a system builder version and so it is transferable to a new motherboard. But the win 10 had a "digital entitlement" that was tied to the original MOBO so it's borked.

 

I had kept the preview after replacing the board, (from Intel to AMD chipset) but then upgraded it to RTM. that's when I noticed the the black screen and CMOS issue. I reinstalled 7 on top of itself so I wouldn't keep getting blue screens. (Frustratingly, a mobo driver is the only one that isn't easily replaced) ^^; *Start

 

Hi if you please could help, i upgraded to windows 10 and everything was fine till yesterday, windows made lots of updates and then suddenly i had black screen saying operating system not install. I shut down the laptop and tried lits of things but nothing worked. It doesn't want to start or even to accept password for my account. Any suggestions please???

 

If you could please start your own thread it would be helpful to both you and the original thread starter. Problems that appear similar are not always caused by the same things.

 

Well that is your problem then, as soon as you changed out the mother board you will loose activation. Right now I believe the only way to join the windows insider is through a upgrade from a "Genuine" win 7 SP1 or win 8.1 and then turn on the start insider builds in windows update> advanced options. There is no way to get your win 10 partition working again. Sorry.

 

After putting in the board and realizing that 10 TP wouldn't get past a blue screen, I used the Reset PC and told it to erase it all. It worked fine after that. <_<