WinFlash For BIOS Update

[PILGRIM]

Just read the closed thread about that guy using WinFlash to update BIOS
then bricking his laptop. Granted, he was disrespectful. Granted, he should be
chastised.
(http://rog.asus.com/forum/showthread.php?17555-Failure-upgrade-bios-208-with-WinFlash-G55VW&country=...)

But the underlying fact is that he bricked his laptop by using this amazingly
helpful BIOS update ASUS software called WinFlash. Of which, as I still recall, has been
one of the two most helpful in producing RMAs and whatnots (the other is the ASUS Live Update).

Evaluated experience is the best teacher, as the saying goes.
But in this case (and the plentiful others), is ASUS evaluating at all
on its consumers' pros and cons of using its own "help" software?
I mean, this WinFlash issue has been prevalent way back (see the older G-series forum).
Hindsight is golden, but ASUS doesn't seem to grasp it.

So, what is it, ASUS? Taking pleasure in more RMAs? :mad:

[xeromist]

I think the number of people bricked by winflash is actually likely very low. ASUS sees the RMA numbers and we don't so if it was causing a large number of RMA's and costing the company money I'm sure they would have changed things by now.

I agree it would be better if everyone could use the easy flash in the BIOS but some people would never update their machine if they couldn't use a Windows tool.

[PILGRIM]

Assuming your estimate is closer to the truth (a part of me would like to believe it),
but it's also a fact that in these ROG forums, using WinFlash has been majorly attributed
to many RMAs.

Assuming the WinFlash success-over-failure ratio is more as to the bigger picture, it still
wouldn't justify ASUS' continuous ramming of this software program to its consumer's
throats. If ASUS finds EasyFlash the safer way to update BIOS, then why doesn't it just
scrap WinFlash? If not, why not make it better and safer?

As a consumer, I was really fortunate of finding these ROG forums and learning their collective
knowledge before I attempted to update my BIOS with EasyFlash, several months back.
Otherwise, I might be one of those unfortunate ones who tried to do it with WinFlash-
and bricked my laptop.

[john_from_ohio]

Marshall noted in a different thread ( just today I think ) the following:

I am in the process of trying to arrange changelogs put on the site and to get WinFlash removed. Please use EZFlash2 from the BIOS itself.

***

I can imagine it might be swimming against the tide to try to get WinFlash removed so don't hold your breath!

[xeromist]

PILGRIM wrote:
Assuming your estimate is closer to the truth (a part of me would like to believe it),
but it's also a fact that in these ROG forums, using WinFlash has been majorly attributed
to many RMAs.

I'm just saying that logically speaking a for-profit business doesn't keep doing something very long if it turns out to be a significant liability. For all I know half of all winflash users need to RMA but that wouldn't make much sense from a business perspective.

It's also worth noting that we get an excessively skewed perspective here. People look for a forum when a flash goes wrong, not when everything goes perfectly.

I'd be willing to bet that further skewing the numbers is that there are more flashes done with winflash due to its accessibility. The average person isn't comfortable with a BIOS but they'll run a Windows tool. What we see could be the same percentage of failures just magnified due to the total number of attempts.

Don't take this as defending winflash necessarily. I'm a proponent of Keep It Simple Stupid. Running an operating system and who knows what else while performing a firmware flash is just adding unneeded risk. The point is that we simply don't know what is causing issues so assuming that we do is not going to produce constructive discussion.

[PILGRIM]

xeromist wrote:
I'm just saying that logically speaking a for-profit business doesn't keep doing something very long if it turns out to be a significant liability. For all I know half of all winflash users need to RMA but that wouldn't make much sense from a business perspective.

It's also worth noting that we get an excessively skewed perspective here. People look for a forum when a flash goes wrong, not when everything goes perfectly.

I'd be willing to bet that further skewing the numbers is that there are more flashes done with winflash due to its accessibility. The average person isn't comfortable with a BIOS but they'll run a Windows tool. What we see could be the same percentage of failures just magnified due to the total number of attempts.

Don't take this as defending winflash necessarily. I'm a proponent of Keep It Simple Stupid. Running an operating system and who knows what else while performing a firmware flash is just adding unneeded risk. The point is that we simply don't know what is causing issues so assuming that we do is not going to produce constructive discussion.

Agree to some extent. And this is exactly the point- that a BIOS flash while running Windows
is a sure way of inviting disaster. And I would bet my wife's cat ASUS knows this.
So how to eliminate impending disaster? As we know it:
1. Scrap WinFlash. (IMO, even a single laptop that was bricked by using it, should be enough
to warrant its termination.)
2. BIOS Updates should be wrapped with a Read Me file giving more details about the update
and a Guide file on how to execute it by using EZFLASH2 (I'd recommend ASUS to compensate
Brody with any of the newer products of his choosing, in exchange of the right to use his BIOS
update guide).

[kiba]

PILGRIM wrote:
Agree to some extent. And this is exactly the point- that a BIOS flash while running Windows
is a sure way of inviting disaster. And I would bet my wife's cat ASUS knows this.
So how to eliminate impending disaster? As we know it:
1. Scrap WinFlash. (IMO, even a single laptop that was bricked by using it, should be enough
to warrant its termination.)
2. BIOS Updates should be wrapped with a Read Me file giving more details about the update
and a Guide file on how to execute it by using EZFLASH2 (I'd recommend ASUS to compensate
Brody with any of the newer products of his choosing, in exchange of the right to use his BIOS
update guide).

^ +1, this has been suggested before though.

[PILGRIM]

That would be one corrective measure, if indeed true.

P.S. And for added measure, scrap ASUS Live Update, too.

[kiba]

while i definitely aggree that winflash and liveupdate should be removed from g series machines, a large number of my freinds have g series laptops and have updated their bios, and not a one of them has ever used winflash or bricked their machines. it takes a little common sense, and i hope most people would check the forums before doing something major like updating their bios, where its made clear to use a FAT32 formatted usb disk from EZFLASH2. also i think that a large number of people who do this are updating their bios too often, just to do it, or whenever a bios update comes out because they think that it is part of keeping their machine up to date. it should be made more clear that the only time you need a bios update is if asus tells you to do it or to solve an issue you are having, and also that it is possible to brick your machine even if you do everything right, due to a corrupted bios file during download, or a power outage during the update, etc. that said i definitely aggree with pilgrim in his original post.

[xeromist]

Actually I'd argue it's a good idea to install updates during the warranty period. That way when the warranty is up you aren't stuck with the retail BIOS and no safety net if you find a reason to update. At least during the warranty you can RMA.