locked
Another OEM Windows Vista Build 6002 Not Genuine Message RRS feed

  • Question

  • One of my customer's computers is a Dell Inspiron with Vista Basic SP 2..  As near as I can tell about 6 months ago the message "This copy of Windows is not Genuine" displayed on the desktop and the computer stopped validating the copy of Windows. In an attempt to fix this I have tried the following:

    • Changing the product key from the OEM number to the COA number. Error code 0xC004F050 appears each time this is attempted.
    • Try to run Windows Update but get Error Code 80070002 every time.
    • Have run MalwareBytes to check for malware but found something minor but removal still didn't allow validation.
    • Ran the diagnostic tool but get an error message when I click Copy in the utility and am unable to send the data.
    • Ran slui 4.exe but do not get the screen for a phone validation and thus am unable to validate via phone. I called Microsoft anyway but was told this is a Dell problem. Dell says it is a Microsoft problem. I know this is a Windows problem from past experience.
    • Ran System Restore but don't have a restore point that goes back to when the problem started last September. Restoring back to November didn't fix anything.

    This is a computer with a pre-installed version of Windows that ran fine for 2 years. The user is unaware of doing anything to instigate the problem which of course doesn't mean she didn't do something but there is no evidence of operator error.

    Any suggestions for getting the validation to work would be greatly appreciated.

    Thanks.

    Sam

     


    Sam
    Tuesday, January 18, 2011 3:58 AM

Answers

  • "srodar" wrote in message news:ada313b7-347b-4436-9bf7-d74f48e6a60d...

    Thanks again Noel,

    This computer actually belongs to a customer's college aged daughter. She confirmed that she has been living with this since last Summer but doesn't recall putting any programs on around that time but she doesn't really know either. I have already run MalwareBytes(also my favorite for detecting rogue programs) but found only one file this way that didn't change anything when it was removed.

    I've run the perfmon.msc utility but the last date that it shows in the System Stability Chart is 9/14/2009, the first date is 1/6/2009. There are no dates showing for 2010 which is when the problem started. Are the later dates what will show up if the process is left running for 3 days or is this information that is lost on this computer.

    I will try running the Windows Live Safety Scan to see if it detects something that MalwareBytes missed.

    I'm starting to think a file backup and clean install may be the best option.

    Anything else you can think of to try?

    Thanks again.

     


    Sam

    It sounds like something has turned of the system performance monitoring on that machine - which means that all records for the intervening time have gone.
    You *may* be lucky, and find something in the event viewer that  tells you what the problem is - but don't hold your breath!
    Apart from that, I'd see if you can get assistance from either the One-Care people, or the WGA support people - this is just not amenable to a forum-based solution.
     
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    • Marked as answer by Darin Smith MS Thursday, January 20, 2011 12:44 AM
    Wednesday, January 19, 2011 7:39 PM
    Moderator

All replies

  • "srodar" wrote in message news:543b0b64-89d7-4b54-8093-5bb642e1c222...

    One of my customer's computers is a Dell Inspiron with Vista Basic SP 2..  As near as I can tell about 6 months ago the message "This copy of Windows is not Genuine" displayed on the desktop and the computer stopped validating the copy of Windows. In an attempt to fix this I have tried the following:

    • Changing the product key from the OEM number to the COA number. Error code 0xC004F050 appears each time this is attempted.
    • Try to run Windows Update but get Error Code 80070002 every time.
    • Have run MalwareBytes to check for malware but found something minor but removal still didn't allow validation.
    • Ran the diagnostic tool but get an error message when I click Copy in the utility and am unable to send the data.
    • Ran slui 4.exe but do not get the screen for a phone validation and thus am unable to validate via phone. I called Microsoft anyway but was told this is a Dell problem. Dell says it is a Microsoft problem. I know this is a Windows problem from past experience.
    • Ran System Restore but don't have a restore point that goes back to when the problem started last September. Restoring back to November didn't fix anything.

    This is a computer with a pre-installed version of Windows that ran fine for 2 years. The user is unaware of doing anything to instigate the problem which of course doesn't mean she didn't do something but there is no evidence of operator error.

    Any suggestions for getting the validation to work would be greatly appreciated.

    Thanks.

    Sam

     


    Sam
    To properly analyse and solve problems with Activation and Validation, we need to see a full copy of the report produced by the MGADiag tool (download and save to desktop - http://go.microsoft.com/fwlink/?linkid=52012 )
    Once saved, run the tool.
    Click on the Continue button, which will produce the report.
    To copy the report to your response, click on the Copy button in the tool (ignore any error messages at this point), and then paste (using either r-click/Paste, or Ctrl+V ) into your response.
     
    IS the system 64-bit? - try the "Fix for ‘Software Licensing service Has Stopped’ on some Vista 64bit systems" in the Announcements section of this forum....
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Tuesday, January 18, 2011 9:07 AM
    Moderator
  • Thanks for the quick reply Noel.

    I already tried running the MGADiag tool but it won't allow me to copy the results. When I press the Copy button I get an error message. Tried it several times before posting the help request. It is a 32 bit system. It did say at the top of the MGADiag tool that it was not genuine with the number 50 on the second line. Got this result every time I ran the tool.

    I suspect I will end up reinstalling Windows on this machine but would prefer just getting it validated. It is definitely a legit OEM system, they have all the disks, original purchaser, etc.

    Any else I might try?

    Thanks again for the quick reply.

    Sam

     

     


    Sam
    Tuesday, January 18, 2011 4:04 PM
  • I can send a screen shot with the limited MGADiag tool info if you think  that would help. I would need an email address to send to with the attachment.

    Let me know if that would help.

    Thanks.


    Sam
    Tuesday, January 18, 2011 4:18 PM
  • "srodar" wrote in message news:121fee9f-58fc-40f9-91d2-a457418d3fbd...

    Thanks for the quick reply Noel.

    I already tried running the MGADiag tool but it won't allow me to copy the results. When I press the Copy button I get an error message. Tried it several times before posting the help request. It is a 32 bit system. It did say at the top of the MGADiag tool that it was not genuine with the number 50 on the second line. Got this result every time I ran the tool.

    I suspect I will end up reinstalling Windows on this machine but would prefer just getting it validated. It is definitely a legit OEM system, they have all the disks, original purchaser, etc.

    Any else I might try?

    Thanks again for the quick reply.

    Sam

     

     


    Sam

    As i said in my original post - IGNORE THE ERROR MESSAGE!! - it usually still pasted fine into Notepad, or anything else.
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Tuesday, January 18, 2011 10:48 PM
    Moderator
  • OK. The file info is below. Thanks again.

    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: *****-*****-4WD8X-M9WM7-CH4CG
    Windows Product Key Hash: EkdqJZ28Y9zyrh7DU/lHNjTXlQY=
    Windows Product ID: 89572-OEM-7332166-00096
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6002.2.00010300.2.0.002
    ID: {9ECFF358-4917-406A-A2A3-839797776806}(3)
    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.100608-0458
    TTS Error: T:20101104190006845-M:20100825131905565-
    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 Ultimate 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\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>{9ECFF358-4917-406A-A2A3-839797776806}</UGUID><Version>1.9.0027.0</Version><OS>6.0.6002.2.00010300.2.0.002</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-CH4CG</PKey><PID>89572-OEM-7332166-00096</PID><PIDType>2</PIDType><SID>S-1-5-21-2467809879-896430231-290729337</SID><SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>Inspiron 1525                   </Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>A11</Version><SMBIOSVersion major="2" minor="4"/><Date>20080310000000.000000+000</Date></BIOS><HWID>5E313507018400FA</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Mountain Standard Time(GMT-07:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>DELL  </OEMID><OEMTableID>M08    </OEMTableID></OEM><GANotification><File Name="OGAAddin.dll" Version="2.0.48.0"/></GANotification></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{91120000-002E-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Ultimate 2007</Name><Ver>12</Ver><Val>B9EF6F7382BEF7A</Val><Hash>fysjf+FiUh80j924EsJlbGkAjvs=</Hash><Pid>81608-957-8301072-65216</Pid><PidType>1</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"/><App Id="A1" Version="12" Result="100"/><App Id="BA" Version="12" Result="100"/></Applications></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAAOYnAAAAAAAAYWECAARQjYfp4IlgikTLAdArSr9MLECc5R83cvYPeMxc+SfTRw5ZPvs+1WDqaliR0MsD59F2BY4+cFKEbWusKBzlbKaVHBjD6SE/4CKjeOvdmgUPSvwoj+/07H9KEWDX27OKLWTN3/xFyngmD3afWQd5BWut+vD3FqOkH5qwY3q1CzF0U07jqdyoAL0aULPNP9KSju/t9vu9LXUgneZO8JuQnPomGb9VupAJaZo25SIJxGN5hPlYXq2AFDshBm86M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAzQK0q/TCxAnOUfN3L2D3jMXPkn00cOWT77PtVg6mpYkW7OMIQQ9yoirBqib2dFQklr8IjIbxP7CjljkDCZf9ifSy4H0Urzq8ZU/i1ZLXoU+tuzii1kzd/8Rcp4Jg92n1kHeQVrrfrw9xajpB+asGN6tQsxdFNO46ncqAC9GlCzzT/Sko7v7fb7vS11IJ3mTvDuaqurm+akCTPQuEveCIS5b+MkK0ENITMqwWcmSOM4ljOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM0CtKv0wsQJzlHzdy9g94zFz5J9NHDlk++z7VYOpqWJHE6kBLXjJEds7rijgVW618I0Rf1MqA3D5sWfEw7WeNf5STeztZlOS77+uX+KdiT0GqLLTr7bXpPf7dikez/iJn5Lw8YlXMBNsR5Ka2Ye/bcd0KFaGScCkglmkzU7p2zsU0pKrOYShnE8yq+B2IYhA5P2+NItX13MX//HgzMeMRFjvf0rhGe2cm64IrmZy/IPoUP4fjYs40W4R/+3spJGqwM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDNArSr9MLECc5R83cvYPeMxc+SfTRw5ZPvs+1WDqaliRsHUEx1NX8HqXKsnj9R2acLRzUqOpy06lA423DlROxyw0DqUG8Z7ybOA/1nLgKiKHqiy06+216T3+3YpHs/4iZ+S8PGJVzATbEeSmtmHv23HdChWhknApIJZpM1O6ds7FNKSqzmEoZxPMqvgdiGIQOT9vjSLV9dzF//x4MzHjERa9l+GtpmKobqSmneqLQb3MFD+H42LONFuEf/t7KSRqsDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAzQK0q/TCxAnOUfN3L2D3jMXPkn00cOWT77PtVg6mpYkWehye52Y4r6jHzaK1rnUNZfoMITbviHkEcYQrOzghfj3diWFzR9LujWpgsab93ycxg/Ne0vArtR1JRjR1RQS05dAaUbA+g8LcegJ8cxFNiJh5BRhkeY9gVsjnGneifskdJzGrd/PyI/Fr8JTdC0e9NAXmHYuVKivAnuRdmEUxDPTzdzF7QrWzqqYVPvi2JZSTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM0CtKv0wsQJzlHzdy9g94zFz5J9NHDlk++z7VYOpqWJHpTDyxKuNu9S/SMS3PDvNGDiUop78HNT99MpkVgBrQZ9M+KhxDdLS+zvyBk4j4Z20YPzXtLwK7UdSUY0dUUEtOXQGlGwPoPC3HoCfHMRTYiYeQUYZHmPYFbI5xp3on7JHScxq3fz8iPxa/CU3QtHvT3IXR4ef/AzMI0n3VmOOJb+9ZUK425cfX/4uCWO60l88zkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDNArSr9MLECc5R83cvYPeMxc+SfTRw5ZPvs+1WDqaliRSWPimlEMkuzlt9wbW7tYv4A7T2DaVg6cD2SLjiwoBx8m+oW0fkn/h702eB8V7qI59x6koTp2wjkQM4duA+DK8VPShUB7hxqRa/JRAlWy+kkBVBUSVbJg1lM7gkMq/m4IBCerXMgWX4ZLkwNC+kE1taWCmYC+GgruwOsRhldUEuQpk1bDB1iJelz+Eg1xoOGKM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAzQK0q/TCxAnOUfN3L2D3jMXPkn00cOWT77PtVg6mpYkbD8WobPjwpT1FAaLHQJllUrDD4HrDkZw1L+b/MWSE84DwE086ZLeFJf6MestgoXOxg/Ne0vArtR1JRjR1RQS05dAaUbA+g8LcegJ8cxFNiJh5BRhkeY9gVsjnGneifskdJzGrd/PyI/Fr8JTdC0e9O+ZRJ0w7jfPDmJzOMRtWkHDfUxUTAlCg1WWZ0veQsn5TOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM0CtKv0wsQJzlHzdy9g94zFz5J9NHDlk++z7VYOpqWJFmXeCgFmNmVK/x7eXVJG3yoKhNRZeGGCzWbbfWYXhCcJN/9NjEMhyZpBna0uarwJXbs4otZM3f/EXKeCYPdp9ZB3kFa6368PcWo6QfmrBjerULMXRTTuOp3KgAvRpQs80/0pKO7+32+70tdSCd5k7wVjgATrjNuipHgLbBl2kxC7xWNu8WOgNnmTiaHmb66REzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDNArSr9MLECc5R83cvYPeMxc+SfTRw5ZPvs+1WDqaliRYEzMS7/HC1Bf4/YPRNo2G/mA2FF124VnPMn56Nv0G9EBy7mRMJRjc7+wnBeyiG8yGD817S8Cu1HUlGNHVFBLTl0BpRsD6Dwtx6AnxzEU2ImHkFGGR5j2BWyOcad6J+yR0nMat38/Ij8WvwlN0LR706J/AdUP4L3wi2m/Gi/9qyM7UcmmKQdXOYNsqcu4BNLbM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAzQK0q/TCxAnOUfN3L2D3jMXPkn00cOWT77PtVg6mpYkT3BMFDpMboCNpAYOOdusBkrDD4HrDkZw1L+b/MWSE84CKPlmvTfk255wCIOYFmiCRg/Ne0vArtR1JRjR1RQS05dAaUbA+g8LcegJ8cxFNiJh5BRhkeY9gVsjnGneifskdJzGrd/PyI/Fr8JTdC0e9O6qvUwIncDAkOrmQUvFJUEK76hG2yNGl2cxd7o0co56jOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM0CtKv0wsQJzlHzdy9g94zFz5J9NHDlk++z7VYOpqWJEVSZTZXq8GG+avIT2kU4GAXx/xTfhoZCyhK0hdjZ3E3vPkvd+TOc2A1+be+e5Vh0r3HqShOnbCORAzh24D4MrxU9KFQHuHGpFr8lECVbL6SQFUFRJVsmDWUzuCQyr+bggEJ6tcyBZfhkuTA0L6QTW1iZoOyr/RwmXFSjMRzj63BSmTVsMHWIl6XP4SDXGg4YozkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDCPvOhE4aiPWkIrToHXwxdrnbrb58tX9wL8zsaFyomoPjCQfNLGuZlw03NjDzrQrejOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw2LChCixnhclyLKxemNGWeOp1ZsZoAV6KCCECnhlkzjl2ZM2Ad3hOiCSr/e/xMjf0zkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM0CtKv0wsQJzlHzdy9g94zG/nBdzQASkN9tVzhPrdIeeDaePSU7FkxP74rexSACk5HOVsppUcGMPpIT/gIqN463X/R6NDMFfyb2O43tr+yafbs4otZM3f/EXKeCYPdp9ZB3kFa6368PcWo6QfmrBjerULMXRTTuOp3KgAvRpQs80/0pKO7+32+70tdSCd5k7wm5Cc+iYZv1W6kAlpmjblIgnEY3mE+VherYAUOyEGbzozkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDCPvOhE4aiPWkIrToHXwxdoMbfu9n5h0Cz3Ypu0Is/2sSeriebrUjH+L+JTvRFr8pzOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw2LChCixnhclyLKxemNGWeAcEQZfpoPpjOd/Ih83lYc5++Ts+IiY+xYO+yc6YnnMgzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgM

    Licensing Data-->
    Software licensing service version: 6.0.6002.18005

    Windows Activation Technologies-->
    N/A

    HWID Data-->
    HWID Hash Current: PAAAAAEABgABAAIAAQABAAAAAwABAAEAJJSwr5yFtsBszMCyCiVsPEaDauQGpJT78vS6f8SArFZMASqF

    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   DELL    M08   
      FACP   DELL    M08   
      HPET   DELL    M08   
      BOOT   DELL    M08   
      MCFG   DELL    M08   
      SLIC   DELL    M08   
      OSFR   DELL    M08   
      SSDT   PmRef  CpuPm


    Sam
    Wednesday, January 19, 2011 4:24 AM
  • "srodar" wrote in message news:cbc04eda-c88a-4515-b075-3c939df1f547...

    OK. The file info is below. Thanks again.

    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: *****-*****-4WD8X-M9WM7-CH4CG
    Windows Product Key Hash: EkdqJZ28Y9zyrh7DU/lHNjTXlQY=
    Windows Product ID: 89572-OEM-7332166-00096
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 6.0.6002.2.00010300.2.0.002
    ID: {9ECFF358-4917-406A-A2A3-839797776806}(3)
    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.100608-0458
    TTS Error: T:20101104190006845-M:20100825131905565-

     


    Sam

    Hmmm - it looks like you've been living with this problem for 6 months, almost!
    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:20100825131905565- This is the Tamper Time Stamp and it breaks down like this:
     
        (year)  (month) (day) (time in 24format) (millisecond)
    M:2010    08         25              1319               05565 -
     
     
     
    Note: I also see a "T" type Tamper Time Stamp. The “T“ stands for Trusted Store tamper. Once you remove the program that is causing the In Memory Mod-Auth tamper, the Trusted Store tamper may be resolved as well. But a Trusted Store Tamper can sometimes indicate a Malware infection. To be on the safe side, we strongly suggest scanning your system with the Anti-Virus program of your choice as well as with the OneCare Safety Scanner for Vista (http://onecare.live.com/site/en-us/center/whatsnew.htm) - and my personal Best-of-Breed, Malwarebytes Anti-Malware (www.malwarebyste.org - the free version!) 
     

    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 25 Aug 2010 
     
    6)    Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 25 Aug 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 21-24 Aug  (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:
     
     
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Wednesday, January 19, 2011 9:02 AM
    Moderator
  • Thanks again Noel,

    This computer actually belongs to a customer's college aged daughter. She confirmed that she has been living with this since last Summer but doesn't recall putting any programs on around that time but she doesn't really know either. I have already run MalwareBytes(also my favorite for detecting rogue programs) but found only one file this way that didn't change anything when it was removed.

    I've run the perfmon.msc utility but the last date that it shows in the System Stability Chart is 9/14/2009, the first date is 1/6/2009. There are no dates showing for 2010 which is when the problem started. Are the later dates what will show up if the process is left running for 3 days or is this information that is lost on this computer.

    I will try running the Windows Live Safety Scan to see if it detects something that MalwareBytes missed.

    I'm starting to think a file backup and clean install may be the best option.

    Anything else you can think of to try?

    Thanks again.

     


    Sam
    Wednesday, January 19, 2011 6:37 PM
  • "srodar" wrote in message news:ada313b7-347b-4436-9bf7-d74f48e6a60d...

    Thanks again Noel,

    This computer actually belongs to a customer's college aged daughter. She confirmed that she has been living with this since last Summer but doesn't recall putting any programs on around that time but she doesn't really know either. I have already run MalwareBytes(also my favorite for detecting rogue programs) but found only one file this way that didn't change anything when it was removed.

    I've run the perfmon.msc utility but the last date that it shows in the System Stability Chart is 9/14/2009, the first date is 1/6/2009. There are no dates showing for 2010 which is when the problem started. Are the later dates what will show up if the process is left running for 3 days or is this information that is lost on this computer.

    I will try running the Windows Live Safety Scan to see if it detects something that MalwareBytes missed.

    I'm starting to think a file backup and clean install may be the best option.

    Anything else you can think of to try?

    Thanks again.

     


    Sam

    It sounds like something has turned of the system performance monitoring on that machine - which means that all records for the intervening time have gone.
    You *may* be lucky, and find something in the event viewer that  tells you what the problem is - but don't hold your breath!
    Apart from that, I'd see if you can get assistance from either the One-Care people, or the WGA support people - this is just not amenable to a forum-based solution.
     
     

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    • Marked as answer by Darin Smith MS Thursday, January 20, 2011 12:44 AM
    Wednesday, January 19, 2011 7:39 PM
    Moderator
  • It turns out after all this that the computer had bad memory in it. On a hunch I took out the 2 DIMMS and put in 1 that I had sitting around. The computer then ran OK. All the updates and blue screens stopped as well. It was apparent after opening the computer that it had been opened before when I suspect someone substituted the bad memory. As I mentioned earlier the computer is owned by a college student.

    Thanks again for all your help.


    Sam
    Sunday, February 27, 2011 5:42 PM
  • "srodar" wrote in message news:16ddb162-1cd7-4df4-a6c5-7213c525b988...

    It turns out after all this that the computer had bad memory in it. On a hunch I took out the 2 DIMMS and put in 1 that I had sitting around. The computer then ran OK. All the updates and blue screens stopped as well. It was apparent after opening the computer that it had been opened before when I suspect someone substituted the bad memory. As I mentioned earlier the computer is owned by a college student.

    Thanks again for all your help.


    Sam

    It would be a good idea, if you still have the machine, to post another MGADiag report.
     
    Glad you seem to have isolated the cause of the problems, anyhow!
     
    Good Luck

    --


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth
    Sunday, February 27, 2011 6:04 PM
    Moderator