Windows Not Genuine, Update Not Working

Page 1 of 2 12 LastLast

  1. Posts : 1,810
    Dual Boot: Windows 8.1 & Server 2012r2 VMs: Kali Linux, Backbox, Matriux, Windows 8.1
       #1

    Windows Not Genuine, Update Not Working


    So I have a client PC that I don't have all the required info for (not logged in right this second) but I have the diag report.

    PC says not genuine and won't update. The key that is coming up seems to be an evaluation copy. Is this just a bad update that may have caused her to become not genuine or is this a non genuine copy? Getting legal is no problem but I don't want to have her buy a new license if its just a problem and not because the previous tech gave her cracked software.

    Tried to run CheckSur but it won't work. I was able to rearm the key because it acts like an evaluation key but that only helps for a couple days.

    One error I was getting :
    0xC004F063 computer bios is missing required license

    I'll add more info when I can get back on the PC.

    Code:
    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    
    Validation Code: 50
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-73CQT-WMF7J-3Q6C9
    Windows Product Key Hash: KaFG+RmurcM3ZxzWyfEP9WtPUJw=
    Windows Product ID: 00359-OEM-8992687-00010
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.1.7601.2.00010300.1.0.003
    ID: {37A32799-CD1C-4787-8B2F-E62412D6A2D2}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Home Premium
    Architecture: 0x00000009
    Build lab: 7601.win7sp1_gdr.150113-1808
    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 Enterprise 2007 - 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_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005_E2AD56EA-765-b01a_E2AD56EA-766-0_E2AD56EA-148-80004005_16E0B333-89-80004005_B4D0AA8B-1029-80004005
    
    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files\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>{37A32799-CD1C-4787-8B2F-E62412D6A2D2}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-3Q6C9</PKey><PID>00359-OEM-8992687-00010</PID><PIDType>2</PIDType><SID>S-1-5-21-1274916623-1545373943-3133267663</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP  Pavilion dv4 Notebook  PC</Model></SYSTEM><BIOS><Manufacturer>Insyde</Manufacturer><Version>F.17</Version><SMBIOSVersion  major="2"  minor="6"/><Date>20091210000000.000000+000</Date></BIOS><HWID>DA0A3407018400F4</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>100</Result><Products><Product   GUID="{90120000-0030-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft  Office Enterprise  2007</Name><Ver>12</Ver><Val>64BC76978749586</Val><Hash>GW6PzcEVEDTVKeO5Ym5UUm41dBk=</Hash><Pid>89388-707-0441865-65791</Pid><PidType>14</PidType></Product></Products><Applications><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-->
    Software licensing service version: 6.1.7601.17514
    
    Name: Windows(R) 7, HomePremium edition
    Description: Windows Operating System - Windows(R) 7, OEM_SLP channel
    Activation ID: d2c04e90-c3dd-4260-b0f3-f845f5d27d64
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00359-00178-926-800010-02-1033-7601.0000-2752014
    Installation ID: 013385457926395250945264290812234020547845948004659165
    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: 3Q6C9
    License Status: Notification
    Notification Reason: 0xC004F063.
    Remaining Windows rearm count: 2
    Trusted time: 3/19/2015 3:41:57 PM
    
    Windows Activation Technologies-->
    HrOffline: 0x00000000
    HrOnline: 0x80072EE7
    HealthStatus: 0x0000000000000000
    Event Time Stamp: 2:26:2015 17:09
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:
    
    
    HWID Data-->
    HWID Hash Current: MgAAAAEAAgABAAIAAAACAAAAAgABAAEA6GEcBF8RVPkeeeRK/EvOcOpFmH6gBzS5GHk=
    
    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            HP            REPLEY  
      HPET            HPQOEM        SLIC-MPC
      BOOT            HPQOEM        SLIC-MPC
      MCFG            HPQOEM        SLIC-MPC
      SLIC            HPQOEM        SLIC-MPC
      SSDT            AMD           PowerNow
      My Computer


  2. Posts : 25,847
    Windows 10 Pro. 64/ version 1709 Windows 7 Pro/64
       #2

    Gator I don't know if I can help but lets see if we can gather some information.

    1. What are the system specs of trouble computer?

    2. Is their a Microsoft COA sticker on the computer? If some what Windows system is it for?

    3. What is a evaluation copy?

    Your first post states.

    So I have a client PC
    From the log shows
    <Manufacturer>Hewlett-Packard</Manufacturer><Model>HP Pavilion dv4 Notebook

    The only bios date I find in the log is.

    <SMBIOSVersion major="2" minor="6"/><Date>20091210000000

    My understand of these things are.
    The date is Jan. 21 of 2009 for the bios.
    Window 7 didn't come out until later.
    I don't think that HP made a Notebook in 2009.

    The log shows
    Windows License Type: OEM SLP
      My Computer


  3. Posts : 1,810
    Dual Boot: Windows 8.1 & Server 2012r2 VMs: Kali Linux, Backbox, Matriux, Windows 8.1
    Thread Starter
       #3

    I don't have the full system specs right now as I only got to be on the computer for a little while before they closed down. They are real estate agents so they are always busy so fixing their PC is not their first priority. Still haven't had a chance to get back on the problem PC.

    The COA sticker is faded beyond recognition according to her. I tried pulling it with magic jelly bean but it seems to have picked up a generic and/or cracked key that I can easily find hits on with Google. As far as I know, thats either the wrong key or its for sure cracked, right?

    When I checked on Microsoft website to see if the key is good, it said "thank you for using the evaluation copy...." so thats why I called it that. It seems like it thinks its a developer preview that only had a limited product key.

    Sorry, I can see how saying I "have" the PC will make it seem like its in my possession but Im working remotely.

    I know your hands are tied until I can get more info so no worries. I will update once I can get back on the PC. Its entirely possible that she may just want to buy a new one and cut ties with this one so Im not sure if she still wants it fixed, just trying to get ideas and see if something is fishy or not.
      My Computer


  4. Posts : 25,847
    Windows 10 Pro. 64/ version 1709 Windows 7 Pro/64
       #4

    The more information you can gather makes it easier for members here to help.
      My Computer


  5. Posts : 17,322
    Win 10 Pro x64
       #5

    That BIOS date would be December 10, 2009, (Year, Month, Day) ,well after win 7 release.

    Any of those key finders can see the SLP key that the factory uses for mass installation, but that key can't be used for activation, you need the one on the COA for that.
      My Computer


  6. Posts : 1,810
    Dual Boot: Windows 8.1 & Server 2012r2 VMs: Kali Linux, Backbox, Matriux, Windows 8.1
    Thread Starter
       #6

    derekimo said:
    That BIOS date would be December 10, 2009, (Year, Month, Day) ,well after win 7 release.

    Any of those key finders can see the SLP key that the factory uses for mass installation, but that key can't be used for activation, you need the one on the COA for that.
    Thanks, I figured it was wrong. I don't deal with activation issues too much thats why I turn to the professional
      My Computer


  7. Posts : 25,847
    Windows 10 Pro. 64/ version 1709 Windows 7 Pro/64
       #7

    Thank you Derek.

    Year-month-day. Now all I have to do is remember that.
    I wrote it down so now all I have to do is remember where I put the note.
      My Computer


  8. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #8

    The problem here is typically caused by installation using Retail media in conjuction with the OEM_SLP Key found by a utility, instead of the proper COA SLP Key from the COA stoicker.
    All that's required is this...

    Please first try recreating Licensing Store.

    Recreate the Licensing Store
    Go to Start > All Programs > Accessories
    Right-Click on Command Prompt and select Run as Administrator - accept the UAC prompt
    Run the following commands in the Command Prompt window, using the Enter key at the end of each

    net stop sppsvc
    (wait until the service has stopped before entering the following lines)

    CD %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform
    REN tokens.dat tokens.bar
    net start sppsvc
    slui.exe

    After a couple of seconds the Windows Activation dialog will appear.
    You may be asked to re-activate and/or re-enter your product key, or Activation may occur automatically.
    If you are asked for your Key, use the one on the COA sticker on the machine's case

    Reboot and Post back with a new MGADiag report.

    (Note: the Line 'CD %win......\SoftwareProtectionPlatform' is all on one line - it may be broken in the Forum listing)
      My Computer


  9. Posts : 2,774
    Windows 7 Professional 64-bit
       #9

    One of my three Windows 7 went inauthentic, invalid, although I never figured what went wrong.
    Even a MS tech over the phone, with a ReInstall ISO/download couldn't get me past the inauthentic, invalid OS. Finally, because I did not have a good working restorable image -- a fresh reInstall from the true-blue MS W7Pro disk worked. I maintain good working OS images on 2 separate external USB HDs as a rule.
      My Computer


  10. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #10

    RolandJS said:
    One of my three Windows 7 went inauthentic, invalid, although I never figured what went wrong.
    Even a MS tech over the phone, with a ReInstall ISO/download couldn't get me past the inauthentic, invalid OS. Finally, because I did not have a good working restorable image -- a fresh reInstall from the true-blue MS W7Pro disk worked. I maintain good working OS images on 2 separate external USB HDs as a rule.
    Until you get to Level 3 techs in MS support, it's unlikely they'll be able to decipher even the most basic parts of an MGADiag report - and very possible that they haven't heard of it at all.
    Most will fumble around a bit and then do a repair install or even a clean install.
    I reckon I can solve something like 80+% of non-genuine problems using MGADiag and other basic tools - MS have kept tight wraps on what the more complex parts of the report can actually tell them (if anything!)
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 05:58.
Find Us