Anyone know how to troubleshoot a bios flash?

Trying to update the bios on my vista32 based HP TX1000.

I've searched the web endlessly and even resorted to HP's online chat help where I got no help at all. They're just refering to their own websites help files and really have no clue beyond that.

Problem...
-I run the bios update and the first thing that happens is my notepad opens with a file called QUANTA.VBE. I close the notepad and Phoenix WinFlash opens. I flash it and get error "the input file 'bios.wph' can not be found."

The only .wph file I can find in the swsetup/ folder is "30BFF1F.WPH" .I've seen some chat about renaming the .wph file to bios.wph but it looks like it can result in a stalled installation and complete system crash so... no thanks. The only reason I'm even trying is because HP Health Check keeps telling me that im 20 versions behind - otherwise everything is working fine(ish)

Is this a problem with the flash utiliy or could it be one of the many services I shut down that is stopping the process? ( I shut down a few services and am wondering if one of them is indirectly needed. )

Any help would be appreciated.

 

As I was reading your thread, this was the first thing I was going to suggest....

Not likely; I'm 99.7% sure that the flash utility is OK. If there was a problem with it, HP probably would have known about it ASAP and fixed it ASAP. Check the release date of the flash utility; if it's more than 3-4 days old, then I'm sure it's OK. As to whether a process is interfering; not likely, but it is possible. If you have ANY anitvirus or antispyware software installed (including firewalls), this could definitely cause an issue. Many systems also have a virus protection setting in the BIOS, so check your BIOS and make sure that it is disabled if applicable.

:confused If it ain't broke, don't fix it! If the PC is running OK, don't mess with the BIOS. So what if it's "20 versions behind". Big whoop. But you did say "fine-ish" which hints at a potential problem. Maybe you could tell us why you want to flash the BIOS (other than the 20 versions thing), or what problems you're having, and we could help you solve these issues, regardless of whether or not they're BIOS related.
:-D

[dlb]

Oh..... Welcome to Major Geeks! :wave :major

 

Oops! Posted this in the software forum thinking I could delete the one here... Didn't work... won't do it again.

Anyways DLB... Thanks.
It ain't broke so, Im reluctant to fix it. In fact, its running pretty hot for a TX1000 so, I've been contemplating leaving it for now. The only reason for the bios update is because I re-enabled HP Health Check service ( for no good reason ) and it pointed out that I have version F.1b and the newest is F.20. Im wondering if they've dealt with some of the bugs, like the repeating loss of my quick launch buttons and the occasional crash on IE.

I've been disabling services to give my cpu a break while Im running video and graphics editors and things are looking fine(ish). I was just wondering if one of those services is causing the flash to fail. And whats with the QUANTA.VBE openning in notepad? This also happens when I try to merge a .reg file... notepad opens... Hmmm.

Im going to try disabling the antivirus and will post if it works out.

Thanks.

 

As to the .reg and .vbe opening in notepad... right click these files and select 'Open With' and de-select notepad as the default application. That should work. If not, use the download from this link to reset all your file associations to default. It is for Windows XP originally but I think it will work for Vista, but if problems arise, don't blame me. More info about Vista file association fixes can be found at the following links:
http://www.winhelponline.com/articles/105/1/File-association-fixes-for-Windows-Vista.html
http://www.mydigitallife.info/2008/...on-in-windows-vista-back-to-original-default/
http://forums.pcworld.com/message/62790

 

Was a solution to this ever found? My HP laptop is doing the same thing! I've spent over 9 hours on the phone with 6 HP technicians trying to get this solved with no success. Trying to upgrade BIOS from version F.07 to F.32 per HP technicians to take care of computer freeze ups (have to hold down power button 5 seconds or if that doesn't work, have to pull the battery to shut it down). Something is forcing the .vbe files to open with Notepad. I've tried changing it with "Open With" and you can't just de-select it, it comes right back. And the other programs you have a choice of to Open With aren't the proper programs either. I've been able to remove .vbe and .vbs files from the File Association list in "Control Panel - Programs - Make a File Type always Open in a Specific Program" in Vista with a free utilty I found online, but it still does not allow you to reset the file association and always defaults to Notepad.

 

Sorry Fairmoor. I've tried prettymuch everything including HP support - and you know how much help they are...

The notepad thing is a puzzle. Nothing you do will change the file associations and I'll bet that it happens when you try to do a .reg merge as well.

I gave up trying and am resigned to the fact that im going to have to just wait till my HP is unusable and junk it or reformat. Your problem is bigger than mine and if I were in your position, I'd back up my files and use Recovery * note * I have never recovered using hp recovery and have no idea how reliable it is. However, if you have all your files backed up and recovery doesn't work for you... think about how much time you've wasted on this and how much trouble its been and fork out the $ to have a local tech reinstall the os.

I like my laptop and its a good little machine but HP as a company really sucks and their support is more like anti-support so, don't wate your time with them.

If I find a solution, I will post it for you.

Good luck and keep me posted on any progress.

 

Smoojik,

Thanks for the reply. Yes, I tried the .reg merge also with no success. It still opens the Quanta.vbe file in Notepad. I've used HP Recovery per HP tech support to at least get my laptop to stop crashing after I tried to Flash the Bios. Unfortunately, as far back as I can go with Recovery, it still opens .vbe files with Notepad. At least it's functioning - sometimes

 

GENERALLY IF A BIOS FLASH GO'S BADLY ON THE FIRST TRY ITS USELY A GOOD IDEA TO FORGET ABOUT IT AS THE POWERS THAT BE ARE TELLING YOU DON'T DO IT

now that thats out of the way if everything is working don't try it

if the bios update should fail it will make your machine completely worthless and you will need to A send it back B take it to someone with special tools to fix it

 

This is similar to the problem I had. My issue was caused by a program called System Mechanic Professional by Iolo software. You may have another "security software package" causing the same issue!

System Mechanic Professional by Iolo Software disables the ability to execute .vbe and .vbs files for “security” reasons. This results in the familiar error, “No script engine for file extension .vbs (or .vbe),” when you attempt to execute one of these type of files. When System Mechanic first runs, it finds what it calls Registry Errors - "HKEY CURRENT USER\SOFTWARE\CLASSES\.vbs" and "HKEY CURRENT USER\SOFTWARE\CLASSES\.vbe" and wants to correct the “errors” by having them open only with Notepad. The problem with this is that BIOS updates from Phoenix Bios (WinFlash) and Microsoft Windows Installer Cleanup Utility (msicuu2.exe) to name a few programs, both utilize .vbe and .vbs files to properly execute! The msicuu2.exe file is actually one that Iolo technicians told me to run after uninstalling System Mechanic Professional because it would not update the Iolo antivirus or firewall! Once System Mechanic Professional has disabled the ability to run .vbe and .vbs files, you can't just re-register the vbsscript.dll or vbescript.dll files and change the file associations back to Wscript or Cscript. I had to uninstall System Mechanic Professional, download Windows Script Host 5.6 or 5.7 (whichever you can get to install) from Microsoft and reinstall it. Then change the file associations for vbe and vbs files in Windows back to Wscript or Cscript, reinstall System Mechanic Professional and let it run, then have it exclude "HKEY CURRENT USER\SOFTWARE\CLASSES\.vbs" and "HKEY CURRENT USER\SOFTWARE\CLASSES\.vbe" from the registry repairs and any future searches of the registry. Now, msicuu2.exe and the Phoenix Bios (WinFlash) upgrade were finally able to install properly.
At last count, 9 senior technicians from HP, Iolo, and Microsoft have tried to help me solve this problem. Their best solution was to return it to HP and have the hard drive wiped and reloaded with the preinstalled software package. If I had done that, it would have started all over again when I let System Mechanic Professional do its stuff without figuring out what was causing the problem in the first place! Thank God I didn’t listen to them!