locked
Windows Activates, but fails genuine validation and updates fail RRS feed

  • Question

  • PLEASE HELP, we randomly get a popup on our machine that is is not genuine and windows will not update.

    Only some select updates will install on our machine, all the rest fail.  Windows is activated, but going to genuine advantage suggests that this version of windows is not genuine?  I am 100% certain my version of windows is genuine.  We are a Microsoft Action Pack member andour subscription is current.  This copy of windows was download direct from the microsoft action pack site and it has only been installed on this machine, NEVER installed on any other!

    1) Windows 7 Ultimate

    2) From Microsoft Action Pack, software downloaded from them and key form them

    Here is the copy of the text from the Windows Genuine Diagnostic Tool.  PLEASE HELP!


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

    Validation Code: 0x8004FE21
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-HCY7G-636BQ-4QPD6
    Windows Product Key Hash: zzdt1g1K/wR8hlENWVPhGToWgFM=
    Windows Product ID: 00426-948-1670601-85299
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7600.2.00010100.0.0.001
    ID: {9F061C83-E1FD-4410-8340-CCD0AAC30EDF}(3)
    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 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:\Program Files (x86)\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-->
    File Mismatch: C:\Windows\system32\wat\watadminsvc.exe[7.1.7600.16395], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\wat\watux.exe[7.1.7600.16395], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\sppobjs.dll[6.1.7600.16385], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\sppc.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppcext.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppwinob.dll[6.1.7600.16385], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\slc.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\slcext.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppuinotify.dll[6.1.7600.16385], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\slui.exe[6.1.7600.16385], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\sppcomapi.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppcommdlg.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppsvc.exe[6.1.7600.16385], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\drivers\spsys.sys[6.1.7127.0], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\drivers\spldr.sys[6.1.7127.0], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\systemcpl.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\user32.dll[6.1.7600.16385], Hr = 0x800b0100

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{2E58CC79-181F-495E-AE61-D2AEFCAFAA8B}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-4QPD6</PKey><PID>00426-948-1670601-85299</PID><PIDType>5</PIDType><SID>S-1-5-21-3480575676-3343595524-287305536</SID><SYSTEM><Manufacturer>INTEL_</Manufacturer><Model>DG45ID__</Model></SYSTEM><BIOS><Manufacturer>Intel Corp.</Manufacturer><Version>IDG4510H.86A.0131.2010.0712.0906</Version><SMBIOSVersion major="2" minor="4"/><Date>20100712000000.000000+000</Date></BIOS><HWID>B3373007018400F8</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-0030-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Enterprise 2007</Name><Ver>12</Ver><Val>21B0B3DA84486AC</Val><Hash>vhf1osNQE6/RiOgJm9XUCT2aid4=</Hash><Pid>81599-854-5808167-65184</Pid><PidType>1</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.7600.16385

    Name: Windows(R) 7, Ultimate edition
    Description: Windows Operating System - Windows(R) 7, RETAIL channel
    Activation ID: ac96e1a8-6cc4-4310-a4ff-332ce77fb5b8
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00426-00170-948-167060-00-1033-7600.0000-0972011
    Installation ID: 005443983354058993947266555316541926300933699994154494
    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: 4QPD6
    License Status: Licensed
    Remaining Windows rearm count: 4
    Trusted time: 9/16/2011 2:41:15 PM

    Windows Activation Technologies-->
    HrOffline: 0x8004FE21
    HrOnline: N/A
    HealthStatus: 0x000000000001EFF0
    Event Time Stamp: 9:14:2011 20:16
    ActiveX: Registered, Version: 7.1.7600.16395
    Admin Service: Registered, Version: 7.1.7600.16395
    HealthStatus Bitmask Output:
    Tampered File: %systemroot%\system32\sppobjs.dll
    Tampered File: %systemroot%\system32\sppc.dll|sppc.dll.mui
    Tampered File: %systemroot%\system32\sppcext.dll|sppcext.dll.mui
    Tampered File: %systemroot%\system32\sppwinob.dll
    Tampered File: %systemroot%\system32\slc.dll|slc.dll.mui
    Tampered File: %systemroot%\system32\slcext.dll|slcext.dll.mui
    Tampered File: %systemroot%\system32\sppuinotify.dll|sppuinotify.dll.mui
    Tampered File: %systemroot%\system32\slui.exe|slui.exe.mui|COM Registration
    Tampered File: %systemroot%\system32\sppcomapi.dll|sppcomapi.dll.mui
    Tampered File: %systemroot%\system32\sppcommdlg.dll|sppcommdlg.dll.mui
    Tampered File: %systemroot%\system32\sppsvc.exe|sppsvc.exe.mui
    Tampered File: %systemroot%\system32\drivers\spsys.sys


    HWID Data-->
    HWID Hash Current: LgAAAAEAAAABAAEAAQADAAAAAQABAAEAln2uFWwj6EgwDf6FEoa6Y71+DnRGyg==

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes, but no SLIC table
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information:
      ACPI Table Name OEMID Value OEMTableID Value
      APIC   INTEL   DG45ID 
      FACP   INTEL  A M I
      MCFG   INTEL   DG45ID 
      ASF!   INTEL   DG45ID 

     

    Friday, September 16, 2011 6:56 PM

Answers

  • Problem SOLVED! After running sfc /scannow, chkdsk /r, secedit, etc...  all of which appeared to not finish fully due to log writing errors, I ran an upgrade reinstall from the installation DVD in windows and after the install finished, Internet Explorer 9 and Windows 7 Service Pack one and all other updates installed fine.

    For whatever reason, the upgrade reinstall took an exceptionally long time, maybe as it was repairing the file and folder security?  In any case the upgrade install took just over an hour on our 8GB Quad core machine, when the original fresh load of windows took around 20 minutes.

    Thinking back, I can't remember one catalyst, but this could have happened after we replaced the main drive and cloned the OS to the new drive...that was the last time we can remember when it was last updating properly.

    Sunday, September 18, 2011 4:51 AM

All replies

  • Make sure that the software protection service is running.

    Use system restore to recover to a time before the issue.  If that does not work, try the system file scanner.

    Click Start, type 'cmd' in the Search/Run box, and right click on the CMD icon at the top of the results pane.  Select Run as Administrator.  When the cmd window opens type 'sfc /scannow' at the prompt and hit Enter.  When the scan completes close the cmd window. 

    Restart and paste another MGADiag report in your reply.


    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.
    Friday, September 16, 2011 7:45 PM
    Answerer
  • "Crown Computers" wrote in message news:3acec99c-11eb-4973-a233-12404f74afcf...

    PLEASE HELP, we randomly get a popup on our machine that is is not genuine and windows will not update.

    Only some select updates will install on our machine, all the rest fail.  Windows is activated, but going to genuine advantage suggests that this version of windows is not genuine?  I am 100% certain my version of windows is genuine.  We are a Microsoft Action Pack member andour subscription is current.  This copy of windows was download direct from the microsoft action pack site and it has only been installed on this machine, NEVER installed on any other!

    1) Windows 7 Ultimate

    2) From Microsoft Action Pack, software downloaded from them and key form them

    Here is the copy of the text from the Windows Genuine Diagnostic Tool.  PLEASE HELP!


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

    Validation Code: 0x8004FE21
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-HCY7G-636BQ-4QPD6
    Windows Product Key Hash: zzdt1g1K/wR8hlENWVPhGToWgFM=
    Windows Product ID: 00426-948-1670601-85299
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7600.2.00010100.0.0.001

    File Scan Data-->
    File Mismatch: C:\Windows\system32\wat\watadminsvc.exe[7.1.7600.16395], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\wat\watux.exe[7.1.7600.16395], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\sppobjs.dll[6.1.7600.16385], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\sppc.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppcext.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppwinob.dll[6.1.7600.16385], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\slc.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\slcext.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppuinotify.dll[6.1.7600.16385], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\slui.exe[6.1.7600.16385], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\sppcomapi.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppcommdlg.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\sppsvc.exe[6.1.7600.16385], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\drivers\spsys.sys[6.1.7127.0], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\drivers\spldr.sys[6.1.7127.0], Hr = 0x80092003
    File Mismatch: C:\Windows\system32\systemcpl.dll[6.1.7600.16385], Hr = 0x800b0100
    File Mismatch: C:\Windows\system32\user32.dll[6.1.7600.16385], Hr = 0x800b0100

     

    Your problem is caused by the file mismatches above – unfortunately, to date, we’ve been unable to fix this particular set of mismatches in the forums.
    Try running the CheckSUR tool and upload the resulting log files to your sky drive – it may help.
     
     
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Friday, September 16, 2011 7:47 PM
    Moderator
  • Software protection was not running - started now

    System restore not an option, problem has existed for nearly a year and I finally got around to focusing on repairing it.

    Running SFC now

    Will Advise later

    Friday, September 16, 2011 7:50 PM
  • SFC Failed, see below:

    C:\>sfc /scannow

    Beginning system scan.  This process will take some time.

    Beginning verification phase of system scan.
    Verification 100% complete.
    Windows Resource Protection found corrupt files but was unable to fix some of th
    em.
    Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
    C:\Windows\Logs\CBS\CBS.log

    Friday, September 16, 2011 7:52 PM
  • Really!  You sound confident.  That does not sound completely reasonable to me.  I will try what you suggest within 24 hours.  So, sounds like your saying wipe and reload short of a miracle from the CheckSUR tool results.  PS. an SFC scan did fail as noted above...would that matter?

    Friday, September 16, 2011 7:55 PM
  • I ran the checksur tool update and it completed successfully.  However, for some reason it did not create any checksur log files in the CBS folder?????
    Friday, September 16, 2011 8:57 PM
  • "Crown Computers" wrote in message news:a0c5fa7c-e4cf-4c93-b2c2-b04f47ae27cb...

    Really!  You sound confident.  That does not sound completely reasonable to me.  I will try what you suggest within 24 hours.  So, sounds like your saying wipe and reload short of a miracle from the CheckSUR tool results.  PS. an SFC scan did fail as noted above...would that matter?

    Wipe & reload would work, yes – but a repair install may also work, and should preserve data and settings.
     
    SFC looks at different things to the CheckSUR tool – and works in a different way. I have honestly no idea whether it would work, but it is updated relatively frequently with new fixes, and may show some details that the SFC doesn’t, so feel free to post the logs from both to your SkyDrive and post the links here.
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Friday, September 16, 2011 9:04 PM
    Moderator
  • "Crown Computers" wrote in message news:69e9ee57-7702-4dbd-8793-7ff43d3f6875...
    I ran the checksur tool update and it completed successfully.  However, for some reason it did not create any checksur log files in the CBS folder?????
     
     
    First time I’ve heard of that one!
    Please run another MGADiag report, and put the SFC log on your SkyDrive.
     

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Friday, September 16, 2011 9:37 PM
    Moderator
  • After more digging, not only did the checksur not leave a report, but I did a chkdsk /r from a windows 7 boot disc, and it also reported to me that it could not write a log...error 50 or the like.  I am beginning to suspect that the heart of this issue is that some of the system folders may somehow have altered permissions?  PS, when I went in to look at the CBS log from the failed scannow I had to add security to the folder so I could access the file

    Any idea how I might fix this?

    Saturday, September 17, 2011 10:10 PM
  • "Crown Computers" wrote in message news:9a3b178e-e851-4b7f-a47b-eaeae7fbe731...

    After more digging, not only did the checksur not leave a report, but I did a chkdsk /r from a windows 7 boot disc, and it also reported to me that it could not write a log...error 50 or the like.  I am beginning to suspect that the heart of this issue is that some of the system folders may somehow have altered permissions?  PS, when I went in to look at the CBS log from the failed scannow I had to add security to the folder so I could access the file

    Any idea how I might fix this?

    The usual reason for this type of thing is where the System32 folder has become read-only somehow – but yours sounds a more complex problem.
    Please check permissions on the System32 folder – specifically the Administrator and Trusted Installer ones.

    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Saturday, September 17, 2011 10:21 PM
    Moderator
  • Problem SOLVED! After running sfc /scannow, chkdsk /r, secedit, etc...  all of which appeared to not finish fully due to log writing errors, I ran an upgrade reinstall from the installation DVD in windows and after the install finished, Internet Explorer 9 and Windows 7 Service Pack one and all other updates installed fine.

    For whatever reason, the upgrade reinstall took an exceptionally long time, maybe as it was repairing the file and folder security?  In any case the upgrade install took just over an hour on our 8GB Quad core machine, when the original fresh load of windows took around 20 minutes.

    Thinking back, I can't remember one catalyst, but this could have happened after we replaced the main drive and cloned the OS to the new drive...that was the last time we can remember when it was last updating properly.

    Sunday, September 18, 2011 4:51 AM