-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Notebooks
- Notebook Hardware and Upgrade Questions
- BIOS update issue

Create an account on the HP Community to personalize your profile and ask a question
03-09-2019 02:50 AM
Dear All,
I have an HP ENVY x360 - 15-bp102n latop. I check in my laptop has a old BIOS ver 38. I download from HP webpage two newer version (rev 42, rev 44) I tried to install booth without sussecc. After the .exe installation, nothing happened. Not start the BIOS update softver.
Do anyone has this problem? How can I solve it?
Thank you for your support!
03-09-2019 03:05 AM
03-09-2019 07:04 AM
Hi
Make, Model and OS please.
SKU: if possible by this method
WinKey + R and type
msinfo32
Read Line 9
System SKU: N6K07EA#ABU
Please do not post Serial Numbers.
The model number you give is incomplete, however...
sp93263 is a later version.
HP ENVY x360 - 15-bp102nb You are downloading the following file:
| HP Notebook System BIOS Update (Intel Processors) | 36.7 MB | sp93263.exe |
03-15-2019 02:54 AM
Hi
https://support.hp.com/us-en/product/hp-envy-15-bp100-x360-convertible-pc/16851044/model/19768275

03-15-2019 05:46 AM
Hi
Hopefully one of these documents will cover (and solve) your problem...
https://support.hp.com/ca-en/document/c00042629
https://support.hp.com/us-en/document/c02693833
My final suggestion is to make a Flash Drive version if you can.
Step 2: Create a USB recovery drive
03-15-2019 12:31 PM
Hi
I think the software package is possibly broken, however I did download sp93263.exe.
AND using 7zip expanded/extracted the file list, therein.....
s:\biosdl>dir
15/03/2019 18:20 <DIR> sp93263 (extracted from the .exe file)
15/03/2019 17:56 38,391,480 sp93263.exe
s:\biosdl\sp93263>dir
Directory of s:\biosdl\sp93263
15/03/2019 18:20 <DIR> InsydeFlash
16/11/2018 08:22 19,230,261 InsydeFlash.exe
15/03/2019 18:18 <DIR> Lakers_F44
16/11/2018 08:22 19,230,261 Lakers_F44.exe
Directory of s:\biosdl\sp93263\InsydeFlash
15/11/2018 10:54 9,177,600 08313F44.bin
15/11/2018 10:45 9,177,600 083C83CF44.bin
15/11/2018 10:51 9,177,600 083C8C3F44.bin
01/11/2018 15:07 <DIR> CrisisFolder
07/07/2017 06:51 249,856 CrisisKeyDLL.dll
01/11/2018 15:07 <DIR> DEVFW
25/03/2013 11:39 231,936 FlsHook.exe
25/03/2013 11:39 195,584 FlsHookDll.dll
26/04/2017 03:29 215,040 FormatFat.dll
04/11/2010 10:36 944,664 FWUpdLcl.exe
03/11/2017 06:35 8,868 h2offt.cat
03/11/2017 06:35 3,964 H2OFFT.inf
03/11/2017 06:35 62,904 H2OFFT32.sys
03/11/2017 06:35 76,728 H2OFFT64.sys
15/03/2018 10:24 924,160 InsydeFlash.exe
15/03/2018 10:23 1,820,160 iscflash.dll
15/11/2018 16:57 35,705 platform.ini
15/11/2018 17:02 35,666 platform8313.ini
15/11/2018 17:02 35,672 platform83C8.ini
15/11/2018 17:02 35,672 platform8C38.ini
24/08/2017 10:13 246,272 WDFInst.exe
Directory of s:\biosdl\sp93263\Lakers_F44
15/11/2018 10:54 9,177,600 08313F44.bin
15/11/2018 10:45 9,177,600 083C83CF44.bin
15/11/2018 10:51 9,177,600 083C8C3F44.bin
01/11/2018 15:07 <DIR> CrisisFolder
07/07/2017 06:51 249,856 CrisisKeyDLL.dll
01/11/2018 15:07 <DIR> DEVFW
25/03/2013 11:39 231,936 FlsHook.exe
25/03/2013 11:39 195,584 FlsHookDll.dll
26/04/2017 03:29 215,040 FormatFat.dll
04/11/2010 10:36 944,664 FWUpdLcl.exe
03/11/2017 06:35 8,868 h2offt.cat
03/11/2017 06:35 3,964 H2OFFT.inf
03/11/2017 06:35 62,904 H2OFFT32.sys
03/11/2017 06:35 76,728 H2OFFT64.sys
15/03/2018 10:24 924,160 InsydeFlash.exe
15/03/2018 10:23 1,820,160 iscflash.dll
15/11/2018 16:57 35,705 platform.ini
15/11/2018 17:02 35,666 platform8313.ini
15/11/2018 17:02 35,672 platform83C8.ini
15/11/2018 17:02 35,672 platform8C38.ini
24/08/2017 10:13 246,272 WDFInst.exe
SO IT IS ACTUALLY ALL THERE.
But how you get it to run is beyond me.
