locked
Windows 7 complaining its not genuine: 3rd time in 2 months RRS feed

  • Question

  • Microsoft...

    WTF are you playing at with regards to the WGA in W7, My Copy IS BLOODY GENUINE...!!!!¬!!!!"!!!!!!"!

    This is the 3rd damn time W7 has complained its not genuine for no apparent reason, I have not made ant chaged to the OS or installed any programs, I'VE JUST DONE A REBOOT and now yet again W7 is BLOODY complaining its not genuine.

    Ran the WGA diag tool and it CLEARLY shows my DAMN windows key...!!! yet it says the key is missing...

    Diagnostic Report (1.9.0019.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Invalid License
    Validation Code: 50
    
    Cached Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: (hidden for privacy)
    Windows Product Key Hash: Wxaa7uzRogLowS2whtzgX8/QN5Y= Windows Product ID: 00426-065-0157195-86005 Windows Product ID Type: 5 Windows License Type: Retail Windows OS version: 6.1.7600.2.00010100.0.0.001 ID: {208E49AF-1B17-49E4-8092-02B13C0EC5AA}(1) Is Admin: Yes TestCab: 0x0 WGA Version: N/A, hr = 0x80070002 Signed By: N/A, hr = 0x80070002 Product Name: Windows 7 Ultimate Architecture: 0x00000000 Build lab: 7600.win7_rtm.090713-1255 TTS Error: T:20100208165431606- Validation Diagnostic: Resolution Status: N/A WgaER Data--> ThreatID(s): N/A, hr = 0x80070002 Version: N/A, hr = 0x80070002 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 OGAExec.exe Signed By: N/A, hr = 0x80070002 OGAAddin.dll Signed By: N/A, hr = 0x80070002 OGA Data--> Office Status: 100 Genuine Microsoft Office Standard Edition 2003 - 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--> File Mismatch: C:\Windows\system32\wat\watadminsvc.exe[hr = 0x80070002] File Mismatch: C:\Windows\system32\wat\npwatweb.dll[hr = 0x80070002] File Mismatch: C:\Windows\system32\wat\watux.exe[hr = 0x80070002] File Mismatch: C:\Windows\system32\wat\watweb.dll[hr = 0x80070002] Other data--> Office Details: <GenuineResults><MachineData><UGUID>{208E49AF-1B17-49E4-8092-02B13C0EC5AA}</UGUID><Version>1.9.0019.0</Version><OS>6.1.7600.2.00010100.0.0.001</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-P3MFJ</PKey><PID>00426-065-0157195-86005</PID><PIDType>5</PIDType><SID>S-1-5-21-3839179961-1406575452-3311429655</SID><SYSTEM><Manufacturer>Gigabyte Technology Co., Ltd.</Manufacturer><Model>X38-DS5</Model></SYSTEM><BIOS><Manufacturer>Award Software International, Inc.</Manufacturer><Version>F7F</Version><SMBIOSVersion major="2" minor="4"/><Date>20090424000000.000000+000</Date></BIOS><HWID>FABA3607018400F8</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/><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{90120409-6000-11D3-8CFE-0150048383C9}"><LegitResult>100</LegitResult><Name>Microsoft Office Standard Edition 2003</Name><Ver>11</Ver><Val>3A9A22B6280E500</Val><Hash>GN3Qjj7oYSAJJbc29+GJR/YGHmU=</Hash><Pid>70141-640-9616085-57347</Pid><PidType>14</PidType></Product></Products><Applications><App Id="16" Version="11" Result="100"/><App Id="18" Version="11" Result="100"/><App Id="1A" Version="11" Result="100"/><App Id="1B" Version="11" Result="100"/></Applications></Office></Software></GenuineResults> Spsys.log Content: U1BMRwEAAAAAAQAABAAAAM4jAAAAAAAAYWECAEj9iKM1cMLXh6LKAWbXGpOihAOpMHzDmWxsjuo5QM4xz90aoQbd22RkE7alyHshZhb2J68LmFqaVTE2DTOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAx4dZsxs/sxaQSZh6DCEuBH9b5a8pUkm1J2e0PD41qeEPjCOHFjQVXUuzbbI3zTOcIzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMZtcak6KEA6kwfMOZbGyO6j8KfBHVbCmN9CR2pFnuGoCbGFPYaDcI5tGIT5j2moVRM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDHh1mzGz+zFpBJmHoMIS4EcBgDg7JWySdf9ZQnArpi/AE1cT97XzzhzkZDvU8QKpizOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw= Licensing Data--> Software licensing service version: 6.1.7600.16385 Error: product key not found. Windows Activation Technologies--> HrOffline: N/A HrOnline: N/A HealthStatus: N/A Event Time Stamp: N/A WAT Activex: Not Registered - 0x80040154 WAT Admin Service: Not Registered - 0x80040154 HWID Data--> HWID Hash Current: MgAAAAEAAAABAAEAAQADAAAAAwABAAEA6GF0P6ryhm8Kn2peYj0KEfdqpqhyir5BTFg= 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 GBT GBTUACPI FACP GBT GBTUACPI HPET GBT GBTUACPI MCFG GBT GBTUACPI
    And it looks like the only way I can make my copy genuine is to BLOODY install the DAMN OS... As an IT professional I find this new level of WGA intrusive and disruptive, its complete BOLLOX.
    Monday, February 8, 2010 5:26 PM

Answers

  • Hello b1k3rdude,

    I will explain what I see from your Diagnostic Report and recommend steps you may try.  

    1) I am unable to analyze your Product key.  The Diagnostic Report is designed to not show the first 10 out of the 25 digits of the product key.  This allows support to look up information on the product key (That may help in troubleshooting an issue) without exposing the full key to the public.

    2) TTS error T:20100208165431606-

    TTS stand for Tamper Time Stamp.   The "T" stands for Trusted Store and the number is the Time Stamp of when the tamper was last detected. In this case:  Year: 2010, Month: 02, Day:08, Time (in 24hour format):1654, Milisec:31606.

    Trusted Store Tampers are fairly rare.  They are caused when a Signed file is modified in some way (replaced, become corrupt and so on) The File's Cert (in the Trusted Store) becomes invalid which triggers the Tamper event which results in a Non-Genuine event. Generally, it has been found that Drivers are usually the files that cause the problem, but it can, in fact, be caused by any Signed file.  (My apologies. I checked with my Devs and confirmed that I was incorrect about semi-incompatible Drivers also being a possible cause. It just seems that the fix for most people was to update Drivers which I, incorrectly, assumed were incompatible)

    Unfortunately, none of my tools can tell me which file/cert is causing the problem. As I mentioned before, updating hardware drivers have been known to fix the issue, but failing that, you can also try the below steps

    a) System Restore to a point before the issue occurred:

    1) Boot into Windows
    2) Click the Start button
    3) In the Start Search field, type: System Restore and hit Enter
    4) Select "Choose Different Restore Point", Put a check in the box that says "Show restore points older than 5 days", select the restore point that corresponds to a date Before you first noticed the issue.
    5) Click the Next button.
    6) Reboot
    7) Confirm the issue is resolved

    b) Attempt to repair using sfc /scannow

    1) Boot into Windows
    2) Click the Start button
    3) In the Start Search field, type: CMD
    4) Right-click the CMD.exe file and select 'Run as Administrator'
    5) In the CMD window, type: sfc /scannow
    8) Reboot twice and see if that resolves the issue.


    3) I also see that the Licensing Data section of the Diagnostic Report is showing an error that the Product key is not found. This suggests that Windows Licensing Store may be corrupt of unreadable for some reason. In this case, I recommend the below steps that will force Windows to recreate (and repopulate) the Store.

    1) Click Start button.
    2) Type: CMD.exe into the 'Search programs and files' field
    3) Right-Click on CMD.exe and select 'Run as Administrator'
    4) Type: net stop sppsvc   (It may ask you if you are sure, select yes)
    Note: the Software Protection servive may not be running, this is ok.
    5) Type: cd %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform
    6) Type: rename tokens.dat tokens.bar
    7) Type: cd %windir%\system32
    8) Type: net start sppsvc
    9) Type: slui.exe
    10) After a couple of seconds Windows Activation dialog will appear. You may be asked to re-enter the Product Key and/or re-activate or Activation may occur automatically.

    If none of the above steps appeared to resolve the Non-genuine issue, please re-run and post the MGA Diagnostic Report again so I may see if anything has changed. 



      The customer may be treated as Always Right, but in support they are often not Right. Regardless this does not give the customer the right to swear. And while most of the words you used may not be swear words in the UK, one of the words is a reference to part of the male reproductive organ, which I can only see as offensive to most people.  In addition, in the edits of the post that you eventually deleted (but which I can still see) the F word is used on multiple occasion and I know that is not an acceptable word in the UK or anywhere else. This is a public area, I have explained what I feel is inappropriate behavior in this area and if it occurs again, all troubleshooting of your issue, on this forum, will cease. 

      As to Venting, that's fine and I am very sorry that this issue is so frustrating.  However, support's job is to attempt to fix the issue. Support generally does not have any control over how the software was made and they are seldom asked their opinion on this or that design decision.  So it just seems counterproductive to yell at support when we then have to wade thru the resulting Wall of Text looking for information on which to troubleshoot your issue. The Comments and Feedback forum seems a better place for that type of communication.

    Thank you,
    Darin MS

    • Proposed as answer by Darin Smith MS Friday, February 12, 2010 8:08 PM
    • Marked as answer by Darin Smith MS Monday, February 15, 2010 6:44 PM
    Friday, February 12, 2010 8:02 PM

All replies


  • File Mismatch: C:\Windows\system32\wat\watadminsvc.exe[hr = 0x80070002]
    File Mismatch: C:\Windows\system32\wat\npwatweb.dll[hr = 0x80070002]
    File Mismatch: C:\Windows\system32\wat\watux.exe[hr = 0x80070002]
    File Mismatch: C:\Windows\system32\wat\watweb.dll[hr = 0x80070002]


    And dispite what the bollox above says, I didnt not delete the damn files and neither did I upgrade from a previous version of windows...!!!
    Monday, February 8, 2010 6:04 PM
  • Have you intentionally muddled with any of Windows 7's Services, such as disabling the SPP Notification or Software Protection services?
    Carey Frisch
    Monday, February 8, 2010 9:00 PM
    Moderator
  • As an IT professional I am sure you understand that yelling and swearing at support (the people you are asking to fix your issue) is probably not the best idea.

    Please answers Carey's question without any further expletives and we will try to resolve your issue as quickly as possible.


    One thing I do see in your Diagnostic Report is a Trusted Store tamper.  This is usually associated with a semi-incompatible Driver.  You may want to confirm that all your drivers are up to date and fully compatible with Windows 7.


    Note: Any File Mismatchs with 'wat' in thier names are a result of additions to the Diagnostic Tool that is not yet fully enabled and should be ignored. 

    Thank you,
    Darin MS
    Tuesday, February 9, 2010 9:00 PM
  • Have you intentionally muddled with any of Windows 7's Services, such as disabling the SPP Notification or Software Protection services?

    No... but 'Windows' has set it to manual. Which according the list here is as it should be - http://www.blackviper.com/Windows_7/servicecfg.htm

     On a different note i see that one of the dependencies is the DCOM service, I googled and found the following threads -

    • http://www.overclock.net/windows/597240-windows-7-dcom-services-being-terminated.html
    • http://www.overclock.net/windows/564141-windows-must-restart-dcom-process-terminated.html

    But in my case I don't think that applies as I didn't get that error, all I got was the "windows is not genuine" message and after the second reboot windows prompted me to enter the CD key....again..... for the 3rd time.....
    Wednesday, February 10, 2010 12:50 PM
  • As an IT professional I am sure you understand that yelling and swearing at support (the people you are asking to fix your issue) is probably not the best idea.

    Please answers Carey's question without any further expletives and we will try to resolve your issue as quickly as possible.

    One thing I do see in your Diagnostic Report is a Trusted Store tamper.  This is usually associated with a semi-incompatible Driver.  You may want to confirm that all your drivers are up to date and fully compatible with Windows 7.

    • And as a fellow IT professional I'm sure your aware the customer has to be treated as 'Always Right' which means that they are ALWAYS allowed to vent.... In the UK we say how we see it and bollox, bloody and damn are Not swear words... :-/
    • Done.
    • All the drivers I am using are the latest WHQL certified versions. But on that subject thats a Bloody Pis poor show if a driver that isnt the latest up-to-date-whql etc can cause windows to de-authorise itself... What the Hel are MS playing at, the two should not be inter-dependant at ALL and its utterly unacceptable. Or is this another case of DRM causing yet more unnecessary bollox.
    • As you seem to be the MS person answering the issues in this forum, what are the top five causes of Windows 7 de-authorising itself... As Ive not seen this with vista and Xp is not applicable (as its not infected with DRM)
    Wednesday, February 10, 2010 1:03 PM
  • bump
    Friday, February 12, 2010 12:15 PM
  • Hello b1k3rdude,

    I will explain what I see from your Diagnostic Report and recommend steps you may try.  

    1) I am unable to analyze your Product key.  The Diagnostic Report is designed to not show the first 10 out of the 25 digits of the product key.  This allows support to look up information on the product key (That may help in troubleshooting an issue) without exposing the full key to the public.

    2) TTS error T:20100208165431606-

    TTS stand for Tamper Time Stamp.   The "T" stands for Trusted Store and the number is the Time Stamp of when the tamper was last detected. In this case:  Year: 2010, Month: 02, Day:08, Time (in 24hour format):1654, Milisec:31606.

    Trusted Store Tampers are fairly rare.  They are caused when a Signed file is modified in some way (replaced, become corrupt and so on) The File's Cert (in the Trusted Store) becomes invalid which triggers the Tamper event which results in a Non-Genuine event. Generally, it has been found that Drivers are usually the files that cause the problem, but it can, in fact, be caused by any Signed file.  (My apologies. I checked with my Devs and confirmed that I was incorrect about semi-incompatible Drivers also being a possible cause. It just seems that the fix for most people was to update Drivers which I, incorrectly, assumed were incompatible)

    Unfortunately, none of my tools can tell me which file/cert is causing the problem. As I mentioned before, updating hardware drivers have been known to fix the issue, but failing that, you can also try the below steps

    a) System Restore to a point before the issue occurred:

    1) Boot into Windows
    2) Click the Start button
    3) In the Start Search field, type: System Restore and hit Enter
    4) Select "Choose Different Restore Point", Put a check in the box that says "Show restore points older than 5 days", select the restore point that corresponds to a date Before you first noticed the issue.
    5) Click the Next button.
    6) Reboot
    7) Confirm the issue is resolved

    b) Attempt to repair using sfc /scannow

    1) Boot into Windows
    2) Click the Start button
    3) In the Start Search field, type: CMD
    4) Right-click the CMD.exe file and select 'Run as Administrator'
    5) In the CMD window, type: sfc /scannow
    8) Reboot twice and see if that resolves the issue.


    3) I also see that the Licensing Data section of the Diagnostic Report is showing an error that the Product key is not found. This suggests that Windows Licensing Store may be corrupt of unreadable for some reason. In this case, I recommend the below steps that will force Windows to recreate (and repopulate) the Store.

    1) Click Start button.
    2) Type: CMD.exe into the 'Search programs and files' field
    3) Right-Click on CMD.exe and select 'Run as Administrator'
    4) Type: net stop sppsvc   (It may ask you if you are sure, select yes)
    Note: the Software Protection servive may not be running, this is ok.
    5) Type: cd %windir%\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform
    6) Type: rename tokens.dat tokens.bar
    7) Type: cd %windir%\system32
    8) Type: net start sppsvc
    9) Type: slui.exe
    10) After a couple of seconds Windows Activation dialog will appear. You may be asked to re-enter the Product Key and/or re-activate or Activation may occur automatically.

    If none of the above steps appeared to resolve the Non-genuine issue, please re-run and post the MGA Diagnostic Report again so I may see if anything has changed. 



      The customer may be treated as Always Right, but in support they are often not Right. Regardless this does not give the customer the right to swear. And while most of the words you used may not be swear words in the UK, one of the words is a reference to part of the male reproductive organ, which I can only see as offensive to most people.  In addition, in the edits of the post that you eventually deleted (but which I can still see) the F word is used on multiple occasion and I know that is not an acceptable word in the UK or anywhere else. This is a public area, I have explained what I feel is inappropriate behavior in this area and if it occurs again, all troubleshooting of your issue, on this forum, will cease. 

      As to Venting, that's fine and I am very sorry that this issue is so frustrating.  However, support's job is to attempt to fix the issue. Support generally does not have any control over how the software was made and they are seldom asked their opinion on this or that design decision.  So it just seems counterproductive to yell at support when we then have to wade thru the resulting Wall of Text looking for information on which to troubleshoot your issue. The Comments and Feedback forum seems a better place for that type of communication.

    Thank you,
    Darin MS

    • Proposed as answer by Darin Smith MS Friday, February 12, 2010 8:08 PM
    • Marked as answer by Darin Smith MS Monday, February 15, 2010 6:44 PM
    Friday, February 12, 2010 8:02 PM
  • As mentioned already the issue fixed itself after few reboots where I was forced to re-enter the CD key.

    Regarding my language and with no offence to you as you have been quite helpful, but I have to say Americans are far to bloody over sensitive the point where its quite frankly immature and pathetic. They get their knickers in a twist about a slight bit of nudity on TV, or words 'THEY' consider offensive(that aren't anywhere else in the world). Yet don't bat an eyelid over graphic and gratuitous violence.

    So on that note, is there a MS UK support forum ?
    Monday, February 15, 2010 6:55 PM
  • As an IT professional I am sure you understand that yelling and swearing at support (the people you are asking to fix your issue) is probably not the best idea.

    Please answers Carey's question without any further expletives and we will try to resolve your issue as quickly as possible.

    One thing I do see in your Diagnostic Report is a Trusted Store tamper.  This is usually associated with a semi-incompatible Driver.  You may want to confirm that all your drivers are up to date and fully compatible with Windows 7.

    • And as a fellow IT professional I'm sure your aware the customer has to be treated as 'Always Right' which means that they are ALWAYS allowed to vent.... In the UK we say how we see it and bollox, bloody and damn are Not swear words... :-/
    • Done.
    • All the drivers I am using are the latest WHQL certified versions. But on that subject thats a Bloody Pis poor show if a driver that isnt the latest up-to-date-whql etc can cause windows to de-authorise itself... What the Hel are MS playing at, the two should not be inter-dependant at ALL and its utterly unacceptable. Or is this another case of DRM causing yet more unnecessary bollox.
    • As you seem to be the MS person answering the issues in this forum, what are the top five causes of Windows 7 de-authorising itself... As Ive not seen this with vista and Xp is not applicable (as its not infected with DRM)

    As also a fellow IT professional, I can share the frustration that makes people want to swear. If you had to stand in front of your customers face to face looking like a prize id**t trying to deal with some of the more "unnecessary" Microsoft issues, you would get very frustrated too.  I'm know for my patience, but some of the flaws in the Microsoft products really push my limits and those of my colleagues of not wanting to swear at (nay, sometimes even punch) someone at "Microsoft".

    I agree no one should be rude to you, you are trying to help us. However what we would really like you to also do, for the sake of our own wavering sanity, please;- contact the departments that wrote this sub standard code tell them that there are IT professionals out in the field that wish very negative and horrible things on them (pass on the rude words verbatim) because something they wrote is making the end customer wonder if the field professional is capable of plugging the computer in and that department is the reason.  What do you think the customer thinks of us when we have to research something as simple as an activation? Isn't that supposed to be a user thing? I makes them wonder why they called us in when we have to ask you about apparently simple things.

    Don't take it personally, but pass on the message, because there is now way for us to escalate this problem to the right people, which makes us more frustrated. If we could talk to the person that wrote some of the worst Microsoft hash ups, we would never dream of shouting or venting at you.  But we can't. So please pass it on, you don't deserve it. BUT SOMEONE THERE CERTAINLY DOES!!!!

    Mark

    Thursday, August 12, 2010 9:15 PM