Windows 7 Not Genuine Error

All replies

• 

  

  0

  Sign in to vote

  "S. Alan" wrote in message news:73fdd0ce-3e96-4e80-a850-9b4b54749df6...

  Hi,

  I have just been hit with the "This computer is not running genuine Windows" problem.  The laptop is a 2 year-old Acer that came with a free Win7 upgrade which was applied about a year ago.  No problem until now.  Last thing significant I did was change to a new internal hard disk.   Appreciate if someone can review and advise.

  Diagnostic report below:

  Diagnostic Report (1.9.0027.0):

  -----------------------------------------

  Windows Validation Data-->

   

  Validation Code: 0x8004FE21

  Cached Online Validation Code: 0x0

  Windows Product Key: *****-*****-GKCRB-FPV86-FD6QM

  Windows Product Key Hash: 4nWyRJvTGP/2PyQ+1NfeCRSksMw=

  Windows Product ID: 00359-OEM-8882234-48241

  Windows Product ID Type: 3

  Windows License Type: OEM System Builder

  Windows OS version: 6.1.7601.2.00010300.1.0.003

   

  File Scan Data-->

  File Mismatch: C:\Windows\system32\sppobjs.dll[6.1.7601.17514], Hr = 0x800b0100

  File Mismatch: C:\Windows\system32\sppc.dll[6.1.7601.17514], Hr = 0x800b0100

  File Mismatch: C:\Windows\system32\sppcext.dll[6.1.7600.16385], Hr = 0x800b0100

  File Mismatch: C:\Windows\system32\sppwinob.dll[6.1.7601.17514], Hr = 0x800b0100

  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.7601.17514], Hr = 0x800b0100

  File Mismatch: C:\Windows\system32\slui.exe[6.1.7601.17514], Hr = 0x800b0100

  File Mismatch: C:\Windows\system32\sppcomapi.dll[6.1.7601.17514], Hr = 0x800b0100

  File Mismatch: C:\Windows\system32\sppcommdlg.dll[6.1.7600.16385], Hr = 0x800b0100

  File Mismatch: C:\Windows\system32\sppsvc.exe[6.1.7601.17514], Hr = 0x800b0100

  File Mismatch: C:\Windows\system32\drivers\spsys.sys[6.1.7127.0], Hr = 0x800b0100

  File Mismatch: C:\Windows\system32\systemcpl.dll[6.1.7601.17514], Hr = 0x800b0100

  File Mismatch: C:\Windows\system32\user32.dll[6.1.7601.17514], Hr = 0x800b0100

   

  Other data-->

  SYSTEM><Manufacturer>Acer            </Manufacturer><Model>Aspire 4736     </Model></SYSTEM><BIOS><Manufacturer>Acer</Manufacturer><Version>V1.05</Version><SMBIOSVersion major="2" minor="4"/><Date>20090330000000.000000+000</Date></BIOS

   

  Licensing Data-->

  Software licensing service version: 6.1.7601.17514

   

  Name: Windows(R) 7, HomePremium edition

  Description: Windows Operating System - Windows(R) 7, OEM_COA_NSLP channel

  Partial Product Key: FD6QM

  License Status: Licensed

  Remaining Windows rearm count: 5

  Trusted time: 26/9/2011 4:05:48 PM

   

  OEM Activation 2.0 Data-->

  BIOS valid for OA 2.0: yes

  Windows marker version: 0x0

   

   

   

  It looks to me as if this machine was one of the ones which came with a free Upgrade offer when Win7 was first released?

   

  Your problem is the list of File Mismatches highlighted above.

  This set of files is often seen when the user has used 3rd-party software to transfer the installation from one hard drive to another, or to back up and restore an installation.

  Unfortunately, we have not yet been able to reproduce the problem, and find a way of fixing it, in these forums.

   

  The only ‘solutions’ found so far appear to be either a repair install using Retail media, or a complete reformat/reinstall – although one or two users have said that uninstalling and reinstalling Service Pack 1 fixed the problem.

   

  You could try MSWGA Support to see if they have any better news – but the latest news we have from them is pretty much the same.

  WGA Support can be found here.
  North America: http://support.microsoft.com/contactus/cu_sc_genadv_master?ws=support&ws=support#tab4
  
  Outside North America:
  http://support.microsoft.com/contactus/?ws=support#tab0
  
  Please let us know if (and how) MS manage to repair the problem without a repair install of the OS - it would be useful for future reference!

   

  ---

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

  • Marked as answer by Darin Smith MS Tuesday, September 27, 2011 9:46 PM
  • Unmarked as answer by S. Alan Wednesday, September 28, 2011 12:41 AM
  • Marked as answer by Darin Smith MS Tuesday, October 4, 2011 9:08 PM

  Monday, September 26, 2011 11:20 AM

  Moderator
• 

  

  0

  Sign in to vote

  Sorry to report that the problem has not been resolved after trying the following:

  1. Uninstall and re-install service pack 1 - Managed to uninstall the service pack, but re-installation failed with a 8000ffff error.  Following the suggestions from the support page, I tried running the windows update readiness tool, which now failed with a 8000247 error.  Still following the line of action, I tried running the MS Fix It tool that reset/repairs windows update components.  That worked, but both earlier tasks still failed with the same error. 

  2. MS WGA doesn't have anything useful to offer.  Basically reinstall Win7 from original media, which I am resisting because it takes too much time to re-install all my software.

  3. I've tried doing a repair install using the Win7 media that I got as a free upgrade with the purchase of my laptop.  The only acceptable option I could find when I ran from the DVD was to do an upgrade from the current installed Windows version.  That failed because they said the installed version is newer than the "upgrade" version on the media.  Doing a custom install would be the same as re-installing from scratch because I would have to re-install all my existing software.  Or did I miss something?

  Any other ideas?

  Tuesday, September 27, 2011 11:49 PM
• 

  

  0

  Sign in to vote

  By the way, Noel mentioned that my problem is "often seen when the user has used 3rd-party software to transfer the installation from one hard drive to anotherr".  Yes, I had used the Acronis software that came with the hard disk to clone the old hard disk.  I'm curious if there is another way to doing this using Microsoft software that will overcome this problem?  I still have my old hard disk, and would rather redo the cloning than the re-install Win7 if that is a feasible option.

  Wednesday, September 28, 2011 12:46 AM
• 

  

  0

  Sign in to vote

  "S. Alan" wrote in message news:dfc7a8cb-76f9-4c8f-9890-c83928d5a7b2...

  By the way, Noel mentioned that my problem is "often seen when the user has used 3rd-party software to transfer the installation from one hard drive to anotherr".  Yes, I had used the Acronis software that came with the hard disk to clone the old hard disk.  I'm curious if there is another way to doing this using Microsoft software that will overcome this problem?  I still have my old hard disk, and would rather redo the cloning than the re-install Win7 if that is a feasible option.

   

   

  Windows 7 comes with its own full system backup capability which can do the job.

  http://windows.microsoft.com/en-US/windows7/products/features/backup-and-restore

   

  ---

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

  Thursday, September 29, 2011 6:06 AM

  Moderator
• 

  

  0

  Sign in to vote

  "S. Alan" wrote in message news:b2b6cee1-222c-45b3-b887-2a53958b6d73...

  Sorry to report that the problem has not been resolved after trying the following:

  1. Uninstall and re-install service pack 1 - Managed to uninstall the service pack, but re-installation failed with a 8000ffff error.  Following the suggestions from the support page, I tried running the windows update readiness tool, which now failed with a 8000247 error.  Still following the line of action, I tried running the MS Fix It tool that reset/repairs windows update components.  That worked, but both earlier tasks still failed with the same error.

  2. MS WGA doesn't have anything useful to offer.  Basically reinstall Win7 from original media, which I am resisting because it takes too much time to re-install all my software.

  3. I've tried doing a repair install using the Win7 media that I got as a free upgrade with the purchase of my laptop.  The only acceptable option I could find when I ran from the DVD was to do an upgrade from the current installed Windows version.  That failed because they said the installed version is newer than the "upgrade" version on the media.  Doing a custom install would be the same as re-installing from scratch because I would have to re-install all my existing software.  Or did I miss something?

  Any other ideas?

   

  The repair install possibly failed because you attempted it while SP1 was still present – it should be OK once sp1 is removed.

  Note that you should uninstall completely any anti-virus product, since this is often a cause of problems with installing the Service Pack.

  Since your problem is now with a Service Pack installation, you should either post in a Windows Updates forum, or request assistance (free) from MS direct - http://support.microsoft.com/ph/6527

  ---

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

  Thursday, September 29, 2011 6:11 AM

  Moderator
• 

  

  0

  Sign in to vote

  The repair install still failed at the last step ("transferring files & programs" or something like that).  I even tried on a clean boot but same result.

  This is taking a bit more time than I can afford right now.  I could seek MS help with the service pack installation, but I suspect that would still not solve the original problem. 

   I've googled for similar problems and it seems this happens quite a lot.  I really wish MS could offer a more definitive solution for users.  I've also read that people do not advise doing a disk clone operation with MS Backup and Restore, and ironically one of the recommended tools was Acronis True Image, which I used.  The other is Paragon, which I will probably try.  If the problem arose due to disk cloning, then I'd rather try to solve it at the source, i.e. do the cloning another way which will not have MS thinking that Win7 is not genuine.

  Thursday, September 29, 2011 2:21 PM
• 

  

  0

  Sign in to vote

  "S. Alan" wrote in message news:c38cc556-4026-4373-9dc8-be25f7dd873b...

  The repair install still failed at the last step ("transferring files & programs" or something like that).  I even tried on a clean boot but same result.

  This is taking a bit more time than I can afford right now.  I could seek MS help with the service pack installation, but I suspect that would still not solve the original problem.

  I've googled for similar problems and it seems this happens quite a lot.  I really wish MS could offer a more definitive solution for users.  I've also read that people do not advise doing a disk clone operation with MS Backup and Restore, and ironically one of the recommended tools was Acronis True Image, which I used.  The other is Paragon, which I will probably try.  If the problem arose due to disk cloning, then I'd rather try to solve it at the source, i.e. do the cloning another way which will not have MS thinking that Win7 is not genuine.

  When you consider the number of installations of Windows, the failure rate is pretty small, and most of those are attributable to corruption caused by malware or bad practise.

  Unfortunately, the quickest route to a fix is almost certain to be a nuke&pave reinstall  - so I’d start backing up now.

  ---

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

  Thursday, September 29, 2011 3:40 PM

  Moderator
• 

  

  0

  Sign in to vote

  "S. Alan" wrote in message news:c38cc556-4026-4373-9dc8-be25f7dd873b...

  The repair install still failed at the last step ("transferring files & programs" or something like that).  I even tried on a clean boot but same result.

  This is taking a bit more time than I can afford right now.  I could seek MS help with the service pack installation, but I suspect that would still not solve the original problem.

  I've googled for similar problems and it seems this happens quite a lot.  I really wish MS could offer a more definitive solution for users.  I've also read that people do not advise doing a disk clone operation with MS Backup and Restore, and ironically one of the recommended tools was Acronis True Image, which I used.  The other is Paragon, which I will probably try.  If the problem arose due to disk cloning, then I'd rather try to solve it at the source, i.e. do the cloning another way which will not have MS thinking that Win7 is not genuine.

  When you consider the number of installations of Windows, the failure rate is pretty small, and most of those are attributable to corruption caused by malware or bad practise.

  Unfortunately, the quickest route to a fix is almost certain to be a nuke&pave reinstall  - so I’d start backing up now.

  ---

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

  
  Well, I won't argue about the percentage of failure rate, but I doubt many of the problems are caused by malware or bad practice.  Certainly not in my case.  There is no evidence of malware, and the problem more or less coincided with the upgrading to a new hard disk.  I would argue that if there was malware, the problem would have surfaced even if I had not done the disk upgrade, but I did not have problems before.  Secondly, using the disk cloning software provided by the hard disk manufacturer (Acronis True Image in this case) would surely not qualify as bad practice.  In fact Acronis has been recommended by many users as a better tool than MS Backup and Restore.

  Now for an update.  I have gone back to my original hard disk, used MS Backup and Restore to save my files and system image to an external hard disk, then used a rescue disc to boot up and restore the system to the new hard disk.  That took many hours but at least not much intervention was needed so I just let it run and went about doing other stuff.

  Now for the bottomline.  So far no problems yet, but I ran MGADiag again just to check.  The results are pasted below.  Am I mistaken or are the file corruption/mismatches still there?

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

  Validation Code: 0x8004FE21
  Cached Online Validation Code: 0x0
  Windows Product Key: *****-*****-GKCRB-FPV86-FD6QM
  Windows Product Key Hash: 4nWyRJvTGP/2PyQ+1NfeCRSksMw=
  Windows Product ID: 00359-OEM-8882234-48241
  Windows Product ID Type: 3
  Windows License Type: OEM System Builder
  Windows OS version: 6.1.7601.2.00010300.1.0.003
  ID: {DB99EA0B-3C50-41FA-B7A8-9C4A33E6FAEB}(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: 0x00000000
  Build lab: 7601.win7sp1_gdr.110622-1506
  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 Home and Student 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\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\sppobjs.dll[6.1.7601.17514], Hr = 0x800b0100
  File Mismatch: C:\Windows\system32\sppc.dll[6.1.7601.17514], Hr = 0x800b0100
  File Mismatch: C:\Windows\system32\sppcext.dll[6.1.7600.16385], Hr = 0x800b0100
  File Mismatch: C:\Windows\system32\sppwinob.dll[6.1.7601.17514], Hr = 0x800b0100
  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.7601.17514], Hr = 0x800b0100
  File Mismatch: C:\Windows\system32\slui.exe[6.1.7601.17514], Hr = 0x800b0100
  File Mismatch: C:\Windows\system32\sppcomapi.dll[6.1.7601.17514], Hr = 0x800b0100
  File Mismatch: C:\Windows\system32\sppcommdlg.dll[6.1.7600.16385], Hr = 0x800b0100
  File Mismatch: C:\Windows\system32\sppsvc.exe[6.1.7601.17514], Hr = 0x800b0100
  File Mismatch: C:\Windows\system32\drivers\spsys.sys[6.1.7127.0], Hr = 0x800b0100
  File Mismatch: C:\Windows\system32\systemcpl.dll[6.1.7601.17514], Hr = 0x800b0100
  File Mismatch: C:\Windows\system32\user32.dll[6.1.7601.17514], Hr = 0x800b0100

  Other data-->
  Office Details: <GenuineResults><MachineData><UGUID>{DB99EA0B-3C50-41FA-B7A8-9C4A33E6FAEB}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-FD6QM</PKey><PID>00359-OEM-8882234-48241</PID><PIDType>3</PIDType><SID>S-1-5-21-3136223725-2940333540-554230609</SID><SYSTEM><Manufacturer>Acer            </Manufacturer><Model>Aspire 4736     </Model></SYSTEM><BIOS><Manufacturer>Acer</Manufacturer><Version>V1.05</Version><SMBIOSVersion major="2" minor="4"/><Date>20090330000000.000000+000</Date></BIOS><HWID>C6CD3B07018400F8</HWID><UserLCID>4809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Malay Peninsula Standard Time(GMT+08:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>ACRSYS</OEMID><OEMTableID>ACRPRDCT</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-002F-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Home and Student 2007</Name><Ver>12</Ver><Val>1CC88CF95345F38</Val><Hash>Kib9cu06y0+g4y6+dca4/OJB1HM=</Hash><Pid>81602-924-2069263-68559</Pid><PidType>1</PidType></Product></Products><Applications><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="A1" 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_COA_NSLP channel
  Activation ID: 9f83d90f-a151-4665-ae69-30b3f63ec659
  Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
  Extended PID: 00359-00176-822-348241-02-18441-7600.0000-3232009
  Installation ID: 002126919400884183656333122172672814843946479284111500
  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: FD6QM
  License Status: Licensed
  Remaining Windows rearm count: 5
  Trusted time: 1/10/2011 11:17:50 PM

  Windows Activation Technologies-->
  HrOffline: 0x8004FE21
  HrOnline: N/A
  HealthStatus: 0x000000000001EFF0
  Event Time Stamp: 9:30:2011 22:05
  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: NAAAAAIAAQABAAIAAQABAAAAAwABAAEAeqgWbE40XoHejCzagok+r96IAG6aKmjO1K1Gyg==

  OEM Activation 1.0 Data-->
  N/A

  OEM Activation 2.0 Data-->
  BIOS valid for OA 2.0: yes
  Windows marker version: 0x0
  OEMID and OEMTableID Consistent: yes
  BIOS Information:
    ACPI Table Name OEMID Value OEMTableID Value
    APIC   ACRSYS  ACRPRDCT
    FACP   ACRSYS  ACRPRDCT
    HPET   ACRSYS  ACRPRDCT
    BOOT   ACRSYS  ACRPRDCT
    MCFG   ACRSYS  ACRPRDCT
    ASF!   ACRSYS  ACRPRDCT
    SLIC   ACRSYS  ACRPRDCT
    SSDT   PmRef  CpuPm

   

  
  

  • Edited by S. Alan Saturday, October 1, 2011 3:19 PM

  Saturday, October 1, 2011 3:18 PM
• 

  

  0

  Sign in to vote

  "S. Alan" wrote in message news:cb8e1fa0-3984-4d11-b674-762bf56b0ad3...

  "S. Alan" wrote in message news:c38cc556-4026-4373-9dc8-be25f7dd873b...

  The repair install still failed at the last step ("transferring files & programs" or something like that).  I even tried on a clean boot but same result.

  This is taking a bit more time than I can afford right now.  I could seek MS help with the service pack installation, but I suspect that would still not solve the original problem.

  I've googled for similar problems and it seems this happens quite a lot.  I really wish MS could offer a more definitive solution for users.  I've also read that people do not advise doing a disk clone operation with MS Backup and Restore, and ironically one of the recommended tools was Acronis True Image, which I used.  The other is Paragon, which I will probably try.  If the problem arose due to disk cloning, then I'd rather try to solve it at the source, i.e. do the cloning another way which will not have MS thinking that Win7 is not genuine.

  When you consider the number of installations of Windows, the failure rate is pretty small, and most of those are attributable to corruption caused by malware or bad practise.

  Unfortunately, the quickest route to a fix is almost certain to be a nuke&pave reinstall  - so I’d start backing up now.

  ---

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

  
  Well, I won't argue about the percentage of failure rate, but I doubt many of the problems are caused by malware or bad practice.  Certainly not in my case.  There is no evidence of malware, and the problem more or less coincided with the upgrading to a new hard disk.  I would argue that if there was malware, the problem would have surfaced even if I had not done the disk upgrade, but I did not have problems before.  Secondly, using the disk cloning software provided by the hard disk manufacturer (Acronis True Image in this case) would surely not qualify as bad practice.  In fact Acronis has been recommended by many users as a better tool than MS Backup and Restore.

  Now for an update.  I have gone back to my original hard disk, used MS Backup and Restore to save my files and system image to an external hard disk, then used a rescue disc to boot up and restore the system to the new hard disk.  That took many hours but at least not much intervention was needed so I just let it run and went about doing other stuff.

  Now for the bottomline.  So far no problems yet, but I ran MGADiag again just to check.  The results are pasted below.  Am I mistaken or are the file corruption/mismatches still there?

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

  Validation Code: 0x8004FE21
  Cached Online Validation Code: 0x0
  Windows Product Key: *****-*****-GKCRB-FPV86-FD6QM
  Windows Product Key Hash: 4nWyRJvTGP/2PyQ+1NfeCRSksMw=
  Windows Product ID: 00359-OEM-8882234-48241
  Windows Product ID Type: 3
  Windows License Type: OEM System Builder
  Windows OS version: 6.1.7601.2.00010300.1.0.003
  

  Windows Activation Technologies-->
  HrOffline: 0x8004FE21
  HrOnline: N/A
  HealthStatus: 0x000000000001EFF0
  Event Time Stamp: 9:30:2011 22:05
  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

   

   

   

  Unfortunately,  it looks as if you’re right – which means either that the  problem predates your backup, or that there is something else going on.

  I honestly have no idea where to go from here, except to again point you in the direction of either WGA Support, or a reinstall.

   

   

  ---

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

  Saturday, October 1, 2011 3:57 PM

  Moderator
• 

  

  0

  Sign in to vote

  Thanks for your input so far anyway.

  I just wanted to confirm that my original installation wasn't the problem, so I switched back to my old hard disk and ran MGADiag again.  The output is appended below, and if I am not mistaken it was a clean bill of health.  So, that has to mean something went wrong with the Backup and Restore, despite me using the MS tool itself to do that.

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

  Validation Code: 0
  Cached Online Validation Code: 0x0
  Windows Product Key: *****-*****-GKCRB-FPV86-FD6QM
  Windows Product Key Hash: 4nWyRJvTGP/2PyQ+1NfeCRSksMw=
  Windows Product ID: 00359-OEM-8882234-48241
  Windows Product ID Type: 3
  Windows License Type: OEM System Builder
  Windows OS version: 6.1.7601.2.00010300.1.0.003
  ID: {18D48873-610C-4622-9CDB-3BC66B636946}(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: 0x00000000
  Build lab: 7601.win7sp1_gdr.110622-1506
  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 Home and Student 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_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-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>{18D48873-610C-4622-9CDB-3BC66B636946}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-FD6QM</PKey><PID>00359-OEM-8882234-48241</PID><PIDType>3</PIDType><SID>S-1-5-21-3136223725-2940333540-554230609</SID><SYSTEM><Manufacturer>Acer            </Manufacturer><Model>Aspire 4736     </Model></SYSTEM><BIOS><Manufacturer>Acer</Manufacturer><Version>V1.05</Version><SMBIOSVersion major="2" minor="4"/><Date>20090330000000.000000+000</Date></BIOS><HWID>C6893F07018400F8</HWID><UserLCID>4809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Malay Peninsula Standard Time(GMT+08:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>ACRSYS</OEMID><OEMTableID>ACRPRDCT</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-002F-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Home and Student 2007</Name><Ver>12</Ver><Val>1CC88CF95345F38</Val><Hash>Kib9cu06y0+g4y6+dca4/OJB1HM=</Hash><Pid>81602-924-2069263-68559</Pid><PidType>1</PidType></Product></Products><Applications><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="A1" 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_COA_NSLP channel
  Activation ID: 9f83d90f-a151-4665-ae69-30b3f63ec659
  Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
  Extended PID: 00359-00176-822-348241-02-18441-7600.0000-3232009
  Installation ID: 015321608540184445273731820695529511915783011875196442
  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: FD6QM
  License Status: Licensed
  Remaining Windows rearm count: 5
  Trusted time: 2/10/2011 10:19:49 AM

  Windows Activation Technologies-->
  HrOffline: 0x00000000
  HrOnline: 0x00000000
  HealthStatus: 0x0000000000000000
  Event Time Stamp: 9:30:2011 22:05
  ActiveX: Registered, Version: 7.1.7600.16395
  Admin Service: Registered, Version: 7.1.7600.16395
  HealthStatus Bitmask Output:

  
  HWID Data-->
  HWID Hash Current: NAAAAAIAAQABAAIAAQABAAAAAwABAAEAeqgWbE40XoHejG6bPq+Cid6IAG6aKmjO1K1Gyg==

  OEM Activation 1.0 Data-->
  N/A

  OEM Activation 2.0 Data-->
  BIOS valid for OA 2.0: yes
  Windows marker version: 0x0
  OEMID and OEMTableID Consistent: yes
  BIOS Information:
    ACPI Table Name OEMID Value OEMTableID Value
    APIC   ACRSYS  ACRPRDCT
    FACP   ACRSYS  ACRPRDCT
    HPET   ACRSYS  ACRPRDCT
    BOOT   ACRSYS  ACRPRDCT
    MCFG   ACRSYS  ACRPRDCT
    ASF!   ACRSYS  ACRPRDCT
    SLIC   ACRSYS  ACRPRDCT
    SSDT   PmRef  CpuPm

   

  Sunday, October 2, 2011 2:26 AM
• 

  

  0

  Sign in to vote

  "S. Alan" wrote in message news:85ba0911-6092-428c-84bf-eb0b76d93133...

  Thanks for your input so far anyway.

  I just wanted to confirm that my original installation wasn't the problem, so I switched back to my old hard disk and ran MGADiag again.  The output is appended below, and if I am not mistaken it was a clean bill of health.  So, that has to mean something went wrong with the Backup and Restore, despite me using the MS tool itself to do that.

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

  Validation Code: 0
  Cached Online Validation Code: 0x0
  Windows Product Key: *****-*****-GKCRB-FPV86-FD6QM
  Windows Product Key Hash: 4nWyRJvTGP/2PyQ+1NfeCRSksMw=
  Windows Product ID: 00359-OEM-8882234-48241
  Windows Product ID Type: 3
  Windows License Type: OEM System Builder
  Windows OS version: 6.1.7601.2.00010300.1.0.003
  

   

  You’re correct.

  Doing some reading around the subject yesterday I was struck by the apparent importance of ensuring that the configuration of the restored HD is functionally equivalent to the original – it seems to be that it’s important for it to be in the same motherboard position and place in the BIOS boot order as the original drive, and MUST have the same partition layout as the original drive (as far as the Boot and System partitions are concerned). I have no idea how or if this relates to your error, unless there’s a tag somewhere that gets changed in the process, which identifies the primary boot device in some way, and relates that tag somewhere in the registry to these files.

   

   

  ---

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

  • Marked as answer by Darin Smith MS Tuesday, October 4, 2011 9:07 PM

  Sunday, October 2, 2011 7:13 AM

  Moderator