To Flash or Not to Flash update BIOS h8-1380t

[captlat]

Recently purchased HP Pavilion h8-1380t Intel Core i7-3280 @ 3.6GHz - 14GB DDR3 1600MHz SDRAM - Wind 7 Pro 64-bit.

Really wanted to install & run Win XP Mode, install says hardware-assisted virtualization not turned on in BIOS. Let me tell you the BIOS on this machine is as lame as I have seen in 30 years of doing this stuff. It has no menu item for turning on Hardware-Assisted Virtualization and no revision number or date. If I remember it is American Megatrends(?). Two  sessions with HP Tech Support resulted in "maybe" updting the BIOS would provide the H-A Virtualization menu item. I have downloaded the available update sp56214.exe. Does anyone think its a good idea to update the BIOS? Does anyone have Win XP Mode running on a similar HP Desktop? And what is the CTRL-I to enter setup flash when booting up? Is that a different BIOS setup? I haven't tried, but I wil shortly.

[Paul_Tikkanen]

Hi:

Isn't the VT enable option buried in the Security menu under device security?

Paul

[captlat]

Thanks Paul. It was not under device security, but System Security. I really had to stretch my memory banks to remember how to change an option. Turns out the plus key. And I did find a rev # 2.14.1219. Now to continue installing XP Mode. You have an opinion on flashing BIOS or if it ain't broke don't fix it!

[Paul_Tikkanen · Accepted solution]

You're very welcome.

Yes, that is my opinon (if it's not broke, don't fix it) unless after you read the BIOS release notes there is something you just have to have.

If there was a way you could flash the BIOS in DOS, then I would be more liberal in my thoughts, but those Windows based flashes...I read too many horror stories on this forum about failed BIOS flashes.

Just for kicks, do a search on "Failed BIOS flash" and see many threads pop up.

Paul

[Big_Dave]

Something to think about:

The term "If ain't broke don't fix it" doesn't apply to PC updates. Many $$ were spent to create fixes and updates to not only solve problems but prevent problems. The cost of rediscovery was found to be more than the cost to apply the updates.

[Paul_Tikkanen]

Tell that to these guys...and that is a BIOS update to an HP business PC!

Then you have to wait for a fix to the fix. In the corporate environment that could spell big trouble.

http://h30499.www3.hp.com/t5/Business-PCs-Deskpro-EVO/Elite-8200-SFF-BIOS-Update-to-2-15/m-p/5440533...

Nope...read the release notes first, and make your own decision whether or not it is worth the risk to flash.

Some BIOS updates do nothing but update processor microcodes which is meaningless if you have no intention of upgrading the processor.

Others do this:

- Fixed an issue that caused USB mouse input to kill the keyboard during POST or DOS. - Fixed an issue with the F10 Setup user interface for Boot Order, where making more than one change at a time could cause other unexpected boot order changes. - Corrected a problem with restoring a saved Master Boot Record (MBR) backup image when a Setup password is set. - Restored the F10 Setup / Advanced / AMT Configuration menu which can disappear when the system is updated from BIOS v2.09 to v2.15. - Disabled Wake-on-LAN function as expected when the F10 Setup option 'S5 Maximum Power Savings' is Enabled, even if the Power Savings mode is overridden by the AMT policy 'On in S0, ME Wake in S4, S4-5'. - Allow systems with blank Universally Unique Identifiers (UUIDs) to autogenerate an appropriate value. - Fixed a compatibility issue with an LSI Logic PCI Express RAID card, where the card's option ROM was unable to load. - Fixed an issue where options in the ESC (Startup) Menu are not suppressed if the associated feature is disabled. - Fixed an issue where removing the Smart Cover sensor from the unit when active would cause display issues with the F10 Setup Smart Cover menu. - Corrected Windows Management Interface (WMI) reporting of Smart Cover status. - Fixed an issue where WMI commands fail to parse white spaces in the password preamble. - Fixed WMI BIOS Configuration response to return failing error code if password is incorrect. - Corrected the System Management BIOS type 1 data field for 'Wakeup Type' to properly display 'Remote' when the system is powered on by a Wake-on-LAN event. - Changed the default setting of Lock Legacy Resources to Disabled. - Changed Asset Tag (System IDs) properties so that it does not get deleted on Apply Defaults and Exit. - Fixed a compatibility issue with a US Robotics PCI modem card, where the BIOS was generating a "PXE-01" warning message during POST.

[Big_Dave]

@Paul,

My advice comes from the corporate environment!   If the updates are worthless then can you explain why from a financial viewpoint why all of the software and hardware manufacturers continue to produce updates?

[captlat]

Thanks for opinions. I will wait until I have installed Win XP Mode.

[Paul_Tikkanen]

@ Big Dave.

I'm not going to bicker with you.

Where did I state that BIOS updates were worthless?

Have you not read all of the tales of woe from folks that have had failed flashes when they had no real need to flash the BIOS?

Well, here's just a few!

http://h30434.www3.hp.com/t5/forums/searchpage/tab/message?q=Failed+BIOS+Flash

You have your opinion, and I have mine.

I'm not saying don't flash the BIOS, or never flash the BIOS.

All I am saying is to read the release notes first.

Then decide if flashing the BIOS is worth the risk.