通过

WGA service outage

  • 项目

Earlier this week a server on the backend of the WGA service experienced a bug that resulted in a temporary outage. As a result, some systems were incorrectly flagged as being non-genuine, and we want to confirm for those who contacted us about this that it was indeed an error.  The WGA team apologizes for any disruption this may have caused for our customers.
The bug that caused this issue was identified and fixed within twenty four hours of being discovered. 

Here are the specific steps that can be taken now to fix this issue on any affected system that is genuine:

1)      Delete the data.dat file from C:\Documents and Settings\All Users\Application Data\Windows Genuine Advantage\data (The drive letter will depend on where the OS was installed)

2)      Revisit https://www.microsoft.com/genuine/downloads/validate.aspx to confirm whether the machine is genuine.

3)      Run wgatray.exe /b from the command line to ensure that the latest validation is updated for WGA Notifications.  This command may be absent from the user’s machine and should not be considered an error.  Please ensure that this is run as an Administrator.  A reboot may be required to remove all non-genuine notifications.

We also implemented a webpage with special instructions that will receive any traffic from systems that are running on product keys that could have been affected by this issue.

Also, systems that validated during this time and were given the incorrect answer may have cached that answer and could continue to use that locally cached value (of “not-genuine”) for up to 90 days for most systems or until the data.dat file is deleted.  Our routing of systems running on affected keys to a special webpage where steps can be found for fixing this issue will remain in place to help users of affected systems.

Comments

  • Anonymous
    October 05, 2006
    Here's a KB they [WGA team] threw together that has a little more to offer in way of support and guidance that the author did not include for whatever reasons. http://support.microsoft.com/kb/926333 Ultimately the best fix would have been for the same WGA application that phones home every so often to correct itself by eradicating any corrupt data.dat files.  It's a pity that such a burden has been placed on the customer to correct a mistake caused by WGA.

  • Anonymous
    October 06, 2006
    If the server outage the reason for not offering KB905474 (WGA Notifcation Tool) via Auto/Windows/Microsoft Update at the moment anymore?

  • Anonymous
    October 09, 2006
    This is why even "a fraction of a percent" of failure of WGA (and Vista Reduced Functionality Mode) is an awful idea--because with hundreds of millions of Windows users, that amounts to thousands of people who Microsoft must support with servers that are not 100% reliable. What if it were your deadline-critical, mission-critical work that was blocked by reduced functionality mode? I think the right way to "dogfood" this is to have WGA/Vista Reduced Functionality kick in at deadline for the people working on the team--for example, just as RC2 or RTM is due.  Only then will they understand what they're doing to users. I have a free copy of Vista Ultimate (I'm a beta tester) and even I'm not happy about the idea of installing it on my primary machine because I don't want to be locked out when I need my computer most. Truly, Windows is no longer a mission critical-suitable operating system, as we are now at the whims of the WGA servers which can decide that it's time to prevent users from getting their work done.   I don't envy the job that the WGA team has.  Anything less than 100% success is a complete failure.

  • Anonymous
    October 09, 2006
    The comment has been removed

  • Anonymous
    October 10, 2006
    The comment has been removed

  • Anonymous
    October 16, 2006
    It really isn't acceptable for a server outage to disadvantage genuine users in any way. WGA must err on the side of the end user. There should be no circumstances under which a genuine user can have their products flagged as non-genuine. If that happens, if you harm the people who are following the rules, you lose the battle of hearts and minds.

  • Anonymous
    October 23, 2006
    The attitude presented by this blog reflects my experience with dealing with a false positive on my HP laptop.  I have rectified my situation.  The things I was told to do by Microsoft was unbelieveable (all the way up to re-installing my OS).  All that matters is that I'm fixed now and have no intention of installing IE 7 or Vista (EVER). To me a false positive is never acceptable.  The fact that it can happen is reason not to do it. Bruce

  • Anonymous
    November 01, 2006
    I keep checking back to this blog to see if our gracious host will respond.  I don't see anything thus far.  I take that as a tacit admission of failure by Alex--and agreement that Windows Genuine Advantage can be dangerous to some people.

  • Anonymous
    August 25, 2007
    Find out what Social News Sites are discussing this post over at metagg.com

  • Anonymous
    August 27, 2007
    The comment has been removed

  • Anonymous
    August 31, 2007
    The comment has been removed

  • Anonymous
    September 04, 2007
    The comment has been removed