locked
I seem to have the same issue that many here have - issues in MGA Diagnostics RRS feed

  • Question

  • I have a Toshiba Satellite E105-1402.  Came with Vista Home Premium and I upgraded it myself with Windows Ultimate (upgrade) purchased at retail.  Was fine for 6 months.  Hard drive started failing, so I bought a new one, restored the laptop to original state using Toshiba recovery discs, and then did a clean install with the same Windows Ultimate upgrade disc.  Couple days later I tried to plug in a USB device and got a warning message about unsigned drivers.  At the same time, started getting the "your Windows isn't genuine" pop up.

    Seems like some of them have the "MUI" extension that  points to Vistalizator, but not all.

    Ran MGADiag, and saw pretty much the same set of files that everyone in this situation seems to see (copied below).  I haven't tried any of the remedies out on the forums yet (SFC, Windows Repair, etc.) but will try them this weekend.  Just wanted to see what the latest thoughts and knowledge are -- is this a known bug that is being worked on, or is it my own problem that I should take all possible actions to correct (I hate to do ANOTHER clean install, but will if I have to).

     

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

    Validation Code: 0x8004FE21
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-B6TF2-C2CY2-8BK2C
    Windows Product Key Hash: vOQJU0Ev5tNC3Y38LoMYLLllYl4=
    Windows Product ID: 00426-292-9710146-85104
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7600.2.00010100.0.0.001
    ID: {DA31311B-B733-4A34-ADBA-0596A8F82834}(1)
    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.110408-1633
    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
    2007 Microsoft Office system - 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 (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>{DA31311B-B733-4A34-ADBA-0596A8F82834}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-8BK2C</PKey><PID>00426-292-9710146-85104</PID><PIDType>5</PIDType><SID>S-1-5-21-1706929360-444433892-4142652735</SID><SYSTEM><Manufacturer>TOSHIBA</Manufacturer><Model>Satellite E105</Model></SYSTEM><BIOS><Manufacturer>INSYDE</Manufacturer><Version>1.10</Version><SMBIOSVersion major="2" minor="4"/><Date>20080913000000.000000+000</Date></BIOS><HWID>79BA3607018400F8</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05:00)</TimeZone><iJoin>1</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>TOSINV</OEMID><OEMTableID>TOSINV00</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-0031-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>2007 Microsoft Office system</Name><Ver>12</Ver><Val>B1B640738EEDB3E</Val><Hash>SuD6/rgTvqoC3l05v83Nwr021mg=</Hash><Pid>89451-415-7945881-66254</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"/></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-292-971014-00-1033-7600.0000-1882011
    Installation ID: 015766983540364994387491548022675325575816871072749933
    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: 8BK2C
    License Status: Licensed
    Remaining Windows rearm count: 3
    Trusted time: 7/8/2011 9:06:50 AM

    Windows Activation Technologies-->
    HrOffline: 0x8004FE21
    HrOnline: N/A
    HealthStatus: 0x000000000001EFF0
    Event Time Stamp: 7:7:2011 14:34
    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: NgAAAAEABAABAAIAAAACAAAAAgABAAEA6GE+JCrwLqnUVDAG3p1EIPTROgyU0tRfvnj+gEbK

    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            TOSINV        TOSINV00
      FACP            TOSINV        TOSINV00
      HPET            TOSINV        TOSINV00
      BOOT            TOSINV        TOSINV00
      MCFG            TOSINV        TOSINV00
      ASF!            TOSINV        TOSINV00
      SLIC            TOSINV        TOSINV00
      SSDT            PmRef        CpuPm



     

     

    Friday, July 8, 2011 7:09 PM

Answers

  • Issue was resolved by performing a clean install again on the laptop.  Noel was extremely helpful, but nothing suggested here (or anywhere else, including sevenforums.com) could resolve the issue.  I would suggest that MGADIAG be run extensively when building up a PC (i.e., between various steps) to check for file mismatches and tampered files. 

    Thursday, July 14, 2011 9:25 PM

All replies

  • An upgrade license requires the presence of the previous version of Windows on the hard drive at the time you run Setup.  If you formatted the drive and then ran Setup you have an issue.  Restore the previous version of Windows and then run Setup using the upgrade key.  You do not have to perform a software upgrade.  You can perform a custom installation with an upgrade key and you can format the hard drive if you wish once the upgrade product key has been accepted.  But with Windows 7 the word "upgrade" in upgrade product key means a literal upgrade.  You can no longer upgrade as you could with XP (with qualifying media).  The previous copy of Windows needs to be on the computer when you start.  You don't have to upgrade over the previous copy; you can remove it during the installation process, but it needs to be there at the beginning.
    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.
    Friday, July 8, 2011 8:42 PM
    Answerer
  • Thanks for the reply -- sorry if I wasn't clear above.

    I used the Toshiba recovery discs to get back to original state (Windows Vista Home Premium installed) on the laptop.  I then used the Ultimate Upgrade discs to upgrade.  Windows 7 Ultimate had no trouble applying updates from Windows Update right after, and shows as "activated" in the "View Basic Information about your computer" screen.

    Friday, July 8, 2011 9:52 PM
  • It is not a bug.  It is more likely a corrupted file.  Run the system file checker, reboot, and then run the MGADiag tool again.  Windows is activated but you need to get rid of the errors.

    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. 


    Colin Barnhorst Windows 7 Ultimate x64 on DIY with 6GB ram.
    Friday, July 8, 2011 10:59 PM
    Answerer
  • "NeveradullmomentwithWindows" wrote in message news:b6e7344b-8177-4b91-8297-48c46793f9dd...

    Thanks for the reply -- sorry if I wasn't clear above.

    I used the Toshiba recovery discs to get back to original state (Windows Vista Home Premium installed) on the laptop.  I then used the Ultimate Upgrade discs to upgrade.  Windows 7 Ultimate had no trouble applying updates from Windows Update right after, and shows as "activated" in the "View Basic Information about your computer" screen.


    Hmmm - my personal opinion is that you need to check your Upgrade disks - see if the MD5 hash meets the expected value,]
     
    Check also that your Upgrade system is the correct one - there are a LOT of bogus download sites around, so check the ash of the downloaded file - and its provenance.
     
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Friday, July 8, 2011 11:53 PM
    Moderator
  • "NeveradullmomentwithWindows" wrote in message news:5488b7f4-38a5-43b0-8da8-47d19ba0c2f4...

    I have a Toshiba Satellite E105-1402.  Came with Vista Home Premium and I upgraded it myself with Windows Ultimate (upgrade) purchased at retail.  Was fine for 6 months.  Hard drive started failing, so I bought a new one, restored the laptop to original state using Toshiba recovery discs, and then did a clean install with the same Windows Ultimate upgrade disc.  Couple days later I tried to plug in a USB device and got a warning message about unsigned drivers.  At the same time, started getting the "your Windows isn't genuine" pop up.

    Seems like some of them have the "MUI" extension that  points to Vistalizator, but not all.

    Ran MGADiag, and saw pretty much the same set of files that everyone in this situation seems to see (copied below).  I haven't tried any of the remedies out on the forums yet (SFC, Windows Repair, etc.) but will try them this weekend.  Just wanted to see what the latest thoughts and knowledge are -- is this a known bug that is being worked on, or is it my own problem that I should take all possible actions to correct (I hate to do ANOTHER clean install, but will if I have to).

     

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

    Validation Code: 0x8004FE21
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-B6TF2-C2CY2-8BK2C
    Windows Product Key Hash: vOQJU0Ev5tNC3Y38LoMYLLllYl4=
    Windows Product ID: 00426-292-9710146-85104
    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



    This set of File Mismatches is unfortunately common - and we haven't as yet found a cause or solution in the forums -
    If you're willing to spend some time on it, then I'm willing to have a go at troubleshooting it to find a solution - but if you need a quick fix, possibly the best thing would be to go straight to WGA Support.
    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
    Saturday, July 9, 2011 9:20 AM
    Moderator
  • Thanks for the input.  I will check the hash.  I'm fairly confident that it is a legit copy, as I bought it at my company's expense off the shelf at Fry's.  I ran SFC as Colin suggested.  It reached 100% completion, but said, "Windows Resource Protection found corrupt files but was unable to fix some of them.  Below is the re-run MGADiag -- not a lot of change from the first run.  As you say, Noel, this seems to be a recurring issue with users -- virtually the same set of files.  If these core files were truly corrupt, I would think I would see more issues in how Windows was running.  The only symptoms are the issues I had with processing drivers on the install of USB devices, and the "Windows isn't genuine" pop up.  Although I get the driver warnings, the devices still work completely fine.

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

    Validation Code: 0x8004FE21
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-B6TF2-C2CY2-8BK2C
    Windows Product Key Hash: vOQJU0Ev5tNC3Y38LoMYLLllYl4=
    Windows Product ID: 00426-292-9710146-85104
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7600.2.00010100.0.0.001
    ID: {DA31311B-B733-4A34-ADBA-0596A8F82834}(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.110408-1633
    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
    2007 Microsoft Office system - 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>{DA31311B-B733-4A34-ADBA-0596A8F82834}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-8BK2C</PKey><PID>00426-292-9710146-85104</PID><PIDType>5</PIDType><SID>S-1-5-21-1706929360-444433892-4142652735</SID><SYSTEM><Manufacturer>TOSHIBA</Manufacturer><Model>Satellite E105</Model></SYSTEM><BIOS><Manufacturer>INSYDE</Manufacturer><Version>1.10</Version><SMBIOSVersion major="2" minor="4"/><Date>20080913000000.000000+000</Date></BIOS><HWID>79BA3607018400F8</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05:00)</TimeZone><iJoin>1</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>TOSINV</OEMID><OEMTableID>TOSINV00</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-0031-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>2007 Microsoft Office system</Name><Ver>12</Ver><Val>B1B640738EEDB3E</Val><Hash>SuD6/rgTvqoC3l05v83Nwr021mg=</Hash><Pid>89451-415-7945881-66254</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"/></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-292-971014-00-1033-7600.0000-1882011
    Installation ID: 015766983540364994387491548022675325575816871072749933
    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: 8BK2C
    License Status: Licensed
    Remaining Windows rearm count: 3
    Trusted time: 7/9/2011 1:50:46 PM

    Windows Activation Technologies-->
    HrOffline: 0x8004FE21
    HrOnline: N/A
    HealthStatus: 0x000000000001EFF0
    Event Time Stamp: 7:7:2011 14:34
    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: NgAAAAEABAABAAIAAAACAAAAAgABAAEA6GE+JCrwLqnUVDAG3p1EIPTROgyU0tRfvnj+gEbK

    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   TOSINV  TOSINV00
      FACP   TOSINV  TOSINV00
      HPET   TOSINV  TOSINV00
      BOOT   TOSINV  TOSINV00
      MCFG   TOSINV  TOSINV00
      ASF!   TOSINV  TOSINV00
      SLIC   TOSINV  TOSINV00
      SSDT   PmRef  CpuPm

     

    Saturday, July 9, 2011 5:56 PM
  • "NeveradullmomentwithWindows" wrote in message news:63b0b165-5d11-47a2-91d9-7ffcd671e91b...

    Thanks for the input.  I will check the hash.  I'm fairly confident that it is a legit copy, as I bought it at my company's expense off the shelf at Fry's.  I ran SFC as Colin suggested.  It reached 100% completion, but said, "Windows Resource Protection found corrupt files but was unable to fix some of them.  Below is the re-run MGADiag -- not a lot of change from the first run.  As you say, Noel, this seems to be a recurring issue with users -- virtually the same set of files.  If these core files were truly corrupt, I would think I would see more issues in how Windows was running.  The only symptoms are the issues I had with processing drivers on the install of USB devices, and the "Windows isn't genuine" pop up.  Although I get the driver warnings, the devices still work completely fine.

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

    Validation Code: 0x8004FE21
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-B6TF2-C2CY2-8BK2C
    Windows Product Key Hash: vOQJU0Ev5tNC3Y38LoMYLLllYl4=
    Windows Product ID: 00426-292-9710146-85104
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7600.2.00010100.0.0.001


    Unfortunately, no change :(
     
    In respect of the actual problem, I think that it's more likely that there is another file or a registry entry that is corrupted, and that as a result these files are being flagged as corrupt.
    One thing that occurred to me recently is that this may be an issue that the CheckSUR Tool may work on.- it certainly won't hurt to give it a go.
    CheckSUR Tool -
    http://support.microsoft.com/kb/947821
     
    When it's complete, upload the log file to your SkyDrive or other media-sharing portal, and we'll take a look and see if it's done anything.
    again, reboot, post another MGADiag report, and the link to your log file.
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Saturday, July 9, 2011 6:08 PM
    Moderator
  • Downloading the tool now.  On checking hash -- I'm not the most technical person out there.  I've installed HashTab.  I'm assuming that I have to create an ISO from my Windows Ultimate DVD and check the hash of the resulting .iso file?  Thanks for all the help.
    Saturday, July 9, 2011 6:46 PM
  • "NeveradullmomentwithWindows" wrote in message news:3b94e61e-1208-4657-babc-5533fbe105d1...
    Downloading the tool now.  On checking hash -- I'm not the most technical person out there.  I've installed HashTab.  I'm assuming that I have to create an ISO from my Windows Ultimate DVD and check the hash of the resulting .iso file?  Thanks for all the help.

    You should be able to hash the DVD, if I remember rightly (it's years since I tried it - and then only once or twice)
    Having said that, I just noticed that you say it's a shop-bought copy (for some reason I thought it was a download), so it's very unlikely to be the DVD

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Saturday, July 9, 2011 7:15 PM
    Moderator
  • Here's another symptom/issue -- Windows Update is hosed.  This is a work PC.  After I got Windows reinstalled, I took it in and they created another profile that would automatically connect to our domain.  They also changed settings to allow our administrator to push updates via a SUS server.  Not sure why that would be an issue, but Windows Update was pulling down everything on its own just fine.  After I got it back, Windows Update hasn't pulled anything at all.  I had them switch it back to be under my control, and it still doesn't work.  I ran FIXIT 50202 in both default and aggressive mode, and it doesn't hang anymore, but it tells me the service isn't running.  I've restarted a couple times, and the service won't start up for some reason.

    Saturday, July 9, 2011 7:21 PM
  • "NeveradullmomentwithWindows" wrote in message news:39d0d671-4af8-4655-a181-f3178e5316a9...

    Here's another symptom/issue -- Windows Update is hosed.  This is a work PC.  After I got Windows reinstalled, I took it in and they created another profile that would automatically connect to our domain.  They also changed settings to allow our administrator to push updates via a SUS server.  Not sure why that would be an issue, but Windows Update was pulling down everything on its own just fine.  After I got it back, Windows Update hasn't pulled anything at all.  I had them switch it back to be under my control, and it still doesn't work.  I ran FIXIT 50202 in both default and aggressive mode, and it doesn't hang anymore, but it tells me the service isn't running.  I've restarted a couple times, and the service won't start up for some reason.


    Oh brother - I hate it when IT departments screw things up - it usually means that they've put GPO's in place that are incorrect. (and my knowledge of GPS's could be written on a postage stamp in 20pt)
    Which service isn't running? BITS? WUAUserv (Windows Update)?
     
    The CheckSUR may fix that too :)
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Saturday, July 9, 2011 7:38 PM
    Moderator
  • Both those services report they are running.  I saw tried a fix in this article...

    http://helpdeskgeek.com/windows-7/cannot-run-windows-update-on-a-windows-7-pc/

    It stops the service, you delete the items in the Software Download folder in Windows, and then start it to allow it to rebuild the folders and resolve any confusion.

    It didn't work. 

    I downloaded the CheckSUR, but when I went to install it, it refused with error code 0xc800247.

    Saturday, July 9, 2011 7:56 PM
  • "NeveradullmomentwithWindows" wrote in message news:acaee15b-698c-457c-b5f5-ca4a63f80d50...

    Both those services report they are running.  I saw tried a fix in this article...

    http://helpdeskgeek.com/windows-7/cannot-run-windows-update-on-a-windows-7-pc/

    It stops the service, you delete the items in the Software Download folder in Windows, and then start it to allow it to rebuild the folders and resolve any confusion.

    It didn't work. 

    I downloaded the CheckSUR, but when I went to install it, it refused with error code 0xc800247.


    That error code is short a digit :)
    How about the Crypto Services? (Cryptsvc)
     
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Saturday, July 9, 2011 8:02 PM
    Moderator
  • Sorry- it's 0xc8000, not 0xc800...

    Yes - Crypto Services is running.  The only services set to Automatic that weren't running were Software Protection and Windows Search, which are both set to Delayed Start

    Saturday, July 9, 2011 8:10 PM
  • What is your opinon of doing a Repair Install?
    Saturday, July 9, 2011 8:27 PM
  • "NeveradullmomentwithWindows" wrote in message news:e0bc8929-a784-4948-a19d-b143dfdf536c...
    What is your opinon of doing a Repair Install?

    What happens if you attempt to start the Software Protection service? (it should start without a problem, or the MGADiag wouldn't produce some of the results it has done.)
     
     
    A repair install is really a (2nd) last resort - and shouldn't be necessary.

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Saturday, July 9, 2011 8:51 PM
    Moderator
  • It did start with no problem.  At that point, the Action Center asked me to change Windows Update settings (i.e., automatic versus you decide) -- almost as if they hadn't been set.  Still says service isn't running, though, even though they all are...
    Saturday, July 9, 2011 9:17 PM
  • "NeveradullmomentwithWindows" wrote in message news:8f820697-4624-4442-8a34-c8a52843b915...
    It did start with no problem.  At that point, the Action Center asked me to change Windows Update settings (i.e., automatic versus you decide) -- almost as if they hadn't been set.  Still says service isn't running, though, even though they all are...

    It'll be one of the ones on Manual.....
    Possibly you'd be best asking this question in the Windows Update Answers forum - WU is not something I know much about. http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_update?page=1&tab=all 

    I can't find anything about the 0x8000247 error in Google that seems either relevant or informative. :(
    About the best thing that I've seen is the suggestion to create a new user profile and try again from there ( not quite sure whether it's terribly likely to work, but it won't hurt :)
     
     
    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Saturday, July 9, 2011 9:36 PM
    Moderator
  • No further reply from the Original Poster.

    Issue is assumed to be resolved.


    Darin MS
    Thursday, July 14, 2011 8:42 PM
  • Issue was resolved by performing a clean install again on the laptop.  Noel was extremely helpful, but nothing suggested here (or anywhere else, including sevenforums.com) could resolve the issue.  I would suggest that MGADIAG be run extensively when building up a PC (i.e., between various steps) to check for file mismatches and tampered files. 

    Thursday, July 14, 2011 9:25 PM
  • "NeveradullmomentwithWindows" wrote in message news:3cff28cc-015d-4b5e-aa96-15d5bdd3b5a7...

    Issue was resolved by performing a clean install again on the laptop.  Noel was extremely helpful, but nothing suggested here (or anywhere else, including sevenforums.com) could resolve the issue.  I would suggest that MGADIAG be run extensively when building up a PC (i.e., between various steps) to check for file mismatches and tampered files. 


    For that to be helpful, one first has to know of the existence of the Tool :)
     
    I did have occasion (for various reasons) to do exactly that today - and was quite surprised not to hit a problem (but the OS involved was XP, rather than the primary current targets of Vista and Win7). I await with interest the first complaint from the client, as I warned them of the problem before dealing with the rest of the system issues (like missing updates and broken .NET installs <g>)
    Running MGADiag is one of the first things I do when approaching a 'new' (i.e. unfamiliar) machine - as it can shorten the maintenance time considerable (but can also make it a lot longer!) to know the provenance of any install.
     
    As I said (somewhere in the thread) your particular problem was almost unique - and until we get at least three or four 'dead bodies' with the same symptoms, and some form of 'medical history' then there's not a lot we can do except say 'keep taking the tablets' <eg>
     
    A clean install is always something that I shy away from - it's almost impossible not to forget something in the process, and occasionally that something is a critical piece of data (like a license key) which is not recoverable elsewhere. Upgrade installs aren't so bad (with a lot of 'but's' in there!), and they are 2nd-worst.
    Best solution is to identify the precise cause, fix it, and modify the system so that it can never happen again - unfortunately the number of cases this is possible is small - and when dealing with a forum context that 'small' becomes 'vanishingly small'.
     
    Whatever - Glad you seem to be all sorted, so well done, and good luck!
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Thursday, July 14, 2011 9:58 PM
    Moderator