1 of 1 people found this helpful
I had our validation team run a series of tests but was unable to reproduce your issue. In all cases, the system properly responded to the press of the "Reboot to Install BIOS" button and started the reboot process...
Obviously, there are other factor(s) that are affecting this situation. Here is the process that my team followed; please respond with any differences from your process:
ITK version: 22.214.171.1242
Tested in following environments:
1. Windows 7 PE 32 bit
2. Windows XP PE 32 bit (Case A only)
1. Launched GUI application
2. Downloaded EB0099 from RSS feed
3. Generated EB0099.exe package ( with no customization )
4. Copied the EB0099.exe package into pen drive WinPE environment,
5. Case A: Created test.bat with the command “C:\EB0099.exe” in pen drive ( C:\ ).
Case B: Copied C:\EB0099.exe ( from pen drive ) to X:\ drive ( copy command );
Created test.bat with the command “X:\EB0099.exe” in X:\ drive.
6. Executed test.bat
7. In both the cases EB0099.exe flashed successfully on pressing “Reboot to install BIOS” and
BIOS was upgraded from EB0085 to EB0099.
Also executed above test case using SI1551 BIOS; no issues observed...
Let us know...
Thanks for taking the time to test this.
My environment is based on deployment software so the bat file and the exe get copied to the X:\ from a remote location. But issuing the bat file results in all of normal update steps until the final step.
Normally the command to update the BIOS is ex: GA0063.exe -s, but in silent mode *nothing* happens. Which isn't very graceful.