locked
Genuine Vista flagged as "Not Genuine" - now locked out of PC!! Now what?? RRS feed

  • Question

  • I have a genuine copy of Vista HP and have used it for over a year happily.

    Few days ago was synching my Nokia N95 8GB with PC when suddenly PC switched off.Upon reboot error was given that PC not shut down correctly. I continued to load windows normally but when logged in was presented with Software Protection Platform error stating that a system file had been altered. I followed link online to Vista Genuine Advantage site to re vlaidate Vista.

    Bizzarely it failed!!

    I followed the instructions given, booted into Safe Mode and uninstalled the Nokia PC Suite that I'd been using for months.

    Same issue with failing to pass Genuine advantage.

    NOW upon login I get black screen with option box to open my web browser to Validate windows.

    It fails every time and then logs me off.

    How on earth am I supposed to fix this and get access to my PC and valuable files????

    It's a genuine copy with licence.

    I filed a report to MS after following trouble shooting wizard - NO REPLY!!!!!

    I'm disgusted with MS and their aggressive pursuit of pirates, but it's genuine customers who suffer.

    If this can't be solved I'm off to buy a MAC!!

    Any clues on solving this issue guys??

    Please!!
    Friday, March 14, 2008 3:53 PM

Answers

  • Hello Spikesclone,

     

    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 usually caused by a running program that is incompatible with Vista.

     

    Because there are No Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, your issue is a 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.

     

    In addition to why a Tamper occurs, it's also important to understand how Vista detects the Tamper 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 Tamper State and it could take some time for the Tamper to be detected. The important point to note is that the moment 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:
     
      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:xxxxxxxxxxxxxxxxx- This is the Tamper Time Stamp and it breaks down like this:

     

        (year)  (month) (day) (time in 24format) (millisecond)
    M:2008       03       14            1658                     23788-

     


    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 03/214 

    6) Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 03/14/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 Vista to a Tamper State. Because of this, please repeat steps 5) thru 7) for the dates 03/13/2008, 03/12/2008 and 03/12/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 03/14/2008 , 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 as well since it may fall outside of the 3 day time frame described above.

     
    Thank you,
    Darin Smith
    WGA Forum Manager
    Friday, March 14, 2008 7:43 PM

All replies

  • Please follow this simple troubleshooting procedure:

     

    1. Download and run the MGA Diagnostic Tool: http://go.microsoft.com/fwlink/?linkid=52012

     

    2. After running the MGA Diagnostic Tool, click on the "Windows" tab and then click on "Copy".

     

    3. Next, visit the following website and create a post in the "WGA Validation Problems" forum and paste the results of the WGA Diagnostic Data in a detailed post. http://forums.microsoft.com/Genuine/default.aspx?SiteID=25

     

    4. A WGA troubleshooting specialist will analyze the data and recommend an appropriate solution.

     

     

    Friday, March 14, 2008 3:55 PM
    Moderator
  • OK, here's my log:

     

     

    Diagnostic Report (1.7.0069.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Online Validation Code: 0x80070426
    Cached Validation Code: N/A, hr = 0x80070426
    Windows Product Key: *****-*****-3K2H7-QKTPB-YWMD7
    Windows Product Key Hash: l06IGCcP6SOaqGVJmgju7Z1uOIE=
    Windows Product ID: 89578-OEM-7304142-48212
    Windows Product ID Type: 3
    Windows License Type: OEM System Builder
    Windows OS version: 6.0.6000.2.00010300.0.0.003
    CSVLK Server: N/A
    CSVLK PID: N/A
    ID: {5835F543-FB41-464A-A2D7-6E3A17D1693F}(3)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: Registered, 1.7.59.1
    Signed By: Microsoft
    Product Name: Windows Vista (TM) Home Premium
    Architecture: 0x00000000
    Build lab: 6000.vista_gdr.071023-1545
    TTS Error: M:20080314165823788-
    Validation Diagnostic:
    Resolution Status: N/A

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

    Notifications Data-->
    Cached Result: N/A
    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 Data-->
    Office Status: 100 Genuine
    OGA Version: Registered, 1.6.28.0
    Signed By: Microsoft
    Office Diagnostics: B4D0AA8B-531-645_025D1FF3-282-80041010_025D1FF3-170-80041010_025D1FF3-171-1_025D1FF3-434-80040154_025D1FF3-178-80040154_025D1FF3-179-2_025D1FF3-185-80070002_025D1FF3-199-3

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Win32)
    Default Browser: C:\PROGRA~1\MOZILL~1\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>{5835F543-FB41-464A-A2D7-6E3A17D1693F}</UGUID><Version>1.7.0069.0</Version><OS>6.0.6000.2.00010300.0.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-YWMD7</PKey><PID>89578-OEM-7304142-48212</PID><PIDType>3</PIDType><SID>S-1-5-21-3582119240-212430896-814333237</SID><SYSTEM><Manufacturer>Sony Corporation</Manufacturer><Model>VGN-FS315S</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies LTD</Manufacturer><Version>R0084J1</Version><SMBIOSVersion major="2" minor="34"/><Date>20060602000000.000000+000</Date></BIOS><HWID>B6323507018400F2</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><BRT/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-0030-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Enterprise 2007</Name><Ver>12</Ver><Val>30E847CB45ABECE</Val><Hash>slfxCCc9IwRJsg8crrS3nwFZggs=</Hash><Pid>81599-871-1228233-65631</Pid><PidType>1</PidType></Product></Products></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAACU1AAAAAAAAWmICADAgAACvyqoekYTIAVMWKYGB4wMcsbz+lAen7WdhQxfnw5kjo2Q1mtt3Y+DUV4c5xCP7JnMfDOWubCbFlu97BuxrKcj+9gzTrUJt+r1VBuBN7aoAILXVoMA6yoQInKfOZv/AmB9uvmxWADGc/AFrdnzWO+jF8eq69LRpcSiTN/jEi/pgsTdkQKOEZadnYeIFmHEs83923aEKqaV7o3ahIBpTbeopSs8i4ZePvEQhLRUSI+U3SBDxSocUJDOz74TgJfOd1LfEdWT9Qb1zuiT+h08wRI5b3Ii0HwoRaNfY7o+X32CpOdJhHiPQVqyFM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxTFimBgeMDHLG8/pQHp+1nsuw1ni+H7Es/JQYMt6Z4vJ6GNK2VYRKgtuyzH7v1BI/vewbsaynI/vYM061Cbfq9swNBvNzdMKGgQdxh8Fkr9Jynzmb/wJgfbr5sVgAxnPwBa3Z81jvoxfHquvS0aXEokzf4xIv6YLE3ZECjhGWnZ2HiBZhxLPN/dt2hCqmle6N2oSAaU23qKUrPIuGXj7xEIS0VEiPlN0gQ8UqHFCQzs++E4CXzndS3xHVk/UG9c7ok/odPMESOW9yItB8KEWjX2O6Pl99gqTnSYR4j0FashTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMUxYpgYHjAxyxvP6UB6ftZ9rpUSTqFilbRDfdc0uwVfhwZtVYqYzf5WPva+8bYgwi73sG7GspyP72DNOtQm36vaenFYdYYyofcfYeQ1FoNPacp85m/8CYH26+bFYAMZz8AWt2fNY76MXx6rr0tGlxKJM3+MSL+mCxN2RAo4Rlp2dh4gWYcSzzf3bdoQqppXujdqEgGlNt6ilKzyLhl4+8RCEtFRIj5TdIEPFKhxQkM7PvhOAl853Ut8R1ZP1BvXO6JP6HTzBEjlvciLQfChFo19juj5ffYKk50mEeI9BWrIUzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDFMWKYGB4wMcsbz+lAen7WcT182gKznMMT6aAo/yOnylKqVhCU+MShHC4DCoecVyJO97BuxrKcj+9gzTrUJt+r0vhktSTHPen2chvDnI54DenKfOZv/AmB9uvmxWADGc/AFrdnzWO+jF8eq69LRpcSiTN/jEi/pgsTdkQKOEZadnYeIFmHEs83923aEKqaV7o3ahIBpTbeopSs8i4ZePvEQhLRUSI+U3SBDxSocUJDOz74TgJfOd1LfEdWT9Qb1zuiT+h08wRI5b3Ii0HwoRaNfY7o+X32CpOdJhHiPQVqyFM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxTFimBgeMDHLG8/pQHp+1nouinr3ZqItAuM5NybFiXGzAMn8ezAE987NrLesZ18NzvewbsaynI/vYM061Cbfq93PsTk5pf/78gJTOEVkjLSZynzmb/wJgfbr5sVgAxnPwBa3Z81jvoxfHquvS0aXEokzf4xIv6YLE3ZECjhGWnZ2HiBZhxLPN/dt2hCqmle6N2oSAaU23qKUrPIuGXj7xEIS0VEiPlN0gQ8UqHFCQzs++E4CXzndS3xHVk/UG9c7ok/odPMESOW9yItB8KEWjX2O6Pl99gqTnSYR4j0FashTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMUxYpgYHjAxyxvP6UB6ftZ5Fphg5BWvitEoqjbG1zVQlMA1RqoWAr/tmD6UlrgpX273sG7GspyP72DNOtQm36vez6rHKJqLNYj7YYcibakhCcp85m/8CYH26+bFYAMZz8AWt2fNY76MXx6rr0tGlxKJM3+MSL+mCxN2RAo4Rlp2dh4gWYcSzzf3bdoQqppXujdqEgGlNt6ilKzyLhl4+8RCEtFRIj5TdIEPFKhxQkM7PvhOAl853Ut8R1ZP1BvXO6JP6HTzBEjlvciLQfChFo19juj5ffYKk50mEeI9BWrIUzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDFMWKYGB4wMcsbz+lAen7Wf1wtjBP5Whd6QC+2ctlSiQcyBAqokbhGJVqWSPqtUL5u97BuxrKcj+9gzTrUJt+r26UGwoPP6wz16Nhjj6UV2znKfOZv/AmB9uvmxWADGc/AFrdnzWO+jF8eq69LRpcSiTN/jEi/pgsTdkQKOEZadnYeIFmHEs83923aEKqaV7o3ahIBpTbeopSs8i4ZePvEQhLRUSI+U3SBDxSocUJDOz74TgJfOd1LfEdWT9Qb1zuiT+h08wRI5b3Ii0HwoRaNfY7o+X32CpOdJhHiPQVqyFM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAxTFimBgeMDHLG8/pQHp+1nsuw1ni+H7Es/JQYMt6Z4vHJglMORmwzdtPuhzPvXUkXvewbsaynI/vYM061Cbfq9BkDv7F6OhHgm1JMk8AJ8Upynzmb/wJgfbr5sVgAxnPwBa3Z81jvoxfHquvS0aXEokzf4xIv6YLE3ZECjhGWnZ2HiBZhxLPN/dt2hCqmle6N2oSAaU23qKUrPIuGXj7xEIS0VEiPlN0gQ8UqHFCQzs++E4CXzndS3xHVk/UG9c7ok/odPMESOW9yItB8KEWjX2O6Pl99gqTnSYR4j0FashTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMUxYpgYHjAxyxvP6UB6ftZ7LsNZ4vh+xLPyUGDLemeLzpSZQh/608rObJdw+dUu4173sG7GspyP72DNOtQm36vSesklnFbp3E6p8f1z0XCoycp85m/8CYH26+bFYAMZz8AWt2fNY76MXx6rr0tGlxKJM3+MSL+mCxN2RAo4Rlp2dh4gWYcSzzf3bdoQqppXujdqEgGlNt6ilKzyLhl4+8RCEtFRIj5TdIEPFKhxQkM7PvhOAl853Ut8R1ZP1BvXO6JP6HTzBEjlvciLQfChFo19juj5ffYKk50mEeI9BWrIUzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDA==

     

     

     

    Error code at end of failed advantage was [0x80070426]

    Any help would be great.

     

    Thanks

    Friday, March 14, 2008 5:05 PM
  • Hello Spikesclone,

     

    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 usually caused by a running program that is incompatible with Vista.

     

    Because there are No Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, your issue is a 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.

     

    In addition to why a Tamper occurs, it's also important to understand how Vista detects the Tamper 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 Tamper State and it could take some time for the Tamper to be detected. The important point to note is that the moment 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:
     
      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:xxxxxxxxxxxxxxxxx- This is the Tamper Time Stamp and it breaks down like this:

     

        (year)  (month) (day) (time in 24format) (millisecond)
    M:2008       03       14            1658                     23788-

     


    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 03/214 

    6) Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 03/14/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 Vista to a Tamper State. Because of this, please repeat steps 5) thru 7) for the dates 03/13/2008, 03/12/2008 and 03/12/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 03/14/2008 , 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 as well since it may fall outside of the 3 day time frame described above.

     
    Thank you,
    Darin Smith
    WGA Forum Manager
    Friday, March 14, 2008 7:43 PM
  • Hi Darin,

     

    I looked at the reliability chart and the last entries were from 13/03/08 not 14/03/08 so difficult to pinpoint problem program.

     

    I had installed Nokia PC Suite Ver 2.0 and had a Java 6 update 5 installation on 13th.

     

    I have uninstalled both these programs yet still end up with a black scren with a box pointing to open my browser to "solve" this problem, but I always fail the Validation procedure.

     

    The only other items for the past few weeks have ben Vista and Office 2007 updates via Windows update.

     

    Any other clues for help please?

     

     

    Spikesclone

    Friday, March 14, 2008 10:12 PM
  •  Spikesclone wrote:

    Hi Darin,

     

    I looked at the reliability chart and the last entries were from 13/03/08 not 14/03/08 so difficult to pinpoint problem program.

     

    I had installed Nokia PC Suite Ver 2.0 and had a Java 6 update 5 installation on 13th.

     

    I have uninstalled both these programs yet still end up with a black scren with a box pointing to open my browser to "solve" this problem, but I always fail the Validation procedure.

     

    Did you try rebooting after uninstalling the programs? If not please do so now.

     

     Spikesclone wrote:

    The only other items for the past few weeks have ben Vista and Office 2007 updates via Windows update.

     

    Any other clues for help please?

     

     

      The only other tips I can provide is that

     

    a) At the time the issue occures, the program that is causing the problem Has to be actively running.

     

    b) Since the program that is causing the issue has to be running for the problem to occure, and since Updates usually only run once, it is very unlikely that the updates are the cause.  

     

    You may also open a (no cost) WGA Support request at http://go.microsoft.com/fwlink/?linkid=52029 but since we have no way of knowing what program is causing the problem, I'm afraid they may only provide the same tricks and tips, to identifying the offending program, as I have.

     

    Thank you,

    Darin Smith

    WGA Forum Manager

    Friday, March 14, 2008 11:08 PM