Windows 7 Home Premium (64 bit) reports it's not Genuine anymore

All replies

• 

  

  0

  Sign in to vote

  Also, no hardware has been changed in the laptop nor has a system restore from the DVDs ever been done.

  Friday, February 17, 2012 12:39 AM
• 

  

  0

  Sign in to vote

  Below are things you can try to repair the files and resolve the issue:

  First try doing a System Scan. The scan will look for bad system 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.

  If that doesn't work, try 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.

  ---

  Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.

  • Proposed as answer by Darin Smith MS Friday, February 17, 2012 11:17 PM
  • Unproposed as answer by Grinnell Saturday, February 18, 2012 3:06 AM

  Friday, February 17, 2012 2:03 AM

  Answerer
• 

  

  0

  Sign in to vote

  "Grinnell" wrote in message news:db61a361-593c-4f82-bb39-8d3c457f0050...

   

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

  Validation Code: 0x8004FE21
  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.7600.2.00010300.0.0.003
  

  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

   

  
   

   

   

  The set of file mismatches above are typical of one of three causes:-

  1) a restore from an image backup of the system

  2) a failed driver update

  3) a disabled Cryptographic service

  The main one for which we currently have a solution is the second.....

  Installing the Intel Rapid Storage Drivers

  try downloading and installing them from here -

  http://downloadcenter.intel.com/Detail_Desc.aspx?ProductID=2101&DwnldID=20215&lang=eng&iid=dc_rss

  Once complete, please reboot twice, then post another MGADiag report.

  Note that if this set of drivers fails to install, there is a second set that could also cure the problem – from

  http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=hr&prodTypeId=12454&prodSeriesId=5060844&prodNameId=5060846&swEnvOID=4054&swLang=13&mode=2&taskId=135&swItem=vc-93541-1

  Good Luck!

  ---

  Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

  • Proposed as answer by Darin Smith MS Friday, February 17, 2012 11:17 PM

  Friday, February 17, 2012 8:42 AM

  Moderator
• 

  

  0

  Sign in to vote

  Concerning the first two suggestions:

  SFC reported that it could not fix all the problems.  And it didn't.

  System Restore shows no points that were useful (the oldest is only a week old, and it's apparently creating them almost every day due to (unsuccessfully) attempting to install Microsoft Updates!).  This is not going to help unless there is some way of accessing a MUCH older restore point.  And again, there had never been a Restore performed.

  Saturday, February 18, 2012 2:51 AM
• 

  

  0

  Sign in to vote

  1.  None has ever been done.

  3.  Unless something came on the laptop from HP, no such items should be on the PC.

  2.  Is there something in the original MGADiag log that suggests that Intel Rapid Storage Drivers are a problem or their update failed?  Or are they a known problem item for WGA?  I haven't been able to try this yet (maybe tomorrow).

  
  Is there some kind of Repair or restore I can do from my DVD install package for Windows Home Premium (32 and 64 bit versions) Upgrade (from Vista)?

  Saturday, February 18, 2012 3:05 AM
• 

  

  0

  Sign in to vote

  The report does not look for the Intel RS drivers but the drivers have caused similar problems lately.

  Since you have retail Windows dvds you can perform an in-place-upgrade (aka "repair install") but you will have to use one of the family pack product keys when you do.  There is no way to do a repair install with your OEM recovery disks.  Those can only reinstall the original software.

  An in-place-upgrade does not require reinstallation of programs and files but I would use Windows Easy Transfer to save your files and settings just in case something goes wrong. 

  To do an in-place-upgrade you proceed exactly the same as you do when you upgrade Windows 7 from one edition to another.  You start Windows, insert the Family Pack dvd, run Setup from the desktop by clicking Install Now on the splash screen, enter the Family Pack product key, and choose Upgrade Install when asked for the installation type. 

  The service pack level on the dvd must be equal to or greater than the service pack level installed on the hard drive.  Since it appears you have not installed SP1 on the hard drive you should have no problem regardless of when you got the Family Pack.  Afterwards you will need to go to Windows Update and reapply all the updates released after your Family Pack Windows 7 released.  If your Family Pack dvds do not say "SP1 included" it would be a very good time to upgrade to SP1 and avoid installing at least some of the individual updates.

  ---

  Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.

  
  
  
  

  • Edited by CbarnhorstEditor Saturday, February 18, 2012 4:24 AM

  Saturday, February 18, 2012 4:09 AM

  Answerer
• 

  

  0

  Sign in to vote

  "Grinnell" wrote in message news:e6dbf4df-7a53-4e9b-99c8-75886c2bee77...

  1.  None has ever been done.

  3.  Unless something came on the laptop from HP, no such items should be on the PC.

  2.  Is there something in the original MGADiag log that suggests that Intel Rapid Storage Drivers are a problem or their update failed?  Or are they a known problem item for WGA?  I haven't been able to try this yet (maybe tomorrow).

  
  Is there some kind of Repair or restore I can do from my DVD install package for Windows Home Premium (32 and 64 bit versions) Upgrade (from Vista)?

  The problem is actually one of HP’s making :)

  As  understand it, they installed a dodgy set of drivers that weren’t fully compliant, and an update broke something.

  DO NOT bother with a reinstall – you’ll end up with the same problem eventually.

  Just update the drivers, and run the MGADiag again to check that the problem has gone.

   

  ---

  Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

  Saturday, February 18, 2012 10:32 AM

  Moderator
• 

  

  0

  Sign in to vote

  "Noel Paton" wrote:

  The main one for which we currently have a solution is the second.....

  Installing the Intel Rapid Storage Drivers

  try downloading and installing them from here -

  http://downloadcenter.intel.com/Detail_Desc.aspx?ProductID=2101&DwnldID=20215&lang=eng&iid=dc_rss

  Once complete, please reboot twice, then post another MGADiag report.

  Note that if this set of drivers fails to install, there is a second set that could also cure the problem – from

  http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=hr&prodTypeId=12454&prodSeriesId=5060844&prodNameId=5060846&swEnvOID=4054&swLang=13&mode=2&taskId=135&swItem=vc-93541-1

  Good Luck!

  ---

  Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

  I finally got enough time to try the Intel link and try alternates when the Intel link above didn't work, as noted in another thread, but I used your substitute from there of:

  "Blasted Intel keep changing their Search format :(

  "try this link....

  http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=20624&ProdId=2101&lang=eng&OSVersion=%0A&DownloadType=Drivers&OSVersion=%0A&DownloadType=Drivers "

  The drivers seemed to uninstall the old and install the new correctly, and i rebooted twice.

  MS Updates seem to still fail, but the Not Genuine error message has not yet poped up.  I did not try the HP link. (yet.)

  Here is the updated MGA report:

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

  Validation Code: 0x8004FE21
  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.7600.2.00010300.0.0.003
  ID: {01E86BEA-AE85-42CE-884A-35E2A903A898}(3)
  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: 7600.win7_gdr.110622-1503
  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:\PROGRA~2\MOZILL~1\FIREFOX.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>{01E86BEA-AE85-42CE-884A-35E2A903A898}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010300.0.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-3Q6C9</PKey><PID>00359-OEM-8992687-00010</PID><PIDType>2</PIDType><SID>S-1-5-21-3324083032-2110168627-1205226150</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP Pavilion dv4 Notebook PC</Model></SYSTEM><BIOS><Manufacturer>Insyde</Manufacturer><Version>F.0C</Version><SMBIOSVersion major="2" minor="6"/><Date>20100330000000.000000+000</Date></BIOS><HWID>88BA3607018400FC</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Pacific Standard Time(GMT-08: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.7600.16385

  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-7600.0000-1272010
  Installation ID: 004340935903929450718350692983180430117153419825187955
  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: Licensed
  Remaining Windows rearm count: 1
  Trusted time: 2/20/2012 10:29:31 PM

  Windows Activation Technologies-->
  HrOffline: 0x8004FE21
  HrOnline: N/A
  HealthStatus: 0x000000000001EFF0
  Event Time Stamp: 2:18:2012 14:08
  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: LAAAAAEAAQABAAEAAAABAAAAAgABAAEA6GHSR88PtjQq7pDHFKsod7TMXF0=

  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      SLIC-MPC
    HPET   HPQOEM  SLIC-MPC
    BOOT   HPQOEM  SLIC-MPC
    MCFG   HPQOEM  SLIC-MPC
    WDRT   HPQOEM  SLIC-MPC
    ASF!   HPQOEM  SLIC-MPC
    SLIC   HPQOEM  SLIC-MPC
    SSDT   TrmRef  PtidDevc
    SSDT   TrmRef  PtidDevc
    SSDT   TrmRef  PtidDevc
    SSDT   TrmRef  PtidDevc
    SSDT   TrmRef  PtidDevc
    SPCR   HPQOEM  SLIC-MPC
    ASPT   HPQOEM  SLIC-MPC
    SSDT   TrmRef  PtidDevc

  Since I don't know how to interpret it, does it say I'm fixed or not, and what now?  Thanks.

  Tuesday, February 21, 2012 6:48 AM
• 

  

  0

  Sign in to vote

  "Grinnell" wrote in message news:e428b9b1-e514-4f3e-8dbf-5e20f7a50d61...

  Here is the updated MGA report:

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

  Validation Code: 0x8004FE21
  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.7600.2.00010300.0.0.003
  

  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

  Since I don't know how to interpret it, does it say I'm fixed or not, and what now?  Thanks.

  Sorry – it’s still the same.

  Which version of the drivers did you end up installing?

  Have you tried installing the HP set?

  ---

  Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
  
  

  • Edited by Noel D PatonModerator Tuesday, February 21, 2012 11:29 AM

  Tuesday, February 21, 2012 8:18 AM

  Moderator
• 

  

  0

  Sign in to vote

  Concerning the first two suggestions:

  SFC reported that it could not fix all the problems.  And it didn't.

  I didn't notice this before.

  Please upload your C:\Windows\Logs\CBS\CBS.log file to your public SkyDrive, or other fileshare service, and post a link in your response - it may give a clue as to what the problem is.

  ---

  Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

  Tuesday, February 21, 2012 11:33 AM

  Moderator
• 

  

  0

  Sign in to vote

  I'll post the CBS file on Friday when I reconnect with the troublesome laptop and have figured out where and how to post such a file.

  Wednesday, February 22, 2012 2:56 PM
• 

  

  0

  Sign in to vote

  No reply from the Original Poster.

  Issue is assumed to be resolved.

  Unknown what post (if any) resolved the issue.

  ---

  Darin MS

  
  

  • Marked as answer by Darin Smith MS Monday, February 27, 2012 11:34 PM
  • Edited by Darin Smith MS Monday, February 27, 2012 11:34 PM

  Monday, February 27, 2012 11:29 PM