Is the .exe file run?

Never. It is only read: the server never runs an uploaded file.

Which formats are accepted?

Updates as published: executables, archives (.zip, .cab, .7z…), disk images (.iso, .img…), capsules and raw images (.cap, .fd, .bin…); the exact list is shown at upload. RAR archives are not opened, and an unrecognised format is flagged.

Can I program the extracted image straight onto a chip?

Not for a given machine: the manufacturer's image carries no machine identity (serial, MAC address, Windows key), and it is not always a full chip image, as each file's kind says. For a machine, use the rebuild.

How long are the files kept?

24 h after upload: the package, the extracted files and their list are then erased.

What does the inventory say?

For each file, its kind: full or truncated chip image, BIOS region, ME, EC, tool, text. The ZIP is named after the brand, model and version, when they are recognised.

What about encrypted HP images?

Some HP consumer images are encrypted: they are flagged as such.

A package with hundreds of files: how do I find my way?

A checkbox shows only the firmware (chip images, BIOS, ME, EC…), and a field searches for a name in the open folder and its subfolders.

Operation

Extract a manufacturer BIOS package

Upload the update file downloaded from the manufacturer: it is unpacked, every file is identified, and you take what you need.

Create an account See pricing

Every operation is free during launch.

When to extract a manufacturer package

See what an update contains before flashing
Prepare a rebuild
Take the EC or ME image out of a package
Check the shipped version

Before flashing, to prepare a rebuild, or to take out one specific image: each file's kind is stated, and nothing is executed.

At a glance

What it does: Opens the update downloaded from the manufacturer and identifies every file; the BIOS, ME and EC images are located.
Which machines: Updates as manufacturers publish them: executables, archives, disk images, capsules.
What you get: Each file, or a whole folder as a ZIP.
Good to know: The package is read, never executed. RAR archives are not opened.

Supported packages

Updates as manufacturers publish them: executables (.exe), archives (.zip, .cab, .7z, .tar, .gz), disk images (.iso, .img, .dmg, .pkg), capsules and raw images (.cap, .fd, .bin, .rom, .wph, .fl1, .fl2, .upd).
HP (SoftPaq), Dell, Lenovo, Acer, MSI, Fujitsu, Panasonic, Toshiba, VAIO, Apple and Portwell packages, AMI, Insyde, Award and Phoenix images, UEFI capsules.
Inno Setup and NSIS installers, and nested archives, opened down to the firmware they hold.
Each file's kind: full or truncated chip image, BIOS region, ME firmware, GbE, EC firmware, pre-UEFI BIOS, flashing tool, text.
The brand, model and version when they are read: they give the ZIP archive its name.
The manufacturer's signature, shown when it is valid.
No dump is needed: the package alone is enough.

What package extraction does not do

The package is never executed: it is only read.
RAR archives are not opened: unpack them before uploading.
An encrypted image is flagged as such, not read: this is the case for some HP consumer images.
A signature is never required: an unsigned package opens like any other.
It does not prepare a BIOS for a given machine: the manufacturer's image carries no machine identity. That is what the rebuild is for.
An extension outside the list is refused at upload; a format nothing recognises is flagged.

How it goes

01
Upload the package
The update file as downloaded from the manufacturer.
02
Unpacking
The package is checked on arrival, then opened. It is never executed.
03
Identification
Every file is named by its kind: chip image, BIOS region, ME, EC, tool…
04
Download
One file, or a whole folder as a ZIP.