Cannot Boot into Windows - File:\windows\system32\winload.efi with Error Code 0xc0000225.

[tamwilliams]

Hello,

My daughter's notebook will not load the operating system. When it starts, it enters "Preparing Automatic Repair" and then moves to the blue screen Recovery. It states File:\windows\system32\winload.efi with Error Code 0xc0000225. The computer is loaded with Windows 8 but I cannot remember if we upgraded to 10.

I cannot enter startup using F8. When I hit "esc" for UEFI firmware settings, it will load to the Startup menu, but the only option that will work is F1 System Information.  These other options do not do anything at all:  F2 System Diagnostics, F9 Boot Device Options, F10 BIOS Setu and F11 System Recovery. 

I have tried loading into BIOS to no avail. I have also tried recovering the BIOS (Win Key+B) but also doesnt work after the recovery process. 

Last thing I tried was connecting a new hard drive, but then I received the Boot Disk error since the computer won't recognize the USB or DVD drive.  

If there are any other options I need to try, please let me know. 

[CherylG]

@tamwilliams

Sounds like the hard drive is for sure dead. A bad drive can prevent the F keys from working. When you put a new drive in it does F9 still not work?

You may need to disable Secure boot and enable Legacy boot in BIOS. After changing it you will reboot and it will ask you to type in the code shown on your screen to confirm. Just type it- no box for it but it takes. Then try again to use Esc. F9 to boot from USB or CD/DVD.

Are you using HP Recovery Media or a plain Windows disc? It would help if you remembered if you upgraded to Windows 10 because Microsoft makes the process of reinstalling simple.

[tamwilliams]

I hooked up a new hard drive and still cannot access BIOS. The new error I saw after connecting the new hard drive was a Boot Disk Not found error. When I inserted a new Windows 10 USB stick, the system still didnt boot from USB. It loaded from back up with the same error - Boot Disk Not Found.

How can I disable Secure boot if I cannot enter BIOS?

Thanks!

Tam

[CherylG]

@tamwilliams

 I was hoping the f keys worked after installing a new drive and you could enter BIOS. So I assume even F9 key isn't working to select USB for boot device?

[tamwilliams]

I attached the new hard drive. The screen says Boot Device Not Found - Please install Operating system on your hard disk. Hard Disk (3F0), F2 System Diagnostics.

When I press F2, nothing happens

When I press F9, nothing happens

I added the new Windows 10 USB and the computer does not recognize it is in.  

Tried Win key+B again, caps lock key blinks twice but the BIOS recovery didn't pop up.

[savvy2]

here are some facts ,  on this failure ( and UEFI horrors)

the PC will in fact boot to a USB device, even a LINUX CD or DVD ro Linux live boot Stick. USB.

you can do that with the HDD removed, try it with a new PC, see, it works, like that now for  over 30 years.

But UEFI is blocking that,  as ALL DO, so turn it off.

what will be dead is F11 key only,  F11 uses the HP recovery partition, now gone.  so is dead. W10 did that, I BET.

the show stopper , UEFI,  (new BIOS, call it BIOS-pain2)

since the PC was new, it prompted you to "hit ESC to enter setup"

for all those long years.  and still does,  if the RTC coin cell is not dead..

this always worked for all those years,  if you had tried it every year owned.

the older PCs had F10 for ESC.  but it tells you what to do endlessly every boot.

so do that, and turn off safeboot.

turn on usb legacy mode.

the change the boot order to USB then CD then HDD.

now boot the PC to USB stick W10 loaded on stick and hammer the F9 key, F9 does not need a working HDD. ever.

F9 key is 100% resident BIOS code running from ROM. no HDD needed.

the boot to USB stick , install a new HDD if its bad, and load W10;

UEFI blocks (OOBE) all alien boots.  by DESIGN.

Booting to CD or DVD or sticks are evil, in there minds eye.

so turn off the block, called safe boot.

I see you changed your BIOS. 

I bet you bricked the PC doing that, never play with BIOS code (updates) or risk bricking the PC.

now only HP can fix that, not me. im not HP

:  F2 System Diagnostics

that key must work,  or you bricked it or the CMOS RTC battery coin cell is dead. did you test it first?

installing a new , hdd, will never self recover, ever. after all the old HDD and the recovery partitions are now gone.

only fresh media installs work on new HDD,

next time ask for help before flashing BIOS.

and win..... 

best is to never flash BIOS unless HP told you to.. for just causes.

read the vast posts here and 100s of other forums with bricked PCs just for that.... endlesss..... vast.......

[savvy2]

lets say it was a  bad HDD ,  worst case.

1. get HP to repair your bricked UEFI BIOS.... (next time please leave BIOS code alone and not add 2nd problem)
2. get w10 on a USB stick from MS.,.. (if you upgraded to w10 the w8 license was commuted to w10 forever)
3. Hit ESC and go in to BIOS and turn off safe boot and turn on  legacy USB.
4. change boot order to USB,CD and HDD, in that order. util PC runs perfect again.
5. boot PC and if the USB does not boot, power on again and hammer F9, and pick USB boot stick.
6. if the USB fails to show up in F9 , then your USB stick was not created properly with MS application, to do that.
7. OK USB boots, and w10 loads.

if not sure, test the USB W10 install stick on the PC you made it from, using the MS  applications

make sure it can boot, on all PCs tested, it must boot to install, then hit abort. 

you can test the USB  stick easy, it's not hard , just turn off UEFI safe boot.

test the stick first on a working PC adds value to easy diagnosis above.

Also read the HP pages on how to fresh load W10,,,, read the words there, and how the New UEFI works.

in the old days 2010 back we only needed to change boot order

for fun, they made this way harder.(sarc)

[tamwilliams2009]

I never messed with the BIOS so not sure how this helps me.