Issue updating new E6420 BIOS silently

Thanks for your post! I'll try to verify that today and report it to the proper team.

I am also having the same issue when trying to update the BIOS from WinPE using the "-NOPAUSE -NOREBOOT" switches. If I just use the the "-NOPAUSE" switch the computer reboots and applies the firmware correct and with the "-NOREBOOT" switch the firmware is never applied.

It also seems that the BIOS EXE can not be executed if using WinPE 3.0 64bit. Trying to run the EXE from a command prompt gives you: "The subsystem needed to support the image type is not present" ...running the same EXE from a 32 bit WinPE environment does not give any errors

I have the same problem (E6420 and E6320). Tested from W7 x64 (via cmd file) and also WinPE (x86). This is the log:

***BIOS flash started on 6/3/2011 at 15:24:26***
Command: C:\Windows\Temp\E6320A03.exe /s /f /noreboot /l="c:\bss.txt"

A01 INSTALLED (Dell System Latitude E6320)
- System BIOS : A01
- Embedded Controller : X068
- Legacy Video OROM : 2089.V.11
- GT1 Legacy Video OROM : 2089.V.11
- GT2 Legacy Video OROM : 2089.V.11
- Legacy RAID OROM : 10.1.0.1008
- Intel Management Engine Update : 7.1.4.1068


A03 UPDATE (Dell System Latitude E6320)
- System BIOS : A03
- Embedded Controller : X068
- Gigabit Ethernet : 0.D.3
- Legacy Video OROM : 2089.V.11
- GT1 Legacy Video OROM : 2089.V.11
- GT2 Legacy Video OROM : 2089.V.11
- Legacy RAID OROM : 10.1.0.1008
- Intel AntiTheft : 3.0.0.18
- Intel Management Engine Update : 7.1.4.1068
- ACPI OS support : 0.0.0.1

Exit Code = 2 (Reboot Required)
***BIOS flash finished at 6/3/2011 at 15:24:29***

After the reboot nothing happend. I need to run this from a task sequence during SCCM OSD without reboot. I am using the same method with older models (6400,4300,6410,4310 ...) and everything is working ok.

FYI - confirmed this is still an issue with the A04 BIOS.

Thanks for the additional info. I'm asking for internal verification.

Thanks,

Warren

Do we know if this ever got fixed and in what BIOS version it was fixed in?

phevier,

Thanks for the confirmation of A05 addressing the issue.