locked
Windows 7 - invalid License after running Genuine Advantage Tools RRS feed

  • Question

  • Hi everyone, 
    the Windows 7 Genuine Advantage Tools decided that my Windows 7 License is no longer Valid.
    Validation Code: 50 

    I'm using Windows 7 Professional in a Upgraded Version and my License indeed is valid.
    As I need Windows 7 as an Software Engineer I think about taking legal steps for that issue.

    Regards from Germany






    Wednesday, March 3, 2010 10:01 AM

Answers

  • Hello Anonym_123456789,

    Your copy of Windows 7 is using an OEM SLP key.  This type of key only comes win Windows that come pre-installed in a computer built by a large manufacturer.

    When an OEM SLP key is in uses, Windows looks to the Bios on the computer's motherboard for a OEM Bios Flag. An OEM Bios Flag is information found only in the bios of computers built by a large manufacturer that come with Windows pre-installed. An OEM Bios Flag is specific to the Manufacturer and the version of Windows it's good for. So, If Windows is using an OEM SLP key and the Proper OEM Bios Flag is present in the computer's Bios, Windows will self-activate.

    Your Diagnostic Report shows that your computer does have a OEM Bios Flag so it did come with Windows pre-installed.  But the flag is am older one which suggests that your computer origianlly came with Vista.

    You have said this copy of Windows 7 was an Upgrade install. However, no copy of Windows (other then ones that come pre-installed in a computer built by a large manufatuere) would come with an OEM SLP key.  From the discripton of how OEM SLP key work, you can understand why.

    There are activation hacks (known as OEM Bios Hacks) avaliable on the internet (and sometimes sold, on a disk, as Genuine Windows) that when installed it makes Windows think that the Proper OEM Bios Flag is in the motherboards bios when it is not. This Hack plus an OEM SLP cause Windows to self-activate without needing a Valid Product key.

    Microsoft recently release an Update that makes Windows 7 ignore 70+ Activation Hacks (including many OEM Bios Hacks).

    To summarize:

    We know that your Upgrade version of Windows 7 was installed using a Product key that only comes in Windows 7 that come Pre-installed on a computer built by a large manufacturer. The key will not allow Windows 7 to run on any computer that does not have the proper OEM Bios Flag and the only computers that come with that proper OEM Bios Flag are ones that come with Windows 7 pre-installed.

    We know that your copy of Windows did, in fact, worked for some time.

    We know there are OEM Bios Hacks that can allow computer that lack the required OEM Blos Flag to run Windows that are using a OEM SLP key

    We know that Microsoft recently release an update that makes Windows ignore many known OEM Bios Hacks.

    And we know that around the same time Microsoft release this update, your Windows 7 stopped working and shows as Not Activated and Non-Genuine.

    Diagnosis:

    Because of these things, the logical conclusion is that your Windows 7 was using a OEM Bios Hack. Further, it is likely that the Upgrade disk (that you installed this copy of Windows 7 from) was the source of this OEM Bios Hack.

    Suggested Resolution:

    First, to confirm that the Upgrade Disk was the source of the OEM Bios Hack, you can first, reinstall Windows using the Upgrade Disk and the key that came with the disk.  When done, go to http://microsoft.com/genuine and click the Validate Windows button. 

    -If the result is Non-Genuine, you know the Upgrade Disk is the source of the OEM Bios Hack and I would recommend contacting the the person or company that sold you the software and return it for a full refund.

    -If the result is Genuine, you know that the Upgrade Disk was not the source of the Hack and it was installed at some later date by persons unknown.

    Thank you,
    Darin MS 
    Monday, March 8, 2010 10:42 PM

All replies

  • Please post your Diagnostic Report here, so someone could look into the details (possible causes) of the issue.
    "I think there is a world market for maybe five computers.” (Thomas J. Watson, Sr.)
    Wednesday, March 3, 2010 11:22 AM
  • To generate a Diagnostic Report, please download and run the Genuine Diagnostics tool (MGADiag.exe) at this link http://go.microsoft.com/fwlink/?linkid=52012. Click "Continue", click the "Copy" button then “Paste” the report into a reply message in this thread.

    Darin MS
    Thursday, March 4, 2010 10:15 PM
  • ... here comes my Diagnostic Report.
    Please Note that i removed some personal Data in it, like my Product key and hash and also my windows User Name.
    There obviosly is a File Mismatch in C:\Windows\system32\en-us\user32.dll.mui  ???

    I'm looking forward to your replies, and hope for some good advices,
    best Regards.



    Diagnostic Report (1.9.0019.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Invalid License
    Validation Code: 50

    Cached Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-*****-*****-*****
    Windows Product Key Hash: ***************
    Windows Product ID: 00371-OEM-8992671-00007
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.1.7600.2.00010100.0.0.048
    ID: {A301EE7B-372A-492A-9053-9311E7328E13}(3)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Professional
    Architecture: 0x00000000
    Build lab: 7600.win7_gdr.091207-1941
    TTS Error: 
    Validation Diagnostic: 
    Resolution Status: N/A

    WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002

    WGA 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: 100 Genuine
    Microsoft Office Visio Professional 2003 - 100 Genuine
    Microsoft Office Enterprise 2007 - 100 Genuine
    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:\*****\*****\*****\*****\chrome.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-->
    File Mismatch: C:\Windows\system32\en-us\user32.dll.mui[hr = 0x80070002]

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{A301EE7B-372A-492A-9053-9311E7328E13}</UGUID><Version>1.9.0019.0</Version><OS>6.1.7600.2.00010100.0.0.048</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-*****</PKey><PID>00371-OEM-8992671-00007</PID><PIDType>2</PIDType><SID>S-1-5-21-3346581737-1276170241-1187997941</SID><SYSTEM><Manufacturer>FUJITSU SIEMENS</Manufacturer><Model>Not your Business</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies Ltd.</Manufacturer><Version>V1.17       </Version><SMBIOSVersion major="2" minor="5"/><Date>20090601000000.000000+000</Date></BIOS><HWID>not your business</HWID><UserLCID>0407</UserLCID><SystemLCID>0407</SystemLCID><TimeZone>Mitteleuropäische Zeit(GMT+01:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>FSC   </OEMID><OEMTableID>PC      </OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91510407-6000-11D3-8CFE-0150048383C9}"><LegitResult>100</LegitResult><Name>Microsoft Office Visio Professional 2003</Name><Ver>11</Ver><Val>A99F37CE2AFBAA0</Val><Hash>fK/0wSwlHT0O1CjynA5e/P3d2+k=</Hash><Pid>73830-336-2567096-55341</Pid><PidType>8</PidType></Product><Product GUID="{91120000-0030-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Enterprise 2007</Name><Ver>12</Ver><Val>B7AA96BA25FA6BA</Val><Hash>*****=</Hash><Pid>81599-861-2110827-65463</Pid><PidType>8</PidType></Product></Products><Applications><App Id="51" Version="11" Result="100"/><App Id="15" Version="12" Result="100"/><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="19" Version="12" Result="100"/><App Id="1A" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="44" Version="12" Result="100"/><App Id="A1" Version="12" Result="100"/><App Id="BA" Version="12" Result="100"/></Applications></Office></Software></GenuineResults>  

    Spsys.log Content: 0x80070002

    Licensing Data-->
    Softwarelizenzierungsdienst-Version: 6.1.7600.16385

    Name: Windows(R) 7, Professional edition
    Beschreibung: Windows Operating System - Windows(R) 7, OEM_SLP channel
    Aktivierungs-ID: *****
    Anwendungs-ID: *****
    Erweiterte PID: *****
    Installations-ID: *****
    Prozessorzertifikat-URL: http://go.microsoft.com/fwlink/?LinkID=88338
    Computerzertifikat-URL: http://go.microsoft.com/fwlink/?LinkID=88339
    Lizenz-URL verwenden: http://go.microsoft.com/fwlink/?LinkID=88341
    Product Key-Zertifikat-URL: http://go.microsoft.com/fwlink/?LinkID=88340
    Teil-Product Key: QB9CK
    Lizenzstatus: Benachrichtigung
    Benachrichtigungsgrund: 0xC004F063.
    Verbleibende Windows Rearm-Anzahl: 3
    Vertrauenswürdige Zeit: 08.03.2010 13:23:47

    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0xC004C533
    HealthStatus: PASS
    Event Time Stamp: 3:8:2010 09:09
    WAT Activex: Registered
    WAT Admin Service: Registered

    HWID Data-->
    HWID Hash Current: *****

    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 PTLTD APIC  
      FACP NVIDIA MCP79   
      HPET PTLTD HPETTBL 
      BOOT PTLTD $SBFTBL$
      MCFG PTLTD  MCFG  
      SLIC FSC   PC      
      SSDT PmRef Cpu0Tst
      SSDT PmRef Cpu0Tst
      SSDT PmRef Cpu0Tst
      SSDT PmRef Cpu0Tst
      SSDT PmRef Cpu0Tst
      SSDT PmRef Cpu0Tst
      SSDT PmRef Cpu0Tst
      SSDT PmRef Cpu0Tst
      SSDT PmRef Cpu0Tst





    Monday, March 8, 2010 12:39 PM
  • You redacted half the information that could have been helpful, the key Had hash, the hardware hash I really don't need but bios and model information can be helpful, this is a SLP activation after all.


    It appears that you have slic 2.0 and windows 7 needs the 2.1 marker. it is possible your bios shipped with an older bios, call your manufacturer or use the windows 7 pro COA on the bottom of your computer to activate.
    • Proposed as answer by Carl Stephens Monday, March 8, 2010 2:24 PM
    Monday, March 8, 2010 2:21 PM
  • Do you need some additional information?

    What is slic 2.0 ?  and why do i need 2.1 marker?  
    I didn't get this in the context of having a invalid License Key. %)  *confused*
    How can my bios shipp with an older bios, and what should i ask my manufacturer?

    By the way, the Manufacturer and also the Retailer for My Windows 7 Upgrade are both not within reach for my company, we are too small for any response from their side. :((((   I tried it hard in the past.

    anyways, thanks for helping me.
    :)




    Monday, March 8, 2010 3:49 PM
  • I jsut noticed you said this was an upgrade installation. Check the packaging of the upgrade disk for the product key and enter it, if none was provided then the upgrade dvd they gave you may not have updated your bios which is why activation is failing. If the manufacturer supplied a disk that updates windows then there should have been a bios update on that disk also.

    I know you said it is hard to get in touch with the manufacturer but that is what you need to do.

    Forget everything I said about the COA, it does not apply in this situation (you may need it if you ever go back to vista however).

    Monday, March 8, 2010 4:06 PM
  • Hello Anonym_123456789,

    Your copy of Windows 7 is using an OEM SLP key.  This type of key only comes win Windows that come pre-installed in a computer built by a large manufacturer.

    When an OEM SLP key is in uses, Windows looks to the Bios on the computer's motherboard for a OEM Bios Flag. An OEM Bios Flag is information found only in the bios of computers built by a large manufacturer that come with Windows pre-installed. An OEM Bios Flag is specific to the Manufacturer and the version of Windows it's good for. So, If Windows is using an OEM SLP key and the Proper OEM Bios Flag is present in the computer's Bios, Windows will self-activate.

    Your Diagnostic Report shows that your computer does have a OEM Bios Flag so it did come with Windows pre-installed.  But the flag is am older one which suggests that your computer origianlly came with Vista.

    You have said this copy of Windows 7 was an Upgrade install. However, no copy of Windows (other then ones that come pre-installed in a computer built by a large manufatuere) would come with an OEM SLP key.  From the discripton of how OEM SLP key work, you can understand why.

    There are activation hacks (known as OEM Bios Hacks) avaliable on the internet (and sometimes sold, on a disk, as Genuine Windows) that when installed it makes Windows think that the Proper OEM Bios Flag is in the motherboards bios when it is not. This Hack plus an OEM SLP cause Windows to self-activate without needing a Valid Product key.

    Microsoft recently release an Update that makes Windows 7 ignore 70+ Activation Hacks (including many OEM Bios Hacks).

    To summarize:

    We know that your Upgrade version of Windows 7 was installed using a Product key that only comes in Windows 7 that come Pre-installed on a computer built by a large manufacturer. The key will not allow Windows 7 to run on any computer that does not have the proper OEM Bios Flag and the only computers that come with that proper OEM Bios Flag are ones that come with Windows 7 pre-installed.

    We know that your copy of Windows did, in fact, worked for some time.

    We know there are OEM Bios Hacks that can allow computer that lack the required OEM Blos Flag to run Windows that are using a OEM SLP key

    We know that Microsoft recently release an update that makes Windows ignore many known OEM Bios Hacks.

    And we know that around the same time Microsoft release this update, your Windows 7 stopped working and shows as Not Activated and Non-Genuine.

    Diagnosis:

    Because of these things, the logical conclusion is that your Windows 7 was using a OEM Bios Hack. Further, it is likely that the Upgrade disk (that you installed this copy of Windows 7 from) was the source of this OEM Bios Hack.

    Suggested Resolution:

    First, to confirm that the Upgrade Disk was the source of the OEM Bios Hack, you can first, reinstall Windows using the Upgrade Disk and the key that came with the disk.  When done, go to http://microsoft.com/genuine and click the Validate Windows button. 

    -If the result is Non-Genuine, you know the Upgrade Disk is the source of the OEM Bios Hack and I would recommend contacting the the person or company that sold you the software and return it for a full refund.

    -If the result is Genuine, you know that the Upgrade Disk was not the source of the Hack and it was installed at some later date by persons unknown.

    Thank you,
    Darin MS 
    Monday, March 8, 2010 10:42 PM
  • Darin, don't the oem's provide disks that prepare qualifying computers and then perform an upgrade installation? Without the manufacturer and model number I couldn't tell the age of the computer or if it qualified for windows 7. My understanding is that the OEM upgrade disk from a given manufacturer would prepare the computer by flashing the bios (installing the SLP 2.1 marker) then perform an upgrade with an SLP OEM key replacing the vista slp key.
    Monday, March 8, 2010 11:24 PM
  • Hi Darin Smith,

    today I was able to solve my Windows 7 License Issue.
    :)))

    Your Diagnosis was wrong, because of missing fact's in your summarize.

    here comes my step-by-step Report and Solution:

    Indeed my computer origianlly came with Vista installed.
    I didn't really use it, and I installed Windows 7 RC on the Day I received my Computer.
    As I knew about all that "we reebot your Windows every 2 hours" Features I decided to upgrade my Vista License quickly to a valid Windows 7 License.
    And I did so in the end of January this year.
    I had to do some tricks to beware Windows 7 Installer from formatting my Hard-disk.
    Formatting my Hard-disk would have taken me at least one week of re-organising and re-installing.
    I was able to avoid this by re-setting the minimum Windows Version for an Upgrade as described in offical MS Forums.

    I'm 99,9 percent sure that i had to type in my new product Key during the Upgrade installation from Windows 7 RC (7100)  to Windows 7 (7600).
    But obviously the Windows Activation Service was not notified about my new key.

    Solution:
    As simple as it can be. I Just typed my Product Key in the Windows Activation Form, and that's it. 
    :D   :)))

    ??? Problem:
    Obviously the Windows Genuine Activation Service was using my Windows 7 RC Product Key. ???


    Thanks for your Help.
    :D



    Tuesday, March 9, 2010 11:36 AM
  • HOHOHOHOHO.......
    Powerthink Melbourne
    Wednesday, March 24, 2010 10:17 PM