locked
windows 7 genuine suddenly not genuine... RRS feed

  • Question

  • Today after windows update my windows not genuine no more

    I have bought a code but it's not working to put it in again

    Ill need help pls

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

    Validation Code: 50
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-7QBHY-MXJQ2-H429F
    Windows Product Key Hash: CC2nyjuEneliiEk0oZgDCzqIvrs=
    Windows Product ID: 00426-956-0189773-85097
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7600.2.00010100.0.0.001
    ID: {1063B71F-1498-44C9-9D8F-FDB5FBB765C4}(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: 100 Genuine
    Microsoft Office FrontPage 2003 - 100 Genuine
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: B4D0AA8B-604-645_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:\Users\Lisa\AppData\Local\Google\Chrome\Application\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-->

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{1063B71F-1498-44C9-9D8F-FDB5FBB765C4}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-H429F</PKey><PID>00426-956-0189773-85097</PID><PIDType>5</PIDType><SID>S-1-5-21-1786173128-598004608-2081457016</SID><SYSTEM><Manufacturer>Gigabyte Technology Co., Ltd.</Manufacturer><Model>P35-DS3</Model></SYSTEM><BIOS><Manufacturer>Award Software International, Inc.</Manufacturer><Version>F14</Version><SMBIOSVersion major="2" minor="4"/><Date>20090618000000.000000+000</Date></BIOS><HWID>53B80600010000FA</HWID><UserLCID>041D</UserLCID><SystemLCID>041D</SystemLCID><TimeZone>Västeuropa, normaltid(GMT+01:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>HPQOEM</OEMID><OEMTableID>SLIC-MPC</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{9017041D-6000-11D3-8CFE-0150048383C9}"><LegitResult>100</LegitResult><Name>Microsoft Office FrontPage 2003</Name><Ver>11</Ver><Val>5EA9C3672EB0500</Val><Hash>GZD+9sfb5ecL3RxyV4F75a86u2M=</Hash><Pid>73336-640-0000106-55910</Pid><PidType>14</PidType></Product></Products><Applications><App Id="17" Version="11" Result="100"/></Applications></Office></Software></GenuineResults> 

    Spsys.log Content: 0x80070002

    Licensing Data-->
    C:\Windows\system32\slmgr.vbs(1333, 5) (null): Felaktig data.

    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0xC004C533
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 11:4:2010 20:18
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:


    HWID Data-->
    N/A, hr = 0x8007000d

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes
    Windows marker version: 0x20001
    OEMID and OEMTableID Consistent: yes
    BIOS Information:
      ACPI Table Name OEMID Value OEMTableID Value
      APIC   GBT     GBTUACPI
      FACP   GBT     GBTUACPI
      HPET   GBT     GBTUACPI
      MCFG   GBT     GBTUACPI
      SLIC   HPQOEM  SLIC-MPC

     

    Thursday, November 4, 2010 7:50 PM

Answers

  • Please Note:

    0xC004C533 means " notification unknown state"

    0xC004C4AB means " Softmod (loader) detected"

     

    So, This user's issue is not being cased by a Loader, but because Windows Licensing Data is messed up in some way.  0xC004C533 is consistent with a Licensing Data issue

      I recommend trying the below steps to reset the Licensing data.
     
    1) Click Start button.
    2) Type: CMD.exe into the 'Search programs and files' field
    3) Right-Click on CMD.exe and select 'Run as Administrator'
    4) Type: net stop sppsvc   (It may ask you if you are sure, select yes)
    Note: the Software Protection service may not be running, this is ok.
    5) Type: cd %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform
    6) Type: rename tokens.dat tokens.bar
    7) Type: cd %windir%\system32
    8) Type: net start sppsvc
    9) Type: slui.exe
    10) After a couple of seconds Windows Activation dialog will appear. It's most likely that Activation will occur automatically but you may be asked to re-enter your product key and/or to reactivate.


    If that does not resolve the issue, you can try

    1) Use System Restore to get back to a point before the issue occurred
     
    or

    2) use the System File Checker to replace the tampered file with a clean copy

    Click on the Start button
    type in the Search  box
    CMD.EXE
    right-click on the only file that is found
    Select Run as Administrator
     - the Elevated Command Prompt window should pop up
    At the Command prompt, type
     
    SFC /SCANNOW

    Thank you

     

     


    Darin MS
    • Proposed as answer by Darin Smith MS Friday, November 5, 2010 7:42 PM
    • Marked as answer by Darin Smith MS Friday, November 12, 2010 7:13 PM
    Friday, November 5, 2010 7:42 PM

All replies

  • ><Manufacturer>Gigabyte Technology Co., Ltd.</Manufacturer><Model>P35-DS3

    Windows marker version: 0x20001

     SLIC   HPQOEM  SLIC-MPC

    C:\Windows\system32\slmgr.vbs(1333, 5) (null): Felaktig data.

    HrOnline: 0xC004C533

    The above indicates that a loader is being used and something has interfered with licensing data, the two may or may not be connected. You must first remove the loader, I am going to suggest that if windows was installed using a downloaded image or non-genuine disk that you do a clean install with the disks that came with your current valid license. If you purchased the key from a digital river outlet or MS store you should have been provided with a download link

    The loader attempts to emulate OEM SLP activation by inserting the bios marker into memory therefore tricking windows into thinking it is genuine. Removing it can be accomplished by performing a clean installation which is what I recommend however if you want to preserve the installation I will provide instructions to remove most loaders.

    The HRonline code listed in your report is not consistent with the loader but could be caused by another underlying problem, possibly caused by the installation media (if non-genuine) or the installation of the loader.

    Thursday, November 4, 2010 10:51 PM
  • Hello Sandersson,

    According to the data provided by the MGADiag tool, you are running a non-genuine version of Windows activated with a bootloader program that emulates a SLIC table in a non-existant virtual BIOS. You should contact the seller that you purchased the product from and possibly report possible piracy to Microsoft Piracy at 1-800-RULEGIT.

    To fix this problem, you need to re-install Windows 7 using either A) the product key provided on the COA on the side, top, or back of your computer assuming you have the OEM Recovery Discs or B) purchase a Get Genuine Kit or a new copy of Windows.

    Friday, November 5, 2010 7:28 PM
  • Please Note:

    0xC004C533 means " notification unknown state"

    0xC004C4AB means " Softmod (loader) detected"

     

    So, This user's issue is not being cased by a Loader, but because Windows Licensing Data is messed up in some way.  0xC004C533 is consistent with a Licensing Data issue

      I recommend trying the below steps to reset the Licensing data.
     
    1) Click Start button.
    2) Type: CMD.exe into the 'Search programs and files' field
    3) Right-Click on CMD.exe and select 'Run as Administrator'
    4) Type: net stop sppsvc   (It may ask you if you are sure, select yes)
    Note: the Software Protection service may not be running, this is ok.
    5) Type: cd %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform
    6) Type: rename tokens.dat tokens.bar
    7) Type: cd %windir%\system32
    8) Type: net start sppsvc
    9) Type: slui.exe
    10) After a couple of seconds Windows Activation dialog will appear. It's most likely that Activation will occur automatically but you may be asked to re-enter your product key and/or to reactivate.


    If that does not resolve the issue, you can try

    1) Use System Restore to get back to a point before the issue occurred
     
    or

    2) use the System File Checker to replace the tampered file with a clean copy

    Click on the Start button
    type in the Search  box
    CMD.EXE
    right-click on the only file that is found
    Select Run as Administrator
     - the Elevated Command Prompt window should pop up
    At the Command prompt, type
     
    SFC /SCANNOW

    Thank you

     

     


    Darin MS
    • Proposed as answer by Darin Smith MS Friday, November 5, 2010 7:42 PM
    • Marked as answer by Darin Smith MS Friday, November 12, 2010 7:13 PM
    Friday, November 5, 2010 7:42 PM
  • I assumed there was a loader or something emulating the SLIC marker because of this entry. I think the cause of that entry may be the culprit.

    SLIC   HPQOEM  SLIC-MPC

    Friday, November 5, 2010 7:47 PM
  • That's right. Keeping in mind that's not the usual OEM_SLP issue (it's a retail version)  and the SLIC marker isn't relevant for retail versions, the whole thing is a bit mysterious to me.
    "192 GB ought to be enough for anybody." (from the miniseries "Next Generation's Jokes")
    Saturday, November 6, 2010 4:34 AM
  •   Most likely, the user installed a Retail copy of Windows 7 on a HP computer that originally came with a Bios locked copy of Windows.

     

    Darin MS
    Monday, November 8, 2010 10:22 PM
  • u'r product key is not genuine

    if u'r product key is genuine then product id is combined with "OEM" LETTERS

    GENUINE PRODUCT ID IS LIKE THIS : ***** - OEM - ******* - *****

    however to overcome this problem with u'r product key just hidden the one update from u'r windows update

    the update number is (KB971033) JUST HIDDEN THIS UPDATE AND INSTALL REMAINING UPDATE'S 

    Sunday, November 28, 2010 9:42 AM
  • u'r product key is not genuine

    if u'r product key is genuine then product id is combined with "OEM" LETTERS

    GENUINE PRODUCT ID IS LIKE THIS : ***** - OEM - ******* - *****

    however to overcome this problem with u'r product key just hidden the one update from u'r windows update

    the update number is (KB971033) JUST HIDDEN THIS UPDATE AND INSTALL REMAINING UPDATE'S 

    1. The product key is RETAIL and therefore would not have OEM in the PID in any windows product ever made.
    2. The product key being genuine or not has nothing to do with the 3 digit section of the PID
    3. The PID does not contain the OEM text anymore.
    4. Removing or blocking the WAT update would do nothing in this case. Your advice is flawed, wrong and in th end would cause more harm than good.

    The OP has a valid retail key. The correct advice is advice that will help him get that key activated. Not some hack and slash work around. I think you are on the wrong forum possibly.

    Sunday, November 28, 2010 3:46 PM