📎 AI Summary:
The thread discusses a Lenovo Y50-70 laptop that boots normally via the Lenovo recovery key but shows a black screen with a blinking cursor when powered on directly. The main question is how to configure the system to boot correctly with the power button instead of using recovery options, with suggestions including checking BIOS settings and boot priorities. Contributors recommend verifying BIOS configuration, default boot device, and attempting to boot into safe mode to diagnose potential driver or startup issues.

Jragon

New Member
Joined
Jun 26, 2015
Messages
1
Thread Author #1
My computer is a Lenovo Y50-70 and if I press the power button to start up I get a black screen with a blinking underline character in the upper left hand corner, I don't seem to be able to type or do anything from this screen. If I start up using the Lenovo one key recovery key I can open up a boot menu and select windows bootloader on what I believe is the 8GB cache on my hard drive and boot fine. I would very much like to be able to just boot using the power button for obvious reasons, any help is appreciated.

Edit : added a picture to show the boot options on imgur it's /zs50ruR (can't post links yet) .
The SATA HDD is what the computer boots off of by default and is what is giving me the black screen.
Windows Boot Manager is what actually works for booting the computer for me.
 

Last edited:
Solution
Check the BIOS and confirm your default boot device.
Make sure you haven't changed any of the default boot behavior. UEFI / Secure to Legacy, or drive controller settings, AHCI, RAID, Native IDE.... etc.

Trouble

Noob Whisperer
Joined
Nov 30, 2009
Messages
13,723
Check the BIOS and confirm your default boot device.
Make sure you haven't changed any of the default boot behavior. UEFI / Secure to Legacy, or drive controller settings, AHCI, RAID, Native IDE.... etc.
 

Solution

Neemobeer

Windows Forum Team
Staff member
Joined
Jul 4, 2015
Messages
8,995
After powering on the computer, press F8 until you get a menu. Try booting into safe mode. If that works I would try and determine if you had a recent driver update.