locked
Odd microsoft not genuine message appearing after last windows update. RRS feed

  • Question

  • Getting an error about my windows not being genuine after my last windows update.  
    It's valid, I know it is because I received this copy legitimately from my company.  
    I will likely be receiving a new copy if this isn't resolved shortly, though I thought a company should know about a fatal error in their software validation making people pay for more than one copy of windows in the cases of which they do.


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

    Validation Code: 0
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-9DD3B-79HQW-FWBFT
    Windows Product Key Hash: +qetqZgUpK//VrPGipp9C6Q9Peo=
    Windows Product ID: 00426-065-2932014-86838
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7601.2.00010100.1.0.001
    ID: {F51B70CD-0C12-4AAA-8222-09BCF2B8FB91}(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: 7601.win7sp1_gdr.130828-1532
    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: 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:\Program Files (x86)\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>{F51B70CD-0C12-4AAA-8222-09BCF2B8FB91}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-FWBFT</PKey><PID>00426-065-2932014-86838</PID><PIDType>5</PIDType><SID>S-1-5-21-289711365-2450036601-2328083978</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP Pavilion dv4 Notebook PC</Model></SYSTEM><BIOS><Manufacturer>Insyde</Manufacturer><Version>F.66</Version><SMBIOSVersion major="2" minor="4"/><Date>20100518000000.000000+000</Date></BIOS><HWID>7BB93D07018400F8</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central Standard Time(GMT-06: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>109</Result><Products/><Applications/></Office></Software></GenuineResults>  

    Spsys.log Content: 0x80070002

    Licensing Data-->
    Software licensing service version: 6.1.7601.17514

    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-065-293201-00-1033-7600.0000-3492013
    Installation ID: 012395279570494902710991087681230621283113691486663985
    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: FWBFT
    License Status: Initial grace period
    Time remaining: 37380 minute(s) (25 day(s))
    Remaining Windows rearm count: 5
    Trusted time: 12/19/2013 5:47:21 PM

    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0x00000000
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 12:18:2013 17:45
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:


    HWID Data-->
    HWID Hash Current: MAAAAAEAAgABAAIAAAABAAAAAgABAAEA6GHWWzfouqt6fz6zLn/U6vBYPu/eOEbK

    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 HPQOEM SLIC-MPC
      FACP HPQOEM SLIC-MPC
      HPET HPQOEM SLIC-MPC
      BOOT HPQOEM SLIC-MPC
      MCFG HPQOEM SLIC-MPC
      DMAR       
      SSDT PmRef CpuPm
      ASF! HPQOEM SLIC-MPC
      SLIC HPQOEM SLIC-MPC
      SSDT PmRef CpuPm

    Thursday, December 19, 2013 10:56 PM

Answers

  • Unfortunately, it has nothing to do with any time tables.

    Your install is counterfeit.  It is labeled as Retail but the -065- portion of your Product Key indicates that it is a Not-For-Resale MSDN version.

    In order to get an MSDN subscription, you need to sign agreements with Microsoft.  Then they allow you access to keys that are to be used ONLY for the purpose for which they were intended.  When those keys are leaked and "activated" enough times, Microsoft will ban them from further use.  That might take over a year before a particular one is banned.  But the effect is the same - the counterfeit installation is then flagged as non-genuine.

    For more information see the following thread:

    http://social.microsoft.com/Forums/en-US/a2444f34-0aff-4f29-a8ac-67e28b0c0285/blocked-product-keys?forum=genuinewindows7

    You will need to purchase a genuine copy of Windows 7, reformat and reinstall.  Be sure to backup your data first.

    Where did your company come by these installs?  They are marked as Retail and are certainly fakes.  They need to go back to whomever they purchased them from and demand a full refund and refuse any offer of replacement Product Keys.


    Please do not read this sentence. Please ignore the previous sentence.


    Thursday, December 19, 2013 11:28 PM
  • Not quite true Kamin :)

    MSDN are perfectly valid in certain contexts - In this case, if the company is the MSDN subscriber, then it may be within the rules to allow their developers to install the Keys, on their machines.

    This machine appears to have been installed 4 days ago? - either that or a hack activating it was broken 4 days ago.

    Ownst

    What exact error message do you get when attempting to activate it? -  there are no obvious signs of problems in the report, apart from it not being activated at all.


    Noel Paton | Nil Carborundum Illegitemi
    CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    Friday, December 20, 2013 8:10 AM
    Moderator

All replies

  • Upon analysis, I'm wondering whether or not this is related to the time table you are allowed to add new validations on your key (depending on the amount of validations present on your retail copy).

    I would prefer not to wait for the validation time limit to expire.

    If that is the case I am sure it is a simple fix for Microsoft.

    Please let me know.
    Thursday, December 19, 2013 11:22 PM
  • Unfortunately, it has nothing to do with any time tables.

    Your install is counterfeit.  It is labeled as Retail but the -065- portion of your Product Key indicates that it is a Not-For-Resale MSDN version.

    In order to get an MSDN subscription, you need to sign agreements with Microsoft.  Then they allow you access to keys that are to be used ONLY for the purpose for which they were intended.  When those keys are leaked and "activated" enough times, Microsoft will ban them from further use.  That might take over a year before a particular one is banned.  But the effect is the same - the counterfeit installation is then flagged as non-genuine.

    For more information see the following thread:

    http://social.microsoft.com/Forums/en-US/a2444f34-0aff-4f29-a8ac-67e28b0c0285/blocked-product-keys?forum=genuinewindows7

    You will need to purchase a genuine copy of Windows 7, reformat and reinstall.  Be sure to backup your data first.

    Where did your company come by these installs?  They are marked as Retail and are certainly fakes.  They need to go back to whomever they purchased them from and demand a full refund and refuse any offer of replacement Product Keys.


    Please do not read this sentence. Please ignore the previous sentence.


    Thursday, December 19, 2013 11:28 PM
  • Not quite true Kamin :)

    MSDN are perfectly valid in certain contexts - In this case, if the company is the MSDN subscriber, then it may be within the rules to allow their developers to install the Keys, on their machines.

    This machine appears to have been installed 4 days ago? - either that or a hack activating it was broken 4 days ago.

    Ownst

    What exact error message do you get when attempting to activate it? -  there are no obvious signs of problems in the report, apart from it not being activated at all.


    Noel Paton | Nil Carborundum Illegitemi
    CrashFixPC | The Three-toed Sloth
    No - I do not work for Microsoft, or any of its contractors.

    Friday, December 20, 2013 8:10 AM
    Moderator