locked
WGA may be economical with the truth RRS feed

  • Question

  • FYI, Just because WGA says you need to activate and the various online MS validation tools (including the Update site) say your implementation is not genuine, it doesn't necessarily mean this is the case.

    R

    Background

    This morning the (4 year old) home PC (XP Pro) threw up a WGA screen splash saying that the machine needed to be re-activated within 3 days etc. etc. which threw me as the system hadn't been changed in 1~2 years.

    On trying to effect re-registration via the WGA screen label/pop-up failed as I had no internet connection. Investigation showed that the system had 'lost' its motherboard LAN adaptor.

    I firstly booted into the BIOS Setup to confirm that the BIOS could still find the adaptor and then booted into safe-mode and deleted/uninstalled relevant drivers, rebooted into safe-mode and re-installed drivers. This got the LAN adaptor up and running again; internet connection restored. However I was still unable to re-activate using the on-screen option given to me by the WGA screen splash. Also the MS website basically directed me to purchase Windows 7...

    Further research lead me to the article How to Backup and Restore to Preserve OEM Offline Pre-Activation When Reinstall Windows XP which gave me the command:

    "you can verify that the OEM pre-activation has been preserved by clicking Start -> Run and typing %SYSTEMROOT%\system32\oobe\msoobe.exe /A and then click OK. If the procedure was successful, a message indicating that Windows has already been activated will be displayed."

    For reasons unknown I found that this enabled me to successfully re-activate my system without any other change; a reboot then got rid of the WGA screen splash and permitted me to use Microsoft Update again (just in time to get the Office 2007 SP3 downloads ...)

     

    For Reference

    My COA is for Microsoft XP Pro / OEM Software / X11-45391.

    My MGADiag log taken prior whilst system requiring re-activation.

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Not Activated
    Validation Code: 1
    Cached Validation Code: N/A
    Windows Product Key: *****-*****-VVV79-DB3D4-BDK2Y
    Windows Product Key Hash: Nctb51ilfMqebfkOCq2/Ymo03RU=
    Windows Product ID: 76487-OEM-2260855-99732
    Windows Product ID Type: 3
    Windows License Type: OEM System Builder
    Windows OS version: 5.1.2600.2.00010100.3.0.pro
    ID: {07E04CAD-FFE7-49A1-ABAF-78300B909234}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: Registered, 1.9.42.0
    Signed By: Microsoft
    Product Name: N/A
    Architecture: N/A
    Build lab: N/A
    TTS Error: N/A
    Validation Diagnostic: 025D1FF3-230-1_025D1FF3-238-2_025D1FF3-258-3
    Resolution Status: N/A

    Vista WgaER Data-->
    ThreatID(s): N/A
    Version: N/A

    Windows XP Notifications Data-->
    Cached Result: 1
    File Exists: Yes
    Version: 1.9.40.0
    WgaTray.exe Signed By: Microsoft
    WgaLogon.dll Signed By: Microsoft

    OGA Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    Version: 2.0.48.0
    OGAExec.exe Signed By: Microsoft
    OGAAddin.dll Signed By: Microsoft

    OGA Data-->
    Office Status: 100 Genuine
    Microsoft Office Standard 2007 - 100 Genuine
    OGA Version: Registered, 2.0.48.0
    Signed By: Microsoft
    Office Diagnostics: 025D1FF3-230-1_025D1FF3-238-2_025D1FF3-258-3_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files\Internet Explorer\iexplore.exe
    Download signed ActiveX controls: Prompt
    Download unsigned ActiveX controls: Disabled
    Run ActiveX controls and plug-ins: Allowed
    Initialize and script ActiveX controls not marked as safe: Disabled
    Allow scripting of Internet Explorer Webbrowser control: Disabled
    Active scripting: Allowed
    Script ActiveX controls marked as safe for scripting: Allowed

    File Scan Data-->

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{07E04CAD-FFE7-49A1-ABAF-78300B909234}</UGUID><Version>1.9.0027.0</Version><OS>5.1.2600.2.00010100.3.0.pro</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-BDK2Y</PKey><PID>76487-OEM-2260855-99732</PID><PIDType>3</PIDType><SID>S-1-5-21-299502267-1454471165-682003330</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>1003   </Version><SMBIOSVersion major="2" minor="4"/><Date>20080325000000.000000+000</Date></BIOS><HWID>B580367F0184EE7A</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification><File Name="WgaTray.exe" Version="1.9.40.0"/><File Name="WgaLogon.dll" Version="1.9.40.0"/><File Name="OGAAddin.dll" Version="2.0.48.0"/></GANotification></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-0012-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Standard 2007</Name><Ver>12</Ver><Val>1DE47D82EDA5778</Val><Hash>0bAuuagwfnMyxVMnNRo1iGQ+T8c=</Hash><Pid>81607-956-0093277-64451</Pid><PidType>1</PidType></Product></Products><Applications><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="1A" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/></Applications></Office></Software></GenuineResults> 

    Licensing Data-->
    N/A

    Windows Activation Technologies-->
    N/A

    HWID Data-->
    N/A

    OEM Activation 1.0 Data-->
    BIOS string matches: yes
    Marker string from BIOS: 14510:ASUSTeK Computer Inc|10322:GENUINE C&C INC
    Marker string from OEMBIOS.DAT: N/A, hr = 0x80004005

    OEM Activation 2.0 Data-->
    N/A
    -----------------------------------------

    My MGADiag output after successful re-activation.

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Genuine
    Validation Code: 0
    Cached Validation Code: N/A
    Windows Product Key: *****-*****-VVV79-DB3D4-BDK2Y
    Windows Product Key Hash: Nctb51ilfMqebfkOCq2/Ymo03RU=
    Windows Product ID: 76487-OEM-2260855-99732
    Windows Product ID Type: 3
    Windows License Type: OEM System Builder
    Windows OS version: 5.1.2600.2.00010100.3.0.pro
    ID: {07E04CAD-FFE7-49A1-ABAF-78300B909234}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: Registered, 1.9.42.0
    Signed By: Microsoft
    Product Name: N/A
    Architecture: N/A
    Build lab: N/A
    TTS Error: N/A
    Validation Diagnostic: 025D1FF3-230-1
    Resolution Status: N/A

    Vista WgaER Data-->
    ThreatID(s): N/A
    Version: N/A

    Windows XP Notifications Data-->
    Cached Result: 0
    File Exists: Yes
    Version: 1.9.40.0
    WgaTray.exe Signed By: Microsoft
    WgaLogon.dll Signed By: Microsoft

    OGA Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    Version: 2.0.48.0
    OGAExec.exe Signed By: Microsoft
    OGAAddin.dll Signed By: Microsoft

    OGA Data-->
    Office Status: 100 Genuine
    Microsoft Office Standard 2007 - 100 Genuine
    OGA Version: Registered, 2.0.48.0
    Signed By: Microsoft
    Office Diagnostics: 025D1FF3-230-1

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files\Internet Explorer\iexplore.exe
    Download signed ActiveX controls: Prompt
    Download unsigned ActiveX controls: Disabled
    Run ActiveX controls and plug-ins: Allowed
    Initialize and script ActiveX controls not marked as safe: Disabled
    Allow scripting of Internet Explorer Webbrowser control: Disabled
    Active scripting: Allowed
    Script ActiveX controls marked as safe for scripting: Allowed

    File Scan Data-->

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{07E04CAD-FFE7-49A1-ABAF-78300B909234}</UGUID><Version>1.9.0027.0</Version><OS>5.1.2600.2.00010100.3.0.pro</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-BDK2Y</PKey><PID>76487-OEM-2260855-99732</PID><PIDType>3</PIDType><SID>S-1-5-21-299502267-1454471165-682003330</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>System Product Name</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>1003   </Version><SMBIOSVersion major="2" minor="4"/><Date>20080325000000.000000+000</Date></BIOS><HWID>B580367F0184EE7A</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification><File Name="WgaTray.exe" Version="1.9.40.0"/><File Name="WgaLogon.dll" Version="1.9.40.0"/><File Name="OGAAddin.dll" Version="2.0.48.0"/></GANotification></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-0012-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Standard 2007</Name><Ver>12</Ver><Val>1DE47D82EDA5778</Val><Hash>0bAuuagwfnMyxVMnNRo1iGQ+T8c=</Hash><Pid>81607-956-0093277-64451</Pid><PidType>1</PidType></Product></Products><Applications><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="1A" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/></Applications></Office></Software></GenuineResults> 

    Licensing Data-->
    N/A

    Windows Activation Technologies-->
    N/A

    HWID Data-->
    N/A

    OEM Activation 1.0 Data-->
    BIOS string matches: yes
    Marker string from BIOS: 14510:ASUSTeK Computer Inc|10322:GENUINE C&C INC
    Marker string from OEMBIOS.DAT: N/A, hr = 0x80004005

    OEM Activation 2.0 Data-->
    N/A
    -----------------------------------------

     

    Tuesday, November 8, 2011 3:35 PM

Answers

  • "RB16" wrote in message news:56969e67-94c1-4ccb-b3f9-50cf7d1a49c5...

    FYI, Just because WGA says you need to activate and the various online MS validation tools (including the Update site) say your implementation is not genuine, it doesn't necessarily mean this is the case.

     

     

    We in this forum (at least the regulars) are well aware of the many circumstances under which the OS will display a non-genuine message, or demand re-activation.
     
    In this case, the trigger was a problem with the LAN drivers.
    LAN adapters carry a higher weighting in the XP activation regime than most other parts of the base system (I like to activate with the LAN adapters switched of in BIOS for this reason – which means that I have to telephone activate), and if there are problems with these, then they can trigger a re-activation request if any other ‘base’ hardware has been changed in the past 120 days. Note that changes may include drivers updates, not just simple hardware swaps. Repairing the fault (or reinstalling the original hardware)  does not, unfortunately, reset the trigger.
     
     
    Effectively, your fix put the machine back into the state it would have been immediately after installing CP, license-wise, forcing a rebuild of the relevant license files – which enabled the activation to proceed over the internet.
    Another possible solution would have been to use the Product Key Update Tool to re-enter the Key (assuming that the machine was connected to the Internet).
    It’s also probable that Telephone activation would have worked – although they may have requested that you run another fix.
     
    The following KB articles also refer
     
     
    Thanks for posting your solution – it offers an approach to the situation that I’ve not seen laid out quite that way before, and forced me to do some research..
     
    Note, however, that your fix may have a limited applicability – it seems to depend on the system having been properly installed using a Sysprepped installer. For many users this is not an option, as their install may have been done with the bare disk.
     
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    • Marked as answer by Darin Smith MS Tuesday, November 8, 2011 11:05 PM
    Tuesday, November 8, 2011 5:27 PM
    Moderator
  • Hello RB16,

     

    Your situation was a case of your activation being "out of tolerance" for reasons of hardware changes.  The loss of the onboard NIC was the cause.  The out of tolerance grace period is 3 days.  As Noel mentioned, NICs carry a lot of weight with respect to the way Windows XP does its periodic activation checks.

    This is probably the best article regarding the nuts and bolts of Windows Product Activation:  http://aumha.org/win5/a/wpa.php

    WGA per se has nothing to do with this---the Windows installation would have acted in the exact same manner regardless of whether it had WGA installed or not.  The notifications you were presented were not WGA notifications but Activation notifications.

    There was no need to scour the internet looking for answers.  The command line you discovered, %SYSTEMROOT%\system32\oobe\msoobe.exe /A, is simply the command executed when you click on Start>All Programs>Accessories>Activate Windows.

     

    But it is good to see that you were able to diagnose the symptoms (lost NIC) and reinstall the drivers in order to reactivate.  Of course, the real question remains:  Why did your NIC drivers disappear?  But that is a question for another forum :-)



    • Edited by Dan at IT Associates Wednesday, November 9, 2011 4:42 PM
    • Marked as answer by RB16 Tuesday, November 15, 2011 2:51 AM
    Wednesday, November 9, 2011 4:40 PM

All replies

  • "RB16" wrote in message news:56969e67-94c1-4ccb-b3f9-50cf7d1a49c5...

    FYI, Just because WGA says you need to activate and the various online MS validation tools (including the Update site) say your implementation is not genuine, it doesn't necessarily mean this is the case.

     

     

    We in this forum (at least the regulars) are well aware of the many circumstances under which the OS will display a non-genuine message, or demand re-activation.
     
    In this case, the trigger was a problem with the LAN drivers.
    LAN adapters carry a higher weighting in the XP activation regime than most other parts of the base system (I like to activate with the LAN adapters switched of in BIOS for this reason – which means that I have to telephone activate), and if there are problems with these, then they can trigger a re-activation request if any other ‘base’ hardware has been changed in the past 120 days. Note that changes may include drivers updates, not just simple hardware swaps. Repairing the fault (or reinstalling the original hardware)  does not, unfortunately, reset the trigger.
     
     
    Effectively, your fix put the machine back into the state it would have been immediately after installing CP, license-wise, forcing a rebuild of the relevant license files – which enabled the activation to proceed over the internet.
    Another possible solution would have been to use the Product Key Update Tool to re-enter the Key (assuming that the machine was connected to the Internet).
    It’s also probable that Telephone activation would have worked – although they may have requested that you run another fix.
     
    The following KB articles also refer
     
     
    Thanks for posting your solution – it offers an approach to the situation that I’ve not seen laid out quite that way before, and forced me to do some research..
     
    Note, however, that your fix may have a limited applicability – it seems to depend on the system having been properly installed using a Sysprepped installer. For many users this is not an option, as their install may have been done with the bare disk.
     
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    • Marked as answer by Darin Smith MS Tuesday, November 8, 2011 11:05 PM
    Tuesday, November 8, 2011 5:27 PM
    Moderator
  • Hello RB16,

     

    Your situation was a case of your activation being "out of tolerance" for reasons of hardware changes.  The loss of the onboard NIC was the cause.  The out of tolerance grace period is 3 days.  As Noel mentioned, NICs carry a lot of weight with respect to the way Windows XP does its periodic activation checks.

    This is probably the best article regarding the nuts and bolts of Windows Product Activation:  http://aumha.org/win5/a/wpa.php

    WGA per se has nothing to do with this---the Windows installation would have acted in the exact same manner regardless of whether it had WGA installed or not.  The notifications you were presented were not WGA notifications but Activation notifications.

    There was no need to scour the internet looking for answers.  The command line you discovered, %SYSTEMROOT%\system32\oobe\msoobe.exe /A, is simply the command executed when you click on Start>All Programs>Accessories>Activate Windows.

     

    But it is good to see that you were able to diagnose the symptoms (lost NIC) and reinstall the drivers in order to reactivate.  Of course, the real question remains:  Why did your NIC drivers disappear?  But that is a question for another forum :-)



    • Edited by Dan at IT Associates Wednesday, November 9, 2011 4:42 PM
    • Marked as answer by RB16 Tuesday, November 15, 2011 2:51 AM
    Wednesday, November 9, 2011 4:40 PM
  • "Dan at IT Associates" wrote in message news:f5772db4-76b6-4fb7-85fd-d2873d69209c...

    Hello RB16,

     

    Your situation was a case of your activation being "out of tolerance" for reasons of hardware changes.  The loss of the onboard NIC was the cause.  The out of tolerance grace period is 3 days.  As Noel mentioned, NICs carry a lot of weight with respect to the way Windows XP does its periodic activation checks.

    This is probably the best article regarding the nuts and bolts of Windows Product Activation:  http://aumha.org/win5/a/wpa.php


     
     
     
    I have to admit trying to avoid mentioning the Alex Nichol article – I suspect that it’s out of date since of SP2, as Alex unfortunately passed away around the time it was released.
    There have been sporadic updates to what was at one time the definitive article on XP activation – but never a complete review and revision, and nothing at all refers to OEM_SLP activation technology.
    I knew Alex – and he was a wonderful and incredibly knowledgeable man, with time for almost anything. I know that all of his friends still miss his humour and knowledge.
     
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Wednesday, November 9, 2011 8:56 PM
    Moderator
  • Thanks for the responses Noel and Dan,

    Yes I haven't had much need to delve into Windows activation as it has in the main worked okay for me and hence this has been a very rapid skills update.

    The reason for scouring the internet for answers was that my build of XP didn't have Start>All Programs>Accessories>Activate Windows, or any other obvious way of entering a registration key - without resorting to a Windows CD (something I've only had to do once, 3~4 years back). So once I had determined that the license files had been reset, all I needed was a way of re-activating Windows XP.

    What I found surprising was that (after re-installing the LAN drivers) I still couldn't get the activation via the screen splash to work, but by directly keying in the command I was able to go online and register etc. Also the license key on my COA worked!

    Yes I've no real idea why the NIC decided to disappear when it did as I was in another room at the time and the event log gives no real hints, also the system has been rock solid (again) these last few days. However, I now know that the NIC is significant for Windows activation and I've located my spare NIC!

    I also posted this as just because you suddenly loose your activation it's not necessarily all doom and gloom as many posters on various Windows forums would have you to believe.


    • Edited by RB16 Tuesday, November 15, 2011 2:53 AM
    Tuesday, November 15, 2011 2:50 AM
  • Ho Hum! got the pulse racing today!

    Submitting a fault report for an IE add-in on the above XP system from a LUA and needed to include a 'System Information' log, so gave myself a shock to see there on the summary sheet (4th line down):

    Activation Status:        Activation Pending (30 days remaining)

    Fortunately KB 817025 (http://support.microsoft.com/kb/817025 ) explained all, so could relax again.

    Monday, November 21, 2011 9:02 PM
  • Hmmm - wonder why it only applies to XP Pro, and not Home?

    Not a problem I ever remember seeing, anyhow :)

     


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Monday, November 21, 2011 9:05 PM
    Moderator