- The HP USB Key Utility for Windows version 1.5 allows the HP Smart Update Firmware DVD to run in Automatic Firmware Update mode with a 30 second timeout. Version:18.104.22.168 (29 Jul 2009).
- I try all method to create bootable usb drive for HP Firmware 8.30 cd under windows 10 with HP USB Key Utility but without sucess The hp USB key not work on Windows 10 even compatibility mode. Thanks for any help! HP USB Key Utility not work on Windows 10. I work for HPE.
- HP USB Key Utility for Windows is a Windows application that will allow you to copy the ISO and CD contents to a USB flash disk using HP SmartStart CD, HP Firmware Maintenance CD, HP Smart Update Firmware DVD, HP Intelligent Provisioning, HP Service Pack for ProLiant. Users may then run the ISO and CD applications from a USB key.
- USB booting possible using UEFI on my laptop? HP 8460p with latest BIOS/firmware. Ask Question. Windows 8.1 installation from USB after deleting Windows Boot Manager in BIOS/UEFI. Booting a GPT USB key on older BIOS laptop. Booting via network does not work with UEFI mode.
HP SPP USB Install Guide January 12, 2016 January 12, 2016 Views: 35723 Articles Firmware, HP, Installer, USB Matthew Marable Previously we have written numerous articles in which we showed you how to make bootable USB installation media for Pfsense using either Rufus or the USB Image Tool. Applying Offline Firmware without HP SUM or Firmware DVD? I've used the HP USB key thing to make a smaller bootable image and then put just the scexe update file needed on there. Copy in USB>: hp swpackages the files needed to update it: - CP019633.scexe SAS Backplane 2.18. HP ProLiant Servers - Preparing a Bootable USB Key with the Firmware Maintenance DVD. Start HP USB Key Utility for Windows from the All Programs group. On the first screen, click Next. Accept the license agreement and click Next. Select Create a bootable USB key from CD/DVD. This option will prepare a bootable USB key from a Firmware.
If I enable UEFI on my laptop, there's no option to boot using USB (using the boot order to determine this).
On BIOS boot, many options are available like SDcard, upgrade bay, network and etc.
On UEFI, I can only see upgrade bay, network and 'OS Manager' (whatever this means).
As this is a laptop from 2011 with experimental UEFI, it boots Windows by default if it's installed and
EFI/Microsoft/Boot/bootmgfw.efi is present. This is because the path to this file is hardcoded in the UEFI.
Some HP models appear to have an option to edit this path, called 'Customized Boot', according to the Arch Wiki. But this is not the case for the Elitebook 8460p, even with the latest firmware update.
There are two ways to 'forcefully' boot other systems in UEFI mode (either from HDD or USB) when MS Windows is installed:
- One is to press F9 to load the boot menu, and then select the option 'Boot from EFI File'. From there you can navigate to the proper file ending in
.efiand load it.
- The other is to replace Windows'
bootmgfw.efiwith your own EFISTUB (always a good idea to create a backup first) - for instance,
grubx64.efi. This allows for dual booting in UEFI mode on this laptop. Remember you may need to repeat this if you update GRUB or if it's reverted by a Windows update.
BIOS-based computers booted 'whole disks' -- or more precisely, the BIOS could load the first sector (aka the Master Boot Record, or MBR) of a disk to run boot loader code stored there. This made for some relatively simple boot management at the firmware level -- you set a default boot device in the firmware setup utility and you could usually override that on a boot-by-boot basis by using a BIOS boot manager. The details of how to do both of these things varied from one computer to another.
With EFI/UEFI, it's more complex. EFI boots from files, most of which are stored on an EFI System Partition (ESP), which is a partition with a specific type code that uses a FAT filesystem. A single ESP can theoretically hold thousands of boot loaders, although just one or two (perhaps with some support programs) is more typical. The computer knows which boot loader to run because that information is stored in NVRAM in a prioritized boot list. This boot list can sometimes be manipulated in the firmware setup utility, similar to how you'd set the boot disk priority in BIOS; and you can usually override it on a boot-by-boot basis with the firmware's built-in boot manager. As with BIOS, the details of how to set the default or enter the boot manager vary from one computer to another; but it's usually done with a keypress at boot time -- typically Esc, Enter, or a function key.
Removable media pose a special challenge to EFI-style booting. Because pointers to boot loaders are stored in NVRAM, you can't put a boot loader on a removable disk using an arbitrary filename and expect it to be booted. Thus, a standard fallback filename is used for removable media. For AMD64/x86-64/x64 systems, this filename is
EFI/BOOT/bootx64.efi. Many EFIs don't generate entries for removable media unless and until they're inserted in the computer. Thus, these entries may not appear in the default boot order list you see in the firmware, just in the boot manager menu if and when you enter it. Sketchpad 4.07. My hunch is that this is your problem; it sounds like you're trying to edit the default boot order, when instead you should be entering the boot manager menu to select the bootable medium.
Also, if an external medium lacks a fallback boot loader, that medium might not show up as a bootable device, even in the boot manager menu. Some tools for creating bootable USB drives were written before EFIs became common, and so may omit the EFI boot loader files. Some source files (
.iso files or whatnot) may lack the EFI boot loader files, too, particularly for OSes that don't support EFI-mode booting.
Finally, you might be running into problems because of security settings. If your computer is configured to require Secure Boot, and if the boot medium doesn't support this, then you might not see a relevant boot entry, or that boot entry might not work. A few EFIs (Acers, I hear, are like this) have particularly obnoxious Secure Boot menus that require jumping through extra hoops even to boot media with properly-signed boot loader files.Rod Smith
Hp Usb Fw Boot Files For WindowsRod Smith
Hp Boot From Usb Drive
Based on what I've heard UEFI is effectively a more advanced version/replacement of BIOS. The difficulty is that in general a smaller subset of technology is bootable via UEFI then when compared with BIOS (mainly in the use of 'Secure Boot' technology. I've heard cynical stories about UEFI being used as a means of locking out alternative Operating Systems such as Linux and BSD for this very reason).
Based on what I've been reading online your machine doesn't seem to be much different from others with UEFI. Basically, any device which you want to alternatively boot off of needs to be compliant with the way it works. Else, there needs to be a chain loader of some sort which loads what you want once it hits the 'OS Manager'. Obviously, if you can't achieve the previous it's quite simply a no go and reversion to standard BIOS operation may be your only choice
Of course, this rules out the possibility of hacked UEFI which I've heard stories about. Some people have figured out a way to overcome some of the limitations that are imposed the OEM UEFI. This may be a possibility but I'm doubtful.
Html2pdf download pdf php tutorial. Obviously, it feels like you want to try alternative Operating Systems. Another option is to use a Virtualisation program such as VMWare or VirtualBox. This allows you to boot what you want though you'll be limited to what that particular environment provides you with