none
Similar PID validation problem, but with endless validation loop result after new product key. RRS feed

  • Question

  • Hi,

    we purchased a streaming video server and recently got the "counterfeit" type message. Contacted MS tech support and received instructions to run MGA diagnostic, which I did. Sent report to MS tech support. Tech support instructed us to run the Windows Product Key Update tool. We did, and the instructions said to contact MS via phone to obtain a new Product Key (something about time expiration prevented us from obtaining a new product key online). Got the automated phone, gave the codes, received the new product key, entered the new product key, rebooted.  Now the system is locked in an endless validation loop (wanna validate? Yes? Already validated. Do it again... No? Saving settings... Wanna validate?... and so on.

    The original screen capture after MAGdiag ran is:

    Diagnostic Report (1.9.0011.0):

    -----------------------------------------

    WGA Data-->

    Validation Status: Blocked PID

    Validation Code: 11

     

    Cached Validation Code: N/A

    Windows Product Key: *****-*****-9C8H8-46RG3-WPBJQ

    Windows Product Key Hash: RZ3rCWWNNxbSQQxm43O6oLWj0hU=

    Windows Product ID: 76487-OEM-2268377-95277

    Windows Product ID Type: 3

    Windows License Type: OEM System Builder

    Windows OS version: 5.1.2600.2.00010100.2.0.pro

    ID: {BD6F2AAC-0056-4AA6-995E-5B91800EBEA5}(3)

    Is Admin: Yes

    TestCab: 0x0

    WGA Version: Registered, 1.9.40.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

     

    WgaER Data-->

    ThreatID(s): N/A

    Version: N/A

     

    WGA Notifications Data-->

    Cached Result: 11

    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: N/A, hr = 0x80070002

    OGAExec.exe Signed By: N/A, hr = 0x80070002

    OGAAddin.dll Signed By: N/A, hr = 0x80070002

     

    OGA Data-->

    Office Status: 109 N/A

    OGA Version: Registered, 1.7.111.0

    Signed By: Microsoft

    Office Diagnostics: B4D0AA8B-543-80070002_025D1FF3-230-1

     

    Browser Data-->

    Proxy settings: N/A

    User Agent: Mozilla/4.0 (compatible; MSIE 7.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>{BD6F2AAC-0056-4AA6-995E-5B91800EBEA5}</UGUID><Version>1.9.0011.0</Version><OS>5.1.2600.2.00010100.2.0.pro</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-WPBJQ</PKey><PID>76487-OEM-2268377-95277</PID><PIDType>3</PIDType><SID>S-1-5-21-5717656-1010840919-3742381961</SID><SYSTEM><Manufacturer>Supermicro</Manufacturer><Model>C2SBA</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies LTD</Manufacturer><Version>6.00</Version><SMBIOSVersion major="2" minor="5"/><Date>20080110000000.000000+000</Date></BIOS><HWID>F73A0CF00184AA6B</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05: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"/></GANotification></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults>  

     

    Licensing Data-->

    N/A

     

    HWID Data-->

    N/A

     

    OEM Activation 1.0 Data-->

    BIOS string matches: no

    Marker string from BIOS: N/A

    Marker string from OEMBIOS.DAT: N/A, hr = 0x80004005

     

    OEM Activation 2.0 Data-->

    N/A



    My case # is Microsoft Incident: SRX1108808325

    We haven't got a response yet. 

    Can anyone help?

    Thanks.


    Tuesday, August 18, 2009 2:33 AM

Answers

  • Hello stefteach,

    Assuming the CD you have is a genuine OEM CD for XP Pro (navigate to the \386 folder on the CD, look for the small text file "setupp.ini," and verify that the last three characters of the Pid=value are "OEM"), then run a repair reinstallation per http://michaelstevenstech.com/XPrepairinstall.htm.

    The repair is designed to preserve data and installed programs, but it would be a good idea to backup your data just in case there's a problem. 
    For great advice on all topics XP, visit http://www.annoyances.org/exec/forum/winxp
    Tuesday, August 18, 2009 4:23 PM

All replies

  • It seems like even if you buy a key to fix the problem, the keys you get seems to have the same problem.

    Has something gone wrong for so many xp machine to have the same problem?

    Tuesday, August 18, 2009 6:23 AM
  • Hello stefteach,

    This is the partial product key currently installed:   *****-*****-9C8H8-46RG3-WPBJQ

    Does this match the product key on your Certificate of Authenticity?
    For great advice on all topics XP, visit http://www.annoyances.org/exec/forum/winxp
    Tuesday, August 18, 2009 2:17 PM
  • Hi Dan,

    nope, it doesn't.. the product key on the sticker is different.

    I tried already to remove the two WMA files and run oobe.exe replacing the product key but no success. The validation screen does not contain the codes necessary for an over-the-phone validation.

    Stefano
    Tuesday, August 18, 2009 3:20 PM
  • Hello stefteach,

    Assuming the CD you have is a genuine OEM CD for XP Pro (navigate to the \386 folder on the CD, look for the small text file "setupp.ini," and verify that the last three characters of the Pid=value are "OEM"), then run a repair reinstallation per http://michaelstevenstech.com/XPrepairinstall.htm.

    The repair is designed to preserve data and installed programs, but it would be a good idea to backup your data just in case there's a problem. 
    For great advice on all topics XP, visit http://www.annoyances.org/exec/forum/winxp
    Tuesday, August 18, 2009 4:23 PM
  • Hi Dan,

    got the problem resolved by MS tech... forked out the $49.95 and got a new Product key. 
    Tuesday, August 18, 2009 5:27 PM
  • Hello stefteach,

    Glad you got it fixed!  :-)

    Although we never got to the point where we were sure that you absolutely needed a new PK and that was the only way you were going to be fixed.
    For great advice on all topics XP, visit http://www.annoyances.org/exec/forum/winxp
    Wednesday, August 19, 2009 2:20 PM