locked
Please Confirm if MSDN Key RRS feed

  • Question

  • I may be overly cautious, but I read on the other thread that if you have a PID close to "065,066,067 for Ultimate" that it may be a MSDN Key. I also recent purchased a what appeared to be a full retail version of Ultimate from someone on Ebay. My PID is "068" which is close so I am concerned. Although everything seems to be working now, I don't want Microsoft to tell me my key is not valid 90 days later (as some other person has posted). Please confirm whether or not it may be possible that this can be a MSDN key. I have pasted the MGADIAG tool below.

    Thanks very much in advance!

    Diagnostic Report (1.9.0027.0):

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

    Windows Validation Data-->

     

    Validation Code: 0

    Cached Online Validation Code: N/A, hr = 0xc004f012

    Windows Product Key: *****-*****-W7MVJ-Y7G6V-TMR6K

    Windows Product Key Hash: 94wP31FqASsPxAP2+RYXUgNRtGM=

    Windows Product ID: 00426-068-0149106-86413

    Windows Product ID Type: 5

    Windows License Type: Retail

    Windows OS version: 6.1.7600.2.00010100.0.0.001

    ID: {E0C2BAE2-D1CE-4C80-A8C4-9E7FE7613498}(1)

    Is Admin: Yes

    TestCab: 0x0

    LegitcheckControl ActiveX: N/A, hr = 0x80070002

    Signed By: N/A, hr = 0x80070002

    Product Name: Windows 7 Ultimate

    Architecture: 0x00000009

    Build lab: 7600.win7_gdr.100618-1621

    TTS Error:

    Validation Diagnostic:

    Resolution Status: N/A

     

    Vista WgaER Data-->

    ThreatID(s): N/A, hr = 0x80070002

    Version: N/A, hr = 0x80070002

     

    Windows XP Notifications Data-->

    Cached Result: N/A, hr = 0x80070002

    File Exists: No

    Version: N/A, hr = 0x80070002

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

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

     

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

    Signed By: N/A, hr = 0x80070002

    Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

     

    Browser Data-->

    Proxy settings: N/A

    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)

    Default Browser: C:\Program Files (x86)\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>{E0C2BAE2-D1CE-4C80-A8C4-9E7FE7613498}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-TMR6K</PKey><PID>00426-068-0149106-86413</PID><PIDType>5</PIDType><SID>S-1-5-21-1447596398-469862465-2349232010</SID><SYSTEM><Manufacturer>MSI</Manufacturer><Model>MS-7522</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>V7.1</Version><SMBIOSVersion major="2" minor="5"/><Date>20090218000000.000000+000</Date></BIOS><HWID>A9BA3607018400FE</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/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults> 

     

    Spsys.log Content: 0x80070002

     

    Licensing Data-->

    Software licensing service version: 6.1.7600.16385

     

    Name: Windows(R) 7, Ultimate edition

    Description: Windows Operating System - Windows(R) 7, RETAIL channel

    Activation ID: a0cde89c-3304-4157-b61c-c8ad785d1fad

    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f

    Extended PID: 00426-00172-068-014910-00-1033-7600.0000-2932010

    Installation ID: 018062083545330863332026756761743030228044658703813444

    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338

    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339

    Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341

    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340

    Partial Product Key: TMR6K

    License Status: Licensed

    Remaining Windows rearm count: 3

    Trusted time: 10/21/2010 1:07:21 AM

     

    Windows Activation Technologies-->

    HrOffline: 0x00000000

    HrOnline: N/A

    HealthStatus: 0x0000000000000000

    Event Time Stamp: N/A

    ActiveX: Registered, Version: 7.1.7600.16395

    Admin Service: Registered, Version: 7.1.7600.16395

    HealthStatus Bitmask Output:

     

     

    HWID Data-->

    HWID Hash Current: NAAAAAEABgABAAEAAAABAAAAAQABAAEAonZ25pyc4mdGvIrVhDQIhRIf+mgyW2qN6g7qgg==

     

    OEM Activation 1.0 Data-->

    N/A

     

    OEM Activation 2.0 Data-->

    BIOS valid for OA 2.0: yes, but no SLIC table

    Windows marker version: N/A

    OEMID and OEMTableID Consistent: N/A

    BIOS Information:

      ACPI Table Name  OEMID Value            OEMTableID Value

      APIC                          7522MS                      A7522700

      FACP                                    7522MS                      A7522700

      MCFG                                    7522MS                      OEMMCFG

      OEMB                                   7522MS                      A7522700

      SSDT                                    DpgPmm                  CpuPm

    Thursday, October 21, 2010 5:33 AM

Answers

  • I may be overly cautious, but I read on the other thread that if you have a PID close to "065,066,067 for Ultimate" that it may be a MSDN Key. I also recent purchased a what appeared to be a full retail version of Ultimate from someone on Ebay. My PID is "068" which is close so I am concerned. Although everything seems to be working now, I don't want Microsoft to tell me my key is not valid 90 days later (as some other person has posted). Please confirm whether or not it may be possible that this can be a MSDN key. I have pasted the MGADIAG tool below.

    Thanks very much in advance!

    Diagnostic Report (1.9.0027.0):

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

    Windows Validation Data-->

     

    Validation Code: 0

    Cached Online Validation Code: N/A, hr = 0xc004f012

    Windows Product Key: *****-*****-W7MVJ-Y7G6V-TMR6K

    Windows Product Key Hash: 94wP31FqASsPxAP2+RYXUgNRtGM=

    Windows Product ID: 00426-068-0149106-86413

    Windows Product ID Type: 5

    Windows License Type: Retail

    Windows OS version: 6.1.7600.2.00010100.0.0.001

    Yep - I'm afraid this is almost certainly a not-for-resale key form an MSDN-style account.
    I suggest that you claim a full refund from the vendor - do NOT accept a replacement Key, as it will almost certainly be of the same kind.
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    • Proposed as answer by Darin Smith MS Thursday, October 21, 2010 8:57 PM
    • Marked as answer by Darin Smith MS Thursday, October 21, 2010 8:57 PM
    Thursday, October 21, 2010 7:12 AM
    Moderator
  • I can confirm that Noel is correct, the key is from MSDN.
    David
    Microsoft Answers Support Engineer
    Visit our Microsoft Answers Feedback Forum and let us know what you think.
    • Marked as answer by Darin Smith MS Thursday, October 21, 2010 8:57 PM
    Thursday, October 21, 2010 8:39 PM
    Moderator

All replies

  • I may be overly cautious, but I read on the other thread that if you have a PID close to "065,066,067 for Ultimate" that it may be a MSDN Key. I also recent purchased a what appeared to be a full retail version of Ultimate from someone on Ebay. My PID is "068" which is close so I am concerned. Although everything seems to be working now, I don't want Microsoft to tell me my key is not valid 90 days later (as some other person has posted). Please confirm whether or not it may be possible that this can be a MSDN key. I have pasted the MGADIAG tool below.

    Thanks very much in advance!

    Diagnostic Report (1.9.0027.0):

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

    Windows Validation Data-->

     

    Validation Code: 0

    Cached Online Validation Code: N/A, hr = 0xc004f012

    Windows Product Key: *****-*****-W7MVJ-Y7G6V-TMR6K

    Windows Product Key Hash: 94wP31FqASsPxAP2+RYXUgNRtGM=

    Windows Product ID: 00426-068-0149106-86413

    Windows Product ID Type: 5

    Windows License Type: Retail

    Windows OS version: 6.1.7600.2.00010100.0.0.001

    Yep - I'm afraid this is almost certainly a not-for-resale key form an MSDN-style account.
    I suggest that you claim a full refund from the vendor - do NOT accept a replacement Key, as it will almost certainly be of the same kind.
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    • Proposed as answer by Darin Smith MS Thursday, October 21, 2010 8:57 PM
    • Marked as answer by Darin Smith MS Thursday, October 21, 2010 8:57 PM
    Thursday, October 21, 2010 7:12 AM
    Moderator
  • I can confirm that Noel is correct, the key is from MSDN.
    David
    Microsoft Answers Support Engineer
    Visit our Microsoft Answers Feedback Forum and let us know what you think.
    • Marked as answer by Darin Smith MS Thursday, October 21, 2010 8:57 PM
    Thursday, October 21, 2010 8:39 PM
    Moderator
  • Thanks for all the replies. I have already requested my refund. I was lucky that I did the research here before it was too late.

    To everyone reading this that might be in the same situation. Be Careful! These packages look like retail. In fact, they were probably packaged and distributed by Microsoft. It had everything: 2 original Microsoft installation discs, Certificate of Authenticity, a small booklet with info and tips, sticker with the product activation code. I was able to activated it with no issues. There would have been no reason for me to believe that it was a MSDN Key that was not meant for resale, other than the slightly lower price.

    To Microsoft: Firstly, if this was package was indeed distributed by Microsoft, then the blame is on them. How hard is it to put a warning on the product key and on that packaging that states, "This is a MSDN Key, NOT FOR RESALE?" Secondly, even if they didn't package it, they would still be at fault for not letting people know this fact when the key was activated. It would have been very easy for them to tell users that it was a MSDN Key (and who is meant to use it) when someone tries to activate it. If Microsoft did this one thing alone, they would have stopped a LOT of the piracy issues right there. This forum is already full of upset people that had their copies of Windows no longer valid after 60-90 days. Sadly, there's usually nothing they can do about it after so long. Worse part of all this is that Microsoft knew about this way back in April and probably way before that! Why not put a stop to it and try to help some of the scammed people going forward?

    Good luck!

     

    Saturday, October 23, 2010 4:58 AM
  • Thanks for all the replies. I have already requested my refund. I was lucky that I did the research here before it was too late.

    To everyone reading this that might be in the same situation. Be Careful! These packages look like retail. In fact, they were probably packaged and distributed by Microsoft. It had everything: 2 original Microsoft installation discs, Certificate of Authenticity, a small booklet with info and tips, sticker with the product activation code. I was able to activated it with no issues. There would have been no reason for me to believe that it was a MSDN Key that was not meant for resale, other than the slightly lower price.

    To Microsoft: Firstly, if this was package was indeed distributed by Microsoft, then the blame is on them. How hard is it to put a warning on the product key and on that packaging that states, "This is a MSDN Key, NOT FOR RESALE?" Secondly, even if they didn't package it, they would still be at fault for not letting people know this fact when the key was activated. It would have been very easy for them to tell users that it was a MSDN Key (and who is meant to use it) when someone tries to activate it. If Microsoft did this one thing alone, they would have stopped a LOT of the piracy issues right there. This forum is already full of upset people that had their copies of Windows no longer valid after 60-90 days. Sadly, there's usually nothing they can do about it after so long. Worse part of all this is that Microsoft knew about this way back in April and probably way before that! Why not put a stop to it and try to help some of the scammed people going forward?

    Good luck!

     


    It's unlikely that MS did the distribution - the problem may be either that the counterfeit software is manufactured in the same plant as the genuine one and stolen off the line, or that the forgery is so good that you may not be able to see the difference. Some copies really are that good.
     
    I'll try to explain why there is a lag between your purchase, and a notification.... (this is my reasoning, and not certain knowledge)
    MSDN keys are issued electronically to members of the MSDN/TechNet/BizSpark programs - and are meant for use only by the owner of the subscription. They are valid for a higher number of activations than normal licenses, and the more clever pirates ensure that they don't exceed the number for any given key until they've made a vast profit, and this can take weeks, if not months. One day, an install will trigger a flag at MS , which then starts the checking process, and MS will eventually block all keys for that subscription. This can take a few more weeks. The validation servers then have to be updated with the blocked keys - which may be done only in batches, rather than individually. It's only then that new installs will find activation with these keys impossible, and that validation will fail.
     
    HTH?
    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Saturday, October 23, 2010 8:19 AM
    Moderator