none
6002 Build Error Not Genuine RRS feed

  • Question

  • Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Genuine
    Validation Code: 0
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-27HYQ-XTKW2-WQD8Q
    Windows Product Key Hash: U8YEZzymoD4DMyaMb32rPrNIS90=
    Windows Product ID: 89578-OEM-7332157-00061
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6002.2.00010300.2.0.003
    ID: {6300A17F-B6BF-4510-806B-42CE622B4ADE}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: Registered, 1.9.9.1
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Home Premium
    Architecture: 0x00000000
    Build lab: 6002.vistasp2_gdr.101014-0432
    TTS Error: M:20100114190759405-
    Validation Diagnostic:
    Resolution Status: N/A

    Vista WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: 6.0.6002.16398

    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: 2.0.48.0
    OGAExec.exe Signed By: Microsoft
    OGAAddin.dll Signed By: Microsoft

    OGA Data-->
    Office Status: 100 Genuine
    Microsoft Office Home and Student 2007 - 100 Genuine
    OGA Version: Registered, 2.0.48.0
    Signed By: Microsoft
    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\Mozilla Firefox\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-->

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{6300A17F-B6BF-4510-806B-42CE622B4ADE}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6002.2.00010300.2.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-WQD8Q</PKey><PID>89578-OEM-7332157-00061</PID><PIDType>2</PIDType><SID>S-1-5-21-103870452-416457179-3713618225</SID><SYSTEM><Manufacturer>HP-Pavilion</Manufacturer><Model>KT373AA-ABA a6519fh</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>5.25   </Version><SMBIOSVersion major="2" minor="5"/><Date>20080616000000.000000+000</Date></BIOS><HWID>83323507018400FA</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>HPQOEM</OEMID><OEMTableID>SLIC-CPC</OEMTableID></OEM><GANotification><File Name="OGAAddin.dll" Version="2.0.48.0"/></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>9B227F688D1F30</Val><Hash>olh17M1KDeqU5eA8QOoqq5VZuA0=</Hash><Pid>81602-920-5908222-68126</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: U1BMRwEAAAAAAQAABAAAAHZRAAAAAAAAYWECAAQQVogoDfB1fZXKARhy9171jCizkdIEkQaJZ64qT1RZOUEVrFS8SVOPQ6YY/prnl1+GmzfrYpXrqhgSflF0H9Oh+hJEw7XKSAShRbcqu0+kydYxzAp0+ryXu83O1mjkjzXhcq94m48ceJqGOPu1UvB7bxiIfUEtgIRGphkOSa+EGUYcOX5/UvkAHnVxypUpTYFJ/5Q9EhdGhJKYTJsbJiscvAYWgzyFZ0z79y0OKm53Bw867hHNE43WvZqUI0Rf1MqA3D5sWfEw7WeNfzOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYcvde9Ywos5HSBJEGiWeu8VQUPjsUuWFuy0p9fo4rEwtiS2v9cs8gyzYb+tH7HndRdB/TofoSRMO1ykgEoUW3H2lUMZZ27aftdzCylm1wmNZo5I814XKveJuPHHiahjj7tVLwe28YiH1BLYCERqYZDkmvhBlGHDl+f1L5AB51ccqVKU2BSf+UPRIXRoSSmEybGyYrHLwGFoM8hWdM+/ctDipudwcPOu4RzRON1r2alCNEX9TKgNw+bFnxMO1njX8zkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM

    Licensing Data-->
    Software licensing service version: 6.0.6002.18005
    Name: Windows(TM) Vista, HomePremium edition
    Description: Windows Operating System - Vista, OEM_SLP channel
    Activation ID: bffdc375-bbd5-499d-8ef1-4f37b61c895f
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 89578-00146-321-500061-02-1033-6001.0000-2692008
    Installation ID: 019923834106021593006193121834105171344526988946630235
    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43473
    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43474
    Use License URL: http://go.microsoft.com/fwlink/?LinkID=43476
    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=43475
    Partial Product Key: WQD8Q
    License Status: Licensed

    Windows Activation Technologies-->
    N/A

    HWID Data-->
    HWID Hash Current: MgAAAAIAAAABAAEAAwABAAAAAgABAAEAeqj8YIraFT+wV4DS4mzy9Hf2CMqsf6xWKoU=

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes
    Windows marker version: 0x20000
    OEMID and OEMTableID Consistent: yes
    BIOS Information:
      ACPI Table Name    OEMID Value    OEMTableID Value
      APIC            HPQOEM        SLIC-CPC
      FACP            HPQOEM        SLIC-CPC
      HPET            HPQOEM        SLIC-CPC
      MCFG            HPQOEM        SLIC-CPC
      OEMB            HPQOEM        SLIC-CPC
      GSCI            HPQOEM        SLIC-CPC
      SLIC            HPQOEM        SLIC-CPC
      SSDT            HPQOEM        SLIC-CPC



    Monday, April 18, 2011 7:43 PM

Answers

  • In this case, since the Tamper Time stamp is from over a year ago, it is unlikely that this is the cause of the current problem.

    (The Tamper Time stamp will alway show the last tamper event, even if that tamper has since been resolved)

     

    I suggest trying the below steps and see if that resolves the issue:

    1) Open an Internet Browser window.
    2) Type: %windir%\system32 into the browser address bar.
    3) Find the file CMD.exe
    4) Right-Click on CMD.exe and select 'Run as Administrator'
    5) Type: net stop slsvc  (it may ask you if you are sure, select yes)
    6) Type: cd %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareLicensing
    7) Type: rename tokens.dat tokens.bar
    8) Type: cd %windir%\system32
    9) Type: net start slsvc
    10) Type: cscript slmgr.vbs -rilc (It may take a long time for this to complete, please be patient)
    11) Restart your computer twice.
    12) You may be required to enter the Product Key and/or re-Activate. (be sure to enter the key from the sticker located on the side, bottom or (for some laptops) the battery compartment of the PC. Also, to activate, use the By Phone method.

     

    Thank you,


    Darin MS
    Tuesday, April 19, 2011 11:22 PM

All replies

  • "GoSuNi" wrote in message news:2e4b94ef-141b-49de-b82e-360fa6d1fc09...
    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Genuine
    Validation Code: 0
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-27HYQ-XTKW2-WQD8Q
    Windows Product Key Hash: U8YEZzymoD4DMyaMb32rPrNIS90=
    Windows Product ID: 89578-OEM-7332157-00061
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6002.2.00010300.2.0.003
    ID: {6300A17F-B6BF-4510-806B-42CE622B4ADE}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: Registered, 1.9.9.1
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Home Premium
    Architecture: 0x00000000
    Build lab: 6002.vistasp2_gdr.101014-0432
    TTS Error: M:20100114190759405-
     

    Vista is in, what we call a 'Mod-Auth' Tamper state.  There are 2 types of Mod-Auth tampers.
     
    1)    A critical system file was modified On Disk - What this means is that the file, located on the hard drive, was modified in some way. This can be caused by a malicious program (spyware, malware, virus) or by manual file modification (by a user of the system). There is also a very small chance that an Update may fail in mid-update and cause this type of issue. As a safety mechanism, Updates are made so that if they fail, they roll back any updating that was done before the failure, but there is an off-chance that the roll back did not occur.
     
     
     
    2)    A critical system file was modified In Memory - What this means is the file itself (on the hard drive) is un-modified, but the code, from that file, running in the system, was modified in some way and is caused by a running program that is incompatible with Vista.
     
     
     
      Because there is No Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, we know that your issue is an In Memory Mod-Auth and therefore caused by an incompatible program. This means there is a program install and Running that is trying to access parts of the OS that Vista does not allow, which by definition, means it is incompatible with Vista.
     
    NOTE: We have seen an increase in this type of issue and we believe it is unlikely that software writers are still making programs that are incompatible with Vista. Instead, we believe that a majority of the issues are being caused by Malware that are doing the same things (on purpose) as incompatible programs do (by accident).
     
     
     
      In addition to why a Mod-Auth occurs, it's also important to understand how Vista detects a Mod-Auth event. There is a Service that runs in Vista that detects a Tamper to a Critical System file. But this Service runs randomly, so if you were to install an incompatible program and run it, Vista (most likely) would not immediately enter a Mod-Auth  State and it could take some time for the Mod-Auth to be detected. The important point to note is that the moment Vista detects the Mod-Auth, you know that the program that is causing the Mod-Auth, is currently running.
     
     
     
       Below I have provided a number of steps to help you identify the program that is causing the tamper:
     
      First, go to http://support.microsoft..com/kb/931699/ and confirm that you do not have any of the programs known to cause this type of issue.
     
      Second, in your Diagnostic report above, you can see the line that starts with 'TTS Error:' followed by a bunch numbers: M:20100114190759405- This is the Tamper Time Stamp and it breaks down like this:
     
        (year)  (month) (day) (time in 24format) (millisecond)
    M:2010      01       14            1907                  59405      -
     
     
     

    This date is a LOT longer ago than is usual in such reports!
     
    Please check your system Time and Date and the Regional Settings, to make sure that they are correct, before we go further.
    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Monday, April 18, 2011 9:50 PM
    Moderator
  • In this case, since the Tamper Time stamp is from over a year ago, it is unlikely that this is the cause of the current problem.

    (The Tamper Time stamp will alway show the last tamper event, even if that tamper has since been resolved)

     

    I suggest trying the below steps and see if that resolves the issue:

    1) Open an Internet Browser window.
    2) Type: %windir%\system32 into the browser address bar.
    3) Find the file CMD.exe
    4) Right-Click on CMD.exe and select 'Run as Administrator'
    5) Type: net stop slsvc  (it may ask you if you are sure, select yes)
    6) Type: cd %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareLicensing
    7) Type: rename tokens.dat tokens.bar
    8) Type: cd %windir%\system32
    9) Type: net start slsvc
    10) Type: cscript slmgr.vbs -rilc (It may take a long time for this to complete, please be patient)
    11) Restart your computer twice.
    12) You may be required to enter the Product Key and/or re-Activate. (be sure to enter the key from the sticker located on the side, bottom or (for some laptops) the battery compartment of the PC. Also, to activate, use the By Phone method.

     

    Thank you,


    Darin MS
    Tuesday, April 19, 2011 11:22 PM
  • "Darin Smith MS" wrote in message news:9940597d-2b71-4563-8e5b-3a1869296043...

    In this case, since the Tamper Time stamp is from over a year ago, it is unlikely that this is the cause of the current problem.

    (The Tamper Time stamp will alway show the last tamper event, even if that tamper has since been resolved)


    Darin MS

    Thanks for the pointer, Darin

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Wednesday, April 20, 2011 12:32 AM
    Moderator