Windows Vista suddenly not genuine?

All replies

• 

  

  0

  Sign in to vote

  Diagnostic Report (1.9.0027.0):

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

  Windows Validation Data-->

  Validation Status: Invalid License

  Validation Code: 50

  Cached Online Validation Code: N/A, hr = 0xc004f012

  Windows Product Key: *****-*****-GD2PK-BD3R2-44MV3

  Windows Product Key Hash: f7FPE6g/CLFmnJ4E6GbEU9Xn1sA=

  Windows Product ID: 89572-OEM-7332166-00021

  Windows Product ID Type: 2

  Windows License Type: OEM SLP

  Windows OS version: 6.0.6002.2.00010300.2.0.002

  ID: {A2B138DF-395A-43D8-9266-CF8E76431C15}(1)

  Is Admin: Yes

  TestCab: 0x0

  LegitcheckControl ActiveX: N/A, hr = 0x80070002

  Signed By: N/A, hr = 0x80070002

  Product Name: Windows Vista (TM) Home Basic

  Architecture: 0x00000000

  Build lab: 6002.vistasp2_gdr.101014-0432

  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 Professional Plus 2007 - 100 Genuine

  OGA Version: N/A, 0x80070002

  Signed By: N/A, hr = 0x80070002

  Office Diagnostics: B4D0AA8B-604-645_025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3_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\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>{A2B138DF-395A-43D8-9266-CF8E76431C15}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6002.2.00010300.2.0.002</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-44MV3</PKey><PID>89572-OEM-7332166-00021</PID><PIDType>2</PIDType><SID>S-1-5-21-1475875624-3912443963-1277181604</SID><SYSTEM><Manufacturer>MICRO-STAR INTERNATIONAL CO.,LTD</Manufacturer><Model>MS-7529</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>V4.7</Version><SMBIOSVersion major="2" minor="6"/><Date>20100728000000.000000+000</Date></BIOS><HWID>82323507018400E8</HWID><UserLCID>4409</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/><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{90120000-0011-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Professional Plus 2007</Name><Ver>12</Ver><Val>C0A25836FDBE5AC</Val><Hash>FmDbcrRY1pTOcrz4ZUZRHhpUuc0=</Hash><Pid>89409-726-2958074-65814</Pid><PidType>14</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"/><App Id="44" Version="12" Result="100"/></Applications></Office></Software></GenuineResults>  

  Spsys.log Content: 0x80070002

  Licensing Data-->

  Software licensing service version: 6.0.6002.18005

  Name: Windows(TM) Vista, HomeBasic edition

  Description: Windows Operating System - Vista, OEM_SLP channel

  Activation ID: 199086aa-6cb8-4e5b-b698-f2be56f1e8ee

  Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f

  Extended PID: 89572-00146-321-600021-02-17417-6001.0000-0722010

  Installation ID: 010196606294160754565942684170697981390770802554170012

  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: 44MV3

  License Status: Notification

  Notification Reason: 0xC004F057.

  Windows Activation Technologies-->

  N/A

  HWID Data-->

  HWID Hash Current: NgAAAAEABAABAAEAAQABAAAAAwABAAEAnJ+yKBi1OjDqS0jkqnawOm668vQYlyaCrFaRXkbK

  OEM Activation 1.0 Data-->

  N/A

  OEM Activation 2.0 Data-->

  BIOS valid for OA 2.0: yes, but no SLIC table

  Windows marker version: N/A

  OEMID and OEMTableID Consistent: N/A

  BIOS Information: 

    ACPI Table Name OEMID Value OEMTableID Value

    APIC 7529MS A7529400

    FACP 7529MS A7529400

    MCFG 7529MS OEMMCFG 

    OEMB 7529MS A7529400

    GSCI 7529MS GMCHSCI 

    SSDT DpgPmm CpuPm

  Monday, April 11, 2011 7:31 AM
• 

  

  0

  Sign in to vote

  "dolahaiman" wrote in message news:8b43728c-126f-4c58-afa8-74366a7f9691...

  Diagnostic Report (1.9.0027.0):

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

  Windows Validation Data-->

  Validation Status: Invalid License

  Validation Code: 50

  Cached Online Validation Code: N/A, hr = 0xc004f012

  Windows Product Key: *****-*****-GD2PK-BD3R2-44MV3

  Windows Product Key Hash: f7FPE6g/CLFmnJ4E6GbEU9Xn1sA=

  Windows Product ID: 89572-OEM-7332166-00021

  Windows Product ID Type: 2

  Windows License Type: OEM SLP

  Windows OS version: 6.0.6002.2.00010300.2.0.002

   

  
  

  To avoid confusion for all, please repost your MGADiag report to your OWN NEW thread, where it can receive proper attention.

  
  --
  
  

  ---

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

  Monday, April 11, 2011 6:20 PM

  Moderator
• 

  

  0

  Sign in to vote

  "heartquake" wrote in message news:5271038d-ba9c-4d6e-8aab-e84edbfc168a...

  I have a HP pavilion laptop and suddenly after around 2 years it became not geunuine. I was using the computer and it turned blue and restarted then became like this. I've tried re-entering the product key. the computer tells me to reinstall with a disc but my computer didn't come with any disc.

  Diagnostic Report (1.9.0027.0):
  -----------------------------------------
  Windows Validation Data-->
  Validation Status: Invalid License
  Validation Code: 50
  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: {D537F9C8-07B1-4C6C-B850-CAD1297A42CD}(1)
  Is Admin: Yes
  TestCab: 0x0
  LegitcheckControl ActiveX: N/A, hr = 0x80070002
  Signed By: N/A, hr = 0x80070002
  Product Name: Windows Vista (TM) Home Premium
  Architecture: 0x00000000
  Build lab: 6002.vistasp2_gdr.101014-0432
  TTS Error: M:20100517184017285-
  

  
  

  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:20100517184017285- This is the Tamper Time Stamp and it breaks down like this:

   

      (year)  (month) (day) (time in 24format) (millisecond)
  M:2010   05         17          1840                     17285     -

  
  Now that you know the time of the tamper, you can now try to connect that time with a program.

   

  1)    Login to Vista and select the option that launches an Internet Browser

   

  2)    Type into the browser address bar: %windir%\system32\perfmon.msc and hit Enter

   

  3)    When asked if you want to Open or Save this file, select Open

   

  4)     In the left hand panel, click Reliability Monitor

   

  5)    Click on the “System Stability Chart” above the date 17 May 2010 

   

  6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 17 May 2010 "

   

  7)    Look for any program that shows "Application Install" in the 'Activity' column.

   

  8)    Since the process that detects Tampers runs randomly, it can take up to 3 days for the process to detect the tamper and set Vista to a Tamper State. Because of this, please repeat steps 5) thru 7) for the dates 14-16 May 2010  (or around the date the issue first occurred)

   

    This could tell you what programs were installed on or around the Tamper date and should help you narrow down the possible programs that could be causing the issue. Unfortunately, if you installed the program at some time in the past, but didn’t run it till now, this process may not be helpful.  The removal of any application you may have installed recently could go a long way to troubleshooting this issues.

   

   

   

  Note: Since everyone has different programs installed on their computer, it is extremely hard for support to figure out what program is causing the problem, but if you still need assistance in identifying the Incompatible Program, please create a no cost support request at http://go.microsoft.com/fwlink/?linkid=52029

   

  Also Note: it has been found that Malware, such as Viruses and Trojans, can also be incompatible with Vista and can cause an In Memory Mod-Auth. A number of users (that were experiencing your same issue) have confirmed that a Malware infection was the cause. If you follow the above steps and cannot find a program that is causing the Mod-Auth, you may want to investigate if a Virus, Worm or Trojan may be to blame. You can contact PC Safety, which is a Microsoft group, which provides free assistance with Malware infections. I encourage you to use the ‘Windows Live Safety Scan for Windows Vista’ (http://onecare.live.com/site/en-us/center/whatsnew.htm) before contacting PC Safety.

   

  PC Safety:

   

  http://www..microsoft.com/protect/support/default.mspx

   

  http://onecare.live.com/site/en-us/center/whatsnew.htm

   

   

  
  --
  
  

  ---

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

  • Marked as answer by Darin Smith MS Thursday, April 14, 2011 12:05 AM

  Monday, April 11, 2011 6:24 PM

  Moderator