Microsoft reports Windows 7 is suddenly not genuine.

All replies

• 

  

  0

  Sign in to vote

  In order for us to analyze and troubleshoot a non-genuine notification issue you may be experiencing, please download and run the   Microsoft Genuine Advantage Diagnostics Tool. 

  After running the tool, click on the Continue button, then click on the Copy button, then Paste the report into your post.  Also, please include a brief question or pertinent background information that would be helpful in our endeavor to assist you.

  Thank you!

  ---

  Carey Frisch

  Monday, July 26, 2010 4:41 PM

  Moderator
• 

  

  0

  Sign in to vote

  The machine was purchased from Best Buy with win 7 installed.  The machine has a MS sticker on the button with a Windows 7 Product code on it that does not seem to match anything in this dianotic report below.  Is there any remedy other than reinstalling Win 7 and entering the product Key that is on the bottom of the laptop? 

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

  Validation Code: 0x8004FE22
  Cached Online Validation Code: 0x0
  Windows Product Key: *****-*****-4THM3-74PDB-4P2KH
  Windows Product Key Hash: 88kCx56CIRkBJG3+gKpBHkCTqAA=
  Windows Product ID: 00371-OEM-8992671-00137
  Windows Product ID Type: 2
  Windows License Type: OEM SLP
  Windows OS version: 6.1.7600.2.00010100.0.0.048
  ID: {FF6556CE-A50A-4889-BE68-74AB594D2E33}(3)
  Is Admin: Yes
  TestCab: 0x0
  LegitcheckControl ActiveX: N/A, hr = 0x80070002
  Signed By: N/A, hr = 0x80070002
  Product Name: Windows 7 Professional
  Architecture: 0x00000009
  Build lab: 7600.win7_gdr.100226-1909
  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 Standard 2007 - 100 Genuine
  Microsoft Office Home and Student 2007 - 100 Genuine
  OGA Version: N/A, 0x80070002
  Signed By: N/A, hr = 0x80070002
  Office Diagnostics: 77F760FE-153-80070002_7E90FEE8-175-80070002_025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3_B4D0AA8B-920-80070057

  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\sppcomapi.dll[Hr = 0x80004005]

  Other data-->
  Office Details: <GenuineResults><MachineData><UGUID>{FF6556CE-A50A-4889-BE68-74AB594D2E33}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-4P2KH</PKey><PID>00371-OEM-8992671-00137</PID><PIDType>2</PIDType><SID>S-1-5-21-1495195957-4292297614-2147043523</SID><SYSTEM><Manufacturer>TOSHIBA</Manufacturer><Model>Satellite A505</Model></SYSTEM><BIOS><Manufacturer>INSYDE</Manufacturer><Version>1.20</Version><SMBIOSVersion major="2" minor="6"/><Date>20100125000000.000000+000</Date></BIOS><HWID>C4B83607018400FC</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central Standard Time(GMT-06:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>TOSINV</OEMID><OEMTableID>TOSINV00</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-0012-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Standard 2007</Name><Ver>12</Ver><Val>2E5FF080757714</Val><Hash>rIuVC5MQjgniZSLynInKLfVWtig=</Hash><Pid>81607-906-2064063-64827</Pid><PidType>1</PidType></Product><Product GUID="{91120000-002F-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Home and Student 2007</Name><Ver>12</Ver><PidType>19</PidType></Product></Products><Applications><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="1A" 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.7600.16385

  Name: Windows(R) 7, Professional edition
  Description: Windows Operating System - Windows(R) 7, OEM_SLP channel
  Activation ID: 50e329f7-a5fa-46b2-85fd-f224e5da7764
  Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
  Extended PID: 00371-00178-926-700137-02-1033-7600.0000-0252010
  Installation ID: 002141335770078745278736808954381732307970206136414656
  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: 4P2KH
  License Status: Licensed
  Remaining Windows rearm count: 2
  Trusted time: 7/26/2010 1:07:24 PM

  Windows Activation Technologies-->
  HrOffline: 0x8004FE22
  HrOnline: N/A
  HealthStatus: 0x0000000000002000
  Event Time Stamp: 7:25:2010 11:49
  ActiveX: Registered, Version: 7.1.7600.16395
  Admin Service: Registered, Version: 7.1.7600.16395
  HealthStatus Bitmask Output:
  Tampered File: %systemroot%\system32\sppcomapi.dll|sppcomapi.dll.mui

  
  HWID Data-->
  HWID Hash Current: MgAAAAEABAABAAEAAAABAAAAAgABAAEA6GGwqALfnmKOaAifBDPavlonPFTWgDqeXF0=

  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   TOSINV  TOSINV00
    FACP   TOSINV  TOSINV00
    HPET   TOSINV  TOSINV00
    BOOT   TOSINV  TOSINV00
    MCFG   TOSINV  TOSINV00
    WDAT   INTEL   Calpella
    ASF!   TOSINV  TOSINV00
    SLIC   TOSINV  TOSINV00
    SSDT   INTEL   SataAhci
    ASPT   INTEL   Calpella
    SSDT   INTEL   SataAhci

   

  Monday, July 26, 2010 6:16 PM
• 

  

  0

  Sign in to vote

  Hello gshane,

  The core of your issue centers on the lines in your Diagnostic Report that reads:

  File Scan Data-->
  File Mismatch: C:\windows\system32\sppcomapi.dll[Hr = 0x80004005]

  Tampered File: %systemroot%\system32\sppcomapi.dll|sppcomapi.dll.mui

   

  This means the file(s) have been Tampered, Modified or has become Corrupt. Windows see this as an attack to bypass it's Licensing security.

  To resolve the issue, you need to repair the file(s) .

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

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

  
  b. Repairing Windows using System Restore:

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

   

   

  If neither of these sets of steps resolves the issue, my only other suggestions would be either to contact Windows support at the below URL or reinstall Windows.

  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

   Thank you,

  ---

  Darin MS

  • Proposed as answer by Darin Smith MS Monday, July 26, 2010 8:29 PM
  • Marked as answer by Darin Smith MS Monday, July 26, 2010 8:29 PM

  Monday, July 26, 2010 8:27 PM
• 

  

  0

  Sign in to vote

  I attempted to resolve the issue via option a (running sfc).  The problem remains.

  The sppcomapi.dll has the expected date/time stamp (7/13/2009 8:41PM), and is empty.  The same file on my in-laws' other Windows 7 machine is 227 KB.

  I do not want to try to use Sysetm Restore to resolve the issue because there are no resonable restore point available.  The only changes that have been made are from Windows Updates.  I coud try removing one at a time until and if the problem goes away.

  I do not know how this system got corrupted.  My in-laws's want to be above board and only will use Validated, Genuine products.   I still have a concern that I see no evidence in the diagnostic info of the Product Key that is on the label affixed to the bottom of this Laptop.

  Can I resolve this issue by copying the sppcomapi.dll file from the other machine?  Once that corruption is removed, how do I use the the Product Key that is affixed to the bottom of the Laptop?

  Tuesday, July 27, 2010 12:10 AM
• 

  

  0

  Sign in to vote

  I replaced the sppcomapi.dll file from a second Windows 7 machine. Windows now reports "Windows validation was successful"!

  Now the only question I have is "Is the machine using the correct Product Key?"  I can provide the Product Key from the sticker on the botton of the Laptop via e-mail (I do not want to post it publically).  Again I want to be legit, but I frankly do not trust that the OEM provider used the proper product key.

  Any suggestions?

  Tuesday, July 27, 2010 1:10 AM
• 

  

  0

  Sign in to vote

  The following was posted previously by Darin Smith MS (MSFT) and can probably answer the issue betther than I could:

  "Computers, which are built by large manufactures that come with Windows Pre-Installed, come with two (2) Product Keys:

  A)   OEM SLP: This key comes pre-installed in Windows, when it comes from the Factory. This key is geared to work with the OEM Bios Flag found only on that Manufacturer's computer hardware. So when Windows was installed using the OEM SLP key (at the factory) Windows looks at the motherboard and sees the proper OEM Bios Flag (for that Manufacturer and that version of Windows) and Self-Activates. (that's why you did not need to Activate your computer after you brought it home)

   

  B)    COA SLP: This is the Product key that you see on the sticker on the side (or bottom or sometimes in a laptop's battery compartment) of your computer. It is a valid product key, but should only be used in limited situations (such as this case when the OEM SLP key stops self-activating for whatever reason). The key must be activated by Phone.

  (Note: All manufacturers that use the OEM SLP system are required by contract to include a Certificate of Authenticity (COA) sticker, that has a COA SLP key, on the computer."

  So what you are seeing in the diagnostic is the preinstalled OEM SLP key (Windows License Type: OEM SLP) while what you are seeing on the actual license COA is the COA SLP key.

  Hope this explanation helps.

  Tuesday, July 27, 2010 2:03 AM
• 

  

  0

  Sign in to vote

  Hello GShane,

  To further build on what LVTravel posted for you, copy and paste the partial product key from your mgadiag report 4THM3-74PDB-4P2KH into an internet search engine and you will come up with many many pages with lists of OEM SLP deployment product keys.  4THM3-74PDB-4P2KH is the standard OEM SLP deployment product key used by Toshiba for Windows 7 Professional.

  So it's normal and expected that your in-Law's Toshiba Satellite laptop with W7Pro would have the standard deployment product key used by Toshiba on their W7Pro laptops.

  ---

  Buy Office 2007 Now, Get Office 2010 Free http://office2010.microsoft.com/en-us/tech-guarantee/microsoft-office-2010-technology-guarantee-FX101825695.aspx?CTT=97

  Tuesday, July 27, 2010 3:40 AM