AFUDOS: Complete Guide

AFUDOS is AMI’s utility for flashing and managing BIOS/UEFI firmware. Compatible with AMIBIOS8, Aptio 3, 4, 4.5, and 5.

In addition to the DOS version, there are also AFUWIN (for Windows) and AFUEFIx64 (for UEFI Shell), but this article covers AFUDOS only.

Features

AFUDOS can flash the main BIOS image and work with individual SPI flash regions such as the Boot Block and NVRAM. With an open Flash Descriptor, Intel service regions become accessible (ME, GbE, and the Descriptor itself). The utility can make a full dump of the current BIOS for backup and later restoration, check an image for compatibility and matching ROM ID, handle capsule files in some cases, start in recovery mode, and, during an update, optionally preserve user settings and SMBIOS tables, perform a silent update, and automatically reboot the system. Note that hardware protections (BIOS Lock, Secure Flash, a closed Flash Descriptor) can block writes and are not bypassed by the utility itself.

⚠️ Critical Safety Warning

AFUDOS carries serious risks. Mistakes can brick your motherboard permanently. The process can erase unique data including serial numbers, MAC addresses, and other identifiers.

Power interruptions or crashes during flashing will corrupt the SPI flash, requiring a hardware programmer for recovery. Always create backups and store them securely!

Disclaimer: We accept no responsibility for any consequences resulting from AFUDOS usage. You perform all operations at your own risk.

Create a bootable USB drive with AFUDOS

Method 1: Rufus + FreeDOS

Create a FreeDOS USB with Rufus for AFUDOS

  1. Download Rufus
  2. Insert a USB flash drive
  3. In Rufus select:
    • Partition scheme: MBR
    • File system: FAT32
    • Boot selection: FreeDOS
  4. Click “Start” and wait for completion
  5. Copy AFUDOS.EXE and your BIOS files to the USB drive

Method 2: HP USB Disk Storage Format Tool

Create a DOS boot USB with HP USB Disk Storage Format Tool

  1. Download HP USB Disk Storage Format Tool
  2. Run the tool as Administrator
  3. Select your USB flash drive
  4. File system: FAT32
  5. Check “Create a DOS startup disk”
  6. Specify the path to DOS system files (you can download them separately)
  7. Click “Start” and wait for completion
  8. Copy AFUDOS.EXE to the root of the USB drive

Booting from the USB drive

There are two ways to boot from the USB drive. We recommend starting with the first method — it’s much simpler and does not change your system’s persistent BIOS settings.

Method 1: Via Boot Menu (Recommended)

Open the Boot Menu and select USB to boot DOS

This menu lets you choose which device to boot from one time without changing persistent BIOS settings.

  1. Insert the USB drive and reboot the computer.
  2. Right after power-on, but before the Windows logo appears, start pressing the Boot Menu key.
    • Common keys: F12, F11, F9, F8, Esc.
    • There’s often an on-screen hint at startup, e.g., Press F12 for Boot Menu.
  3. From the list, select your USB drive (it may appear under the manufacturer’s name, e.g., “Kingston DataTraveler,” or simply “USB-Flash Drive”).
  4. DOS should start.

Method 2: Change boot priority in BIOS (Alternative)

Set the USB as the first boot device in BIOS

Use this method if you can’t open the Boot Menu or your board doesn’t have it.

  1. Insert the USB drive and reboot the computer.
  2. Enter BIOS during power-on by pressing Del, F2, or another key indicated on the startup screen.
  3. Find the “Boot” section.
  4. Locate “Boot Priority” and set your USB drive as the first device (“1st Boot Device”).
  5. Go to the “Exit” section, choose “Save Changes and Exit”, and confirm.

Important: After you’re done, don’t forget to return to BIOS and set your primary disk (SSD/HDD) back to the first boot priority.


After successfully booting into DOS you’ll see a command prompt, e.g., C:>. You can now check compatibility by typing: AFUDOS /S

Basic commands

  • Show system info: AFUDOS /S
  • Back up current BIOS: AFUDOS BACKUP.ROM /O
  • Verify a file without flashing: AFUDOS NEW.ROM /D
  • Standard flash: AFUDOS NEW.ROM /P /B /N
  • Force (only if you’re sure it’s compatible): AFUDOS NEW.ROM /P /B /N /X
  • Restore from backup: AFUDOS BACKUP.ROM /RECOVERY

Note: After a successful flash, reboot and perform “Load Optimized Defaults”.

Full command list

Info/verification

  • /S — show current system ROM ID
  • /U — show ROM ID from file
  • /D — verify file without flashing
  • /O — save current UEFI to file

Flashing regions

  • /P — flash main block (Main BIOS)
  • /B — flash Boot Block
  • /N — flash NVRAM (variables)
  • /E — flash Embedded Controller (if present)
  • /K — flash all non-critical blocks
  • /L — flash all ROM Holes

Intel Flash regions

  • /ME — flash Intel ME region
  • /MEUF — flash ME Ignition Firmware
  • /FDR — flash Flash Descriptor Region
  • /GBER — flash GbE (LAN controller)

Behavior and checks

  • /X — ignore ROM ID check (force, dangerous)
  • /CAPSULE — work with capsule image (if supported)
  • /CAF — cancel update if the file is identical to current
  • /Q — quiet (silent) mode
  • /REBOOT — reboot after flashing
  • /SHUTDOWN — power off after flashing
  • /JBC — ignore battery/power checks on laptops

Preserving data

  • /SP — preserve Setup settings (System Profile)
  • /R — preserve SMBIOS structures

Maintenance/misc

  • /CLNEVNLOG — clear UEFI event log
  • /A — operations with OEM Activation Key
  • /OAD — delete OEM Activation Key

Basic scenario 1: BIOS dump (backup)

  1. Boot from the prepared USB drive
  2. Verify the system is detected:
    AFUDOS /S
  3. Save a full backup of the current BIOS from SPI flash:
    AFUDOS BACKUP.ROM /O
  4. Make sure BACKUP.ROM has the correct size for your chip (typically 8 MB, 16 MB, or 32 MB).
  5. Copy BACKUP.ROM to separate storage/cloud and keep it safe.

Basic scenario 2: Flashing the BIOS

  1. Copy the firmware file to the USB root alongside AFUDOS and rename it for convenience, e.g., NEW.ROM.
  2. Verify the file without flashing:
    AFUDOS NEW.ROM /D
  3. Compare the ROM ID of the file and the system:
    AFUDOS /S
  4. Perform a standard flash of the main regions:
    AFUDOS NEW.ROM /P /B /N
  5. If you are certain the file matches but see a ROM ID error, use force at your own risk:
    AFUDOS NEW.ROM /P /B /N /X
  6. After success, reboot, enter BIOS, perform “Load Optimized Defaults”, save, and reconfigure your settings.

Common errors

  • 0x04 ROM ID not compatible — the utility thinks the file isn’t for this board. Use the correct image, or the /X switch only if you’re sure.
  • 0x34/0x35 Wrong AFU version — use a version compatible with your BIOS.
  • 0x40 BIOS write-protected — writing is blocked. Check BIOS Lock or other protections in settings.
  • ME/FD errors — Flash Descriptor is locked and/or a Secure Flash policy is enforced. You need to unlock FD and/or use a specialized tool (Intel FPT) or a hardware programmer.
All AFUDOS error codes

0x01 Error: Unknown command.
0x02 Error: BIOS has no flash information available.
0x03 Error: ROM file size does not match existing BIOS size.
0x04 Error: ROM file ROMID is not compatible with existing BIOS ROMID.
0x05 Error: Bootblock error.
0x06 Error: This BIOS version has more Non-Critical blocks than supported.
0x07 Error: BIOS checksum error.
0x08 Error: Invalid option
0x09 Error: Size of ROM file does not match the size of system ROM
0x0A Error: Unable to update ROM hole
0x0B Error: ROMHOLE not exist
0x0C Error: BIOS update cancelled by user.
0x0D <Reserved for system>
0x0E Error: Kernel source files cannot be found.
0x10 Error: Unable to load driver.
0x11 Error: Unable to unload driver.
0x12 Error: No non-critical blocks found in ROM file.
0x13 Error: Requested non-critical block not available in ROM file.
0x14 Error: Non-critical blocks in ROM image file do not match those in the system.
0x15 Error: Secure Flash function is not supported on this platform.
0x16 Error: Unable to get Secure Flash policy from BIOS.
0x17 Error: Unsupported Secure Flash policy.
0x18 Error: Unable to start a Secure Flash session.
0x19 Error: Failed to erase flash chip (at Runtime Secure Flash).
0x1A Error: Failed to update flash chip (at Runtime Secure Flash).
0x1B Error: Failed to read flash chip (at Runtime Secure Flash).
0x1C Error: Failed to verify flash chip (at Runtime Secure Flash).
0x1D Error: Failed to load image into memory.
0x1E Error: Secure Flash function is not supported on this file.
0x1F Error: Reserved for Secure Flash.
0x20 Error: Unable to initialize memory manager.
0x21 Error: Unable to close memory manager.
0x22 Error: Problem allocating memory.
0x23 Error: Problem freeing memory.
0x24 Error: Problem allocating BIOS buffer.
0x25 Error: Problem freeing BIOS buffer.
0x26 Error: Problem freeing mapping BIOS.
0x27 Error: Problem freeing unmapping BIOS.
0x28 Error: Problem mapping BIOS data.
0x29 Error: Problem unmapping BIOS data.
0x30 Error: Problem opening file for reading.
0x31 Error: Problem reading file.
0x32 Error: Problem opening file to write.
0x33 Error: Problem writing file.
0x40 Error: BIOS is write-protected.
0x41 Error: Can not close flash interface.
0x42 Error: Problem reading flash.
0x43 Error: Problem erasing flash.
0x44 Error: Problem writing flash.
0x45 Error: Problem verifying flash.
0x46 Error: Problem getting flash information.
0x47 Error: No firmware id.
0x48 Error: Power cord not connected. Plug in power cord to flash.
0x49 Error: A platform condition has prevented flashing.
0x50 Error: This program must be run in MS-DOS mode.
0x60 Error: Accessing registry.
0x61 Error: Program already running.
0x70 Error: BSD access IO.
0x80 Error: Size of system ROM mismatches size of ROM file
0x81 Error: ROM ID mismatch
0x82 Error: Bootblock checksum error
0x90 Error: Error to shutdown
0x91 Error: Error to restart…
0x92 Error: Can’t open ROM ID file
0x93 Error: ROM ID file is not a ROM file.
0x94 Error: Invalid MAC address
0x95 Error: Invalid load current CMOS option
0x96 Error: Invalid retry count
0x97 Error: Invalid defined ROM ID length
0x98 Error: Invalid SMI
0x99 Error: ROM File ID don’t exist
0x9A Error: System ROM ID don’t exist
0x9B Error: Password Retry count exceeded.
0x9C Error: BIOS don’t support NVRAM/SETUP preserve function
0x9D Error: Store SETUP setting error
0x9E Error: Restore SETUP setting error
0x9F Error: Cannot analyze ROM file. ROM file may be corrupted
0xA0 Error: Cannot analyze the ME Data. ROM file may be corrupted
0xA1 Error: BIOS does not support ME Entire Firmware update
0xA2 Error: BIOS does not support ME Ignition Firmware update
0xA3 Error: Invalid EC ROM file
0xA4 Error: EC ROM file checksum error
0xA5 Error: Can’t enter EC flash mode
0xA6 Error: Erasing EC flash memory fail
0xA7 Error: Initial EC programming fail
0xA8 Error: EC flash data transmit error
0xA9 Error: Writing EC flash memory fail
0xAA Error: Exit EC programming mode fail
0xAB Error: ROM Chip ID mismatch
0xAC Error: Invalid EC Header Table
0xAD Error: EC does not permit BIOS update
0xAE Error: BIOS doesn’t support OEMCMD function
0xAF Error: Store DMI Data error
0xB0 Error: Restore DMI Data error
0xB1 Error: Invalid Activation Key file.
0xB2 Error: File Size is greater than image activation key length.
0xB3 Error: Image activation key larger than BIOS activation key.
0xB4 Error: Activation Key checksum error.
0xB5 Error: No Support Activation Key error.
0xB6 Error: OA Key is not NULL at all.
0xB7 Error: OA Key is NULL at all already.
0xB8 Error: OA key region incorrect.
0xB9 Error: BIOS doesn’t support Clear event log function.
0xBA Error: Clear event log error.
0xBB Error: Rom image layout detected RomHole is redesigned.
0xBC Error: BIOS have more than one RomHole’s GUID is the same.
0xBD Error: Requested Rom Hole not available in ROM file.
0xBE Error: Romholes in ROM image file do not match those in the system.
0xBF Error: OA key is not NULL at all. And OA Key is the same as Bin File in system.
0xC0 Error: BIOS doesn’t support process ME information
0xC1 Error: BIOS return error, when trying to re-flash ME Firmware data.
0xC2 Error: Region is write-protected
0xC6 Error: No EC blocks found in system ROM.
0xC7 Error: BIOS doesn’t support all ROM flashing function.
0xD0 Error: OA Data invalid.
0xD1 Error: BIOS has already updated OA.
0xD2 Error: BIOS does not allow updating OA.
0xD3 Error: BIOS doesn’t support updating OA.
0xD4 Error: The DMI data size of system is greater than File’s DMI data length.
0xD5 Error: BIOS doesn’t support EC Battery Check function.

Download AFUDOS

 

⚠️ Disclaimer
These tools are proprietary software owned by their respective copyright holders.
They are not officially distributed to end-users and are provided here strictly for educational and research purposes only.
Use them entirely at your own risk. Neither the website nor the uploader assumes any responsibility for potential damage, misuse, or legal consequences.

📦 Note: Due to hosting and licensing limitations, all software files are shared via Telegram channel.
Join to access the complete collection of tools and updates in one place.

 
tg banner filebox