ลงชื่อเข้าใช้
Microsoft.com
 
Microsoft
 
 
 
Microsoft >
> 
> 
Not Genuie Error - Win7

Answered Not Genuie Error - Win7

  • 21 เมษายน 2553 2:03
     
     
    ลงชื่อเข้าใช้เพื่อโหวต
    0

    Another Genuine Win7 error. After reading these posts, and working with Microsoft support, I have gotten close to understand and fixing the error. It is a Dell machine that clearly came with the BIOS activation COA SLP (as noted in other threads).

    After awhile we started getting the not valid warnings even thought it said genuine and activated. Unable to fix it, I worked with Microsoft. We changed the product code to the one on the sticker on the machine. It will change, and it will say genuie and it would activate, but we still get the warnings. Syytem runs fine otherwise.

    We changed it to a completely different product code. Same story. will accept the new code, will activate, but will NOT stop giving the not genuine warnings. Going to ga.microsoft.com says invalid.

    Further research has given me a bit clue to the potential problem. Right after the machine was new, we tried running HALO. Didn't work on Win7. Searching the internet for help, we found someone saying rename the "/win/system32/catroot" folder. Looks like it was actually the catroot2 folder we were supposed to change, and I am sure we screwed something up there that is now causing our current not genuine issue.

    Regardless, this is where we believe our issue reside, as I was able to rename the catroot folder, and successfully get it to be both genuine and activated. Even said activated when going to ga.microsoft.com. Hurray, problem solved... NOPE

    Now, every time I do that, it won't reboot. get a quick blue screen of error messages (to quick to read) and fails to reboot. Using F8, and restore, and I can get it back to a functioning machine, except with the not genine error.

    Diagnostic Report (1.9.0019.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Genuine
    Validation Code: 0

    Cached Validation Code: 0x0
    Windows Product Key: *****-*****-HDMY8-Q7CGT-3C2PR
    Windows Product Key Hash: JRojazsvgSjYxwiq9w8sB+qswRI=
    Windows Product ID: 00359-OEM-9802063-65693
    Windows Product ID Type: 8
    Windows License Type: COA SLP
    Windows OS version: 6.1.7600.2.00010300.0.0.003
    ID: {41CE1F3D-4B70-43E4-A6E2-9820399A63AE}(3)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Home Premium
    Architecture: 0x00000009
    Build lab: 7600.win7_gdr.100226-1909
    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 FrontPage 2003 - 100 Genuine
    Microsoft Office Small Business Edition 2003 - 119 Cryptographics Error
    OGA Version: Registered, 2.0.48.0
    Signed By: Microsoft
    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 7.0; Win32)
    Default Browser: C:\Program Files (x86)\Mozilla Firefox\firefox.exe
    Download signed ActiveX controls: Prompt
    Download unsigned ActiveX controls: Prompt
    Run ActiveX controls and plug-ins: Allowed
    Initialize and script ActiveX controls not marked as safe: Prompt
    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\sppobjs.dll[6.1.7600.16385]
    File Mismatch: C:\Windows\system32\sppc.dll[6.1.7600.16385]
    File Mismatch: C:\Windows\system32\sppcext.dll[6.1.7600.16385]
    File Mismatch: C:\Windows\system32\sppwinob.dll[6.1.7600.16385]
    File Mismatch: C:\Windows\system32\slc.dll[6.1.7600.16385]
    File Mismatch: C:\Windows\system32\slcext.dll[6.1.7600.16385]
    File Mismatch: C:\Windows\system32\sppuinotify.dll[6.1.7600.16385]
    File Mismatch: C:\Windows\system32\slui.exe[6.1.7600.16385]
    File Mismatch: C:\Windows\system32\sppcomapi.dll[6.1.7600.16385]
    File Mismatch: C:\Windows\system32\sppcommdlg.dll[6.1.7600.16385]
    File Mismatch: C:\Windows\system32\sppsvc.exe[6.1.7600.16385]
    File Mismatch: C:\Windows\system32\drivers\spsys.sys[6.1.7127.0]
    File Mismatch: C:\Windows\system32\drivers\spldr.sys[6.1.7127.0]
    File Mismatch: C:\Windows\system32\systemcpl.dll[6.1.7600.16385]
    File Mismatch: C:\Windows\system32\en-us\user32.dll.mui[6.1.7600.16385]

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{41CE1F3D-4B70-43E4-A6E2-9820399A63AE}</UGUID><Version>1.9.0019.0</Version><OS>6.1.7600.2.00010300.0.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-3C2PR</PKey><PID>00359-OEM-9802063-65693</PID><PIDType>8</PIDType><SID>S-1-5-21-2759156312-2229005240-3686899775</SID><SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>Studio XPS 8000</Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>A01</Version><SMBIOSVersion major="2" minor="5"/><Date>20090811000000.000000+000</Date></BIOS><HWID>97BA3607018400FE</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>DELL  </OEMID><OEMTableID>FX09   </OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{90170409-6000-11D3-8CFE-0150048383C9}"><LegitResult>100</LegitResult><Name>Microsoft Office FrontPage 2003</Name><Ver>11</Ver><Val>5EA9C3672EB0500</Val><Hash>GZD+9sfb5ecL3RxyV4F75a86u2M=</Hash><Pid>72079-640-0000106-55891</Pid><PidType>14</PidType></Product><Product GUID="{91CA0409-6000-11D3-8CFE-0150048383C9}"><LegitResult>119</LegitResult><Name>Microsoft Office Small Business Edition 2003</Name><Ver>11</Ver><Val>28FF969C0A01F0C</Val><Hash>NU/yxgOSuZ8uj+aUmqhfbsXtK1c=</Hash><Pid>70160-OEM-5690251-65106</Pid><PidType>6</PidType></Product></Products><Applications><App Id="16" Version="11" Result="100"/><App Id="17" Version="11" Result="100"/><App Id="18" Version="11" Result="100"/><App Id="19" Version="11" Result="100"/><App Id="1A" Version="11" Result="100"/><App Id="1B" Version="11" Result="100"/></Applications></Office></Software></GenuineResults> 

    Spsys.log Content: 0x80070002

    Licensing Data-->
    Software licensing service version: 6.1.7600.16385

    Name: Windows(R) 7, HomePremium edition
    Description: Windows Operating System - Windows(R) 7, OEM_COA_SLP channel
    Activation ID: 5e017a8a-f3f9-4167-b1bd-ba3e236a4d8f
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00359-00196-067-502449-02-1033-7600.0000-1042010
    Installation ID: 008012630122876792444553623112783294428670915356324416
    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: R7V7J
    License Status: Licensed
    Remaining Windows rearm count: 3
    Trusted time: 4/20/2010 8:58:12 PM

    Windows Activation Technologies-->
    HrOffline: 0x8004FE21
    HrOnline: 0x00000000
    HealthStatus: 0x000000000001EFF0
    Event Time Stamp: 4:20:2010 20:32
    WAT Activex: Registered
    WAT Admin Service: Registered

    HWID Data-->
    HWID Hash Current: NAAAAAEABAABAAIAAAABAAAAAgABAAEAln3MYUztQsb215RWgJZsP85wEng+NwAAXPV2Vg==

    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   DELL    FX09   
      FACP   DELL    FX09   
      HPET   DELL    OEMHPET
      MCFG   DELL    OEMMCFG
      SLIC   DELL    FX09  
      OSFR   DELL    FX09   
      OEMB   DELL    FX09   
      GSCI   DELL    GMCHSCI

     

     

ตอบทั้งหมด

  • 21 เมษายน 2553 3:28
     
     
    ลงชื่อเข้าใช้เพื่อโหวต
    0

    Hello JoeMetz,

    You wrote, "...and I am sure we screwed something up there that is now causing our current not genuine issue."

    Sounds like it's time to man-up, bite the bullet, backup and offload your data, and do a factory restore back to out-of-the-box condition.

    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
     
  • 21 เมษายน 2553 21:28
    เจ้าของ
     
     คำตอบ
    ลงชื่อเข้าใช้เพื่อโหวต
    0

    Hello JoeMetz,

    The line in the Diagnostic Report "HrOffline 0x8004FE22" translates to mean "Selfheal failure". 

    The recent WAT Update gave Windows 7 the ability to self-repair system files when it detects that the files have been modified (either rewritten, replaced or have become corrupt).  The above error code (as well as the code 0x8004FE21) means that Windows did detect that one or more of it's own Activation or Validation system files has been modified, in some way, and that when Windows tried to repair the damage, the operation failed.

    Since the files are still modified (i.e. Non-Genuine), Windows can not trust them. 

    The resolution is to repair the modified files. To do that, there are a few things you can try:

    a. System Scan. The scan will look for bad Windows files and will attempt to repair them, if possible.

    1) Click the Start Button
    2) Type: cmd.exe
    3) Right-click the cmd.exe file and select 'Run as Administrator'
    4) In the CMD window, type: sfc /scannow
    5) Reboot and see if that resolves the issue.


    b. Repairing Windows using System Restore:

    1) Click the Start button
    2) In the Start Search field, type: System Restore and hit “Enter”
    3) Select "Choose Different Restore Point", Put a check in the box that says "Show restore points older than 5 days", select the restore point that corresponds to the date Before you first noticed the issue.
    4) Click the "Next" button.
    5) Reboot and see if that resolves the issue.


    If neither of these sets of steps resolves the issue, my only other suggestions would be either to create a (no cost) suport request at http://support.microsoft.com/gp/contactwga or reinstall.
    Darin MS
    • ทำเครื่องหมายเป็นคำตอบโดย Darin Smith MSOwner 21 เมษายน 2553 21:29
    •