WGA Meltdown Blamed On Human Error

Erris writes "As commentators like Ars Technica slam WGA as deeply flawed, Microsoft is blaming human error and swears it won't happen again. 'Alex Kochis, Microsofts senior WGA product manager, wrote in a blog posting that the troubles began after preproduction code was installed on live servers. ... rollback fixed the problem on the product-activation servers within 30 minutes ... but it didnt reset the validation servers. ... "we didnt have the right monitoring in place to be sure the fixes had the intended effect"' Critics were not impressed. 'A system thats not totally reliable really should not be so punitive, said Gartner Inc. analyst Michael Silver. Michael Cherry, an analyst at Directions on Microsoft in Kirkland, Wash., said he was surprised that it was even possible to accidentally load the wrong code onto live servers ... [and asks], "what other things have they not done?' This is not the first time this has happened, either."

Comments

What happens in Safety Critical Windows installs?

[Anonymous Coward]

So if you were stupid enough to use Windows in a safety critical application you risk WGA putting people's lives at risk?

Imagine if you used Windows in a doctors surgery to hold patient records, or store drug allergy data on it. WGA flags the PC as counterfeit, after that only Window Explorer works, and you can't get their records or allergy info.

As long as Microsoft can deliberately or accidentally remove your right to use your PC, then you can't use it in any cases where you may find yourself in future dispute with MS, or where you need to rely on the PC. Having backups is no fix for the Windows Genuine Advantage bugs, because all Windows PCs go down in one go. It represents the ultimate single point of failure.

Re:Have we gone backwards?

[Ckwop]

Quite simply, you *cannot* have too much processing power when doing OCR -- I'm running multiple instances of ABBYY FineReader Corporate on a 2x Quad Core Xeon that has been pegged for two weeks now.

This is an application task and I'm inclined to agree with you. You can never have enough resources, whether you're encoding HD-DVDs all day or just using Notepad.

However, I was talking about the operating system. The role of an operating system should be to provide a framework for performing tasks and running application as cheaply as possible; that is, using the least amount of resources as possible.

It's a fair bet your program would work on Windows 2000 and Windows Vista. Yet Windows Vista will "tax" your system more to achieve exactly the same result. This is my point - the operating system is gobbling more and more resources that should be used by your applications without giving the user anything in return. In this sense, we are moving backwards.

Simon

Re:What happens in Safety Critical Windows install

[Technician]

So if you were stupid enough to use Windows in a safety critical application you risk WGA putting people's lives at risk?

Imagine if you used Windows in a doctors surgery to hold patient records, or store drug allergy data on it. WGA flags the PC as counterfeit, after that only Window Explorer works, and you can't get their records or allergy info.


Read the EULA. Pay attention to the section regarding life critical application. It clearly states it is not to be used in life support applications. It simply isn't reliable for that. MS is avoiding lawsuits from people depending on Windows for life support by explicitly stating it is not designed, manufactured, or intended for that.

"Note on Java Support. The SOFTWARE may contain support for programs written in Java. Java technology is not fault tolerant and is not designed, manufactured, or intended for use or resale as online control equipment in hazardous environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, direct life support machines, or weapon systems, in which the failure of Java technology could lead directly to death, personal injury, or severe physical or environmental damage. Sun Microsystems, Inc. has contractually obligated MS to make this disclaimer."

snipped from here;
http://www.microsoft.com/msdownload/ieplatform/ie/ license.txt