none
Can't Validate Windows Vista Home Premium... getting multiple errors RRS feed

  • Question

  • 3 months ago i bought a windows vista home premium upgrade /sp1. i had xp pro on my computer before. i installed vista no problem activated it and i have been using it for about 3 months with out a problem. 2 days ago i bought a new motherboard and CPU and installed them into my computer. it worked for about a day until i was unable to login to any accounts that i have. when i click on an account to login to the windows activation thing pops upand says i need to activate my windows. when i try to do so i get either one of these error depending on which way i choose to try and activate:

    if i try to Activate windows online or retype my product key i get this error: 0XC004E003

    if i try to change my product key i get this one: 0XC004F050

    and finally if i try to use the automated phone system i get no installation ID.


    I have no idea what to do. I called customer support only to be transfered around multiple times to multiple people with no help.
    my case number is 1089177155 according to the Customer Service rep but i still have no solution and a computer that might as well be a brick because i can't logon to use it 
    • Changed type 1Dustin1 Tuesday, December 30, 2008 9:16 PM
    • Changed type Stephen Holm Tuesday, December 30, 2008 9:52 PM
    • Changed type 1Dustin1 Tuesday, December 30, 2008 10:53 PM
    • Changed type Stephen Holm Wednesday, December 31, 2008 2:01 AM
    Tuesday, December 30, 2008 9:12 PM

Answers

  • Dustin,
     

    Windows 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, and was modified in some way. This can be caused by a malicious program (malware) 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 usually caused by a running program that is incompatible with Windows Vista.

     Because there is No Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, 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 Windows Vista does not allow which by definition means it is incompatible with Windows Vista.

     

    In addition to why a Tamper occurs, it's also important to understand how Windows Vista detects the Tamper event. There is a Service that runs in Windows 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, Windows Vista (most likely) would not immediately enter a Tamper State and it could take some time for the Tamper to be detected. The important point to note is that the moment Windows Vista detects the Tamper, you know that the program that caused the tamper, is currently running.

     

    Below I have provided a number of steps to help you identify the program that is causing the tamper:

     

    The following Knowledge Base (KB) article may help you confirm that you do not have any of the programs known to cause this type of issue.

     

    KB931699 - Error message when you use Windows Vista: "An unauthorized change was made to your license"

     

    http://support.microsoft.com/kb/931699/

     
    Second, in your Microsoft Genuine Diagnostic Tool (MGADT) report above, you can see the line that starts with 'TTS Error:' followed by a bunch numbers: M:xxxxxxxxxxxxxxxxx- This is the Tamper Time Stamp and it breaks down like this:

     

    (Year)       (Month)      (Day)      (Time in 24format)      (Millisecond)

    M:2008      12               29              1339                            20149-
     

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

     1) Login to Windows Vista and select the option which 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) Then click System Stability Chart above the date 12/29.  

    6) Below the chart, in the System Stability Report section look at the report titled "Software (Un) Installs for 12/29/2008.  

    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 Windows Vista to a Tamper State. Because of this, please repeat steps 5) through 7) for the dates 12/28/2008, 12/27/2008, and 12/25/2008 

    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 (say) on 09/01/2007, but you didn't run (and, hence, prompted the tamper state) till 12/29/2008, this process may not be helpful.  The removal of any application you may have installed recently could go a long way to troubleshooting these issues as well since it may fall outside of the 3 day time frame described above.

    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 the following link below:

    http://go.microsoft.com/fwlink/?linkid=52029



    Thank you for visiting the Genuine Advantage forum.



    Stephen Holm, MS
    WGA Forum Manager


    Stephen Holm
    • Marked as answer by Stephen Holm Wednesday, December 31, 2008 2:02 AM
    Wednesday, December 31, 2008 1:55 AM

All replies

  • Hello Dustin,


    Sounds like the problems occurred after you performed the upgrades. Please run the Microsoft Genuine Advantage Diagnostic Test (MGADT) and answer the questions below so that I may analyze the results
    .

    By clicking the link below, you will download the MGADT.  Then click the Run button. Then click the Run button again. Then click the Continue button to perform the diagnostic. The Windows tab should show, click the Copy button to paste your report to the clipboard.  Then paste the report into a New Post on this Forum by adding a post in it and pressing Ctrl V (to paste the text). Clicking the OK button will clear the Diagnostic window. Here is the download link:

     http://go.microsoft.com/fwlink/?linkid=52012

    Please tell us about the Certificate of Authenticity (COA) for your copy of Windows Vista.

    1. What edition/version of Windows Vista is titled?

    ·         Home Basic

    ·         Home Premium 

    ·         Business

    ·         Ultimate

    2. Does it read "OEM Software" or "OEM Product" in black lettering?

    3.  Did you purchase an OEM System Builder version?


    4. Or, does it have the computer manufacturer's name in black lettering?

    5. Please provide the customer scenario you are experiencing.

    6. DO NOT post the Product Key. 

    Not sure what to look for, see this page to reference your COA:

    http://www.microsoft.com/resources/howtotell/product.aspx?pID=b5c507e5-3522-40de-a2f4-97d82b39cc47&cID=ea710cad-37b0-4975-bcd6-abfee19961df&method=oem&displaylang=en

    NOTE: The data collected with the MGADT does NOT contain any information that can personally identify you. The information can be fully reviewed, by you, before being posted.


    Thank you for your participation here on the Genuine Advantage forum. We look forward to working with you.



    Stephen Holm, MS
    WGA Forum Manager


    Stephen Holm
    Tuesday, December 30, 2008 9:58 PM
  •  

    Diagnostic Report (1.7.0110.1):
    -----------------------------------------
    WGA Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Online Validation Code: 0xc004c4a8
    Cached Validation Code: 0xc004c4a8
    Windows Product Key: *****-*****-V4WDJ-JWHG3-8W2GX
    Windows Product Key Hash: EnO824TG9SFdZpM9EFAI+IZj3/E=
    Windows Product ID: 89578-483-3948713-71601
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.0.6001.2.00010300.1.0.003
    ID: {7A4F7352-DF4E-4CCD-ACA8-520430358F95}(3)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: Registered, 1.7.69.2
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Home Premium
    Architecture: 0x00000000
    Build lab: 6001.vistasp1_gdr.080917-1612
    TTS Error: M:20081229133920149-
    Validation Diagnostic:
    Resolution Status: N/A

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

    WGA 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
    WGATray.exe Signed By: N/A, hr = 0x80070002
    OGAAddin.dll Signed By: N/A, hr = 0x80070002

    OGA Data-->
    Office Status: 103 Blocked VLK
    Microsoft Office Enterprise 2007 - 103 Blocked VLK
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: 025D1FF3-282-80041010_025D1FF3-170-80041010_025D1FF3-171-1_025D1FF3-434-80040154_025D1FF3-178-80040154_025D1FF3-179-2_025D1FF3-185-80070002_025D1FF3-199-3_FA827CE6-153-8007007e_FA827CE6-180-8007007e

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 7.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>{7A4F7352-DF4E-4CCD-ACA8-520430358F95}</UGUID><Version>1.7.0110.1</Version><OS>6.0.6001.2.00010300.1.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-8W2GX</PKey><PID>89578-483-3948713-71601</PID><PIDType>5</PIDType><SID>S-1-5-21-3294037672-199674104-1948831031</SID><SYSTEM><Manufacturer>System manufacturer</Manufacturer><Model>P5Q-E</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>1703   </Version><SMBIOSVersion major="2" minor="5"/><Date>20081212000000.000000+000</Date></BIOS><HWID>7A303507018400F8</HWID><UserLCID>1009</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Atlantic Standard Time(GMT-04:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><BRT/></MachineData><Software><Office><Result>103</Result><Products><Product GUID="{90120000-0030-0000-0000-0000000FF1CE}"><LegitResult>103</LegitResult><Name>Microsoft Office Enterprise 2007</Name><Ver>12</Ver><Val>ACD7202654E586</Val><Hash>fFic3JgCreGGRxyF8uMWB4R4Jcg=</Hash><Pid>89388-707-1528066-65056</Pid><PidType>14</PidType></Product></Products><Applications><App Id="15" Version="12" Result="103"/><App Id="16" Version="12" Result="103"/><App Id="18" Version="12" Result="103"/><App Id="19" Version="12" Result="103"/><App Id="1A" Version="12" Result="103"/><App Id="1B" Version="12" Result="103"/><App Id="44" Version="12" Result="103"/><App Id="A1" Version="12" Result="103"/><App Id="BA" Version="12" Result="103"/></Applications></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAABcIAAAAAAAAYWECAASg6YcpOGdh3GnJARsqbkNny+kXf2cj8k7x9VI0PlaKxd7VuyhhH7ocfpMn3pbGIiNCrvhiP5A/wnye/mjwyAn8sMyz34HfM0IHIZC0q/QqI4KZ/QHGG5+pL12ZsEGnmR0ReJ9KlWCJouxq6PAIwHwHVMfvNauSbFvmaTCDPKtQZQFIQcDXIAwFGl6D9S/GUDYecePFRKM/leS97bxOVVm9fICZUkfHdDNbo725QzYM7NoLIP6BsYz9FHAia30CP0z0OYRuUWLuf4S5JTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw=

    Licensing Data-->
    C:\Windows\system32\slmgr.vbs(1648, 9) (null): 0xC004E017

    HWID Data-->
    HWID Hash Current: PAAAAAIABAABAAEAAgACAAAAAwABAAEAJJRw4mLZ6FWMJmhlRryENJCb8DysKfL0mAOgo/obWuisVkbK

    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   A_M_I_  OEMAPIC
      FACP   A_M_I_  OEMFACP
      HPET   A_M_I_  OEMHPET
      MCFG   A_M_I_  OEMMCFG
      OEMB   A_M_I_  AMI_OEM
      OSFR   A_M_I_  OEMOSFR


     haha here ya go hope you can make sense of that.

    as for your questions:
    1.Home Premium
    2. doesn't seem to say either, maybe i'm looking in the wrong spot. but i bought it from Future Shop for 129.99
    3. i dont think so
    4. nope
    5. do you mean when i called? or what i am experiencing now?
    6. ok :)

    Tuesday, December 30, 2008 10:13 PM
  • Dustin,
     

    Windows 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, and was modified in some way. This can be caused by a malicious program (malware) 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 usually caused by a running program that is incompatible with Windows Vista.

     Because there is No Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, 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 Windows Vista does not allow which by definition means it is incompatible with Windows Vista.

     

    In addition to why a Tamper occurs, it's also important to understand how Windows Vista detects the Tamper event. There is a Service that runs in Windows 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, Windows Vista (most likely) would not immediately enter a Tamper State and it could take some time for the Tamper to be detected. The important point to note is that the moment Windows Vista detects the Tamper, you know that the program that caused the tamper, is currently running.

     

    Below I have provided a number of steps to help you identify the program that is causing the tamper:

     

    The following Knowledge Base (KB) article may help you confirm that you do not have any of the programs known to cause this type of issue.

     

    KB931699 - Error message when you use Windows Vista: "An unauthorized change was made to your license"

     

    http://support.microsoft.com/kb/931699/

     
    Second, in your Microsoft Genuine Diagnostic Tool (MGADT) report above, you can see the line that starts with 'TTS Error:' followed by a bunch numbers: M:xxxxxxxxxxxxxxxxx- This is the Tamper Time Stamp and it breaks down like this:

     

    (Year)       (Month)      (Day)      (Time in 24format)      (Millisecond)

    M:2008      12               29              1339                            20149-
     

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

     1) Login to Windows Vista and select the option which 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) Then click System Stability Chart above the date 12/29.  

    6) Below the chart, in the System Stability Report section look at the report titled "Software (Un) Installs for 12/29/2008.  

    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 Windows Vista to a Tamper State. Because of this, please repeat steps 5) through 7) for the dates 12/28/2008, 12/27/2008, and 12/25/2008 

    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 (say) on 09/01/2007, but you didn't run (and, hence, prompted the tamper state) till 12/29/2008, this process may not be helpful.  The removal of any application you may have installed recently could go a long way to troubleshooting these issues as well since it may fall outside of the 3 day time frame described above.

    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 the following link below:

    http://go.microsoft.com/fwlink/?linkid=52029



    Thank you for visiting the Genuine Advantage forum.



    Stephen Holm, MS
    WGA Forum Manager


    Stephen Holm
    • Marked as answer by Stephen Holm Wednesday, December 31, 2008 2:02 AM
    Wednesday, December 31, 2008 1:55 AM
  • Thank you for your answer.
    i tryed what you said with the %windir%\system32\perfmon.msc  and i had no luck. i can not find anything that has been recently installed other than the drivers for the new motherboard and CPU.
    i will take another look with the above program and go back a bit farther maybe.
    Wednesday, December 31, 2008 8:11 PM
  • i went back and found some "possible" uninstalls (i dont think they are the problem) but i tryed to uninstall them anyways and i am completly locked out of my computer. i cannot login nor can i boot into safe mode to uninstall the programs.
    Wednesday, December 31, 2008 8:21 PM