locked
Windows 7 Ultimate key blocked? RRS feed

  • Question

  • G'day all.

    Now, I'm 99.99% positive that I am using an MSDN generated key. I've been using it since September last year (2009) with no problems. But suddenly, I get this pop-up from the System Tray that my copy of Windows is not genuine? Upon seeing such a thing, it made me very upset. Realising this is a mistake, I decided to research into this and found several tools from Microsoft that determined whether my copy of Windows was indeed a genuine copy. All resulted in false: it was not a genuine copy.

    After some further research, the "Windows is not genuine" may not be technically correct, as any other non-Genuine Microsoft software on a computer may trigger such an alert. However, this is again not the case. The only Microsoft software products I have are: Microsoft Office 2010 BETA and Microsoft Visual Studio 2010 Ultimate BETA; nothing else (apart from Windows of course).

    I can earnestly admit that I have shared this key once, but it was with another computer in my household (which I rarely use).

    So, what do I do now?

    What are the disadvantages of leaving this "non-Genuine" copy of Windows the way it is? Will it not boot after about one week, or what? Is there a severe performance impact?

    Thanks to all :)

     

    EDIT: Here is an MGADiag.exe report:

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->

    Validation Code: 50
    Cached Online Validation Code: 0xc004c4a2
    Windows Product Key: *****-*****-7XCVX-DX9GQ-79YTX
    Windows Product Key Hash: 9os/ADrk057spJn8mlOBcnn7wgo=
    Windows Product ID: 00426-067-0987855-86919
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7600.2.00010100.0.0.001
    ID: {29BC5A33-20A8-43DA-9ED0-96E31A92786C}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Ultimate
    Architecture: 0x00000000
    Build lab: 7600.win7_gdr.100226-1909
    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: X:\Program Files\Mozilla Firefox\firefox.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>{29BC5A33-20A8-43DA-9ED0-96E31A92786C}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.001</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-79YTX</PKey><PID>00426-067-0987855-86919</PID><PIDType>5</PIDType><SID>S-1-5-21-62562211-1119618285-2105335500</SID><SYSTEM><Manufacturer>Acer      </Manufacturer><Model>Aspire 5720Z    </Model></SYSTEM><BIOS><Manufacturer>Acer     </Manufacturer><Version>V1.45</Version><SMBIOSVersion major="2" minor="4"/><Date>20081110000000.000000+000</Date></BIOS><HWID>03B83607018400EA</HWID><UserLCID>0C09</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>AUS Eastern Standard Time(GMT+10:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>ACRSYS</OEMID><OEMTableID>ACRPRDCT</OEMTableID></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-067-098785-00-3081-7600.0000-0702010
    Installation ID: 002130240084080575863772515192131114813780551590047220
    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: 79YTX
    License Status: Notification
    Notification Reason: 0xC004F200 (non-genuine).
    Remaining Windows rearm count: 3
    Trusted time: 10/06/2010 8:42:17 PM

    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0xC004C4A2
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 6:10:2010 20:12
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:


    HWID Data-->
    HWID Hash Current: OAAAAAEABQABAAIAAAABAAAAAwABAAEAnJ+uWGTQQP9Gg4IPBgxCuOwdajsK4bJLaoWOC3oHKoU=

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes
    Windows marker version: 0x0
    OEMID and OEMTableID Consistent: yes
    BIOS Information:
      ACPI Table Name    OEMID Value    OEMTableID Value
      APIC            ACRSYS        ACRPRDCT
      FACP            ACRSYS        ACRPRDCT
      HPET            ACRSYS        ACRPRDCT
      MCFG            ACRSYS        ACRPRDCT
      SLIC            ACRSYS        ACRPRDCT
      SSDT            PmRef        CpuPm
      SSDT            PmRef        CpuPm
      SSDT            PmRef        CpuPm


    Thursday, June 10, 2010 10:40 AM

Answers

  • "Mayazcherquoi" wrote in message news:5fca1ca0-60f2-4517-bb82-22c69cbc7d04...

    G'day all.

    Now, I'm 99.99% positive that I am using an MSDN generated key. I've been using it since September last year (2009) with no problems. But suddenly, I get this pop-up from the System Tray that my copy of Windows is not genuine? Upon seeing such a thing, it made me very upset. Realising this is a mistake, I decided to research into this and found several tools from Microsoft that determined whether my copy of Windows was indeed a genuine copy. All resulted in false: it was not a genuine copy.

    After some further research, the "Windows is not genuine" may not be technically correct, as any other non-Genuine Microsoft software on a computer may trigger such an alert. However, this is again not the case. The only Microsoft software products I have are: Microsoft Office 2010 BETA and Microsoft Visual Studio 2010 Ultimate BETA; nothing else (apart from Windows of course).

    I can earnestly admit that I have shared this key once, but it was with another computer in my household (which I rarely use).

    So, what do I do now?

    What are the disadvantages of leaving this "non-Genuine" copy of Windows the way it is? Will it not boot after about one week, or what? Is there a severe performance impact?

    Thanks to all :)

     

    EDIT: Here is an MGADiag.exe report:

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->

    Validation Code: 50
    Cached Online Validation Code: 0xc004c4a2
    Windows Product Key: *****-*****-7XCVX-DX9GQ-79YTX
    Windows Product Key Hash: 9os/ADrk057spJn8mlOBcnn7wgo=
    Windows Product ID: 00426-067-0987855-86919
    Windows Product ID Type: 5
    Windows License Type: Retail

    Other non-Genuine software will trigger an appropriate alert
     
    Yes it's an MSDN Key, so it doesn't matter how many times you've shared it - it's Blocked on all computers that you shared it with.
     
    Whoever sold it to you did so in breach of the MSDN license, and you should chase them for a refund, and notify MS of the details of the transaction. You may feel inclined to involve the police (or the FBI in the US - it's a federal crime).
     
    Your Office install is not showing on the MGADiag - have you tried Validating that?
    Offhand, apart from the background, I don't think there's much consequence except for the inability to download or install any MS product that requires Validation. This may change in the future (or I may have it wrong now), if MS decide to do so.
     
    A reminder - the License is for ONE installation on ONE PC.
     
    If you read the Stickies and Announcements at the top of the forum Index page, you can get more details of options, etc.
     
    HTH

    --
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Thursday, June 10, 2010 11:57 AM
    Moderator
  • Hello Mayazcherquoi,

    MSDN product keys are purchased by individuals under a licensing agreement which prohibits the sale of the keys and places strict limitations on how the keys can be distributed and used.

    An MSDN subscription is for a finite term.  Most MSDN subscriptions confer perpetual usage rights, but only to the subscriber and only for product that was available during the term of the subscription.  Some product under some MSDN programs do not confer perpetual useage rights.

    So either your source was way more generous with their MSDN keys than they let on to you (assuming they are the original holders of the keys and not themselves the beneficiary of a gift of MSDN keys from someone else or six someone elses up the chain, or the keys may have expired.   


    Buy Office 2007 Now, Get Office 2010 Free http://office2010.microsoft.com/en-us/tech-guarantee/microsoft-office-2010-technology-guarantee-FX101825695.aspx?CTT=97
    Thursday, June 10, 2010 12:50 PM

All replies

  • "Mayazcherquoi" wrote in message news:5fca1ca0-60f2-4517-bb82-22c69cbc7d04...

    G'day all.

    Now, I'm 99.99% positive that I am using an MSDN generated key. I've been using it since September last year (2009) with no problems. But suddenly, I get this pop-up from the System Tray that my copy of Windows is not genuine? Upon seeing such a thing, it made me very upset. Realising this is a mistake, I decided to research into this and found several tools from Microsoft that determined whether my copy of Windows was indeed a genuine copy. All resulted in false: it was not a genuine copy.

    After some further research, the "Windows is not genuine" may not be technically correct, as any other non-Genuine Microsoft software on a computer may trigger such an alert. However, this is again not the case. The only Microsoft software products I have are: Microsoft Office 2010 BETA and Microsoft Visual Studio 2010 Ultimate BETA; nothing else (apart from Windows of course).

    I can earnestly admit that I have shared this key once, but it was with another computer in my household (which I rarely use).

    So, what do I do now?

    What are the disadvantages of leaving this "non-Genuine" copy of Windows the way it is? Will it not boot after about one week, or what? Is there a severe performance impact?

    Thanks to all :)

     

    EDIT: Here is an MGADiag.exe report:

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->

    Validation Code: 50
    Cached Online Validation Code: 0xc004c4a2
    Windows Product Key: *****-*****-7XCVX-DX9GQ-79YTX
    Windows Product Key Hash: 9os/ADrk057spJn8mlOBcnn7wgo=
    Windows Product ID: 00426-067-0987855-86919
    Windows Product ID Type: 5
    Windows License Type: Retail

    Other non-Genuine software will trigger an appropriate alert
     
    Yes it's an MSDN Key, so it doesn't matter how many times you've shared it - it's Blocked on all computers that you shared it with.
     
    Whoever sold it to you did so in breach of the MSDN license, and you should chase them for a refund, and notify MS of the details of the transaction. You may feel inclined to involve the police (or the FBI in the US - it's a federal crime).
     
    Your Office install is not showing on the MGADiag - have you tried Validating that?
    Offhand, apart from the background, I don't think there's much consequence except for the inability to download or install any MS product that requires Validation. This may change in the future (or I may have it wrong now), if MS decide to do so.
     
    A reminder - the License is for ONE installation on ONE PC.
     
    If you read the Stickies and Announcements at the top of the forum Index page, you can get more details of options, etc.
     
    HTH

    --
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Thursday, June 10, 2010 11:57 AM
    Moderator
  • "Mayazcherquoi" wrote in message news:5fca1ca0-60f2-4517-bb82-22c69cbc7d04 ...

    G'day all.

    Now, I'm 99.99% positive that I am using an MSDN generated key. I've been using it since September last year (2009) with no problems. But suddenly, I get this pop-up from the System Tray that my copy of Windows is not genuine? Upon seeing such a thing, it made me very upset. Realising this is a mistake, I decided to research into this and found several tools from Microsoft that determined whether my copy of Windows was indeed a genuine copy. All resulted in false: it was not a genuine copy.

    After some further research, the "Windows is not genuine" may not be technically correct, as any other non-Genuine Microsoft software on a computer may trigger such an alert. However, this is again not the case. The only Microsoft software products I have are: Microsoft Office 2010 BETA and Microsoft Visual Studio 2010 Ultimate BETA; nothing else (apart from Windows of course).

    I can earnestly admit that I have shared this key once, but it was with another computer in my household (which I rarely use).

    So, what do I do now?

    What are the disadvantages of leaving this "non-Genuine" copy of Windows the way it is? Will it not boot after about one week, or what? Is there a severe performance impact?

    Thanks to all :)

     

    EDIT: Here is an MGADiag.exe report:

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->

    Validation Code: 50
    Cached Online Validation Code: 0xc004c4a2
    Windows Product Key: *****-*****-7XCVX-DX9GQ-79YTX
    Windows Product Key Hash: 9os/ADrk057spJn8mlOBcnn7wgo=
    Windows Product ID: 00426-067-0987855-86919
    Windows Product ID Type: 5
    Windows License Type: Retail

    Other non-Genuine software will trigger an appropriate alert
     
    Yes it's an MSDN Key, so it doesn't matter how many times you've shared it - it's Blocked on all computers that you shared it with.
     
    Whoever sold it to you did so in breach of the MSDN license, and you should chase them for a refund, and notify MS of the details of the transaction. You may feel inclined to involve the police (or the FBI in the US - it's a federal crime).
     
    Your Office install is not showing on the MGADiag - have you tried Validating that?
    Offhand, apart from the background, I don't think there's much consequence except for the inability to download or install any MS product that requires Validation. This may change in the future (or I may have it wrong now), if MS decide to do so.
     
    A reminder - the License is for ONE installation on ONE PC.
     
    If you read the Stickies and Announcements at the top of the forum Index page, you can get more details of options, etc.
     
    HTH

    --
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

    Hang on,

    First I would like to know why it was blocked, please :) Is it possible for you to tell me of that? Is it because I used it twice?

    Thursday, June 10, 2010 12:15 PM
  • Hello Mayazcherquoi,

    You can probably answer your question by answering this:

    From where or whom did you acquire or purchase the product key?  And did you purchase just the product key, or did it come with materials such as a retail box, a Certificate of Authenticity, one or two hologrammed installations discs, a yellow-orange Proof of License label with this exact product key printed on it?


    Buy Office 2007 Now, Get Office 2010 Free http://office2010.microsoft.com/en-us/tech-guarantee/microsoft-office-2010-technology-guarantee-FX101825695.aspx?CTT=97
    Thursday, June 10, 2010 12:28 PM
  • Hello Mayazcherquoi,

    You can probably answer your question by answering this:

    From where or whom did you acquire or purchase the product key?  And did you purchase just the product key, or did it come with materials such as a retail box, a Certificate of Authenticity, one or two hologrammed installations discs, a yellow-orange Proof of License label with this exact product key printed on it?


    Buy Office 2007 Now, Get Office 2010 Free http://office2010.microsoft.com/en-us/tech-guarantee/microsoft-office-2010-technology-guarantee-FX101825695.aspx?CTT=97


    Hello :)

    I didn't purchase it. I got given it. However, I was 100% assured that the key was not given to anyone else and solely to me. It has been working so well up until now :(

    Thursday, June 10, 2010 12:42 PM
  • "Mayazcherquoi" wrote in message news:bc2285de-1497-4ea1-ac66-08bf8d174506...
    "Mayazcherquoi" wrote in message news:5fca1ca0-60f2-4517-bb82-22c69cbc7d04 ...

    G'day all.

    Now, I'm 99.99% positive that I am using an MSDN generated key. I've been using it since September last year (2009) with no problems. But suddenly, I get this pop-up from the System Tray that my copy of Windows is not genuine? Upon seeing such a thing, it made me very upset. Realising this is a mistake, I decided to research into this and found several tools from Microsoft that determined whether my copy of Windows was indeed a genuine copy. All resulted in false: it was not a genuine copy.

    After some further research, the "Windows is not genuine" may not be technically correct, as any other non-Genuine Microsoft software on a computer may trigger such an alert. However, this is again not the case. The only Microsoft software products I have are: Microsoft Office 2010 BETA and Microsoft Visual Studio 2010 Ultimate BETA; nothing else (apart from Windows of course).

    I can earnestly admit that I have shared this key once, but it was with another computer in my household (which I rarely use).

    So, what do I do now?

    What are the disadvantages of leaving this "non-Genuine" copy of Windows the way it is? Will it not boot after about one week, or what? Is there a severe performance impact?

    Thanks to all :)

     

    EDIT: Here is an MGADiag.exe report:

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->

    Validation Code: 50
    Cached Online Validation Code: 0xc004c4a2
    Windows Product Key: *****-*****-7XCVX-DX9GQ-79YTX
    Windows Product Key Hash: 9os/ADrk057spJn8mlOBcnn7wgo=
    Windows Product ID: 00426-067-0987855-86919
    Windows Product ID Type: 5
    Windows License Type: Retail

    Other non-Genuine software will trigger an appropriate alert
     
    Yes it's an MSDN Key, so it doesn't matter how many times you've shared it - it's Blocked on all computers that you shared it with.
     
    Whoever sold it to you did so in breach of the MSDN license, and you should chase them for a refund, and notify MS of the details of the transaction. You may feel inclined to involve the police (or the FBI in the US - it's a federal crime).
     
    Your Office install is not showing on the MGADiag - have you tried Validating that?
    Offhand, apart from the background, I don't think there's much consequence except for the inability to download or install any MS product that requires Validation. This may change in the future (or I may have it wrong now), if MS decide to do so.
     
    A reminder - the License is for ONE installation on ONE PC.
     
    If you read the Stickies and Announcements at the top of the forum Index page, you can get more details of options, etc.
     
    HTH

    --
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

    Hang on,

    First I would like to know why it was blocked, please :) Is it possible for you to tell me of that? Is it because I used it twice?


    Read my reply - I explain that - although not in detail.
    MSDN subscribers pay MS for the ability to use many items of software at once, probably in temporary installations. As such they need to be able to reactivate their machine more than the average user, so they are allowed more activations than the average user. As a result, the fakers have taken to buying MSDN subscriptions, and selling all the keys they can as fast as they can - and after a certain point, the keys start getting blocked for overuse.
    Part of the MSDN license states that the Subscriber is in NO WAY allowed to sell or give away any of their licenses, and that the licenses are intended for 'non-production use only' Non-production use is the evaluation and development of software in a controlled environment - not general-purpose use in a live machine by an end-user.
    The person who sold you this Key is therefore in breach of the license, and the key is invalidated by that fact, even if not by the overuse it's received.

    --
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Thursday, June 10, 2010 12:45 PM
    Moderator
  • Hello Mayazcherquoi,

    MSDN product keys are purchased by individuals under a licensing agreement which prohibits the sale of the keys and places strict limitations on how the keys can be distributed and used.

    An MSDN subscription is for a finite term.  Most MSDN subscriptions confer perpetual usage rights, but only to the subscriber and only for product that was available during the term of the subscription.  Some product under some MSDN programs do not confer perpetual useage rights.

    So either your source was way more generous with their MSDN keys than they let on to you (assuming they are the original holders of the keys and not themselves the beneficiary of a gift of MSDN keys from someone else or six someone elses up the chain, or the keys may have expired.   


    Buy Office 2007 Now, Get Office 2010 Free http://office2010.microsoft.com/en-us/tech-guarantee/microsoft-office-2010-technology-guarantee-FX101825695.aspx?CTT=97
    Thursday, June 10, 2010 12:50 PM

  • Read my reply - I explain that - although not in detail.
    MSDN subscribers pay MS for the ability to use many items of software at once, probably in temporary installations. As such they need to be able to reactivate their machine more than the average user, so they are allowed more activations than the average user. As a result, the fakers have taken to buying MSDN subscriptions, and selling all the keys they can as fast as they can - and after a certain point, the keys start getting blocked for overuse.
    Part of the MSDN license states that the Subscriber is in NO WAY allowed to sell or give away any of their licenses, and that the licenses are intended for 'non-production use only' Non-production use is the evaluation and development of software in a controlled environment - not general-purpose use in a live machine by an end-user.
    The person who sold you this Key is therefore in breach of the license, and the key is invalidated by that fact, even if not by the overuse it's received.

    --
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

    Ohhh. Damn. This sucks then.

    So MSDN generated keys have a set time period before they become blocked?

    There are two options for me then:
    1) is to revert to Windows Vista Home Premium :( Which my laptop (Acer Aspire 5720Z) is improperly equipped to run such a resource-intensive operating system (no joke, not even with all tweaks I've applied).
    2) is to install a Linux-based operating system (eww)..

     

    Thank you Dan and Mr. Noel Paton for replying to this everyday and allowing me to completely understand my situation :) Really appreciated :)

    Thursday, June 10, 2010 12:55 PM
  • Hello Mayazcherquoi,

    Third option:  Put your original Vista back onto your Acer, then buy a Genuine upgrade to W7 from a reliable source.


    Buy Office 2007 Now, Get Office 2010 Free http://office2010.microsoft.com/en-us/tech-guarantee/microsoft-office-2010-technology-guarantee-FX101825695.aspx?CTT=97
    Thursday, June 10, 2010 12:59 PM
  • "Mayazcherquoi" wrote in message news:83573585-1bc8-4767-b4d7-78221bda18b3...
    So MSDN generated keys have a set time period before they become blocked?

    No! Like all Licenses they are perpetual - and will become blocked if abused.
     
    There is NO time limit mentioned anywhere in my explanation.

    --
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Thursday, June 10, 2010 4:26 PM
    Moderator