A BIOS/UEFI update failure during deployment is not one standard Windows error. The cause usually lies in the OEM firmware package, the environment it runs in, an uncontrolled reboot, BitLocker, or a vendor-specific return code. Start by identifying the exact computer model, deployment platform, task-sequence phase, command line, and error code; those details determine the safe fix.
First identify what failed
A task sequence can report an error even when the firmware update was staged—or even completed—if the updater returns a code the task-sequence engine treats as failure or restarts the device outside the task sequence. Conversely, a successful command launch does not prove the BIOS was flashed.
- Deployment platform: Configuration Manager (ConfigMgr/SCCM), standalone MDT, MDT integrated with ConfigMgr, an OEM deployment workflow, custom WinPE, or another provisioning method.
- Execution phase: WinPE or full Windows. A package intended for Windows may depend on services or libraries unavailable in WinPE.
- Exact failure: Failing step, complete status message, decimal and hexadecimal exit codes, whether the device rebooted, and whether the firmware version changed.
- Device and package: OEM, exact model or system type, current and target BIOS versions, package version, command line, and package log.
- Security and power state: BitLocker recovery prompt, firmware password, AC adapter and battery status, and any required intermediate firmware version.
Collect smsts.log and the OEM updater log, then compare the firmware version before and after. Without the model, package, execution environment, and exact return code, there is no reliable universal diagnosis.
Choose the deployment path before changing the command
| Environment | What to check |
|---|---|
| Configuration Manager OSD | Use a supported task-sequence restart and ensure package content is available after reboot. The Configuration Manager task-sequence steps documentation describes the Restart Computer and Disable BitLocker steps. |
| Standalone or integrated MDT | For listed ThinkCentre models, Lenovo documents a WinPE-phase BIOS update limitation: the firmware reboot can interrupt MDT. Lenovo recommends updating before MDT starts or after Windows installation as the final deployment step. See Lenovo’s affected-model guidance. Do not generalize it to every Lenovo model or package. |
| Custom WinPE or OEM workflow | Confirm the updater explicitly supports that environment, architecture, firmware interface, and reboot behavior. A command that works in Windows may not work in WinPE. |
| New deployment design | MDT is retired; Microsoft’s MDT troubleshooting reference provides the retirement context. Existing deployments may still need troubleshooting, but evaluate current supported provisioning approaches for new designs. |
Where to place the firmware update
Before imaging
Use this placement when a minimum firmware version is required before installing Windows and the OEM supports flashing from WinPE. Detect the exact model, verify power and package applicability, run the update, handle only documented return codes, restart into the assigned boot image, and verify the firmware version before partitioning or applying the OS. Confirm that the firmware’s boot mode and storage settings still match the deployment’s disk layout.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →#1 Best Overall
- (User manual available if do as follow: click "AITRIP"(you can find "Sold by AITRIP" under Buy Now button), in the new page, click "Ask a question".)we will send you the manual asap）
- Test Clip Pin format: SOIC8 SOP8 matrix ,Programmer TL866 EZP2010 RT809H CH341A;Please confirm the chip voltage to avoid burning the chip.(This product only supports 3.3v 5V switching)
- SOIC8 SOP8 Clip DIP8 for in-circuit programming For EEPROM /25CXX/24CXX on ZIP USB;Serial port: Supports the USB to UART 12CSP port
- Test Clip Beryllium copper plating needle, without welding, can be directly inserted
- USB Programmer CH341A Series Burner Chip 24 EEPROM BIOS Writer 25 SPI Flash AE1185
After Windows installation
Prefer this when the OEM updater requires full Windows or its WinPE reboot behavior is unreliable. Install Windows and required vendor components first, then run the BIOS update as the final task-sequence action or in a separate follow-up deployment. This limits the chance that a firmware reboot strands the sequence before the OS is installed. Lenovo’s guidance for the affected MDT/WinPE models likewise identifies pre-MDT or post-installation updating as workarounds.
As a separate firmware deployment
Separate deployment is often easier to operate across mixed-OEM fleets, especially when firmware tools have different reboot requirements or need staged rollout, retry, and reporting. It also keeps a failed firmware operation from invalidating OS imaging, at the cost of another deployment phase and a process to ensure devices eventually meet the firmware baseline.
Control the reboot and task-sequence result
When supported, suppress the updater’s automatic reboot, let it stage the update, then use the task-sequence engine’s restart step. In Configuration Manager, Restart Computer can restart into the boot image assigned to the task sequence or into the installed default operating system; choose the destination that matches the next deployment phase. The sequence is designed to continue after that controlled restart.
Rank #2
- This unit is suitable for amateur programmers of 24 and 25 series FLASH.
- Programming is faster than ordinary ATMEGA8 25 Series Programmer up to 2-3 times faster. Erasing speed is probably 2-3 Mbit check every minute.
- The programmer uses the specially produced CH341A USB chip USB/usb1.1 comms
- Usage: TV set memory ,desktop motherboard, LCD ,notebook router , card , DVD , set-top boxes ,unlocking software , backup, erasing, burning, checking,repair etc.
- Package : 1 x CH341A 24 25 Series for EEPROM Flash BIOS USB Programmer plus; 1 x 1.8V adapter for iPhone or motherboard 1.8V SPI Flash Memory SOP8 DIP8 plus; 1 x SOP8 SOIC8 to DIP8 EZ Programmer Adapter Socket Converter Module 150mil plus; 1 x SOIC8 SOP8 Flash Chip IC Test Clip socket adapter BIOS/ 24/ 25/ 93 Programmer
A firmware utility that reboots independently can interrupt task-sequence state. Do not add a second restart blindly: depending on the package and firmware mechanism, it may be redundant or may affect a staged update. Microsoft documents multiple-restart state failures in this Configuration Manager guidance. The variable SMSTSWaitForSecondReboot applies to particular software-update scenarios, not as a general BIOS-flash fix.
Do not enable Continue on error broadly to make the sequence appear successful. In a Configuration Manager Run Command Line step, a documented vendor code indicating a successfully staged update or expected reboot can be treated as an acceptable code—but only after checking the exact package documentation. Otherwise, fail clearly and preserve the logs.
Interpret return codes using the package documentation
Return codes are package-specific, not universal across manufacturers. For Dell Update Packages, Dell documents these common BIOS outcomes: 0 success, 1 unsuccessful, 2 reboot required, 6 system is rebooting, and 10 unspecified error. These meanings apply to the documented Dell Update Package context, not every Dell utility or another OEM. See Dell’s BIOS Update Package documentation.
Rank #3
- CH341A Programmer: The main purpose is to backup, erase, programming, calibration and other operations of various software
- Compatible with most 24 / 25 series SOP8 SOP16 chip
- Chip 100% compatible: CH341A and CH341B
- No welding is required, you can directly clamp it with a test clip
- Please confirm the chip voltage to avoid burning the chip.(This product only supports 3.3v 5V switching)
Dell documents silent execution such as package.exe /s and logging such as package.exe /s /l=c:pkg.log; /s is required with several administrative options, including logging. Dell identifies /r as the option that allows an automatic reboot, so omitting it can suppress that package’s explicit automatic restart. It does not guarantee that no later firmware restart is needed. Check the exact package readme for supported switches and behavior.
For the affected Lenovo ThinkCentre workflow, Lenovo gives the model- and package-specific example flash64.cmd /quiet /sccm in a Run Command Line step. Do not assume /sccm applies to other Lenovo packages. For HP or any other vendor, use the exact model’s enterprise firmware instructions rather than borrowing Dell or Lenovo syntax.
Check WinPE compatibility and package delivery
If the command works in an administrator session but not in deployment, reproduce it in the same context as the failing step. Verify each of the following:
Rank #4
- MinPro I Programmer USB Motherboard LCD BIOS SPI Flash 24 25 Burner
- The package targets the exact system family and board revision, and the current-to-target version path is supported.
- The OEM supports the package in WinPE if that is where it runs; check architecture, required runtime libraries, services, and dependencies.
- The task-sequence command uses the correct working directory and can access the local disk and firmware interface in that phase.
- Content is distributed to the relevant distribution points and is available after a restart.
- The command is truly silent and does not wait for a user interface, BIOS-password prompt, or logged-on user profile.
- Power, battery, security, downgrade, capsule-update, and intermediate-version requirements match the package’s readme.
For a same-environment reproduction, use the same task-sequence account, package location, working directory, command line, password handling, and reboot settings. Record standard output, the vendor log, and the returned code.
Protect BitLocker and handle firmware passwords
BitLocker
Firmware and UEFI changes can change measurements BitLocker uses, potentially triggering recovery when protection is active. Microsoft discusses this risk and exceptions in its BitLocker FAQ. For an existing Windows installation, suspend protection before the update when required by the firmware and organizational procedure; suspension does not decrypt the drive.
Configuration Manager’s Disable BitLocker task-sequence step suspends protection. Its reboot count can be set from 1 through 15; setting OSDBitLockerRebootCountOverride to 0 leaves protection disabled indefinitely and should be avoided unless a deliberate recovery plan exists. After the firmware restart, confirm Windows boots and protection has resumed, and validate or escrow the recovery key as policy requires.
Free tools Windows power users keep installed
One-click scans. No signup required.
Best Value
- 1.The SOP8 clip enables in-circuit programming of for EEPROM without disassembling the chip, making flashing the BIOS simpler and more efficient.
- 2.The main purpose of the CH341A Programmer is to back up, erase, program, calibrate and other actions on various software.
- 3.SOIC8 SOP8 Test Clip For EEPROM 24CXX / 25CXX / 93CXX in-circuit programming
- 4.The CH341A Programmer support most 24 / 25 Series for EEPROM BIOS SOP8 SOP16 chip on the market. Note: Due to the characteristics of the CH341A chip, the ESMT SST class 25 chip can only be read and cannot be written.
- 5.5.Tips: Some chips are affected by peripheral circuits and cannot be clipped directly. Please check the chip location on the motherboard before purchasing!
BIOS password
A configured firmware password may cause an interactive hang, authentication error, or failure to apply the update. Use only the OEM-supported parameter and test special-character handling. Dell documents package.exe /s /p=password for supported Update Packages, but a literal password in a command line can appear in task-sequence logs, process listings, package content, or administrative history. Use a protected variable or secret mechanism where supported, prevent or redact sensitive logging, and rotate a password if it was exposed.
Symptom-to-action guide
| Symptom | Likely cause | Next action |
|---|---|---|
| Sequence fails immediately after the package runs | Nonzero vendor code interpreted as failure | Check the exact package’s exit-code table; accept only codes documented as successful or expected workflow states. |
| Device reboots and the sequence does not resume | Updater restarted outside task-sequence control | Suppress the package reboot if supported; arrange a controlled restart and correct resume destination. |
| MDT stops during a WinPE BIOS update | Firmware reboot interrupts MDT on affected workflows | For the Lenovo models covered by its advisory, update before MDT starts or after OS installation; do not infer this limitation applies to all devices. |
| BitLocker recovery appears | Firmware or Secure Boot measurements changed while protection was active | Use the recovery key, then review suspension and resume handling for future updates. |
| Password prompt or authentication failure | Password missing, malformed, or unsupported in the command context | Use the OEM’s supported secure password method and test without exposing the secret. |
| Wrong-model or unsupported-platform error | Package does not match the exact system or board | Correct model detection and package assignment before retrying. |
| Reported success but BIOS version is unchanged | Update may be staged for reboot, blocked by policy, or unsuccessful in the firmware phase | Restart under controlled conditions if indicated by the package, then inspect the firmware log and version. |
| No boot device after update | Boot mode, storage mode, Secure Boot, or boot order changed | Restore the required firmware settings and check that they match the OS disk’s partition and boot configuration. |
| Works manually, fails in the task sequence | Different account, environment, path, permissions, or working directory | Reproduce under the failing task-sequence context and capture its logs. |
| Sequence continues despite an actual firmware failure | Continue on Error or permissive return-code handling hides failure | Fail fast unless the step is explicitly noncritical; verify firmware version before reporting success. |
Verify completion after the restart
Use a post-reboot task-sequence check or follow-up deployment to confirm the BIOS version and, where available, release date. Also check Windows boot, BitLocker protection, Secure Boot, UEFI versus legacy mode, and disk visibility. In Windows, an administrator can inspect reported firmware information with:
Get-CimInstance Win32_BIOS |
Select-Object Manufacturer, SMBIOSBIOSVersion, ReleaseDateThe version string and date format returned by Win32_BIOS depend on the OEM. A command’s exit status alone is not proof of a completed flash.
When to stop retrying inside the task sequence
Move firmware updating to a separate, staged deployment if reboot behavior remains unpredictable, the updater is not supported in WinPE, multiple OEMs require incompatible handling, or a firmware failure should not interrupt OS imaging. Keep model-specific conditions and packages, test on representative hardware, and retain a recovery path. A BIOS update is a model-specific firmware operation, not a generic application install.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
