Execute this under windows and create a HP_TOOLS UEFI boot usb stick.Find the "HP Unified Extensible Firmware Interface (UEFI) Support Environment" for your laptop model from the HP website.This also is the most-correct BIOS recovery procedure. This is the general process I use to flash my BIOS updates on my HP laptops as none of them run Windows. So, my assumptions (may not be true) are the UEFI update for F.24 fails because of the executable missing files which are expected in the root (main) folder? The contents of CrisisFolder is moved to the main folder (root) for F.35. While, as above F.24 has only 0832.bin and 0832D.bin firmware only.
Platform.ini: ASCII text, with CRLF line terminator Insydeflash.exe: MS-DOS executable, COFF for MS-DOS, DJGPP go32 DOS extender Also wondering, if the motherboard revision will have any impact.Īnother doubt is, if suppose you have firmware F.22 on a laptop and the latest is F.35, will there a need to flash the intermediate BIOS-UEFI updates (in this case it is F.24) in succession?įormatFat.dll: PE32 executable (DLL) (GUI) Intel 80386, for MS Windows Platform.ini: ASCII text, with CRLF line terminatorsĪlso, the motherboard of the laptop is 832B with a revision number 23.40 (many have 23.25,23.27 etc motherboard revisions) and if, the installer will identify the board and flash the necessary update, as there ar 08328.bin and 0832D.bin listed. Iscflash圆4.sys: PE32+ executable (native) x86-64, for MS Windows Iscflash.sys: PE32 executable (native) Intel 80386, for MS Windows Iscflash.dll: PE32 executable (DLL) (GUI) Intel 80386, for MS Windows InsydeFlash.exe: PE32 executable (GUI) Intel 80386, for MS Windows And since the SSD behaves perfectly well attached to my desktop, I'm going to assume that the Kingston SUV400 is simply incompatible with this particular hardware/BIOS, return it (god bless Amazon Prime), and try another make of : PE32 executable (DLL) (GUI) Intel 80386, for MS WindowsįlsHookDll.dll: PE32 executable (DLL) (GUI) Intel 80386, for MS WindowsįlsHook.exe: PE32 executable (GUI) Intel 80386, for MS WindowsįWUpdLcl.exe: PE32 executable (console) Intel 80386, for MS Windows I have never encountered such an unbroken string of blue-screen startups (none repairable, automatically or manually) interspersed with occasional "no OS found" BIOS messages.
I've installed Crucial and Samsung SSDs in successive desktop systems of my own, and helped friends install several more, some with fresh Win installs and some cloned from preceding HDD installations. Not when installed from standard OR UEFI (-> GPT partitioning) Windows installation DVD or USB stick, BIOS set appropriately for each.Īnd not when cloned from a working Win 10 HDD created on the HP laptop (and yes, disconnected before booting from the cloned SSD). UEFI) enabled OR disabled in the skimpy BIOS.
Windows scrambled around adapting to the very different environment, loading drivers like mad, then ran fine.īut the SSD has never yet gotten to Win 10 ( or Win 7) login when installed in the HP laptop I want it in: the SSD worked fine with an MBR Win10 installation done on the HP laptop, then installed temporarily to replace the (MBR) boot SSD in my desktop system. (It passes Kingston's and all other drive tests when attached to other systems.) Am I missing a step, or is there something about this hardware/BIOS that just doesn't like SSDs?Ĭlick to expand.Umm, no. In frustration I got another laptop HDD and successfully installed Win 10, then cloned that to the SSD via a USB->SATA cable (don't have an internal cable for the second bay) - and when I put the SSD in as the only drive, it still won't boot, saying either that there's no OS or that it's failing SMART. (I cleared all partitions between each attempt, and have tried both "legacy mode" settings.). I've added SSDs to several desktop systems with no trouble, so I put in a new Kingston 240GB SSD - and can't get to login with either Win10 *or* Win7 installation from DVD or USB, usually BSODing after the first restart with complaints about winload.efi or wlnload.exe. It had run the OEM Win 7 fine, upgraded to Win 10 fine, reinstalled Win 10 clean from other media fine. HP Pavilion M7-1015dx, 2012 vintage, InsydeH20 BIOS (see pix) with no explicit setting for SATA mode, only the legacy mode choice for UEFI/CSM.